Ubuntu
gvfs package

gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()

Bug #1293602 reported by Emit
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gvfs-backends 1.19.90-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 17 15:17:04 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2014-03-14 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/7
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb6fec1e8 <libusb_submit_transfer+24>: mov 0x24(%eax),%eax
 PC (0xb6fec1e8) ok
 source "0x24(%eax)" (0x707a0875) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 libusb_submit_transfer () from /lib/i386-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/i386-linux-gnu/libusb-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libmtp.so.9
 LIBMTP_Read_Event () from /usr/lib/i386-linux-gnu/libmtp.so.9
 ?? ()
Title: gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()
UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

StacktraceTop:
 libusb_submit_transfer (transfer=transfer@entry=0xb400049c) at ../../libusb/io.c:1436
 do_sync_bulk_transfer (dev_handle=0x707a0851, endpoint=<optimized out>, buffer=0xb49fd1a8 "", length=24, transferred=0xb49fd1a4, timeout=0, type=2 '\002') at ../../libusb/sync.c:173
 libusb_bulk_transfer (dev_handle=<optimized out>, endpoint=<optimized out>, data=<optimized out>, data@entry=0xb49fd1a8 "", length=<optimized out>, length@entry=24, transferred=<optimized out>, transferred@entry=0xb49fd1a4, timeout=timeout@entry=0) at ../../libusb/sync.c:256
 ptp_usb_event (wait=0, event=<optimized out>, params=<optimized out>) at libusb1-glue.c:1564
 ptp_usb_event_wait (params=<optimized out>, event=<optimized out>, event@entry=0xb49fd20c) at libusb1-glue.c:1623

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
tags: removed: need-i386-retrace
Apport retracing service (apport)
tags: added: utopic
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
Robert Ancell (robert-ancell)
information type: Private → Public
Revision history for this message
Fenyvesi Attila (fattila2) wrote :

I cannot reproduce the bug but it happened once.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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