gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()

Bug #1711957 reported by Lyn Perrine on 2017-08-20
80
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Medium
Unassigned

Bug Description

On startup of lubuntu 17.04 I get a message that system problem detected when logging into lxde.

gvfs:
  Installed: 1.33.90-0ubuntu1
  Candidate: 1.33.90-0ubuntu1
  Version table:
 *** 1.33.90-0ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

I expected lubuntu to start with no errors. Inseated I got a crash and a browser opened up about gvfs crashing.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gvfs-backends 1.33.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.11.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
Date: Wed Aug 16 14:08:43 2017
ExecutablePath: /usr/lib/gvfs/gvfsd-recent
InstallationDate: Installed on 2015-09-20 (699 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150920)
ProcCmdline: /usr/lib/gvfs/gvfsd-recent --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7fb186da5afe <g_vfs_monitor_emit_event+14>: mov 0x18(%rdi),%rax
 PC (0x7fb186da5afe) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 g_vfs_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
 ?? ()
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_value_set_enum () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()
UpgradeStatus: Upgraded to artful on 2017-08-06 (14 days ago)
UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo

Lyn Perrine (walterorlin) wrote :

StacktraceTop:
 g_vfs_monitor_emit_event (monitor=monitor@entry=0x0, event_type=event_type@entry=G_FILE_MONITOR_EVENT_ATTRIBUTE_CHANGED, file_path=0xe135f33a40 "1e8717540d9b2fcd0db5283d5994b457", other_file_path=other_file_path@entry=0x0) at gvfsmonitor.c:357
 reload_recent_items (backend=<optimized out>) at gvfsbackendrecent.c:566
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=0x7ffc10a761b0) at ../src/x86/ffi64.c:525
 g_value_set_enum (value=<optimized out>, v_enum=<optimized out>) at ../../../../gobject/genums.c:710

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in gvfs (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers