gdmgreeter complains about greeter unable to login

[Tiva]

EDIT: This bug is fixed for me with todays (02/19/09 ) updates to the gtk packages.

I have been running relatively stable Xubuntu AMD64 Jaunty with compiz etc... Today I realized there was a number of updates in my update-manager... I installed them all and upon reboot gdm complained that the current greeter was corrupt/unavailable. Only way for me to login in is to edit the gdm conf file and set auto-login to enabled. That lets me get logged-into my xfce session but upon boot everything seems fine at first.. the mouse changes to my set icon theme and then eveything turns into garbled random collage of pictures, mouse reacts to input (moves)... but everything else is locked up... like the xserver is freezing, however I really have no clue. To get my computer temporarily working... I dropped down CTRL-ALT-1 to CLI.

sudo dpkg-reconfigure -phigh xserver-xorg
(gives me a vanila xorg.conf and backups the one nvidia created)
sudo /etc/init.d/gdm restart

Then I able to login and use my computer... if I try reconfigure the xorg with sudo nvidia-xconfig it leads me back to my initial problem.

I have tried reinstalling nvidia*, gdm, xfdesktop4, xfce4

ctrl-alt-delete which should take me to gdmgreeter screen of course does not work.

just wondering if anyone else is experiencing this... if i should wait out for an update or just reinstall. wouldnt be so bad I can easily backup my home partition.

I not sure what logs I should look into for necessary debug info... but I can reproduce it easily so if you let me know I will post up any log output.

thread in jaunty forums:
http://ubuntuforums.org/showthread.php?t=1074193

[mark stover (stovenator)]

I can confirm this same bug on Ubuntu Jaunty, AMD64, nvidia. gdmgreeter dies upon start. I have attached the crash report from /var/crash/

[Andy Ferguson (teknostatik)]

Marking as confirmed as we've now got two identical reports

[amaxtt (amaxtt)]

seems like conflict with Nvidia driver. replacing in to nv solved this crap bug....

[Noel J. Bergman (noeljb)]

Broken for me, and many others on the IRC channel.

[Noel J. Bergman (noeljb)]

Attaching apport crash report as requested.

[mark stover (stovenator)]

I downgraded libgtk2.0 and everything is back to normal. The following list are interdependent, so I downgraded them all:

libgtk2.0-0
libgtk2.0-bin
libgtk2.0-common
libgtk2.0-dev
libgtk2.0-doc
libgail18
libgail-common
libgail-dev
gtk2-engines-pixbuf

[Don Zavitz (dzavitz)]

i can confirm downgrading of these packages does fix this...

libgtk2.0-0
libgtk2.0-bin
libgtk2.0-common
libgail18
gtk2-engines-pixbuf

and these are the packages i reverted back to....

libgtk2.0-0_2.15.3-0ubuntu2_amd64.deb
libgtk2.0-bin_2.15.3-0ubuntu2_all.deb
libgtk2.0-common_2.15.3-0ubuntu2_all.deb
libgail18_2.15.3-0ubuntu2_amd64.deb
gtk2-engines-pixbuf_2.15.3-0ubuntu2_amd64.deb

[Tiva (ugkbunb)]

This bug is fixed for me with todays updates to the gtk packages.