nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
after unmounting a usb stick
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 26 13:22:56 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-10-26 (30 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/nautilus --gapplication-
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=de_DE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f5d876e9cdf <g_type_
PC (0x7f5d876e9cdf) ok
source "(%rdx)" (0x544155415641
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
g_object_ref () from /usr/lib/
g_list_copy_deep () from /lib/x86_
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
usr_lib_nautilus:
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 #1713581, 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.