Ubuntu
gnome-session package

gnome-session crashed with SIGSEGV in g_main_context_dispatch()

Bug #432541 reported by Vlad
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gnome-session

none

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Sep 18 13:02:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-session
NonfreeKernelModules: fglrx
Package: gnome-session-bin 2.27.92-0ubuntu2
ProcCmdline: gnome-session
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
 Segfault happened at: 0x805a033 <gtk_tree_model_iter_n_children@plt+35051>: mov 0x8(%eax),%eax
 PC (0x0805a033) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
Title: gnome-session crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

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

StacktraceTop:gsm_consolekit_attempt_stop (manager=0x88e4e40)
end_phase (manager=<value optimized out>)
on_phase_timeout (manager=0x8906428) at gsm-manager.c:547
g_timeout_dispatch (source=0x88e14f0, callback=0,
IA__g_main_context_dispatch (context=0x88d0b80)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gnome-session (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Sebastien Bacher (seb128)
visibility: private → public
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The new 2.28.0 upstream tarball that was just uploaded already contains a fix for this one: http://git.gnome.org/cgit/gnome-session/commit/?id=50ba8e6b979989723afd2b932dd1334727eabea5

Changed in gnome-session (Ubuntu):
status: New → Fix Released
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.