gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new() (when plugging in android phone via USB port)

Bug #1229875 reported by Cavsfan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
New
Medium
Unassigned

Bug Description

On Saucy: I got this error when I plugged in my andriod phone into a USB port.
It gave a different error message but is the exact same problem that happened when I did it before and this bug was filed:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1227770

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gvfs-backends 1.17.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 24 13:54:21 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-06-30 (85 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130630)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa22802ddd0: add %al,(%rax)
 PC (0x7fa22802ddd0) in non-executable VMA region: 0x7fa228000000-0x7fa22802f000 rw-p None
 source "%al" ok
 destination "(%rax)" (0x00007fa2) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA None
 writing NULL 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
Cavsfan (cavsfan) wrote :
information type: Private → Private Security
Revision history for this message
Cavsfan (cavsfan) wrote :

Not sure what to set the privacy to.

Revision history for this message
Cavsfan (cavsfan) wrote :

Please change the privacy setting if necessary.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ptp_transaction_new (params=0x7fa228000078, ptp=0x7fa237d34bd0, flags=<optimized out>, sendlen=0, handler=0x7fa237d34b60) at ptp.c:152
 ptp_transaction (params=params@entry=0x7fa228000078, ptp=ptp@entry=0x7fa237d34bd0, flags=flags@entry=2, sendlen=sendlen@entry=0, data=data@entry=0x7fa237d34bc8, recvlen=recvlen@entry=0x7fa237d34bc4) at ptp.c:400
 ptp_getstorageids (params=params@entry=0x7fa228000078, storageids=storageids@entry=0x7fa237d34c40) at ptp.c:596
 LIBMTP_Get_Storage (device=device@entry=0x7fa2280080f0, 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 : StacktraceSource.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() (when plugging in
- android phone via USB port)
+ gvfsd-mtp crashed with SIGSEGV in ptp_transaction_new() (when plugging
+ in android phone via USB port)
tags: removed: need-amd64-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
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.