nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1725249 reported by Jeko on 2017-10-20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Undecided
Unassigned

Bug Description

I was trying to extract a file from an archive by dragging & dropping to Nautilus.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 12:33:25 2017
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2015-11-26 (693 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f1cdad4dcd7 <g_type_check_instance_is_fundamentally_a+7>: mov (%rdi),%rdx
 PC (0x7f1cdad4dcd7) ok
 source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_list_copy_deep () at /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 artful on 2017-10-19 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark

Jeko (markos30) 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