nautilus crashed after resuming the computer from sleep

[Matthias Andree]

The computer resumed from sleep, possible with a USB drive removed during sleep, and nautilus crashed. Not sure if there is a causal relation because I was working in different applications with Nautilus windows and desktop sitting in the background.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Sep 5 08:37:44 2016
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus --new-window /media/username/disk
SegvAnalysis:
 Segfault happened at: 0x4a3d28: mov 0x18(%rax),%rax
 PC (0x004a3d28) 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: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse kvm libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

[Matthias Andree (matthias-andree)]

I've removed log files carring too much information forward; the "VERBATIM_HD" in the traces is an external USB 3.0 HDD mounted with NTFS 3G (through fuse).

[Apport retracing service (apport)]

StacktraceTop:
 nautilus_directory_add_file_to_work_queue (directory=0x0, file=0x326bdf0) at nautilus-directory-async.c:4500
 nautilus_file_invalidate_attributes (file=0x326bdf0, file_attributes=NAUTILUS_FILE_ATTRIBUTE_MOUNT) at nautilus-file.c:7493
 g_closure_invoke () from /tmp/apport_sandbox_2OS13w/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 signal_emit_unlocked_R () from /tmp/apport_sandbox_2OS13w/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_2OS13w/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

[Sebastien Bacher (seb128)]

similar to https://bugzilla.redhat.com/show_bug.cgi?id=1305381

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Ads20000 (ads20000)]

I can't reproduce this bug on Ubuntu 18.04 so am assuming Fix Released. If you can reproduce this on Ubuntu 18.04 or Cosmic then change the bug status to New, and if you can reproduce this on 16.04 but not 18.04 or Cosmic then ask Bug Control (here) to nominate this bug for Xenial.