compiz crashed with SIGSEGV

Bug #920945 reported by Michael Zywek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
uname -a
Linux r8-xubu-1204 3.2.0-10-generic-pae #17-Ubuntu SMP Thu Jan 19 20:56:14 UTC 2012 i686 i686 i386 GNU/Linux

Bug-information appeared after booting. I had no windowmanager (application-windows without frame and minimize-maximize-close-buttons). And the keyboard was dead - no reaction when typing.

I pressed the launching-switch of my computer some seconds, rebooted and everything worked fine - except openshot, but that's another story.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.6+bzr20110929-0ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Jan 24 13:06:06 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: compiz --replace --sm-disable --ignore-desktop-hints ccp
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb60d1e8c: mov (%esi),%edi
 PC (0xb60d1e8c) ok
 source "(%esi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
Stacktrace:
 #0 0xb60d1e8c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x44834004
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 0xb6748880 (LWP 2069)):
 #0 0xb60d1e8c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x44834004
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2011-12-13 (41 days ago)
UserGroups: adm audio cdrom dip lightdm lpadmin netdev plugdev sambashare scanner sudo vboxusers video

Revision history for this message
Michael Zywek (mzpc) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb60d1e8c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x44834004
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 0xb6748880 (LWP 2069)):
 #0 0xb60d1e8c in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x44834004

Changed in compiz (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libx11-xcb1 version 2:1.4.4-4 required, but 2:1.4.99.1-0ubuntu1 is available
libgtk-3-common version 3.3.8-0ubuntu2 required, but 3.3.10-0ubuntu1 is available
libxi6 version 2:1.4.3-3ubuntu1 required, but 2:1.5.99.2-0ubuntu3 is available
x11-common version 1:7.6+7ubuntu7 required, but 1:7.6+10ubuntu1 is available
libx11-data version 2:1.4.4-4 required, but 2:1.4.99.1-0ubuntu1 is available
libgtk-3-0 version 3.3.8-0ubuntu2 required, but 3.3.10-0ubuntu1 is available
libx11-6 version 2:1.4.4-4 required, but 2:1.4.99.1-0ubuntu1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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.