gvfsd-mtp crashed with SIGSEGV in libusb_submit_transfer()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After connecting my phone (Galaxy SIII)
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-4-generic x86_64
NonfreeKernelMo
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sat Feb 16 13:12:31 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2012-10-18 (121 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f385dd72bb5 <libusb_
PC (0x7f385dd72bb5) 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_
?? () from /lib/x86_
libusb_
?? () from /usr/lib/
LIBMTP_Read_Event () from /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV in libusb_
UpgradeStatus: Upgraded to raring on 2013-01-10 (36 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1152472, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.