nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1778420 reported by Gerald Schedl on 2018-06-24
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Undecided
Unassigned

Bug Description

Copied data from my Sony Xperia X mobile to the data HDD. Nautilus freezed and crashed after abort.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 24 20:14:07 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-04-15 (435 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/nautilus --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fab7f0f5cd7 <g_type_check_instance_is_fundamentally_a+7>: mov (%rdi),%rdx
 PC (0x7fab7f0f5cd7) ok
 source "(%rdi)" (0x2e6b74672e67726f) not located in a known VMA region (needed readable region)!
 destination "%rdx" 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 artful on 2018-02-03 (141 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Gerald Schedl (e-gerald) 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