nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
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
ProcVersionSign
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-
SegvAnalysis:
Segfault happened at: 0x7fab7f0f5cd7 <g_type_
PC (0x7fab7f0f5cd7) ok
source "(%rdi)" (0x2e6b74672e67
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_type_
g_object_ref () from /usr/lib/
g_list_copy_deep () from /lib/x86_
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to artful on 2018-02-03 (141 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.