Re: [sabayon] hang during login / completely removing Sabayon

[Alexander Larsson <alexl redhat com>]

On Mon, 2005-11-28 at 09:41 -0700, Andrew Z wrote:
> Hello,
> 
> I used Sabayon on a terminal server running Fedora Core 4.  Then I 
> removed Sabayon, but we are having a strange, annoying problem which 
> seems to be correlated only to the user accounts previously managed 
> Sabayon.  The problem is that *sometimes* when a user logs into Gnome, 
> he sees only the solid blue Gnome background and mouse cursor.  Neither 
> the splash screen nor the desktop ever come up.
> 
> When the problem happens, an inspection of running processes shows these 
> for the user:
> brendab    442  0.0  0.0   2604   752 ?        Ss   Nov17   0:00 
> dbus-daemon --fork --print-pid 8 --print-address 6 --session
> brendab    482  0.0  0.0  13404  1268 ?        S    Nov17   0:00 
> /usr/libexec/gconfd-2 5
> brendab    487  0.0  0.0   8352  1292 ?        Ss   Nov17   0:00 
> /usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=19
> brendab    744  0.0  0.0  91420  1940 ?        Sl   Nov17   0:00 
> /usr/libexec/evolution-data-server-1.2 
> --oaf-activate-iid=OAFIID:GNOME_Evolution_DataServer_InterfaceCheck 
> --oaf-ior-fd=39
> brendab    752  0.0  0.1  58376  3036 ?        Sl   Nov17   0:00 
> /usr/libexec/evolution/2.2/evolution-alarm-notify 
> --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.2 
> --oaf-ior-fd=41
> brendab  17774  0.0  0.0   2520   408 ?        Ss   13:27   0:00 
> dbus-daemon --fork --print-pid 8 --print-address 6 --session
> brendab  17902  0.0  0.2  19900  5204 ?        Ss   13:31   0:00 
> /usr/bin/gnome-session
> brendab  17971  0.0  0.0   3872   660 ?        Ss   13:31   0:00 
> /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session 
> /etc/X11/xinit/Xclients
> brendab  17974  0.0  0.0   2832   980 ?        S    13:31   0:00 
> /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
> brendab  17975  0.0  0.0   2520   404 ?        Ss   13:31   0:00 
> dbus-daemon --fork --print-pid 8 --print-address 6 --session
> 
> The problem is worked around by running "rm -rf /tmp/*usernamefoo*" and 
> then asking the user to login again.  Specifically, it seems 
> "/tmp/gconfd-usernamefoo/lock/ior" may be to blame.
> 
> Does anyone have suggestions on troubleshooting or fixing this problem?  
> Will "rpm -e" remove all of Sabayon and its changes, or are additional 
> steps required?

Sabayon installs /etc/gconf/2/local-defaults.path
and /etc/gconf/2/local-mandatory.path files that include
$(HOME)/.gconf.path.defaults and $(HOME)/.gconf.path.mandatory into the
gconf tree. Maybe these are somehow left?

I'm not sure what else could be wrong.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Alexander Larsson                                            Red Hat, Inc 
                   alexl redhat com    alla lysator liu se 
He's a maverick vegetarian gentleman spy who dotes on his loving old ma. She's 
a chain-smoking thirtysomething safe cracker with the soul of a mighty 
warrior. They fight crime!