gvfsd-mtp crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
my phone is galaxy note 2(N7100), android version is 4.1.2 , gvfs_mtd not work well
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gvfs-backends 1.15.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-0-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Sat Jan 19 19:59:55 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-01-11 (8 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7ffe1709a8c6: movdqu (%rdi),%xmm1
PC (0x7ffe1709a8c6) ok
source "(%rdi)" (0xaaaaaaaaaaaa
destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? () from /lib/x86_
?? ()
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: gvfsd-mtp crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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 #1101986, 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.