Ubuntu
gdm package

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

Bug #413974 reported by Pavel Kukacka on 2009-08-15

This bug report is a duplicate of: Bug #413767: gdm-simple-slave crashed with SIGSEGV in g_cclosure_marshal_VOID(). Edit Remove

This bug affects 10 people

Affects		Status	Importance	Assigned to	Milestone
	gdm	New	Unknown	gnome-bugs #592205
	gdm (Ubuntu)	Triaged	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

crashed soon after startup (of GNOME).

ProblemType: Crash
Architecture: amd64
Date: Sat Aug 15 11:16:19 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:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
Segfault happened at: 0x41110c <dbus_message_append_args@plt+39820>: movzbl 0x5c(%rax),%eax
PC (0x0041110c) ok
source "0x5c(%rax)" (0xaaaaaaaaaaaaab06) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
?? ()
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: gdm-simple-slave crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: users

Tags:

Revision history for this message

Pavel Kukacka (pavel-kukacka) wrote on 2009-08-15:

Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (14.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (727 bytes, text/plain; charset="utf-8")
Registers.txt Edit (956 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (924 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (950 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-15: Stacktrace.txt (retraced)

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

StacktraceTop:worker_exited (job=<value optimized out>, code=1,
IA__g_closure_invoke (closure=0x188f670,
signal_emit_unlocked_R (node=0x1892ba0,
IA__g_signal_emit_valist (instance=0x1893000,
IA__g_signal_emit (instance=0x7ffd583cbe40,

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-15: ThreadStacktrace.txt (retraced)

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

Changed in gdm (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2009-08-18:

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=592205