unity-applications-daemon crashed with SIGSEGV in dee_model_remove()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-lens-applications (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Right after starting my old Pentium 4 (waited until indicators where loaded) I pressed the SUPER key to open the Dash and search for the update-manager by typing 'upd'. The Dash did not react correctly, it showed as first menu entry the system monitor and as second the update-manager. I added an 'a' to the 'upd' = nothing changed. Then I deleted all text and wrote 'update', it showed the 'update-manager' as first entry but I could not launch it by pressing ENTER - so I closed the Dash. Then the error message popped up.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.94-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Mar 3 11:50:37 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120227)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x631978: mov (%edi,%esi,4),%eax
PC (0x00631978) ok
source "(%edi,%esi,4)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
dee_model_remove () from /usr/lib/
?? () from /usr/lib/
dee_model_remove () from /usr/lib/
Title: unity-applicati
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #939383, 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.