I reproduced the bug this evening. I logged in, moved the .gnome2/session file away, turned off session-saving, logged out and logged back in. Everything was back to normal then. When examining the session-file, there was no line for metacity (while there is one when everything is normal). So I think this is what happens, which prevents metacity from starting: * user presses logout * metacity crashes and stays down * gnome saves the state of the session, so without metacity running * shutdown ----> boot * user logs in * gnome reads session file without metacity-line => result = no metacity started. This bug (metacity not starting at login) should thus not happen when you don't save the state of the sessions. Remaining question is why metacity crashes :)
In attachement is the .gnome2/session-file from right after the crash. ** Attachment added: ".gnome2/session file after the crash" http://librarian.launchpad.net/7394214/session -- Metacity crash corrupts future Gnome sessions https://bugs.launchpad.net/bugs/106350 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
