gdmgreeter crashed with SIGSEGV in __libc_start_main()

Bug #331324 reported by Dave Stroud
290
This bug affects 13 people
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Critical
gtk+2.0 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: gdm

after updating I get this crash when desktop loads. Everything is working ok after booting. Loging out crashes the gdmgreeter and causes a kernal panic.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gdm/gdmgreeter
Package: gdm 2.20.8-0ubuntu7
ProcCmdline: /usr/lib/gdm/gdmgreeter --gtk-module=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libkeymouselistener:/usr/lib/gtk-2.0/modules/libdwellmouselistener
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
Signal: 11
SourcePackage: gdm
Stacktrace:
 #0 0x08064931 in ?? ()
 #1 0x0805213e in ?? ()
 #2 0xb73d9775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #3 0x08051671 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: gdmgreeter crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Related branches

Revision history for this message
Dave Stroud (bigdavesr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:main (argc=) at greeter.c:1305

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gdm:
importance: Undecided → Medium
Revision history for this message
Daniel Holbach (dholbach) wrote :

xdm works.

AMD64, nvidia hardware, Jaunty. (Seems to be different from bug 331292).

xdm works.

0 0x000000000041ea8a in gdm_wm_screen_init (cur_screen_num=0) at gdmwm.c:118
 screen = <value optimized out>
 i = 35549984
#1 0x000000000040d41d in main (argc=1, argv=0x7fff3ddfa9c8) at greeter.c:1305
 bg_color = <value optimized out>
 hup = {__sigaction_handler = {sa_handler = 0x7fff3ddfa910, sa_sigaction = 0x7fff3ddfa910}, sa_mask = {__val = {140734231455960, 4131212846, 140734231455936, 0, 139840741856062, 0, 139840743889544, 1,
      0, 1, 139840673514178, 139840673071128, 139840676624896, 35304928, 4294967296, 139840743889544}}, sa_flags = 903844696, sa_restorer = 0x7fff3ddfa940}
 term = {__sigaction_handler = {sa_handler = 0x1a, sa_sigaction = 0x1a}, sa_mask = {__val = {53, 4131212846, 139840741855472, 139840673044852, 46, 64550200, 140734231455536, 140734231455960,
      139840673045352, 0, 139840743889544, 139840743930264, 4222889, 139840673096208, 4202200, 4294967296}}, sa_flags = 1995, sa_restorer = 0x7fff3ddfa78f}
 mask = {__val = {4222889, 35305504, 35305515, 139840649505209, 35305504, 139840649479992, 140734231455976, 140734231455968, 61267, 4096, 94660100, 57662254, 52853800, 48087040, 47561478, 4353680}}
 ctrlch = <value optimized out>
 error = <value optimized out>
 theme_file = <value optimized out>
 theme_dir = <value optimized out>
 gdm_graphical_theme = <value optimized out>
 gdm_gtk_theme = <value optimized out>
 sid = <value optimized out>
 r = <value optimized out>
 i = <value optimized out>
 key_string = <value optimized out>

Revision history for this message
Dave Stroud (bigdavesr) wrote :

Last update seems to have fixed this for me. But now have panel problems. Lost main menue . will file new report

Revision history for this message
Daniel Holbach (dholbach) wrote :

Still not fixed for me.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Hum, now I get bug 331292. Weird.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Ignore my last comment. After retracing the crash it's still the same as in comment 4.

Changed in gdm:
importance: Medium → High
status: New → Confirmed
Revision history for this message
Dave Stroud (bigdavesr) wrote :

I spoke too soon Am still having this problem.

Revision history for this message
Rocko (rockorequin) wrote :

Me too. Thanks to mark stover for his workaround in https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/331292.

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gtk+2.0:
status: Confirmed → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

what video driver are the people getting the bug using?

Revision history for this message
Hernando Torque (htorque) wrote :

Vesa (with Nvidia G73M).

Revision history for this message
İsmail Dönmez (ismaildonmez) wrote :

Using nvidia driver.

Revision history for this message
nullack (nullack) wrote :

Using Nvidia 180.29

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+2.0 - 2.15.4-0ubuntu3

---------------
gtk+2.0 (2.15.4-0ubuntu3) jaunty; urgency=low

  * debian/patches/092_workaround_xrandr_issue.patch:
    - don't init new xrandr to workaround gdm crashing on some config
      (lp: #331324)

 -- Sebastien Bacher <email address hidden> Thu, 19 Feb 2009 10:56:54 +0100

Changed in gtk+2.0:
status: Triaged → Fix Released
Revision history for this message
Daniel Holbach (dholbach) wrote :

Definitely fixed with the new GTK for me.

Thanks a bunch.

Revision history for this message
Hernando Torque (htorque) wrote :

Fixed. Thanks!

Revision history for this message
Mike (bild85) wrote :

Very impressive. Fixed after update. Nicely managed Sebastien!

newbies -steps to get the update:
get to the console (ctrl-alt-f1) and log in.
launch aptitude graphical package manager: "sudo aptitude"
hit "u" to search for updates (you have to be online - plug in a LAN cable if available)
hit "U" to mark all upgradeable packages
hit "g" to start the upgrade
When complete, log out and hit "ctrl-alt-f7" to get back to the login screen

Revision history for this message
Dave Stroud (bigdavesr) wrote :

The fix worked for me. There is a sound issue remaining on log out with the login splash.

Revision history for this message
wulf solter (wulfsolter) wrote :

Its moments like this where I love ubuntu! Bug fix within a matter of hours! Bless you all, Dave Stroud, Sebastien Bacher, Daniel Holbach etc etc etc..

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :

From duplicate... fixed...

Thank you

Revision history for this message
Igor Zakharov (f2404) wrote :

Bug has been fixed but everything is working veeery slow.

Revision history for this message
Dominique Meeùs (dominiquem) wrote :

Using Intel 945G as hardware,
lspci
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
but as vesa because of a bug in xorg-intel.

Gdmgreeter problem solved for me after upgrade a few minutes ago.

Revision history for this message
JasonPorter (jasonporter) wrote :

Confirming here on Jaunty 32bit i386. Dropping to recovery console and running updates fixed login problem, but verifying Igor's comment above that system performance is SIGNIFICANTLY lower. Functionality is restored with new GTK but there is a large performance hit. Hopefully that will be sorted soon... let me know if any further info would assist.

Revision history for this message
JasonPorter (jasonporter) wrote :

After this "fix" to GTK, my system performance is ABYSMALLY slow. At least a 60% overall UI performance hit. Running Nvidia 180.29 (standard Jaunty repo packages) and the new "fixed" GTK as mentioned previously.

Is anyone else experiencing significant performance reduction? Multitasking is almost unusable.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the performance issue is not likely due to this change but to xorg changes rather

Changed in gtk:
status: Unknown → Fix Released
Changed in gtk:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.