gvfsd-fuse crashed with SIGSEGV in g_object_new_valist()

Bug #1054886 reported by Swâmi Petaramesh
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Something looks broke with bluetooth...

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.13.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CheckboxSubmission: 1ea6109db29b53f721a523a77b7f3abf
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Sun Sep 23 09:32:47 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-fuse
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
SegvAnalysis:
 Segfault happened at: 0x7f2e64bd4778: mov 0x8(%r12),%r15
 PC (0x7f2e64bd4778) ok
 source "0x8(%r12)" (0xfe5cb0005970) not located in a known VMA region (needed readable region)!
 destination "%r15" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_themed_icon_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-fuse crashed with SIGSEGV in g_object_new_valist()
UpgradeStatus: Upgraded to quantal on 2012-08-28 (26 days ago)
UserGroups: adm debian-tor disk fax fuse lp lpadmin plugdev scanner sudo vboxusers

Revision history for this message
Swâmi Petaramesh (swami-petaramesh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1054075, 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
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.