gvfsd-fuse crashed with SIGSEGV in g_object_new_valist()

Bug #1059045 reported by LAva
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I just attached my Samsung Galaxy Nexus per USB (MTP was activated on the device).
Then the gvfs crashed.

I did not browse or do anything with it, I just activated the USB tethering.

When the "What to do with this device" dialog appeared, I just closed it without choosing anything.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gvfs-fuse 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 30 15:08:31 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-fuse
ProcCmdline: /usr/lib/gvfs//gvfsd-fuse -f /home/username/.gvfs
SegvAnalysis:
 Segfault happened at: 0x7f68eb6fc778: mov 0x8(%r12),%r15
 PC (0x7f68eb6fc778) ok
 source "0x8(%r12)" (0xfed1b00053a0) 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_icon_new_for_string () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-fuse crashed with SIGSEGV in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
LAva (lavalanche) 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.