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

Bug #1124978 reported by Francesco Astegiano
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
New
Medium
Unassigned

Bug Description

aste@envy:~$ lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
aste@envy:~$ apt-cache policy gdm
gdm:
  Installed: 3.6.1-0ubuntu3
  Candidate: 3.6.1-0ubuntu3
  Version table:
 *** 3.6.1-0ubuntu3 0
        500 http://ubuntu.fastbull.org/ubuntu/ raring/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gdm 3.6.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Thu Feb 14 09:29:33 2013
ExecutablePath: /usr/lib/gdm/gdm-simple-slave
InstallationDate: Installed on 2013-02-11 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130210)
MarkForUpload: True
ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe242819b09 <_IO_default_xsputn+249>: callq 0x7fe24282a340
 PC (0x7fe242819b09) ok
 source "0x7fe24282a340" (0x7fe24282a340) ok
 destination "(%rsp)" (0x7fffc9cc8000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gdm-simple-slave crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Francesco Astegiano (francesco-astegiano-7) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 _g_closure_invoke_va (closure=0x1831e80, return_value=0x0, instance=0x1816890, args=0x7fffc9cc8c98, n_params=0, param_types=0x0) at /build/buildd/glib2.0-2.35.7/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=0x1816890, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffc9cc8c98) at /build/buildd/glib2.0-2.35.7/./gobject/gsignal.c:3225
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.35.7/./gobject/gsignal.c:3370

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gdm (Ubuntu):
importance: Undecided → Medium
summary: - gdm-simple-slave crashed with SIGSEGV in g_signal_emit_valist()
+ gdm-simple-slave crashed with SIGSEGV in _g_closure_invoke_va()
tags: removed: need-amd64-retrace
information type: Private → Public
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.