Thanks for the report.
What version of the gconf2 package do you have installed? Can you see
any gconfd-related output in the .xsession-errors file in your home
directory? (Only a guess that it should output into this file).
** Changed in: Ubuntu
Sourcepackagename: None = gconf2
Status:
I think this is related to bug #45002
--
gconfd not shutting down/not restarting after X server killed
https://launchpad.net/bugs/45122
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Oooh, interesting.
In the hung state, gnome-terminal launched from a panel icon or the
gnome menu fails to appear.
But gnome-terminal run from the command line (from an xterm launched
from a text console login) actually works.
The non-working gnome-terminal hasn't got as far as running
The above all happened in a hang that didn't start with an extra gconfd
running. [details in a reply by email that hasn't made it here yet]
--
gconfd not shutting down/not restarting after X server killed
https://launchpad.net/bugs/45122
--
desktop-bugs mailing list
Ok, I reckon the hang on startup happens if a dead gnome-session has a
left-over socket in /tmp/.ICE-unix. I've just done a successful logon
after cleaning that up, even with a left-over gconfd.
Since I was really reporting the hang on login, it would be worth
renaming this bug and assigning it
