Bug 1631958

Summary: [abrt] nautilus: g_type_check_instance_is_a(): nautilus killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ade Malsasa Akbar <teknoloid>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: alexl, cosimo.cecchi, gabibbo97, john.j5live, mclasen, mikhail.v.gavrilov, rhughes, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e1a7d2808266feacf70af98413cc9f6193c52f3d
Whiteboard: abrt_hash:dddae8e4471fbbcd8475276e2dc5c5229fa97ea3;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 17:48:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ade Malsasa Akbar 2018-09-22 14:39:50 UTC
Version-Release number of selected component:
nautilus-3.30.0-2.fc30

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_type_check_instance_is_a
executable:     /usr/bin/nautilus
journald_cursor: s=2ccab4a2021a40989d1574019ad958cc;i=ca66;b=efe197024d2e43d2aa251fcdcc299539;m=1e66cf06d;t=5767683639bcc;x=3737071153a0b940
kernel:         4.19.0-0.rc3.git2.1.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_is_a at gtype.c:4013
 #1 gtk_widget_get_ancestor at gtkwidget.c:11585
 #2 button_data_file_changed at ../src/nautilus-pathbar.c:1436
 #7 nautilus_file_emit_changed at ../src/nautilus-file.c:8357
 #8 nautilus_directory_emit_change_signals at ../src/nautilus-directory.c:1030
 #9 emit_change_signals_for_all_files at ../src/nautilus-directory.c:415
 #10 emit_change_signals_for_all_files_in_all_directories at ../src/nautilus-directory.c:434
 #14 g_signal_emit_by_name at gsignal.c:3487
 #15 app_chooser_dialog_response_cb at ../src/nautilus-files-view.c:1461
 #20 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102

Comment 1 Ade Malsasa Akbar 2018-09-22 14:40:00 UTC
Created attachment 1485971 [details]
File: backtrace

Comment 2 Ade Malsasa Akbar 2018-09-22 14:40:02 UTC
Created attachment 1485972 [details]
File: cgroup

Comment 3 Ade Malsasa Akbar 2018-09-22 14:40:04 UTC
Created attachment 1485973 [details]
File: core_backtrace

Comment 4 Ade Malsasa Akbar 2018-09-22 14:40:06 UTC
Created attachment 1485974 [details]
File: cpuinfo

Comment 5 Ade Malsasa Akbar 2018-09-22 14:40:13 UTC
Created attachment 1485975 [details]
File: dso_list

Comment 6 Ade Malsasa Akbar 2018-09-22 14:40:20 UTC
Created attachment 1485976 [details]
File: environ

Comment 7 Ade Malsasa Akbar 2018-09-22 14:40:22 UTC
Created attachment 1485977 [details]
File: exploitable

Comment 8 Ade Malsasa Akbar 2018-09-22 14:40:25 UTC
Created attachment 1485978 [details]
File: limits

Comment 9 Ade Malsasa Akbar 2018-09-22 14:40:32 UTC
Created attachment 1485979 [details]
File: maps

Comment 10 Ade Malsasa Akbar 2018-09-22 14:40:35 UTC
Created attachment 1485980 [details]
File: mountinfo

Comment 11 Ade Malsasa Akbar 2018-09-22 14:40:37 UTC
Created attachment 1485981 [details]
File: open_fds

Comment 12 Ade Malsasa Akbar 2018-09-22 14:40:39 UTC
Created attachment 1485982 [details]
File: proc_pid_status

Comment 13 Ade Malsasa Akbar 2018-09-22 14:40:41 UTC
Created attachment 1485983 [details]
File: var_log_messages

Comment 14 Ben Cotton 2019-08-13 16:54:03 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 15 Ben Cotton 2019-08-13 19:42:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 16 Ben Cotton 2020-11-03 15:02:48 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Ben Cotton 2020-11-24 17:48:52 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.