Ticket #979 (closed defect: fixed)
gdm's g-s-d sticks around after login
Reported by: | jdreed | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | Natty Release |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
From #850:
The first time a user logs in, using the Athena default sesion, LP:649809 is triggered (gdm's g-s-d sticks around and conflicts with the users'). Subsequent logins generally work, except when they don't. Logging in with "Ubuntu Classic" sometimes works and sometimes doesn't. I... don't have a good solution here. And of course the user can't kill gdm's g-s-d. My current bad idea involves an Xsession.d that sleeps for up to 10 seconds, checking ps to see if gdm's g-s-d is dead.
Zephyr discussion suggests upstream is also having problems reproducing this on anything but Ubuntu, and that it primarily affects VMs, but does manifest on real hardware. I suggest the following stupid workaround:
Index: debathena-branding =================================================================== --- debathena-branding (revision 25221) +++ debathena-branding (working copy) @@ -109,6 +109,7 @@ # Here on a Stop signal from the session manager. def sm_on_Stop(self): + subprocess.call(["/usr/bin/pkill", "-f", "gnome-settings-daemon"]) gtk.main_quit() def main(options):
r25254