gvfsd-mtp crashed with SIGSEGV

[Till Kamppeter]

I get this every day when I have connected my Android phone for charging its battery.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jul 24 11:29:55 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
InstallationDate: Installed on 2015-04-30 (816 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7fea768b6cc9: mov 0x18(%rax),%rax
 PC (0x7fea768b6cc9) 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:
 () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gvfsd-mtp crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark

[Apport retracing service (apport)]

StacktraceTop:
 unregister_mount_got_proxy_cb () from /tmp/apport_sandbox_1fY0d3/usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 g_task_return_now () from /tmp/apport_sandbox_1fY0d3/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_task_return () from /tmp/apport_sandbox_1fY0d3/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 init_second_async_cb () from /tmp/apport_sandbox_1fY0d3/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_task_return_now () from /tmp/apport_sandbox_1fY0d3/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jamie Bennett (jamiebennett)]

Happens to me, not doing anything in particular as a user to trigger it.

[Sebastien Bacher (seb128)]

seems the same as bug #1718694 reported upstream on https://bugzilla.gnome.org/show_bug.cgi?id=787992

[Chris Hermansen (c-hermansen)]

I reported this separately as 1725030 but it is apparently a duplicate of this.

I'm a bit surprised at that because this problem never occurred in 17.04 but did so the first time I plugged my phone into 17.10.

Anyway if anyone here needs more info, I'm your person.

[forteller (forteller)]

> I'm a bit surprised at that because this problem never occurred in 17.04 but did so the first time I plugged my phone into 17.10.

I have the exact same experience. Got the error today, haven't had it before. And when I disconnected the phone the screen went blank for a few nano seconds.

[michael deer (jasontodd9979)]

I have an android coolpad that works great when plugged in. no problems at
all. The crash my 17.10 suffered was internal and didnt affect anything
going on I was doing (Chromium browsing, transfering files from pc to usb
and android etc), an error message just popped up out of the blue and i
agreed to report it. Sounds like you may be having a hardware conflict
somewhere. The only other problem ive had since install was gparted not
wanting to work at all.

On Sun, Oct 22, 2017 at 2:52 PM, forteller <email address hidden>
wrote:

> > I'm a bit surprised at that because this problem never occurred in
> 17.04 but did so the first time I plugged my phone into 17.10.
>
> I have the exact same experience. Got the error today, haven't had it
> before. And when I disconnected the phone the screen went blank for a
> few nano seconds.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
> gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs package in Ubuntu:
> Confirmed
>
> Bug description:
> I get this every day when I have connected my Android phone for
> charging its battery.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: gvfs-backends 1.32.1-0ubuntu1
> ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
> Uname: Linux 4.11.0-10-generic x86_64
> ApportVersion: 2.20.6-0ubuntu4
> Architecture: amd64
> CrashCounter: 1
> CurrentDesktop: GNOME
> Date: Mon Jul 24 11:29:55 2017
> ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
> InstallationDate: Installed on 2015-04-30 (816 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
> ProcEnviron:
> LANG=en_US.UTF-8
> LANGUAGE=en_US
> PATH=(custom, user)
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> SegvAnalysis:
> Segfault happened at: 0x7fea768b6cc9: mov 0x18(%rax),%rax
> PC (0x7fea768b6cc9) 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:
> () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: gvfsd-mtp crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1706097/+subscriptions
>

[Rakesh (dewgeek)]

Hello everyone,

I am facing this bug, I am not able to mount my android device.
Is there any quick fix for this like restarting gvfsd-mtp?

[michael deer (jasontodd9979)]

Im running android jelly bean on a coolpad quatro 2. No problems so far.
The error was generated automatically and affected nothing on my system.
Not that i could tell anyway

On Thu, Nov 9, 2017 at 11:06 PM, Rakesh <email address hidden> wrote:

> Hello everyone,
>
> I am facing this bug, I am not able to mount my android device.
> Is there any quick fix for this like restarting gvfsd-mtp?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
> gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs package in Ubuntu:
> Confirmed
>
> Bug description:
> I get this every day when I have connected my Android phone for
> charging its battery.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: gvfs-backends 1.32.1-0ubuntu1
> ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
> Uname: Linux 4.11.0-10-generic x86_64
> ApportVersion: 2.20.6-0ubuntu4
> Architecture: amd64
> CrashCounter: 1
> CurrentDesktop: GNOME
> Date: Mon Jul 24 11:29:55 2017
> ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
> InstallationDate: Installed on 2015-04-30 (816 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
> ProcEnviron:
> LANG=en_US.UTF-8
> LANGUAGE=en_US
> PATH=(custom, user)
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> SegvAnalysis:
> Segfault happened at: 0x7fea768b6cc9: mov 0x18(%rax),%rax
> PC (0x7fea768b6cc9) 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:
> () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: gvfsd-mtp crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1706097/+subscriptions
>

[Philip Langdale (langdalepl)]

This has been fixed and released upstream (1.32.2, 1.34.2.1, 1.36.0)

[Rolf Leggewie (r0lf)]

... and thus closing as fixed for bionic

[K. Tibor (ha3flt)]

I've never seen this one fixed. There is a clean install of 18.04 here, I also have a new Android phone - tried to connect my phone using MTP today, and segfault happens everytime in libgvfsdaemon.so...

[michael deer (jasontodd9979)]

I was running android marshmallow on a coolpad quattro 2. Ubuntu 17.10
wasn't allowing me to transfer media/ files to specific folders but i was
allowed to copy/ move stuff as long as just the device was the destination.
Im running 18.04 now and so far so good. I only have 4GB of ram but not
nearly as many freezes as 17.10. My new phone (Blu S1) runs android nougat
and i haven't had one connection error message yet, old or new phone.

On Sat, May 19, 2018 at 3:46 PM, K. Tibor <email address hidden>
wrote:

> I've never seen this one fixed. There is a clean install of 18.04 here,
> I also have a new Android phone - tried to connect my phone using MTP
> today, and segfault happens everytime in libgvfsdaemon.so...
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
> gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs:
> Unknown
> Status in gvfs package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Fedora:
> Unknown
>
> Bug description:
> I get this every day when I have connected my Android phone for
> charging its battery.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: gvfs-backends 1.32.1-0ubuntu1
> ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
> Uname: Linux 4.11.0-10-generic x86_64
> ApportVersion: 2.20.6-0ubuntu4
> Architecture: amd64
> CrashCounter: 1
> CurrentDesktop: GNOME
> Date: Mon Jul 24 11:29:55 2017
> ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
> InstallationDate: Installed on 2015-04-30 (816 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
> ProcEnviron:
> LANG=en_US.UTF-8
> LANGUAGE=en_US
> PATH=(custom, user)
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> SegvAnalysis:
> Segfault happened at: 0x7fea768b6cc9: mov 0x18(%rax),%rax
> PC (0x7fea768b6cc9) 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:
> () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: gvfsd-mtp crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gvfs/+bug/1706097/+subscriptions
>

[Bryan Chan (bryanpkc)]

When will a bionic package be released for the fixed versions of gvfs? I continue to get this crash on a fully updated 18.04.1 system.

[Scott Palmer (skewty)]

Don't get too excited.. https://gitlab.gnome.org/GNOME/nautilus/issues/703

[michael deer (jasontodd9979)]

Try to install things without selecting a specific folder. That was how I
got around the error before it was patched.

On Sun, Oct 21, 2018, 5:40 PM Scott Palmer <email address hidden>
wrote:

> Don't get too excited..
> https://gitlab.gnome.org/GNOME/nautilus/issues/703
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
> gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs:
> Unknown
> Status in gvfs package in Ubuntu:
> Fix Released
> Status in gnome-shell package in Fedora:
> Unknown
>
> Bug description:
> I get this every day when I have connected my Android phone for
> charging its battery.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: gvfs-backends 1.32.1-0ubuntu1
> ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
> Uname: Linux 4.11.0-10-generic x86_64
> ApportVersion: 2.20.6-0ubuntu4
> Architecture: amd64
> CrashCounter: 1
> CurrentDesktop: GNOME
> Date: Mon Jul 24 11:29:55 2017
> ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
> InstallationDate: Installed on 2015-04-30 (816 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
> ProcEnviron:
> LANG=en_US.UTF-8
> LANGUAGE=en_US
> PATH=(custom, user)
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> SegvAnalysis:
> Segfault happened at: 0x7fea768b6cc9: mov 0x18(%rax),%rax
> PC (0x7fea768b6cc9) 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:
> () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
> Title: gvfsd-mtp crashed with SIGSEGV
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gvfs/+bug/1706097/+subscriptions
>