xfce4-session crashed with SIGSEGV in g_slice_alloc()

Bug #1168239 reported by Václav Haisman
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xfce4-session (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After update from 12.10 to 13.04 beta.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xfce4-session 4.10.0-2ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 12 07:28:27 2013
ExecutablePath: /usr/bin/xfce4-session
InstallationDate: Installed on 2011-11-13 (515 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: xfce4-session
SegvAnalysis:
 Segfault happened at: 0x7fc180e55f7f <g_slice_alloc+223>: mov (%rbx),%rax
 PC (0x7fc180e55f7f) ok
 source "(%rbx)" (0xffffffff00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-session
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_array_sized_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: xfce4-session crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to raring on 2013-04-07 (4 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin netdev plugdev sambashare scanner tape vboxusers video

Revision history for this message
Václav Haisman (vzeman79) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xfce4-session (Ubuntu):
status: New → Confirmed
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.