unity-applications-daemon crashed with SIGSEGV in g_closure_invoke()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-lens-applications (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
After finishing a failed upgrade (virtual machine was unresponsive and a soft reset was done), I restarted the VM, then ran sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade, everything updated successfully, I exited the terminal, stepped away from my desk for 10 minutes and the crash occured during that time. No applications were running and the machine was pretty much idle.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-
ProcVersionSign
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 26 11:03:33 2012
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_ZA:en
LANG=en_ZA.UTF-8
SegvAnalysis:
Segfault happened at: 0x7ff44fcb3d3b: mov (%rdx),%eax
PC (0x7ff44fcb3d3b) ok
source "(%rdx)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-
StacktraceTop:
?? () from /lib/x86_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: unity-applicati
UpgradeStatus: Upgraded to precise on 2012-01-26 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Bruce Pieterse (octoquad) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-amd64-retrace |
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 #917194, 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.