compiz crashed with signal 7 in g_settings_get_value() from g_settings_get_strv() from unity::dash::HomeLens::Impl::FindLensPriority() from unity::dash::HomeLens::Impl::EnsureCategoryAnnotation()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
High
|
Unassigned | ||
d-conf (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libunity-core-5.0-5 5.10.0-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 14 10:59:33 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321)
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 7
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: compiz crashed with signal 7
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm lpadmin sambashare sudo
summary: |
- compiz crashed with signal 7 + compiz crashed with signal 7 in g_settings_get_value() from + g_settings_get_strv() from + unity::dash::HomeLens::Impl::FindLensPriority() from + unity::dash::HomeLens::Impl::EnsureCategoryAnnotation() |
Changed in unity: | |
status: | New → Confirmed |
milestone: | none → 5.12.0 |
affects: | unity (Ubuntu) → d-conf (Ubuntu) |
Changed in unity (Ubuntu): | |
status: | New → Confirmed |
Changed in unity: | |
importance: | Undecided → High |
Changed in d-conf (Ubuntu): | |
importance: | Medium → High |
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
Changed in unity: | |
milestone: | 5.12.0 → 5.14.0 |
Changed in unity: | |
milestone: | 5.14.0 → 5.16.0 |
Changed in unity: | |
milestone: | 5.16.0 → 5.18.0 |
Changed in unity: | |
milestone: | 5.18.0 → 7.0.0 |
Changed in unity: | |
milestone: | 7.0.0 → 7.0.1 |
Changed in unity: | |
milestone: | 7.0.1 → 7.3.1 |
Changed in unity: | |
milestone: | 7.3.1 → 7.3.2 |
Changed in unity: | |
milestone: | 7.3.2 → 7.3.3 |
When I think about it, this problem also could have easily been caused by Bleachbit. Could any of the devs look into this?