Comment 28 for bug 424511

Revision history for this message
rtimai (rtimai) wrote :

https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/424511

Ubuntu 9.10 Karmic upgraded from Jaunty
rtimai@rtimai-desktop:~$ uname -a
Linux rtimai-desktop 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

NV5M64 [RIVA TNT2 Model 64/Model 64 Pro]

Metacity is not running after I log in also, even after I added it to Startup Applications with "remember running applications" selected. Re-registering the schemas according to earlier instructions also did not have any effect. I have to run "metacity --replace &" from Terminal on every login or run it from the Other > Metacity menu.

More seriously, the regular (secondary?) user is unable to log in, and keeps getting kicked back to the login screen. This problem is critical to the regular user, as it involves access to job application records and resumes. Rarely, but at times we can choose "other user" at the login prompt, re-enter the username, then password, and log in successfully. (Possibly that procedure is only coincidental to login success.)

In those rare sessions when the regular user is able to log in, Metacity or "Window Manager" does NOT appear in the Startup Applications list. So, the window manager must normally be starting up some other way, and must then be crashing... Except when the regular user is successfully logging in, then Metacity has not crashed, because it is not starting up from the Startup Applications list.

MORE: I don't know if this is relevant, but after entering the regular username and password, and just before the user gets kicked back to the login screen, TTY1 appears briefly with a password prompt for the PRIMARY user, then disappears before any password can be entered. This occurs even when the primary user has not logged in then out, and the regular user is attempting to login in after a restart command. Is this normal?

MORE: Just before the login screen is displayed there is a brief message, something about 1152 X 864 resolution being set up, then resetting to 1028 X 768 (my preference, as the higher mode reduces the refresh rate from 85 to 75Mhz.) The login screen background briefly appears off center to the right, the screen flashes before it re-centers. I have an old nVidia RIVA TNT2 card which apparently is no longer supported by Jockey, so the Legacy driver is not detected, and I have no nVidia enhanced features.

Could video mode resets have something to do with the crashing window manager, and the regular user being unable to log in?

If anyone wants log records, please provide the command line entry. Thanks.