compiz crashed with SIGSEGV

Bug #981907 reported by Hugo Venhorst
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

i made a manual bug report about this earlier, see Bug #981737

this time, the system picked up on the crash and offered to report.
this automated bug report might contain more useful information

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.10.0-0ubuntu3
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-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 14 23:06:53 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120209)
ProcCmdline: compiz --replace
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa6631917c8: mov (%rsi),%rcx
 PC (0x7fa6631917c8) ok
 source "(%rsi)" (0x7fa63e0b0000) not located in a known VMA region (needed readable region)!
 destination "%rcx" 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/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.295.40
 ?? () from /usr/lib/nvidia-current/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
Hugo Venhorst (yougo) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _wordcopy_fwd_aligned (dstp=63906672, srcp=140351982206976, len=687) at wordcopy.c:71
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 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:

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
Hugo Venhorst (yougo) wrote :

well, that's nice. rendered invalid on some sort of technicality?! :-/

my system is very much up to date, compiz still craps out on me, no new crash alert pops up, so i can't file a new bug.
i tried purging compiz and unity and reinstalling them but it stays broken.

is there anyone out there that can tell me what to do to get the right info up here, and compiz fixed?

Revision history for this message
Hugo Venhorst (yougo) wrote :

this forum thread talks about the issue:

http://ubuntuforums.org/showthread.php?t=1957518&page=4

the thread mentioned the following bugs:
980672
980298

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.