compiz crashed with SIGSEGV on disconnecting external monitor

Bug #1247899 reported by joehill
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
Won't Fix
Medium
Unassigned
compiz (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I disconnected my laptop from a projector and compiz immediately crashed (then automatically restarted). This crash recurs often but not always under Saucy for me.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: compiz-core 1:0.9.10+13.10.20131011-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,resize,regex,imgpng,mousepoll,vpswitch,move,animation,place,grid,wall,unitymtgrabhandles,workarounds,session,wobbly,expo,ezoom,staticswitcher,fade,trailfocus,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Nov 4 09:50:53 2013
DistUpgraded: 2013-10-17 15:49:02,561 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:057d]
InstallationDate: Installed on 2012-09-24 (405 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: Dell Inc. Latitude E6430s
MarkForUpload: True
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=9f662ce4-0587-4b5a-88f5-8ef3d2b3c38d ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xba765c8: add %dl,0x7b(%edi)
 PC (0x0ba765c8) in non-executable VMA region: 0x0a00a000-0x0bbf2000 rw-p [heap]
 source "%dl" ok
 destination "0x7b(%edi)" (0xb1b82a4b) in non-writable VMA region: 0xb19af000-0xb1e1a000 r-xp /usr/lib/compiz/libunityshell.so
SegvReason:
 executing writable VMA [heap]
 writing VMA /usr/lib/compiz/libunityshell.so
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: compiz crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-10-17 (17 days ago)
UserGroups: adm audio cdrom dip lp lpadmin plugdev sambashare sudo
dmi.bios.date: 05/02/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0N9T9J
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/02/2012:svnDellInc.:pnLatitudeE6430s:pvr01:rvnDellInc.:rn0N9T9J:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6430s
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Sat Nov 2 15:55:03 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 830
 vendor LGD
xserver.version: 2:1.14.3-3ubuntu2

Revision history for this message
joehill (joseph-hill) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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 libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18
outdated debug symbol package for libindicator3-7: package version 12.10.2+13.10.20130913-0ubuntu2 dbgsym version 12.10.2+13.10.20130913-0ubuntu1
outdated debug symbol package for libunity-protocol-private0: package version 7.1.2+13.10.20131010-0ubuntu2 dbgsym version 7.1.2+13.10.20131010-0ubuntu1

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
Revision history for this message
joehill (joseph-hill) wrote :

Is there any way to report bugs when the debug symbol packages in the repository are out of date? Should I file a separate bug reporting that the debugging packages need to be updated?

Changed in compiz (Ubuntu):
status: Invalid → New
Revision history for this message
Stephen M. Webb (bregma) wrote :

I'm afraid the apport service is a little overenthusiastic about marking bugs as invalid on the slightest pretext. In this case, the debug packages you have are indeed out of date (you need to refresh them, it's not a bug), but irrelevant to the problem you encountered. The other unfortunate aspect is the backtrace really is unuseful for developers to analyze.

We'll queue this bug up for developers to try, since there is at least a test case attached.

information type: Private → Public
Changed in compiz (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in compiz:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Will Cooke (willcooke) wrote :

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 compiz:
status: Triaged → Won't Fix
Changed in compiz (Ubuntu):
status: Triaged → Won't Fix
tags: added: desktop-bugscrub-autoclosed
To post a comment you must log in.