gvfsd-mtp crashed with SIGSEGV in g_datalist_id_set_data_full()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Error when trying umount Android device with Android version 4.1.2
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.3-0ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-8-generic i686
ApportVersion: 2.9-0ubuntu2
Architecture: i386
Date: Fri Mar 1 18:15:16 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-21 (8 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20121227)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=es_ES.UTF-8
SegvAnalysis:
Segfault happened at: 0xb775dc6a: mov 0x10(%eax),%eax
PC (0xb775dc6a) ok
source "0x10(%eax)" (0xaaaaaaba) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_datalist_
?? () from /usr/lib/
g_object_unref () from /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV in g_datalist_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare 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 #1130597, 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.