gvfsd-google crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed whilst connecting to Google Drive through file system.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gvfs-backends 1.36.0-1ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 12 21:09:50 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2018-04-12 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f69cad57d6e: mov 0x38(%rax),%ecx
PC (0x7f69cad57d6e) ok
source "0x38(%rax)" (0x00000038) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
g_task_
() at /usr/lib/
Title: gvfsd-google crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-04-12 (0 days ago)
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 #1763395, 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.