nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After an OS update a few hours ago, nautilus stopped working. It crashes on startup and when I run the command "sudo nautilus" I get the response "Segmentation fault"
I am unable to open the file browser GUI.
I tried reinstalling and restarting a couple of times, it did not work.
lsb_release -rd:
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
apt-cahce policy nautilus:
nautilus:
Installed: 1:3.24.1-0ubuntu5
Candidate: 1:3.24.1-0ubuntu5
Version table:
*** 1:3.24.1-0ubuntu5 500
500 http://
100 /var/lib/
I am using gnome-tweak-tool, I am not sure if that is relevant.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu5
ProcVersionSign
Uname: Linux 4.11.0-11-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sat Jul 29 10:34:23 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-07-19 (9 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: nautilus
SegvAnalysis:
Segfault happened at: 0x7f2af417818a <g_type_
PC (0x7f2af417818a) ok
source "(%rdi)" (0xffffffffeafd
destination "%r9" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1707346, 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.