upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and unable to console

[Eduard Sanchez Biete]

Binary package hint: gdm

Yesterday I did upgrade from gdm 2.20.10-0ubuntu5 to gdm 2.26.1-0ubuntu2 on my HP2133 netbook.

Ubuntu 9.10
Kernel: 2.6.31-1-generic
GNOME: 2.27.3

After rebooting erratic behavior is observed:

1) login is asked in correct resolution (1024x600). I'm able to switch to console with CTRL+ALT+F2.

From here I've found 2 possible scenarios:

A) after login correctly I'm redirected to gnome desktop with correct resolution, and an error Metacity window is shown: "These windows do not support "save current setup" and will have to be restarted manually next time you log in", referring to Class: Login Window, Window: Gdm-simple-greeter. Still in the correct resolution 1024x600. I'm able to open console with CTRL+ALT+F2 and operate normally until something breaks the resolutions (for example running package manager)

B) after login correctly it switches screen mode to a lower resolution, non supported (800x600) but partially visible and ask to login again. "gdm-simple-greeter" error window appears again. From here I'm not able to open a console using CTRL+ALT+Fn, the screen is crewed if I try.

I'll attach gdm logs on the next post. Is there a way to be back to v2.20?

Thanks

[Sebastien Bacher (seb128)]

the resolution is an xorg thing

[Eduard Sanchez Biete (esbiete)]

Sebastien, I do agree about the resolution, but I think you may have missed rest of the bug report about double login and erratic behavior after login. That happened after upgrading gdm, and that's why I've classified it under gdm and not xorg

[Eduard Sanchez Biete (esbiete)]

Reverting the system to gdm 2.20.10-0ubuntu5 solves the problem, so may be there's some problem with xorg on the last release, but definitively there is something wrong on 2.26.1 that breaks, at least, my installation.

I think this bug has to be assigned to gdm team.

Please ask for any test you want me to do.

Thanks.

[Martin Pitt (pitti)]

The first issue is bug 395324

[Martin Pitt (pitti)]

I just uploaded gdm 2.26.1-0ubuntu5 which should finally solve most gdm issues. (Please do read https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-July/000586.html before, though). Does it behave any better? If you still have problems, please do this:

 press ctrl+alt+f1 and log into text terminal
 sudo /etc/init.d/gdm stop
 sudo -i
 rm /var/log/gdm/*
 reboot

then please reboot the computer, log in, and do

  sudo tar czf /tmp/gdm-logs.tar.gz /var//log/gdm

and attach /tmp/gdm-logs.tar.gz here.

[Eduard Sanchez Biete (esbiete)]

Thank you Martin.

I've upgraded from 2.20.10-ubuntu5 and the process has renamed custom, deleted some obsolete conffiles and installed the new ones. Gdm action "reload" failed but installation finished correctly without closing any active screen. When trying to reboot the system asked me for authorization because other users were logged in (not possible).

After reboot appeared the default login screen with my username on tty7 and was able to login ok (correctly, only once). The Metacity error described on bug https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/395324 still appears, but, as it was mentioned in your update, it's an expected behavior to be addressed.

So, if you do agree, this update closes this bug also. Please ask for any test or logs you may want.

Thanks!

[Martin Pitt (pitti)]

Thanks for testing! The "multiple users require authentication" is tracked in bug 287715.

Closing.