nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1741627 reported by Carlos Gomes on 2018-01-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

crashed after hitting crtl+n to open a new window

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-14.17-generic 4.14.11
Uname: Linux 4.14.0-14-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 6 13:36:57 2018
ExecutablePath: /usr/bin/nautilus
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'166'
 b'org.gnome.nautilus.window-state' b'geometry' b"'941x1007+36+32'"
InstallationDate: Installed on 2017-12-28 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201)
ProcCmdline: /usr/bin/nautilus --gapplication-service
 Segfault happened at: 0x7f8c39c09cdf <g_type_check_instance_is_fundamentally_a+15>: mov (%rdx),%rdx
 PC (0x7f8c39c09cdf) ok
 source "(%rdx)" (0x5d00000001) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
 g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/
 g_object_ref () at /usr/lib/x86_64-linux-gnu/
 g_list_copy_deep () at /lib/x86_64-linux-gnu/
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
usr_lib_nautilus: dropbox 2015.10.28

Carlos Gomes (gocarlos) wrote :

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers