gdm-simple-slave crashed with SIGSEGV in g_main_dispatch()

Bug #477724 reported by Håvard Berland
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: gdm

This (automatic) bug report is to be considered a follow up to the report for bug

https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/471282

ProblemType: Crash
Architecture: amd64
Date: Fri Nov 6 19:28:15 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: gdm 2.28.1-0ubuntu1
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x416293: mov 0x8(%rax),%ecx
 PC (0x00416293) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ?? ()
 ?? ()
 g_main_dispatch (context=0xfad6d0)
 IA__g_main_context_dispatch (context=0xfad6d0)
 g_main_context_iterate (context=0xfad6d0,
Title: gdm-simple-slave crashed with SIGSEGV in g_main_dispatch()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

XsessionErrors: (polkit-gnome-authentication-agent-1:2193): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Håvard Berland (berland) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gdm_slave_connect_to_x11_display (slave=0xfb9010) at gdm-slave.c:391
idle_connect_to_display (slave=0xfb9010)
g_main_context_dispatch ()
?? () from /lib/libglib-2.0.so.0
g_main_loop_run () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gdm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Håvard Berland (berland) wrote :

I did a clean reinstall of Ubuntu 9.10 32-bit on the same machine. On the tenth reboot (after setting up stuff), gdm started to crash again, meaning this issue has nothing to do with 32-bit or 64-bit. No particular action before last reboot before crash that I can correlate to gdm crashing.

visibility: private → public
Revision history for this message
Manoel Luis Fr.Belem (mlbelem) wrote :

no comments

Revision history for this message
Gergely Mészáros (meszaros-gergely) wrote :

Same problem here. Karmic 32 bit, nvidia-185, gdm 2.28.1 and massive crashes at gdm starts.
Starting by hand (startx/startxfce) works nicely. Compositing is working perfectly. Seems to be gdm specific.
(dual screen config in case if it matters)

Revision history for this message
Gergely Mészáros (meszaros-gergely) wrote :

Same problem here. Karmic 32 bit, nvidia-185, gdm 2.28.1 and massive crashes at gdm starts.
Starting by hand (startx/startxfce) works nicely. Compositing is working perfectly. Seems to be gdm specific.
(dual screen config in case if it matters)

Revision history for this message
derVerzweifler (derverzweifler) wrote :

Same problem here, but

VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]

and Karmic 32 bit.
GDM crashes but startx ist still working.

Revision history for this message
Ludwin Janvier (lud-janvier) wrote :

After karmic to lucid upgrade, I have the same bug. startx and kdm are working fine. Changed my card from nvidia to ATI and get the same problem.

Revision history for this message
Håvard Berland (berland) wrote :

Bug confirmed for Lucid here as well. kdm workaround works. Immediate symptoms are changed in that you now get a message that Ubuntu is booting in low resolution instead of an all black screen (but I cannot get into a desktop nevertheless).

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

Changed in gdm (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in gdm (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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