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

Bug #931729 reported by Martin Lindhe on 2012-02-13
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-lens-files (Ubuntu)
Undecided
Unassigned

Bug Description

after installing and launching a wine app, sqlyog, from http://code.google.com/p/sqlyog/

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-lens-files 5.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Mon Feb 13 22:47:23 2012
ExecutablePath: /usr/lib/unity-lens-files/unity-files-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120212)
ProcCmdline: /usr/lib/unity-lens-files/unity-files-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa9f61f8130: cmp %rdi,0x18(%rdx)
 PC (0x7fa9f61f8130) ok
 source "%rdi" ok
 destination "0x18(%rdx)" (0x00000017) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-lens-files
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () 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-files-daemon crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Martin Lindhe (martinlindhe) wrote :

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

visibility: private → public
visibility: private → public
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