http://qa.mandrakesoft.com/show_bug.cgi?id=6140
------- Additional Comments From [EMAIL PROTECTED] 2003-16-10 09:16 ------- Good news: 1) I updated GconfX anf libGconfX packages => it does not solve my daemon problem. 2) I set the TMPDIR variable => it does not solve it either (I think this is normal since it was for the locking problem, not the daemon problem, right?) 3)When I log in with error messages concerning the deamon, I can launch gnome-settings-daemon by hand and IT WORKS FINE. If I logout and try to log in again, still the same daemon problem. 4)If I logout, run bonobo-slay, I have a message explaining that some processes will be killed, exactly the same related by fabrice: /usr/lib/bonobo-activation-server * 2 /usr/lib/evolution/1.4/evolution-wombat * 3 THEN I CAN LOGIN WITHOUT PROBLEM!!!! I no longer need to reboot my computer now :-=) -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: Environment : /home NFS mount ( vers=3, tcp, rsize=8192, wsize=8192, nosuid, soft, intr, timeo=600 ) serveur = mdk 9.1 + soft RAID1 ( ext3 partition ), PIV client = current cooker ( 2.4.22-10mdk, GConf-1.0.9-11mdk, GConf2-2.4.0.1-1mdk, nfs-utils-clients-1.0.5-1mdk, kdebase-3.1.92-2mdk, metacity-2.6.1-1mdk ), AMD Symptoms : if for example I quit abruptly gnome - CTRL+ALT+BACKSPACE ), next time I want to log, I can't because gnome can't remove the lock ( or find a lock ) in ~/tmp/gconf-username/ ( this location change between mdk 9.1 and mdk 9.2, before this was ~/.gconfd/... ). Sometimes you can read the message saying that you have a locking problem ( and thus read the path to the lock ) but sometimes you see nothing ( just some windows with dash instead of text ... ). A bad combinaisaison is when you log in and have the gnome preference daemon bug ( see #6138 ), then you decide to stop everything before it mess up your session config ( as it asks to remove some applets ... ) by hitting CTRL+ALT+BACKSPACE. You reboot the computer to resolve the problem ( argh )and when you try to log in again ... gconf locking problem ( so you need to remove manually the lock ) and then you can log in ( so 3 attempts and 1 reboot just to log in in Gnome ! ). This is really painfull when you have several computers to administer under gnome. the locking proble can be solve by erasing by hand the lock at each gnome start ( i put this in /etc/gnome/gnomerc ), but this is just a hack. Gnome is really too fragile in an NFS environment ...
