Unity

unity/compiz crashed in dee_model_get_tag() from unity::dash::TextureContainer* unity::dash::RowAdaptorBase::renderer<unity::dash::TextureContainer*>() () from unity::dash::ResultRendererTile::Preload(unity::dash::Result&) () from /usr/lib/compiz/libunityshell.so

Bug #1010003 reported by JW
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Confirmed
Critical
Unassigned
dee
New
Critical
Unassigned
unity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Regularly (let's say once every day), unity and compiz crash.

Steps to reproduce:
1. Press the Window key.
2. Start typing, e.g. type "calculator"
3. The first two or three letters of the search term appear in the search box.
4. The screen freezes for about 10 seconds, then unity/compiz crashes.
5. Unity/compiz restarts, no windows were closed but everything is moved onto the first workspace.
6. apport appears offering to report the bug, but doing so appears to do nothing.

So, next to the crash I'm reporting (of which I don't know the root cause), apport doesn't seem to be reporting the error successfully. I send in the report, but afterwards nothing happens (I expected a browser window to pop up as described in https://help.ubuntu.com/community/ReportingBugs). I added the crash file I found in /var/crash here as an attachment manually.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.12-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
CheckboxSubmission: 60a1cbca22e9e051c51fe9ef4512b4a7
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
Date: Thu Jun 7 15:13:20 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
ProcEnviron:
 LANGUAGE=nl_BE:nl
 TERM=xterm
 PATH=(custom, user)
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
JW (jw-00000) wrote :
Daniel van Vugt (vanvugt)
summary: - unity/compiz crashes after entering search them in launcher
+ unity/compiz crashed in dee_model_get_tag() from
+ unity::dash::TextureContainer*
+ unity::dash::RowAdaptorBase::renderer<unity::dash::TextureContainer*>()
+ () from unity::dash::ResultRendererTile::Preload(unity::dash::Result&)
+ () from /usr/lib/compiz/libunityshell.so
Revision history for this message
Omer Akram (om26er) wrote :

instead of attaching the .crash file I would have preferred if you double clicked it and followed the onscreen instructions. that way launchpad can mark crash reports as duplicates and gives us a better picture of the issue.

Revision history for this message
JW (jw-00000) wrote :

@om26er: Sorry, but as I mentioned in my bug report, that doesn't seem to work.

If I try to report the bug using Apport, it asks me a few questions, but at the end no browser window pops up pointing to a bug report. That's why I created this bug manually.

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

@JW: Is it because that bug has already been reported? What does Apport say right at the end?

Bilal Akhtar (bilalakhtar)
Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The .crash file provides plenty of details including a full stack trace (search for "Stacktrace:").

Changed in unity:
status: Incomplete → Confirmed
Changed in unity (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Omer Akram (om26er) wrote :

but we still prefer a real crash report so that launchpad could do its voodoo and help us with finding duplicates.

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

OK, so as soon as a duplicate of this bug is reported via apport, we should make this a duplicate of that one. To help Launchpad do automatic de-duplication in future.

Revision history for this message
JW (jw-00000) wrote :

@Bilal (comment #4): the reason I didn't respond to your questions for such a long time, was because I was waiting for the crash to happen again so I could answer them. However, this bug hasn't appeared anymore since Saturday (while before it would happen at least once a day).

Maybe the bug was fixed? I installed updates on Friday, but there was no update for unity (maybe the update of libcairo2 and libcairo-gobject2 from 1.10.2-6.1ubuntu2 to 1.10.2-6.1ubuntu3 is related? Or ubuntuone-client 3.0.0-0ubuntu1 to 3.0.0-0ubuntu1.1?)

Also, I've been following bug #994921 (and just read #993450 and [1]), and it appears apport doesn't automatically file bug reports on Launchpad anymore. When I was still using the beta release of Precise, I got used to a browser window popping up right after I reported a crash, but it seems this doesn't happen anymore. As a user, I got no feedback on whether my crash report was sent in successfully or not. I assumed not, but maybe it did, and maybe the bug was already fixed by the time I filed this report manually? (It's still not entirely clear to me how the crash report system works, and what the relation is between apport, whoopsie, errors.ubuntu.com and Launchpad...)

[1] http://askubuntu.com/a/149455/4335

Marco Trevisan (Treviño) (3v1n0)
Changed in dee:
importance: Undecided → Critical
Changed in unity:
importance: Undecided → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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