Ubuntu
nux package

compiz crashed with SIGSEGV

Bug #957917 reported by josthohad on 2012-03-17

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Nux	Won't Fix	Undecided	Unassigned
	nux (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

12.04 beta 1

really not mutch to say it crashes sometimes, but i can't relate the crashes to eatchother. it might be the configuaration of compiz?

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 17 14:50:17 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: compiz
ProcEnviron:
LANG=da_DK.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0c31546ec3: movslq 0x314,%rax
PC (0x7f0c31546ec3) ok
source "0x314" (0x00000314) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.20
?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.20
?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.20
?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.20
?? () from /usr/lib/nvidia-current-updates/libnvidia-glcore.so.295.20
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-15 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

josthohad (johannes-t-hadsund) wrote on 2012-03-17:

#1

CoreDump.gz Edit (6.1 MiB, application/x-gzip)
Dependencies.txt Edit (1.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (641 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (79.9 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (815 bytes, text/plain; charset="utf-8")
Registers.txt Edit (777 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (7.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (10.0 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (79.2 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-17:

#2

StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-17: Stacktrace.txt

#3

Stacktrace.txt Edit (1.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-17: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (8.0 KiB, text/plain)

tags:	added: apport-failed-retrace
tags:	removed: need-amd64-retrace

Revision history for this message

Will Cooke (willcooke) wrote on 2015-09-16:

#5

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in nux:
status:	New → Won't Fix
Changed in nux (Ubuntu):
status:	New → Won't Fix
tags:	added: desktop-bugscrub-autoclosed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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