unity-applications-daemon crashed with SIGSEGV in g_closure_invoke()

Bug #928020 reported by Jason Warner on 2012-02-07
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-lens-applications (Ubuntu)
Undecided
Unassigned

Bug Description

random crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-applications 5.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Feb 7 14:19:52 2012
ExecutablePath: /usr/lib/unity-lens-applications/unity-applications-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/unity-lens-applications/unity-applications-daemon
SegvAnalysis:
 Segfault happened at: 0x7fe3e96c0c78: mov 0x0(%rbp,%r14,8),%rdi
 PC (0x7fe3e96c0c78) ok
 source "0x0(%rbp,%r14,8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-lens-applications
StacktraceTop:
 ?? () from /usr/lib/libdee-1.0.so.4
 ?? () from /usr/lib/libdee-1.0.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-applications-daemon crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-02-01 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Jason Warner (jasoncwarner) wrote :
visibility: private → public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-lens-applications (Ubuntu):
status: New → Confirmed

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 #916356, 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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers