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

Bug #431852 reported by Tommi Saira
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Undecided
Unassigned

Bug Description

I was installing some sowtfare when ubuntu crashed and goed pack to login screen (gdm). My computer is acers aspire one aoa110 and i ubraged to 9.10 from 9.04.

ProblemType: Crash
Architecture: i386
Date: Thu Sep 17 15:11:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
Package: gdm 2.27.90-0ubuntu6
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
ProcEnviron:
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x8058065 <endutxent@plt+43229>: movzbl 0x30(%eax),%eax
 PC (0x08058065) 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-10-generic i686
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #413767, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.