gdmgreeter crashed with SIGSEGV in __libc_start_main()

[perlluver]

Binary package hint: gdm

Just happened after updating, was working fine until the recent updates came through. Had to install KDM to login.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gdm/gdmgreeter
NonfreeKernelModules: nvidia
Package: gdm 2.20.8-0ubuntu7
ProcCmdline: /usr/lib/gdm/gdmgreeter
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
Title: gdmgreeter crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups:

[Marc Deslauriers (mdeslaur)]

I got this also after updating.

Switching xorg.conf from nvidia to nv worked for me.

[Hernando Torque (htorque)]

Here too using vesa (my nvidia GPU is half dead, nv and nvidia won't work).

[perlluver (plaufcan)]

I just switched to KDM, and I am logged in, with the Nvidia driver still working. Otherwise, my refresh rate, hurts my head.

[İsmail Dönmez (ismaildonmez)]

Confirming, problem with latest jaunty updates.

[Mikael Karon (mikael-karon)]

Confirmed here to.

[mark stover (stovenator)]

I added this in duplicate Bug# 331390, but here too for posterity:

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

===============================

What I did was Ctrl-Alt-F1 to a terminal. Then I changed to /var/cache/apt/archives/

and then did:

sudo dpkg -i libgtk2.0-doc_2.15.3-0ubuntu2_all.deb libgtk2.0-common_2.15.3-0ubuntu2_all.deb libgtk2.0-bin_2.15.3-0ubuntu2_all.deb libgtk2.0-dev_2.15.3-0ubuntu2_amd64.deb libgtk2.0-0_2.15.3-0ubuntu2_amd64.deb gtk2-engines-pixbuf_2.15.3-0ubuntu2_amd64.deb libgail-dev_2.15.3-0ubuntu2_amd64.deb libgail-common_2.15.3-0ubuntu2_amd64.deb libgail18_2.15.3-0ubuntu2_amd64.deb

That's assuming you have those versions of the files in your apt archive.

[Nikola Yanev (gericom)]

the same here, but i think it is as mark stover says, because these lib's and not nvidias', but also realize, that putting gdm on autologin with my username it work perfect, but i know it can be security vulnerability, but we can use it some days until it be fixed ;)

[Efraim Karsh (efraimkarsh)]

Confirmed. But there seems to be a "pulseaudio catch", see below.

Btw, you can have users remain on a GUI (useful for correcting the problem over the phone):
You can in fact also

reboot to safety
get to a prompt
sudo /etc/init.d/gdm stop
startx
and then just paste Mark Stover's string launching from any GUI terminal, inside
/var/cache/apt/archives/

sudo dpkg -i libgtk2.0-doc_2.15.3-0ubuntu2_all.deb libgtk2.0-common_2.15.3-0ubuntu2_all.deb libgtk2.0-bin_2.15.3-0ubuntu2_all.deb libgtk2.0-dev_2.15.3-0ubuntu2_amd64.deb libgtk2.0-0_2.15.3-0ubuntu2_amd64.deb gtk2-engines-pixbuf_2.15.3-0ubuntu2_amd64.deb libgail-dev_2.15.3-0ubuntu2_amd64.deb libgail-common_2.15.3-0ubuntu2_amd64.deb libgail18_2.15.3-0ubuntu2_amd64.deb

This will restore the previous configuration BUT seems at the same time to destroy the recent (yesterday or the day before) welcome uodate fix for all our pulseuadio problems on 64 bit boxes.

This -afaics- will compel us again to ditch pulseaudio or kill & restart it every boot with the usual
pulseaudio -k ; start-pulseaudio-x11
command

Any better solution?

[Daniel Holbach (dholbach)]

A new GTK (2.15.4-0ubuntu3) was just uploaded that will likely fix the issue - please report back if it does or doesn't.

[Casey J Peter (caseyjp1)]

that update fixed the issue under virtualbox 2.1.4 just fyi.