nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Nautilus crashed after login and cant be opened Segmentation fault
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.24.1-0ubuntu5
ProcVersionSign
Uname: Linux 4.11.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Sat Jul 29 15:39:26 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-06-20 (39 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170620)
ProcCmdline: nautilus
ProcEnviron:
LANG=de_DE.UTF-8
TERM=xterm-
LANGUAGE=de_DE
PATH=(custom, no user)
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f50f459f18a <g_type_
PC (0x7f50f459f18a) ok
source "(%rdi)" (0x57e63660) not located in a known VMA region (needed readable region)!
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.