Ubuntu
gdm package

gdmgreeter crashed with signal 5

Bug #128571 reported by Durand D'souza on 2007-07-26

26

Affects		Status	Importance	Assigned to	Milestone
	gdm (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: gdm

After an update, gdm seems to have segfaulted and just crashes as soon as it starts. It repeatedly restarts and crashes, until it shows an error which is something along the lines of GDM has just crashed 6 times in the last 60 seconds, it will be run in 2 minutes. After 2 minutes, it does the exact same thing.

I temporarily fixed logging in by installing kdm and running sudo kdm. That works so it must be a gdm error.

ProblemType: Crash
Architecture: i386
Date: Thu Jul 26 18:36:45 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/gdm/gdmgreeter
NonfreeKernelModules: nvidia
Package: gdm 2.19.4-0ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/gdm/gdmgreeter --gtk-module=gail:atk-bridge:/usr/lib/gtk-2.0/modules/libkeymouselistener:/usr/lib/gtk-2.0/modules/libdwellmouselistener
ProcCwd: /var/lib/gdm
ProcEnviron:
LANG=en_GB.UTF-8
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
LANGUAGE=
SHELL=/bin/false
Signal: 5
SourcePackage: gdm
StacktraceTop:
?? () from /usr/lib/libgdk-x11-2.0.so.0
?? () from /usr/lib/libgdk-x11-2.0.so.0
?? ()
?? () from /usr/lib/libgdk-x11-2.0.so.0
?? ()
Title: gdmgreeter crashed with signal 5
Uname: Linux Carbon-14 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups:

Tags:

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-26:

#1

Dependencies.txt Edit (8.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (808 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (12.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (611 bytes, text/plain; charset="utf-8")
Registers.txt Edit (475 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (530 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (557 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (11.5 KiB, text/plain)

StacktraceTop:gdk_x_error (display=0x8086108, error=0xbfc69488) at /build/buildd/gtk+2.0-2.11.6/gdk/x11/gdkmain-x11.c:641
_XError (dpy=0x8086108, rep=0xbfc6955c) at ../../src/XlibInt.c:2907
_XReply (dpy=0x8086108, rep=0xbfc6955c, extra=0, discard=0) at ../../src/XlibInt.c:1833
XOpenDevice (dpy=0x8086108, id=2) at ../../src/XOpenDev.c:83
gtk_module_init (argc=0xb7e940f0, argv=0xb7e940f4) at keymouselistener.c:174

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (11.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2007-07-26: Stack trace with source code

#4

StacktraceSource.txt Edit (3.4 KiB, text/plain)

Changed in gdm:
importance:	Undecided → Medium

Revision history for this message

Philip Kent (lsproc) wrote on 2007-07-27:

#5

I can confirm this on Ubuntu Gutsy, upgraded from Feisty. The X server will repeatedly flash, until I kill the virtual machine.

Revision history for this message

Elliot Hughes (elliot-hughes) wrote on 2007-07-27:

#6

HI, Thanks for your bug report.
I am confirming as all information has been made available.
Thanks again for reporting.

Changed in gdm:
status:	New → Confirmed

Revision history for this message

Philip Kent (lsproc) wrote on 2007-07-28:

#7

Signal 5 is a trace/breakpoint trap, if you did not know.

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-29:

#8

you've just confused me even more ;)

Revision history for this message

Philip Kent (lsproc) wrote on 2007-07-29:

#9

As far as I know, SIGTRAP means a point where the program expects a debugger to step in and help. Obviously, this is not the case, so the process dies.

Probably programming error, but dont quote me.

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-29:

#10

i wonder if any admins are going to look at this...

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-07-29:

#11

who are the admins you mention?

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-29:

#12

anyone :)

Revision history for this message

Philip Kent (lsproc) wrote on 2007-07-29:

#13

Generally its the developers who look into this :)

I think the Canonical admins have other things to do :)

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-29:

#14

sry, thats what i meant :P

Revision history for this message

Donnie Pennington (donniepennington) wrote on 2007-07-30:

#15

I just had the exact same thing happen as described in this bug.

Revision history for this message

Durand D'souza (durand1) wrote on 2007-07-30:

#16

I think its caused by gdm updates cos I only started getting this error after updating...

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-08-08:

#17

Do you have easy steps to trigger the bug?

Revision history for this message

Hew (hew) wrote on 2008-12-23:

#18

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in gdm:
status:	Confirmed → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-01-16:

#19

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gdm:
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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