gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new()

Bug #1194677 reported by Rainer Rohde
108
This bug affects 24 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Fix Released
Medium
Philip Langdale

Bug Description

This error popped up as soon as I clicked the unmount icon to remove the Nexus 4.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
Uname: Linux 3.9.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Tue Jun 25 17:30:29 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.4 /org/gtk/gvfs/exec_spaw/12
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0d40000078: add %dl,0x7f0d4002(%rip) # 0x7f0dbf0d4080
 PC (0x7f0d40000078) in non-executable VMA region: 0x7f0d40000000-0x7f0d40029000 rw-p None
 source "0x7f0dbf0d4080" (0x7f0dbf0d4080) not located in a known VMA region (needed readable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA None
 reading unknown VMA
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

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ptp_transaction_new (params=0x7f0d40007de0, ptp=0x7f0d4dbb6bd0, flags=<optimized out>, sendlen=0, handler=0x7f0d4dbb6b60) at ptp.c:152
 ptp_transaction (params=params@entry=0x7f0d40007de0, ptp=ptp@entry=0x7f0d4dbb6bd0, flags=flags@entry=2, sendlen=sendlen@entry=0, data=data@entry=0x7f0d4dbb6bc8, recvlen=recvlen@entry=0x7f0d4dbb6bc4) at ptp.c:400
 ptp_getstorageids (params=params@entry=0x7f0d40007de0, storageids=storageids@entry=0x7f0d4dbb6c40) at ptp.c:596
 LIBMTP_Get_Storage (device=device@entry=0x7f0d40007d60, sortby=sortby@entry=0) at libmtp.c:3960

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
summary: - gvfsd-mtp crashed with SIGSEGV in LIBMTP_Get_Storage()
+ gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
Philip Langdale (langdalepl) wrote :

Assuming that the clean shutdown fix in 1.17.3 addressed this. Unplug problems are unpredictable and hard to reproduce, so I want to clean the slate and only look at reports from new releases with that possible fix.

Changed in gvfs (Ubuntu):
assignee: nobody → Philip Langdale (langdalepl)
status: Confirmed → Fix Released
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.