gvfsd-mtp crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs |
Expired
|
Critical
|
|||
gvfs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm copy of celular to folder.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSign
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed May 24 21:03:44 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2015-07-26 (668 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f6ba0663cc9: mov 0x18(%rax),%rax
PC (0x7f6ba0663cc9) ok
source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-05-15 (9 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
Changed in gvfs: | |
importance: | Unknown → Critical |
status: | Unknown → Expired |
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 #1689770, 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.