gdm-simple-slave crashed with signal 5 in g_closure_invoke()

Bug #423123 reported by Dave Morley
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gdm

This bug is the result of trying to setup an end uesr on an oem install using a live ubuntu install cd dated 20090902

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 2 12:28:24 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
Package: gdm 2.27.90-0ubuntu1
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
Signal: 5
SourcePackage: gdm
StacktraceTop:
 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
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Title: gdm-simple-slave crashed with signal 5 in g_closure_invoke()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups:

Revision history for this message
Dave Morley (davmor2) wrote :
Dave Morley (davmor2)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__g_closure_invoke (closure=0xa5a450,
signal_emit_unlocked_R (node=0xa51920,
IA__g_signal_emit_valist (instance=0xa35ad0,
IA__g_signal_emit (instance=0x7f2b38b33e40,
greeter_server_message_handler (connection=0xa60a20,

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
Pedro Villavicencio (pedro) wrote :

Hello Dave, is this still an issue with latest package on Lucid?

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

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 (Ubuntu):
status: Incomplete → Invalid
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.