compiz crashed with SIGSEGV

Bug #980879 reported by Uxío Fernández
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading several packages, including the driver nvidia video card, compiz is closed with an error on login.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 13 16:49:36 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f03b214c7e5: mov (%rsi),%rax
 PC (0x7f03b214c7e5) ok
 source "(%rsi)" (0x7f038c369000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.40
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Uxío Fernández (uxiofp) wrote :
description: updated
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _wordcopy_fwd_aligned (dstp=33059968, srcp=139653214015488, len=640) at wordcopy.c:80
 ?? ()
 ?? ()
 ?? ()
 ?? ()

affects: ubuntu → unity (Ubuntu)
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (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:

compiz version 1:0.9.7.4-0ubuntu3 required, but 1:0.9.7.6-0ubuntu1 is available
libnux-2.0-common version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
unity-common version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu3 is available
nux-tools version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
outdated debug symbol package for nux-tools: package version 2.10.0-0ubuntu1 dbgsym version 2.8.0-0ubuntu2
unity-services version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu3 is available
outdated debug symbol package for unity-services: package version 5.10.0-0ubuntu3 dbgsym version 5.8.0-0ubuntu2
libunity-core-5.0-5 version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu3 is available
outdated debug symbol package for libunity-core-5.0-5: package version 5.10.0-0ubuntu3 dbgsym version 5.8.0-0ubuntu2
unity version 5.8.0-0ubuntu2 required, but 5.10.0-0ubuntu3 is available
outdated debug symbol package for unity: package version 5.10.0-0ubuntu3 dbgsym version 5.8.0-0ubuntu2
libnux-2.0-0 version 2.8.0-0ubuntu2 required, but 2.10.0-0ubuntu1 is available
outdated debug symbol package for libnux-2.0-0: package version 2.10.0-0ubuntu1 dbgsym version 2.8.0-0ubuntu2
outdated debug symbol package for libgconf2-4: package version 3.2.5-0ubuntu2 dbgsym version 3.2.3-0ubuntu0.1

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-amd64-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 980298, so it 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. Feel free to continue to report any other bugs you may find.

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.