gvfsd-mtp crashed with SIGSEGV in list_add_tail()

Bug #1152472 reported by numan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs
Expired
Critical
gvfs (Ubuntu)
Incomplete
Medium
Philip Langdale

Bug Description

Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
gvfs:
  Installed: 1.15.4-0ubuntu1
  Candidate: 1.15.4-0ubuntu1
  Version table:
 *** 1.15.4-0ubuntu1 0
        500 http://hk.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1
Uname: Linux 3.8.0-9-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 8 14:41:13 2013
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2013-03-05 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130305)
MarkForUpload: True
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.11 /org/gtk/gvfs/exec_spaw/12
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_HK:en
 LANG=en_HK.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8a0dcb3bb5 <libusb_submit_transfer+485>: mov %rax,0x8(%rdx)
 PC (0x7f8a0dcb3bb5) ok
 source "%rax" ok
 destination "0x8(%rdx)" (0x00000008) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 libusb_submit_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 libusb_bulk_transfer () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
 LIBMTP_Read_Event () from /usr/lib/x86_64-linux-gnu/libmtp.so.9
Title: gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
numan (nomi-ali) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 list_add_tail (head=0x7f8a000070b0, entry=0x7f89fc0008c8) at ../../libusb/libusbi.h:103
 add_to_flying_list (transfer=0x7f89fc0008c0) at ../../libusb/io.c:1196
 libusb_submit_transfer (transfer=transfer@entry=0x7f89fc000918) at ../../libusb/io.c:1306
 do_sync_bulk_transfer (dev_handle=0x7f8a00007910, endpoint=<optimized out>, buffer=buffer@entry=0x7f8a06ffcd50 "", length=length@entry=24, transferred=transferred@entry=0x7f8a06ffcd4c, timeout=timeout@entry=0, type=type@entry=2 '\002') at ../../libusb/sync.c:175
 libusb_bulk_transfer (dev_handle=<optimized out>, endpoint=<optimized out>, data=data@entry=0x7f8a06ffcd50 "", length=length@entry=24, transferred=transferred@entry=0x7f8a06ffcd4c, timeout=timeout@entry=0) at ../../libusb/sync.c:270

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 libusb_submit_transfer()
+ gvfsd-mtp crashed with SIGSEGV in list_add_tail()
tags: removed: need-amd64-retrace
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
information type: Private → Public
tags: added: trusty
Revision history for this message
Philip Langdale (langdalepl) wrote :

This is the very first version with any mtp support, and a lot of fixes have gone in since then. Please reopen if you can reproduce on 14.04 or newer.

Changed in gvfs (Ubuntu):
assignee: nobody → Philip Langdale (langdalepl)
status: Confirmed → Incomplete
Changed in gvfs:
importance: Unknown → Critical
status: Unknown → Expired
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.