When I start XFCE4, it triggers gconfd multiple times and generates many messages stating that gconfd Failed to get lock for daemon. XFCE4 is started with startxfce4 This does not seem to cause any operational problems, but it clutters the logs. When I start GNOME, I get these many messages: Mar 19 00:21:11 lmo gconfd (wnh-5487): starting (version 2.14.0), pid 5487 user 'wnh' Mar 19 00:21:11 lmo gconfd (wnh-5487): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Mar 19 00:21:11 lmo gconfd (wnh-5487): Resolved address "xml:readwrite:/home/wnh/.gconf" to a writable configuration source at position 1 Mar 19 00:21:11 lmo gconfd (wnh-5487): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Mar 19 00:21:13 lmo gconfd (wnh-5487): Resolved address "xml:readwrite:/home/wnh/.gconf" to a writable configuration source at position 0 Mar 19 00:21:18 lmo pcscd: winscard.c:219:SCardConnect() Reader E-Gate 0 0 Not Found Mar 19 00:21:18 lmo last message repeated 4 times When I start XFCE4 (startxfce4), I get these many messages: Mar 19 00:22:23 lmo gconfd (wnh-5719): starting (version 2.14.0), pid 5719 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5719): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Mar 19 00:22:24 lmo gconfd (wnh-5719): Resolved address "xml:readwrite:/home/wnh/.gconf" to a writable configuration source at position 1 Mar 19 00:22:24 lmo gconfd (wnh-5719): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Mar 19 00:22:24 lmo gconfd (wnh-5734): starting (version 2.14.0), pid 5734 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5734): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:24 lmo gconfd (wnh-5736): starting (version 2.14.0), pid 5736 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5739): starting (version 2.14.0), pid 5739 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5739): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:24 lmo gconfd (wnh-5741): starting (version 2.14.0), pid 5741 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5745): starting (version 2.14.0), pid 5745 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5745): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:24 lmo gconfd (wnh-5747): starting (version 2.14.0), pid 5747 user 'wnh' Mar 19 00:22:24 lmo gconfd (wnh-5751): starting (version 2.14.0), pid 5751 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5751): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:24 lmo gconfd (wnh-5755): starting (version 2.14.0), pid 5755 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5747): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5755): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5770): starting (version 2.14.0), pid 5770 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5766): starting (version 2.14.0), pid 5766 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5766): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:24 lmo gconfd (wnh-5757): starting (version 2.14.0), pid 5757 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5774): starting (version 2.14.0), pid 5774 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5776): starting (version 2.14.0), pid 5776 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5778): starting (version 2.14.0), pid 5778 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5768): starting (version 2.14.0), pid 5768 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5757): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5781): starting (version 2.14.0), pid 5781 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5768): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5783): starting (version 2.14.0), pid 5783 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5778): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5781): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5789): starting (version 2.14.0), pid 5789 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5774): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5748): starting (version 2.14.0), pid 5748 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5796): starting (version 2.14.0), pid 5796 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5796): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5798): starting (version 2.14.0), pid 5798 user 'wnh' Mar 19 00:22:25 lmo gconfd (wnh-5748): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:25 lmo gconfd (wnh-5772): starting (version 2.14.0), pid 5772 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5801): starting (version 2.14.0), pid 5801 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5770): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5803): starting (version 2.14.0), pid 5803 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5803): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5805): starting (version 2.14.0), pid 5805 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5805): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5807): starting (version 2.14.0), pid 5807 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5772): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5785): starting (version 2.14.0), pid 5785 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5787): starting (version 2.14.0), pid 5787 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5736): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5741): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5776): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5785): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5787): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5783): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5789): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5815): starting (version 2.14.0), pid 5815 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5817): starting (version 2.14.0), pid 5817 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5798): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5820): starting (version 2.14.0), pid 5820 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5801): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5809): starting (version 2.14.0), pid 5809 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5811): starting (version 2.14.0), pid 5811 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5809): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5811): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5807): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo pcscd: winscard.c:219:SCardConnect() Reader E-Gate 0 0 Not Found Mar 19 00:22:26 lmo last message repeated 4 times Mar 19 00:22:26 lmo gconfd (wnh-5824): starting (version 2.14.0), pid 5824 user 'wnh' Mar 19 00:22:26 lmo gconfd (wnh-5824): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5815): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:26 lmo gconfd (wnh-5820): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:27 lmo gconfd (wnh-5831): starting (version 2.14.0), pid 5831 user 'wnh' Mar 19 00:22:27 lmo gconfd (wnh-5833): starting (version 2.14.0), pid 5833 user 'wnh' Mar 19 00:22:27 lmo gconfd (wnh-5831): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:27 lmo gconfd (wnh-5817): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:27 lmo gconfd (wnh-5822): starting (version 2.14.0), pid 5822 user 'wnh' Mar 19 00:22:27 lmo gconfd (wnh-5822): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:27 lmo gconfd (wnh-5829): starting (version 2.14.0), pid 5829 user 'wnh' Mar 19 00:22:27 lmo gconfd (wnh-5833): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:27 lmo gconfd (wnh-5829): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:28 lmo gconfd (wnh-5835): starting (version 2.14.0), pid 5835 user 'wnh' Mar 19 00:22:28 lmo gconfd (wnh-5835): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) Mar 19 00:22:28 lmo gconfd (wnh-5840): starting (version 2.14.0), pid 5840 user 'wnh' Mar 19 00:22:28 lmo gconfd (wnh-5840): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-wnh/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
This is not a problem with Xfce, as it does not use gconf. Likely you are running an application on startup that *does* use gconf, and there's something wrong with it (or wrong with gconf).
Remember bug 453 complained of Xfce session depends on GNOME libs. Everything is supposed to work smoothly together.
Unrelated, (In reply to comment #2) > Remember bug 453 complained of Xfce session depends on GNOME libs. > Everything is supposed to work smoothly together. Of course, we don't have the resource to fix every single broken app out there. As Brian said, this is a problem with gconf, not xfce (a bit of googling should help you). BTW, xfce4-session doesn't require gnome-libs, it's is able to run gconf (if available) to speed up startup of GNOME apps, that's it.
(In reply to comment #3) > Unrelated, (In reply to comment #2) > > Remember bug 453 complained of Xfce session depends on GNOME libs. > > Everything is supposed to work smoothly together. > > Of course, we don't have the resource to fix every single broken app out there. > As Brian said, this is a problem with gconf, not xfce (a bit of googling should > help you). > BTW, xfce4-session doesn't require gnome-libs, it's is able to run gconf (if > available) to speed up startup of GNOME apps, that's it. > Xfce4 is working great except for the messy messages from gconf. I have no desire for xfce to fix gnu. And I don't think the offending app is broken. But there is somebody somewhere who knows how to tell xfce4 not to use gconf, or how to pacify gconf and this should be documented somewhere, if not here. I ran startxfce4 from a failsafe terminal and captured this output which is beyond my understanding: wnh@lmo:~$ startxfce4 /usr/bin/startxfce4: X server already running on display :0.0 /etc/xdg/xfce4/xinitrc: line 58: xscreensaver: command not found Agent pid 3847 ** Message: This build doesn't include support for XF86Misc extension ** Message: Querying Xkb extension ** Message: Xkb extension found ** Message: Querying Xkb extension ** Message: Xkb extension found gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Adding directory '/desktop/gnome/sound' gconf trace: Adding notify to engine at '/desktop/gnome/sound' gconf trace: Error 'Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0' gconf trace: Unreturned error 'Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/COMM_FAILURE:1.0' ... and it goes on and on
Ok, get this through your head: XFCE IS NOT USING GCONF. Some app that you are running on startup is. If you have 'Launch GNOME services on startup' checked in the Sessions and Startup settings panel, it will launch GNOME apps. Thunar can query gconf to get a list of video thumbnailers. Xfce does not use gconf directly for anything. They're just log messages. Is your system broken in any way? Is something not working? If not, just ignore it. If that's not possible for you for some reason, this is not the forum for you to discuss it or look for help.
I fully agree with Brian, this is not something we can fix in xfce. What I believe is that xfce4-session might start gconf while it's already being started, or vice-versa, causing the trouble. This is possibly related to some custom startup script, provided by you rdistibution or something, because I'm not having such problems here. Did you try to run the "Session and startup" settings dialog, switch to the "advanced" tab folder and disable the "Launch Gnome services on startup"? In any case, he messages are nothing serious and your system should behave normally.
(In reply to comment #6) > I fully agree with Brian, this is not something we can fix in xfce. > > What I believe is that xfce4-session might start gconf while it's already being > started, or vice-versa, causing the trouble. This is possibly related to some > custom startup script, provided by you rdistibution or something, because I'm > not having such problems here. > > Did you try to run the "Session and startup" settings dialog, switch to the > "advanced" tab folder and disable the "Launch Gnome services on startup"? > > In any case, he messages are nothing serious and your system should behave > normally. > Maybe not a bug in xfce per se. And apparently system behaves normally except for the messages. I tried removing "Gnome Desktop Environment" which also removed many desired applications. This got rid of the messages, but is an unacceptable solution, so I restored from a backup. I am attempting to discover if it always generates those messges when both xfce and gnome are installed on the same system. The only box checked under "Sessions and Startup" is "Prompt on logout". All autostarted applications are un-checked.
(In reply to comment #7) > I tried removing "Gnome Desktop Environment" which also > removed many desired applications. This got rid of the messages, but is an > unacceptable solution, so I restored from a backup. Ouch, seems there's been a huge misunderstanding here! I never said to remove GNOME all together, I just suggested to disable the option in xfce session manager that start GNOME "services"... > I am attempting to discover > if it always generates those messages when both xfce and gnome are installed on > the same system. The only box checked under "Sessions and Startup" is "Prompt > on logout". All autostarted applications are un-checked. You mean that in the "advanced" tab folder, all "Launch XXX services on startup are unchecked"? If that's the case, it means that it's not xfce that fires up gconf.