Ubuntu
compiz package

compiz crashed with SIGSEGV after selecting 'KDE compaitibility' in CCSM, while running Unity

Bug #1059347 reported by Edward Donovan on 2012-10-01

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	compiz (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

This was reported as bug 1059218, but no crash data was uploaded there. I can confirm the crash, so I"m filing this, and duping that bug here.

Perhaps checking 'KDE Compatibility' falls under the 'CCSM may break your system' warning. An immediate crash seems severe. :) But, if no better is expected, this can be marked invalid. Thanks.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.2+bzr3377-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.15-lowlatency 3.5.4
Uname: Linux 3.5.0-16-lowlatency x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Sun Sep 30 21:56:09 2012
Disassembly: => 0x7f0d8ae92460: Cannot access memory at address 0x7f0d8ae92460
DistUpgraded: 2012-06-14 12:52:30,002 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
MachineType: System manufacturer System Product Name
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-lowlatency root=UUID=779b6708-eeec-4cc0-9701-d76b020f7ffb ro splash quiet irqfixup vt.handoff=7
SegvAnalysis:
Segfault happened at: 0x7f0d8ae92460: Cannot access memory at address 0x7f0d8ae92460
PC (0x7f0d8ae92460) ok
SP (0x7fff51914928) ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: compiz
Stacktrace:
#0 0x00007f0d8ae92460 in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
StacktraceTop:
?? ()
?? ()
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-06-14 (108 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo
dmi.bios.date: 03/26/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/26/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39+git20120918.2426a6a7-0ubuntu0ricotz2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.1~git20120927.6d6aef79-0ubuntu0ricotz
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.1~git20120927.6d6aef79-0ubuntu0ricotz
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu2

Tags:

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-10-01:

BootDmesg.txt Edit (71.7 KiB, text/plain; charset="utf-8")
BootLog.txt Edit (2.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (2.9 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (39.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (848 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (123.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (824 bytes, text/plain; charset="utf-8")
Registers.txt Edit (665 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.7 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (181.0 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (399.2 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (616 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (59.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (78.2 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (8.5 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (261.8 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (13.4 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-10-01:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in compiz (Ubuntu):
status:	New → Confirmed

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-01:

Stacktrace:
#0 0x00007f0d8ae92460 in ?? ()
No symbol table info available.
#1 0x0000000000000000 in ?? ()
No symbol table info available.
StacktraceSource:
#0 0x00007f0d8ae92460 in ?? ()
#1 0x0000000000000000 in ?? ()
StacktraceTop:
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-01: ThreadStacktrace.txt

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

Changed in compiz (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2012-10-01: 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:

libglapi-mesa version 9.1~git20120927.6d6aef79-0ubuntu0ricotz required, but 9.0~git20120917.7cfd42ce-0ubuntu3 is available
libdrm-nouveau2 version 2.4.39+git20120918.2426a6a7-0ubuntu0ricotz2 required, but 2.4.39-0ubuntu1 is available
libdrm-intel1 version 2.4.39+git20120918.2426a6a7-0ubuntu0ricotz2 required, but 2.4.39-0ubuntu1 is available
libcairo2 version 1.12.3+git20120608.f228769d-0ubuntu0ricotz~quantal0 required, but 1.12.2-1ubuntu2 is available
libgl1-mesa-dri version 9.1~git20120927.6d6aef79-0ubuntu0ricotz required, but 9.0~git20120917.7cfd42ce-0ubuntu3 is available
libgl1-mesa-glx version 9.1~git20120927.6d6aef79-0ubuntu0ricotz required, but 9.0~git20120917.7cfd42ce-0ubuntu3 is available
libdrm-radeon1 version 2.4.39+git20120918.2426a6a7-0ubuntu0ricotz2 required, but 2.4.39-0ubuntu1 is available
outdated debug symbol package for libtxc-dxtn-s2tc0: package version 0~git20110809-3 dbgsym version 0~git20110809-2.1
libdrm2 version 2.4.39+git20120918.2426a6a7-0ubuntu0ricotz2 required, but 2.4.39-0ubuntu1 is available
outdated debug symbol package for libstdc++6: package version 4.7.2-2ubuntu1 dbgsym version 4.6.3-1ubuntu5

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

Marius B. Kotsbak (mariusko) wrote on 2012-10-01:

Did you update all packages first?

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-10-01:

Ah, I see I actually have some versions that are too new. I was running xorg-edgers PPA for a while, and I guess the PPA purge that I did wasn't good enough. It would be good if one of us generated a good crash report; I'll see if I can tomorrow.

Since this didn't work, I'll undupe your report; at least until we get a core dump to trace. I do think these crashes are best assigned to compiz, not Unity, so I'll change the assignement on that. Thanks.

Revision history for this message

Marius B. Kotsbak (mariusko) wrote on 2012-10-01:

I can try again. The strange thing was that the apport reporter did not appear. Do you have a trick for getting the stracktrace added here after the crash?

Revision history for this message

Edward Donovan (edward.donovan) wrote on 2012-10-03:

I don't know, Marius, it just came up for me, as usual. Compiz was gone, and I did have to click 'Relaunch' on the apport window, to get a window manager again. But it sounds like you didn't even get to that point. I guess you could check whether you have a

~/.apport-ignore

file, just in case.

I haven't had an opportunity yet where I'm free to crash my desktop session, again. But hopefully soon.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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

Ubuntucompiz package

compiz crashed with SIGSEGV after selecting 'KDE compaitibility' in CCSM, while running Unity

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
compiz package