nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1762053 reported by Abe Birnbaum
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Don't know what was happening. It seemed to crash in background while I was taking a break pkaying a game

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Apr 7 13:53:37 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2018-03-25 (13 days ago)
InstallationMedia: budgie-remix 16.04.3 "Budgie-remix" - Release amd64 (20170804)
ProcCmdline: nautilus --new-window /media/username/hybrid
SegvAnalysis:
 Segfault happened at: 0x7ffb3cf7dc31 <g_type_check_instance_is_fundamentally_a+49>: movzbl 0x14(%rdx),%eax
 PC (0x7ffb3cf7dc31) ok
 source "0x14(%rdx)" (0x107f8b48fb894864) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to bionic on 2018-04-06 (1 days ago)
UserGroups: libvirt libvirtd sudo
usr_lib_nautilus:

Revision history for this message
Abe Birnbaum (texadian) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.