Bug 1665852

Summary: [abrt] nautilus: g_type_check_instance_is_fundamentally_a(): nautilus killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: bbrryyaann, caillon+fedoraproject, cosimo.cecchi, gnome-sig, john.j5live, mclasen, rhughes, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e6423aa3cfefeb8d0e3291eaf105eaef0c248209
Whiteboard: abrt_hash:bba5b9b408678f84321198adabff55eac3b85fc9;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-12 22:16:22 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

Description Jan Vlug 2019-01-14 09:24:16 UTC 
Version-Release number of selected component:
nautilus-3.30.5-1.fc29

Additional info:
reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/bin/nautilus
journald_cursor: s=52ccfe5dbe904445a70ec852ac984790;i=27e;b=43ee98b1e78042d4ac4d583c5c93f947;m=2130dee62b;t=57f6749ec2962;x=77546b34ba2ab5e9
kernel:         4.19.13-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_is_fundamentally_a at gtype.c:4026
 #1 g_value_set_object at gobject.c:3898
 #2 object_get_property at gobject.c:1402
 #3 g_object_get_property at gobject.c:2599
 #4 on_source_notify at gbinding.c:316
 #5 g_object_bind_property_full at gbinding.c:959
 #6 g_object_bind_property at gbinding.c:1010
 #7 nautilus_window_slot_switch_new_content_view at ../src/nautilus-window-slot.c:3023
 #8 change_view at ../src/nautilus-window-slot.c:3054
 #9 setup_view at ../src/nautilus-window-slot.c:2098
Comment 1 Jan Vlug 2019-01-14 09:24:20 UTC 
Created attachment 1520489 [details]
File: backtrace
Comment 2 Jan Vlug 2019-01-14 09:24:22 UTC 
Created attachment 1520490 [details]
File: cgroup
Comment 3 Jan Vlug 2019-01-14 09:24:24 UTC 
Created attachment 1520491 [details]
File: core_backtrace
Comment 4 Jan Vlug 2019-01-14 09:24:25 UTC 
Created attachment 1520492 [details]
File: cpuinfo
Comment 5 Jan Vlug 2019-01-14 09:24:27 UTC 
Created attachment 1520493 [details]
File: dso_list
Comment 6 Jan Vlug 2019-01-14 09:24:28 UTC 
Created attachment 1520494 [details]
File: environ
Comment 7 Jan Vlug 2019-01-14 09:24:30 UTC 
Created attachment 1520495 [details]
File: exploitable
Comment 8 Jan Vlug 2019-01-14 09:24:35 UTC 
Created attachment 1520496 [details]
File: limits
Comment 9 Jan Vlug 2019-01-14 09:24:40 UTC 
Created attachment 1520497 [details]
File: maps
Comment 10 Jan Vlug 2019-01-14 09:24:49 UTC 
Created attachment 1520498 [details]
File: mountinfo
Comment 11 Jan Vlug 2019-01-14 09:24:50 UTC 
Created attachment 1520499 [details]
File: open_fds
Comment 12 Jan Vlug 2019-01-14 09:24:52 UTC 
Created attachment 1520500 [details]
File: proc_pid_status
Comment 13 Jan Vlug 2019-02-06 18:01:29 UTC 
Similar problem has been detected:

Opening Nautilus. Clicking on a directory. Starting to type to seach causes this crash, right after typing the first letter. Interestingly, this does not happen on my other Fedora system.

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/bin/nautilus
journald_cursor: s=0c571fe60795442cbd6fc18bc4785495;i=504ad;b=dc2f6587b6d245108b5f998b185311ce;m=115d837488;t=5813d63c1fdb0;x=4ac896086ccf9b00
kernel:         4.20.5-200.fc29.x86_64
package:        nautilus-3.30.5-1.fc29
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Bryan Paget 2019-03-12 14:37:59 UTC 
Similar problem has been detected:

Nautillus crashes very often when I use the search feature.  I start typing my search query, and it crashes.  Local disks.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/bin/nautilus
journald_cursor: s=a21e2221100542ca908da5688bdd999f;i=1238b;b=0c14d7dc41ef416eb7f7fa7b368d1248;m=15ee0f499;t=583e671bf6463;x=10ee3bf25f50a108
kernel:         4.20.14-200.fc29.x86_64
package:        nautilus-3.30.5-1.fc29
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Jan Vlug 2019-03-12 15:52:12 UTC 
This is probably a duplicate of bug 1672275. This issue is 100% reproducible for me.
Comment 16 Jan Vlug 2019-03-12 20:16:24 UTC 
Similar problem has been detected:

Crash when searching by typing in Nautilus. This crash happens all the time on one of my systems.

I noticed that around the crash of Nautilus, also a System Failure happens that cannot be reported by ABRT:
The backtrace does not contain enough meaningful function frames to be reported. It is annoying but it does not necessary signalize a problem with your computer. ABRT will not allow you to create a report in a bug tracking system but you can contact kernel maintainers via e-mail.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: g_type_check_instance_is_fundamentally_a
executable:     /usr/bin/nautilus
journald_cursor: s=9ab7c0e065ba46ba8766fe5f08465cfd;i=fc6f8;b=5a447fd6ca0f411b9f51371ec8877dc8;m=1badb3d2c5;t=583eb39607f31;x=5b700157593461e2
kernel:         4.20.13-200.fc29.x86_64
package:        nautilus-3.30.5-1.fc29
reason:         nautilus killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Jan Vlug 2019-03-12 22:16:22 UTC 

*** This bug has been marked as a duplicate of bug 1672275 ***