unity-window-decorator crashed with SIGSEGV in g_slice_alloc()

Bug #877269 reported by Daniel Hahler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

It crashed when trying to configure two external monitors.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compiz-gnome 1:0.9.6+bzr20110929-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Oct 18 11:38:36 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-window-decorator
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: /usr/bin/unity-window-decorator
ProcEnviron:
 LANGUAGE=en_US:en
 LC_TIME=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0xb6dc19cd <g_slice_alloc+269>: mov (%edi),%edx
 PC (0xb6dc19cd) ok
 source "(%edi)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gdk_event_new () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
Title: unity-window-decorator crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to oneiric on 2011-09-29 (18 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
Daniel Hahler (blueyed) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #741395, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.