unity-applications-daemon crashed with SIGSEGV in g_variant_type_info_get_type_string()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-lens-applications (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) Ubuntu 12.04 LTS
2) unity-lens-
Installed: 5.6.0-0ubuntu1
Candidate: 5.6.0-0ubuntu1
Version table:
*** 5.6.0-0ubuntu1 0
3) Clicking on lens, and sorting through categories to find an application.
4) Received an error that stated there was a problem. Also, clicking on specific categories, such as "office", did not sort the applications. Clicking on the category lens did not do anything. All applications still showed up on my screen. This occurs on and off while using Unity.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-
ProcVersionSign
Uname: Linux 3.2.0-18-generic i686
NonfreeKernelMo
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sat Mar 17 04:29:57 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x4cf37e: movzbl 0x4(%eax),%edx
PC (0x004cf37e) ok
source "0x4(%eax)" (0x675f5f04) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-lens-
StacktraceTop:
?? () from /lib/i386-
g_variant_
g_variant_get_type () from /lib/i386-
?? () from /usr/lib/
?? () from /usr/lib/
Title: unity-applicati
UpgradeStatus: Upgraded to precise on 2012-03-15 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #953978, 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.