gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()

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

Bug Description

gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
Uname: Linux 3.9.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Fri Jul 12 11:39:51 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-06-11 (30 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.5 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fcf54000078: lock and $0x7fcf5402,%eax
 PC (0x7fcf54000078) in non-executable VMA region: 0x7fcf54000000-0x7fcf54029000 rw-p None
 source "$0x7fcf5402" ok
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: executing writable VMA None
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Get_Storage () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
howefield (howefield) 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 #1202188, 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.

information type: 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.