gvfsd-mtp crashed with SIGSEGV in do_sync_bulk_transfer()

Bug #1121285 reported by BertN45 on 2013-02-10
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Medium
Unassigned

Bug Description

Error occured when dropping a playlist on the media player device icon in Rhythmbox.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
Uname: Linux 3.8.0-5-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sun Feb 10 12:59:35 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2012-11-08 (93 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121107.2)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
SegvAnalysis:
 Segfault happened at: 0xb70e6393: mov 0x1c(%eax),%eax
 PC (0xb70e6393) ok
 source "0x1c(%eax)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () 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
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV in LIBMTP_Read_Event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

BertN45 (lammert-nijhof) wrote :

StacktraceTop:
 do_sync_bulk_transfer (dev_handle=0xb5b051e0, dev_handle@entry=0xb52fe1d8, endpoint=endpoint@entry=24 '\030', buffer=0xb52fe1d8 "", length=24, transferred=0xb52fe1d4, timeout=0, type=2 '\002') at ../../libusb/sync.c:182
 libusb_bulk_transfer (dev_handle=0xb52fe1d8, endpoint=24 '\030', data=0xb52fe1d4 "", data@entry=0xb52fe1d8 "", length=0, length@entry=24, transferred=0x2, transferred@entry=0xb52fe1d4, timeout=timeout@entry=0) at ../../libusb/sync.c:270
 ptp_usb_event (wait=0, event=0xb52fe23c, params=0xb5b052c0) at libusb1-glue.c:1548
 ptp_usb_event_wait (params=0xb5b052c0, event=event@entry=0xb52fe23c) at libusb1-glue.c:1607
 LIBMTP_Read_Event (device=0xb5b05270, event=0xb52fe298, out1=0xb52fe29c) at libmtp.c:2142

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
summary: - gvfsd-mtp crashed with SIGSEGV in LIBMTP_Read_Event()
+ gvfsd-mtp crashed with SIGSEGV in do_sync_bulk_transfer()
tags: removed: need-i386-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in gvfs (Ubuntu):
status: New → Confirmed
Philip Langdale (langdalepl) wrote :

This happened because rhythmbox and gvfs cannot both access the same MTP device at the same time. The MTP protocol doesn't support multiple clients. Rhytmbox's attempt to communicate with the device kills gvfs' session, resulting in this.

You should explicitly unmount the device in Nautilus before attempting to interact with it through Rhythmbox.

BertN45 (lammert-nijhof) wrote :

Try to explain that to a Windows User or Tablet User of Ubuntu, (s)he will run away screaming!

metalbrick (metalbrick) on 2013-05-14
description: updated
tags: added: saucy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers