compiz crashed with SIGSEGV in unity::indicator::DBusIndicators::Impl::RequestSyncAll()

Bug #913147 reported by Jack Leigh
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash occurred when trying to set up a second monitor

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libunity-core-4.0-4 4.24.0-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.0.0-15.25-generic-pae 3.0.13
Uname: Linux 3.0.0-15-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sat Jan 7 15:05:07 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0xb44850f8 <_ZN5unity9indicator14DBusIndicators4Impl14RequestSyncAllEv+120>: mov %eax,0x4(%edx)
 PC (0xb44850f8) ok
 source "%eax" ok
 destination "0x4(%edx)" (0xb7227d64) in non-writable VMA region: 0xb7226000-0xb722a000 r-xp /usr/lib/libsigc-2.0.so.0.0.0
SegvReason: writing VMA /usr/lib/libsigc-2.0.so.0.0.0
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity::indicator::DBusIndicators::Impl::RequestSyncAll() () from /usr/lib/libunity-core-4.0.so.4
 unity::indicator::DBusIndicators::Impl::OnRemoteProxyReady(_GDBusProxy*) () from /usr/lib/libunity-core-4.0.so.4
 ?? () from /usr/lib/libunity-core-4.0.so.4
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: compiz crashed with SIGSEGV in unity::indicator::DBusIndicators::Impl::RequestSyncAll()
UpgradeStatus: Upgraded to oneiric on 2011-09-22 (107 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

Revision history for this message
Jack Leigh (leighman) wrote :
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 this software better. This particular crash has already been reported and is a duplicate of bug #910175, 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.