compiz crashed with SIGSEGV in dee_model_get_tag()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Possibly a duplicate of bug #840758
Compiz died and came back to life (with my applications all on the wrong workspaces) when I was viewing my installed applications in the unity application launcher (not sure what it's called).
Description: Ubuntu oneiric (development branch)
Release: 11.10
unity:
Installed: 4.16.0-0ubuntu1
Candidate: 4.16.0-0ubuntu1
Version table:
*** 4.16.0-0ubuntu1 0
500 http://
100 /var/lib/
compiz:
Installed: 1:0.9.5.
Candidate: 1:0.9.5.
Version table:
*** 1:0.9.5.
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.16.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.0.0-11-generic i686
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CheckboxSubmission: 4f5564c50a42755
CheckboxSystem: b845c366ea09c60
Date: Mon Sep 19 18:04:51 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, user)
LANG=en_HK.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x856c969: mov (%edx),%edx
PC (0x0856c969) ok
source "(%edx)" (0x00000006) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
dee_model_get_tag () from /usr/lib/
?? () from /usr/lib/
dee_model_get_tag () from /usr/lib/
Title: compiz crashed with SIGSEGV in dee_model_get_tag()
UpgradeStatus: Upgraded to oneiric on 2011-09-17 (2 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin mythtv netdev plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #840758, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.