Compiz closed unexpectedly

Bug #1044813 reported by Akhila
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Compiz closed unexpectedly and apport failed to report the same problem twice. Screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8+bzr3319-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic i686
ApportVersion: 2.5.1-0ubuntu4
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sun Sep 2 00:51:17 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120901)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=e253f238-8803-49d8-9c80-2f44c7a25fcb ro quiet splash vt.handoff=7
SourcePackage: compiz
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu3
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
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~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

Revision history for this message
Akhila (akhilahegde) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1044813

tags: added: iso-testing
tags: added: compiz-0.9
Revision history for this message
Sasa Paporovic (melchiaros) wrote :

There is no reporting problem with apport.

Apport reject reports on developer versions when your system is not upgraded to the latest packages.

When you start a Ubuntu run the first thing you should do is to open a terminal and run:

sudo apt-get update

and then

sudo apt-get dist-upgrade

the last line also upgrades the core components like the kernel itself.

When a new kernel is installed make a newstart, when only compiz and unity upgrades are there a new llogin should be enough, but a newstart is more clean.

So, what you describe is a worksform problem.

Sorry, that I tell it the hard way, but I close this ticket here.

Anyway, thank you for reporting. Please incorporate the describded above and do bughunting further.

greetings

melchiaros

Changed in compiz (Ubuntu):
status: New → Invalid
Revision history for this message
Akhila (akhilahegde) wrote :

I'm very much on the learning curve. So every little input matters to me, whether said the hard way or soft :). Thanks for the info. But to keep you informed, I've been executing the same testcase for past couple of days with same images and updated builds. I was doing the job like I did everyday. But the response was different, output was different. Testcase in the scene requires me to do just sudo apt-get update. I did that yesterday as well. Even then, there was this compiz core problem. I've filed couple of bugs to be familiar enough with apport. The way it responded yesterday was totally new to me as I hadn't experienced any problem with apport thus far. It's known that changes are happening with Quantal. There's a fair possibility that a change impacts something which was previously working fine. That was the sole reason for filing the bug.

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.