Ubuntu
gdm package

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

Bug #413767 reported by norbulinux
216
This bug affects 42 people
Affects Status Importance Assigned to Milestone
gdm
Expired
Critical
gdm (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: gdm

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

ProblemType: Crash
Architecture: i386
Date: Fri Aug 14 21:12:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
Package: gdm 2.27.4-0ubuntu11
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
ProcEnviron:
 PATH=(custom, no user)
 LANG=ca_ES.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x8058015 <endutxent@plt+43165>: movzbl 0x30(%eax),%eax
 PC (0x08058015) ok
 source "0x30(%eax)" (0xaaaaaada) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID(int0_t) ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gdm-simple-slave crashed with SIGSEGV in g_cclosure_marshal_VOID()
Uname: Linux 2.6.31-5-generic i686
UserGroups:

Revision history for this message
norbulinux (norbulinux) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:worker_exited (job=0x9744aa0, code=1, session=0x9763c00)
IA__g_cclosure_marshal_VOID__INT (closure=0x97657e8,
IA__g_closure_invoke (closure=0x97657e8, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,
IA__g_signal_emit_valist (instance=0x9744aa0, signal_id=54,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gdm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Rolf Leggewie (r0lf)
Changed in gdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue is similar to bug #413974

visibility: private → public
Changed in gdm (Ubuntu):
status: Confirmed → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gdm:
status: Unknown → New
Sebastien Bacher (seb128)
Changed in gdm (Ubuntu):
milestone: none → ubuntu-9.10
Sebastien Bacher (seb128)
Changed in gdm (Ubuntu):
milestone: ubuntu-9.10 → none
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
assignee: Ubuntu Desktop Bugs (desktop-bugs) → Robert Ancell (robert-ancell)
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug seems to get quite some duplicates, it's not clear if that's a crash on reboot in which case a non issue or something which can lead to close running session though, Robert could you have a look to this one, if it's crashing session we should consider a karmic update to fix the issue

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

the comments in duplicate are not really angry ones which would suggest nobody got its session closed with work open or that sort of issues, could just be a restart case caught by apport which will not run on stable

Revision history for this message
BrokenWiz (giuliett) wrote :

in my case it got solved with 9.10 release of 2009-10-29

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

is anybody still getting this issue?

Changed in gdm (Ubuntu):
assignee: Robert Ancell (robert-ancell) → nobody
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now

Changed in gdm (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

wrong bug...

Changed in gdm (Ubuntu):
status: Fix Committed → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gdm:
status: New → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in gdm:
importance: Unknown → Critical
Bug Watch Updater (bug-watch-updater)
Changed in gdm:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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