I use pcmanfm to manage the desktop, starting it with X.
With current git, after startup, if I click a folder on the desktop then a pcmanfm window opens straight away.
But if I instead try to start pcmanfm from the lxpanelx "application launch bar", or from the run dialog, or by clicking on /usr/share/applications/pcmanfm.desktop, then it doesn't open the first time - I need to try a second time before it opens.
Anonymous
That is very strange, I never had such issue. I would ask you to try starting pcmanfm from command line, just enter "pcmanfm" - will it have the same behavior? Thank you very much.
Yes, it does.
Another question. Is pcmanfm as desktop manager already started at that time? I would like to get your help then. Could you rebuild it with debug enabled (as described in http://wiki.lxde.org/en/LXDE:PCManFM_build_and_setup_guide\) then relaunch it in debug mode from separate console (killall pcmanfm && G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all pcmanfm --desktop), then try to launch it in another console then report all that is shown in console where pcmanfm --desktop is running (there will be plenty of messages there), I hope you can catch your bug it that setup so we can find out what happens. Thank you.
> Is pcmanfm as desktop manager already started at that time?
Yes. If I kill it and start it without the desktop manager, then it opens the first time. But now I see that the problem only occurs if it was started with the option -d.
# G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all pcmanfm --desktop -d
** (pcmanfm:30120): DEBUG: fm_desktop_constructor for monitor 0
** (pcmanfm:30120): DEBUG: starting modules initialization
** (pcmanfm:30120): DEBUG: found module file: vfs-menu.so
** (pcmanfm:30120): DEBUG: found handler vfs:menu
** (pcmanfm:30120): DEBUG: found module file: vfs-search.so
** (pcmanfm:30120): DEBUG: found handler vfs:search
** (pcmanfm:30120): DEBUG: found module file: gtk-menu-actions.so
** (pcmanfm:30120): DEBUG: found handler gtk_menu_scheme:*
** (pcmanfm:30120): DEBUG: found module file: gtk-fileprop-x-desktop.so
** (pcmanfm:30120): DEBUG: found handler gtk_file_prop:application/x-desktop
** (pcmanfm:30120): DEBUG: found module file: gtk-menu-trash.so
** (pcmanfm:30120): DEBUG: found handler gtk_menu_scheme:trash
** (pcmanfm:30120): DEBUG: found module file: gtk-fileprop-x-shortcut.so
** (pcmanfm:30120): DEBUG: found handler gtk_file_prop:inode/x-shortcut
** (pcmanfm:30120): DEBUG: done with modules
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
** (pcmanfm:30120): DEBUG: got working area: 0.0.1280.996
** (pcmanfm:30120): DEBUG: adding new FmBackgroundCache for /usr/local/share/wallpaper/gnome/background-default.jpg
** (pcmanfm:30120): DEBUG: got working area: 0.0.1280.996
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon application-x-xpinstall gnome-mime-application-x-xpinstall application-x-generic
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon application-x-ms-shortcut gnome-mime-application-x-ms-shortcut application-x-generic
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon inode-symlink gnome-mime-inode-symlink inode-x-generic
** (pcmanfm:30120): DEBUG: line = /root
** (pcmanfm:30120): DEBUG: line = 0
** (pcmanfm:30120): DEBUG: line = /root
** (pcmanfm:30120): DEBUG: line = 0
** (pcmanfm:30120): DEBUG: reactivated gestures to page 0
** (pcmanfm:30120): DEBUG: reactivated gestures to page 0
** (pcmanfm:30120): DEBUG: FmJob error: /Documents/Mum: No such file or directory
** (pcmanfm:30120): DEBUG: FmJob error: /Documents/Nathaniel: No such file or directory
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon application-x-sqlite3 gnome-mime-application-x-sqlite3 application-x-generic
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon application-x-trash gnome-mime-application-x-trash application-x-generic
** (pcmanfm:30120): DEBUG: unable to load icon . GThemedIcon application-x-trash gnome-mime-application-x-trash application-x-generic
The first instance of the two lines ending in "= /root" and "= 0" are what were output the first time I tried to start it.
Debug output attached since it didn't show up well in-line.
It's 1AM here, so I'm going home to bed ;)
Thank you very much. So you tell me without -d it works just well? It seems it is the source of your problem. I'll try to do something with it later.
And BTW, why do you run it as root? Just out of curiosity. It is dangerous and some programs may behave a bit different when you run them as root. :)