compiz crashed while xbmc [unredirected fullscreen window] was running and notify-osd poped up.

Bug #1070201 reported by Achim
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I was in xbmc while notify-osd poped up. The windows where flickering and compiz/unity was not running any more.
But after a view seconds compiz/unity recovered itself from the crash.

In general "unredirect fullscreen windows" is working very well for me.
I am not sure but this also may be a driver issue.

Kernel and video driver in ubuntu are both not up to date, in comparison to upstream.
If you need more information please let me know.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz 1:0.9.8.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Tue Oct 23 08:42:11 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2034]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=022ced93-aaf6-4492-82df-8ba5daa9cbbd ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KCH7710H.86A.0100.2012.0906.1136
dmi.board.name: DH77DF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG40293-300
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrKCH7710H.86A.0100.2012.0906.1136:bd09/06/2012:svn:pn:pvr:rvnIntelCorporation:rnDH77DF:rvrAAG40293-300:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.8.4-0ubuntu3
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
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-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

Revision history for this message
Achim (ach1m) wrote :
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. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in compiz (Ubuntu):
status: New → Incomplete
Revision history for this message
Achim (ach1m) wrote :

Daniel, I am sorry but it seems apport doesn't like to upload the crash report.
It asks me If I would like to send an error-report but then nothing happens.
Does it make sense If I attach the crash-file directly to this bug-report?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, the crash file *sometimes* contains a usable trace. Please attach it in case.

Revision history for this message
Achim (ach1m) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
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.