Bug 1652866 - g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0)
Summary: g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0)
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 29
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-23 10:53 UTC by bugz
Modified: 2018-11-24 23:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-11-24 23:40:55 UTC
Type: Bug

Attachments (Terms of Use)
Event dump from journal (15.53 KB, text/plain)
2018-11-23 10:53 UTC, bugz
no flags Details

Description bugz 2018-11-23 10:53:03 UTC
Created attachment 1508248 [details]
Event dump from journal

Description of problem:

Nautilus crashes

Version-Release number of selected component (if applicable):

GNOME nautilus 3.30.3

How reproducible:

When searching by typing directly to Nautilus, it crashes except if there are no files/folders in the folder chosen.

Steps to Reproduce:
1. Create empty testdir in /home/user/"atest"
2. Start Nautilus, goto "atest", type searchstring "test" - Nothing found OK
3. Stop Nautilus
4. Add a file including punctation in "atest", "touch test.file"
5. Start Nautilus, goto "atest" type searchstring "test", Nautilus crashes
6. Rename file in "atest" "mv test.file testfile"
7  Start Nautilus, goto "atest", type searchstring "test", Nautilus finds "testfile"

Actual results:


Expected results:

Search completing

Additional info:

Happens after update from Fedora 28 to 29
I'm on Fedora 29 Modular repos, danish localization

Downgrade to version 3.30.2 does not solve problem.

Lauched from terminal to follow:

$ nautilus
Initializing nautilus-search-tool extension
Initializing nautilus-image-converter extension

(nautilus:9775): GLib-GObject-CRITICAL **: 11:26:13.134: g_value_set_object: assertion 'G_IS_OBJECT (v_object)' failed
Segmentation fault (smed kerne)

Dump from journal attached

Comment 1 bugz 2018-11-23 22:07:55 UTC
I've investigated further. It seems as I cannot consistently copy the faulty behaviour on another machine I have.

I will do some more research and return.


Comment 2 bugz 2018-11-24 23:40:55 UTC
I've finished investigation. Showed up I had a defective piece of hardware in my workstation.
Component exchanged, problem solved.

Sorry for the inconvenience!


Note You need to log in before you can comment on or make changes to this bug.