Can you get a backtrace of the stuck gsettings process? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/974938
Title: Process "gsettings" prevents logging in Status in “glib2.0” package in Ubuntu: New Bug description: When I try to login with my newly upgraded Ubuntu 12.04 (development branch), nothing happens. It just shows the same empty background that LightDm has. I have found one solution to get myself logged: If I go to virtual console and display what processes I have, there are about six processes, and one of them is "gsettings". It does not consume any CPU resources, and when I kill it (with -3), the login process immediately continues and finally gets me logged in. To my knowledge, gsettings comes from package libglib2.0-bin and I have version 2.32.0-1ubuntu1 of it. How to reproduce: 1 Try to log in. 2 Wait for several minutes to be sure it is stuck 3 Go to virtual console and killall -3 gsettings 4 Logging in immediately continues and finally completes in few seconds Possible causes: 1 I'm using LDAP. My user information comes from LDAP-server, and this has caused lots of other logging problems, thanks to software developers not realizing the fact, that people use stuff like LDAP. 2 I had some problems when upgrading to 12.04, so that might have screwed things up. The funny thing is, that logging in works on my other PC, which has almost identical system and package configuration. So if you give me some hints, I can try to compare differences between them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/974938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
