#758 xterm is always called for desktop files

1.1
closed-fixed
libfm (248)
4
2013-08-26
2013-07-30
Sworddragon
No

I'm using PCManFM 1.1.0 and making a double click on a desktop files can cause xterm to open even if another terminal emulator is defined. For example on my system libfm.conf contains the line "terminal=x-terminal-emulator %s". x-terminal-emulator is linking to this:

sworddragon@ubuntu:~$ ls -al /usr/bin/x-terminal-emulator
lrwxrwxrwx 1 root root 37 Dez 28 2012 /usr/bin/x-terminal-emulator -> /etc/alternatives/x-terminal-emulator
sworddragon@ubuntu:~$ ls -al /etc/alternatives/x-terminal-emulator
lrwxrwxrwx 1 root root 19 Jan 4 2013 /etc/alternatives/x-terminal-emulator -> /usr/bin/lxterminal

The content of the desktop file looks this:

[Desktop Entry]
Exec=/usr/bin/passwd
Terminal=true
Type=Application

Making a double click on this file will open xterm instead of lxterminal.

Discussion

1 2 > >> (Page 1 of 2)
  • Could you tell me what is set in your settings? You know, your own settings override system ones. Open Preferences dialog and look what is shown there, please. Thank you.

     
    • priority: 5 --> 4
    • milestone: --> 2334032
    • labels: --> libfm
     
  • Sworddragon
    Sworddragon
    2013-07-30

    ~/.config/libfm/libfm.conf

     
    Attachments
  • Sworddragon
    Sworddragon
    2013-07-30

    ~/.config/pcmanfm/LXDE/pcmanfm.conf

     
    Attachments
  • Sworddragon
    Sworddragon
    2013-07-30

    In the attachments are both configuration files for my user.

     
    • milestone: 2334032 --> 1.1
     
  • It appear 1.1.0 has broken parsing of terminal statement in config file. Try to do a workaround on this removing %s from your line in config. That should help. Thank you very much.

     
  • I hope version 1.1.2 fixed your issue. Thanks.

     
    • assigned_to: nobody --> lstranger
    • status: open --> closed-fixed
     
  • Sworddragon
    Sworddragon
    2013-08-14

    I'm still able to reproduce this problem on PCManFM 1.1.2. Also the workaround removing %s doesn't help too. It seems something else is still making troubles there.

     
  • Sworddragon
    Sworddragon
    2013-08-14

    • status: closed-fixed --> open-fixed
     
  • Sworddragon
    Sworddragon
    2013-08-14

    • status: open-fixed --> open
     
  • Have you updated libfm to 1.1.2?

     
  • Sworddragon
    Sworddragon
    2013-08-14

    PCManFM and libfm are version 1.1.2 (pcmanfm 1.1.2-0ubuntu1 and libfm3 1.1.2-0ubuntu1 from Ubuntu 13.10 dev).

     
  • I'm afraid it's the same problem that is with # 3598808 and your configuration file is just neither loaded nor saved. You can test it though just removing directories ~/.config/pcmanfm and ~/.config/libfm - if they reappear after you close pcmanfm then those settings should work and your bugs should never happen, otherwise something is wrong.

     
  • In latter case (config directories are not created and config not saved) I would like to see your environment variables as they are set when you start pcmanfm - the most probably something is wrong with your environment.

     
  • Sworddragon
    Sworddragon
    2013-08-14

    ~/.config/libfm/libfm.conf and ~/.config/pcmanfm/LXDE/pcmanfm.conf get definitely read as both contain some user defined changes which are applied successfully. Changing the terminal emulator will also immediately write the change to ~/.config/libfm/libfm.conf even without logout. Interestingly the same happens with ~/.config/pcmanfm/LXDE/pcmanfm.conf if I'm changing any setting in the interface (is this a new feature to write immediately instead of waiting until PCManFM closes?).

     
  • That immediate change always been there, it did not always work though and that was fixed in 1.0 or 1.0.1 version yet.

    Another possible problem is may be you have another x-terminal-emulator around and you can check it with command 'which x-terminal-emulator'. Try to change your terminal setting to something another, even absurd such as 1234567890 - the error window when you try to open something in terminal will tell you your setting was applied.

     
  • Sworddragon
    Sworddragon
    2013-08-14

    sworddragon@ubuntu:~$ which x-terminal-emulator
    /usr/bin/x-terminal-emulator
    sworddragon@ubuntu:~$ ls -l /usr/bin/x-terminal-emulator
    lrwxrwxrwx 1 root root 37 Dez 28 2012 /usr/bin/x-terminal-emulator -> /etc/alternatives/x-terminal-emulator
    sworddragon@ubuntu:~$ ls -l /etc/alternatives/x-terminal-emulator
    lrwxrwxrwx 1 root root 19 Jan 4 2013 /etc/alternatives/x-terminal-emulator -> /usr/bin/lxterminal

    Open the terminal with F4 will successfully open lxterminal. But making a double click on the desktop file results in the error 'Failed to execute child process "xterm" (No such file or directory)'. Changing the terminal setting to 1234567890 and pressing F4 will result in the error 'Failed to execute child process "1234567890" (No such file or directory)' while making another double click on the desktop file will result again in the error 'Failed to execute child process "xterm" (No such file or directory)'.

     
  • Well. Another question. What 'Properties' window says about type of your file? Is it 'desktop entry file'?

     
  • Sworddragon
    Sworddragon
    2013-08-14

    It says "desktop configuration file". In the attachments is a screenshot which provides some information.

     
  • Sworddragon
    Sworddragon
    2013-08-14

    Screenshot with some informations

     
  • Sworddragon
    Sworddragon
    2013-08-14

    I have seen now that the terminal is showing me an error (I'm starting PCManFM manually for such tests to set the language to C): (pcmanfm:4068): GLib-GIO-WARNING **: couldn't find a terminal, falling back to xterm

     
  • That pretty much seem as if the desktop configuration files aren't opened by pcmanfm itself but GIO tries to open them. I have no idea how this can happen in case it was already detected right. I'd fix it if I could reproduce it but I cannot, no matter how I rename the file or which permissions I set. And I use pcmanfm-1.1.1 on my desktop.

     
  • Sworddragon
    Sworddragon
    2013-08-14

    The permissions of the file was 0600 if this helps.

     
1 2 > >> (Page 1 of 2)