Description of problem: Open a folder in nautilus, and while the content of the folder is still updating, right click on a sub-folder and click on "open in a new window". That will cause nautilus to crash (~50% probability). (note that the first folder should contain enough files to have time to click when the display is not yet fully updated) Version-Release number of selected component: nautilus-3.30.0-2.fc29 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=0f9abd41419748eca4967f330be5460b;i=33de48;b=8245f49221da41039b37b438c42cef57;m=95a4b31c;t=5768515df93ed;x=89796a4f83486e73 kernel: 4.18.9-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 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 Potential duplicate: bug 1631958
Created attachment 1486138 [details] File: backtrace
Created attachment 1486139 [details] File: cgroup
Created attachment 1486140 [details] File: core_backtrace
Created attachment 1486141 [details] File: cpuinfo
Created attachment 1486142 [details] File: dso_list
Created attachment 1486143 [details] File: environ
Created attachment 1486144 [details] File: exploitable
Created attachment 1486145 [details] File: limits
Created attachment 1486146 [details] File: maps
Created attachment 1486147 [details] File: mountinfo
Created attachment 1486148 [details] File: open_fds
Created attachment 1486149 [details] File: proc_pid_status
Similar problem has been detected: I had at least one nautilus window with several tabs open already. Then I tried to open a new instance (window) by pressing a custom global keyboard shortcut in GNOME shell. Instead of opening a new window, all previously opened windows closed (crashed). 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=ef01adf0829f42b2896c9a5bb27a1bac;i=4dda6e;b=35f0936881ee437e9d8987f4fef05fd7;m=b44bfd0b;t=5777ae37b0117;x=e49d7dfb1608927e kernel: 4.18.11-301.fc29.x86_64 package: nautilus-3.30.1-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp
Similar problem has been detected: I was selecting and deleting large amount of files 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=360f0474bca5409ab63c97c82a56c8e4;i=29c07;b=93e6c168409e46d0a1e98ecdaedc3caf;m=ed6a7239;t=5778b6b7e2f4a;x=3c26770810487df4 kernel: 4.18.11-301.fc29.x86_64 package: nautilus-3.30.1-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was copying files from local drive to online account (Google Drive). 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=c1628fbed72546a0a3b3aa5219ff0229;i=19291;b=e08b55296179497682a8799af3dacff8;m=23d0b893;t=57790637b908f;x=b459b9b6f82334c2 kernel: 4.18.12-300.fc29.x86_64 package: nautilus-3.30.1-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1637404 has been marked as a duplicate of this bug. ***
*** Bug 1637569 has been marked as a duplicate of this bug. ***
*** Bug 1638532 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Cold boot Fedora 29 Beta Log in Desktop comes up Move mouse to select activities Observe pop up that Nautilus crashed reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=5fafd3729338467781c84ee021edfc6e;i=609c9;b=e30f42cdf432405491d2c54e47adbab4;m=d56a9b5c;t=57810d7c5b85a;x=72bd11819836ae6e kernel: 4.18.13-300.fc29.x86_64 package: nautilus-3.30.1-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was just browsing pictures when nautilus crashed reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=f69ddf50c9ff4afcb228a3f7a4c55519;i=bfff5;b=043e648474de42b6a7d09c7e14bc6c0a;m=b2d9a612c;t=5783b47c7e1df;x=3f59958346ecf8c4 kernel: 4.18.13-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: close window reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus global_pid: 28139 kernel: 4.18.10-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: attempted to open a file. as soon as the application (in this case videos) was chosen, nautilus crashed reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus global_pid: 31809 kernel: 4.18.10-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I cut a folder and nautilus crashed while I was clicking "home" (to paste the folder somewhere else) reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=ad62c3320021482a86bdf80b9e278644;i=33fefa;b=053faaee39554a978609b552516ae35d;m=231115497;t=5783ef1a4ca51;x=18c8af25819a4e1 kernel: 4.18.13-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was opening MS Office 2007 via wine then nautilus crashed. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=f52ed9316a6d491abd360208e2885fe2;i=201b42;b=9b39a47327974ea58ff217902818669e;m=4707ece03;t=5785325607826;x=b8c0349df9e25e7d kernel: 4.18.13-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: open archive in file-roller reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=a98b5953f81f46deb0ac156353a4dc17;i=37cf0;b=47e30b7547284cbc865017451a79cb05;m=cda41be60;t=578a2ab1b6c6d;x=495b8e3a5448c7e kernel: 4.18.14-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1642195 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I am not sure how this produced but thisis second time hapned since yesterday and I also have one more information. nautilus didnt open once when I restart the system. I unintalled it and reinstalled. yesterday. it was after the first bug. Now nautilus had crashed for second time. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=7727879dd295438d97faddfd0357d091;i=1617;b=018f7267d7ab4fe08f4f2e8b86fbc0bb;m=87018bb3;t=57906ada7db8e;x=2f328835d7497205 kernel: 4.18.12-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I dragged and dropped a bunch of files between two Nautilus windows. Then (I think) I tried changing directories, or maybe right-clicked, and got a crash. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=b178945068a04ee48c03c9f6df96cf26;i=15c647;b=3af9f9ad52b74273a116307bea93988c;m=128302faa2;t=57907872419cf;x=a668320e6e37896a kernel: 4.18.15-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: i has two window sideby side and copying files from onw file to another. when I right click and select cut option, nautilus crashed suddenly. The nautilus ha crashed for 3rd time since 3 days after installing fedora 29 beta. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=ede672c54f4a48efb14957bd7f4ff352;i=3893;b=b174ab8d2a1e412cb1ac02e0fc9fe90a;m=1418a9b98;t=57921fade68b4;x=f8f973c3c3e111a4 kernel: 4.18.12-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Hello all, I add a backtrace obtained with gdb: Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault. 0x00007ffff7271150 in g_type_check_instance_is_a () from /lib64/libgobject-2.0.so.0 Missing separate debuginfos, use: and a lot of library names here, left out for clarity... (gdb) bt #0 0x00007ffff7271150 in g_type_check_instance_is_a () at /lib64/libgobject-2.0.so.0 #1 0x00007ffff7aad8b4 in gtk_widget_get_ancestor () at /lib64/libgtk-3.so.0 #2 0x000055555562fb28 in button_data_file_changed (file=0x5555581783c0, button_data=0x555560434640) at ../src/nautilus-pathbar.c:1430 #3 0x00007ffff724cc9d in g_closure_invoke () at /lib64/libgobject-2.0.so.0 #4 0x00007ffff7260203 in () at /lib64/libgobject-2.0.so.0 #5 0x00007ffff726932a in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0 #6 0x00007ffff7269923 in g_signal_emit () at /lib64/libgobject-2.0.so.0 #7 0x00005555555e9189 in nautilus_file_emit_changed (file=0x5555581783c0) at ../src/nautilus-file.c:8350 #8 0x00005555555ca5d8 in nautilus_directory_emit_change_signals (directory=0x555556433880, changed_files=0x7fffffffd100 = {...}) at ../src/nautilus-directory.c:1030 #9 0x00005555555e9405 in nautilus_file_changed (file=file@entry=0x5555581783c0) at ../src/nautilus-file.c:8302 #10 0x000055555564f250 in dequeue_pending_idle_callback (callback_data=callback_data@entry=0x5555735579f0) at ../src/nautilus-directory-async.c:1013 #11 0x000055555564ff34 in directory_load_done (directory=0x5555735579f0, error=0x0) at ../src/nautilus-directory-async.c:1145 #12 0x0000555555650174 in more_files_callback (source_object=<optimized out>, res=0x55555df1d420, user_data=0x5555568018e0) at ../src/nautilus-directory-async.c:2102 #13 0x00007ffff72e733f in () at /lib64/libgio-2.0.so.0 #14 0x00007ffff7321f74 in () at /lib64/libgio-2.0.so.0 #15 0x00007ffff7321fad in () at /lib64/libgio-2.0.so.0 #16 0x00007ffff7eb8b7b in () at /lib64/libglib-2.0.so.0 #17 0x00007ffff7ebc26d in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #18 0x00007ffff7ebc638 in () at /lib64/libglib-2.0.so.0 #19 0x00007ffff7ebc6d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #20 0x00007ffff7336465 in g_application_run () at /lib64/libgio-2.0.so.0 #21 0x00005555555a89b4 in main (argc=1, argv=0x7fffffffd4b8) at ../src/nautilus-main.c:81
I also add a valgrind output. It seemd to have segfaulted at another place, although there were bad reads in g_type_check_instance_is_a() also. [stienlet@work_pc ~]$ valgrind nautilus ==20707== Memcheck, a memory error detector ==20707== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==20707== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==20707== Command: nautilus ==20707== ==20707== Invalid read of size 8 ==20707== at 0x4D378A3: gtk_widget_get_ancestor (in /usr/lib64/libgtk-3.so.0.2400.1) ==20707== by 0x1E3B27: button_data_file_changed (nautilus-pathbar.c:1430) ==20707== by 0x5593C9C: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55A7202: ??? (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0329: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0922: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x19D188: nautilus_file_emit_changed (nautilus-file.c:8350) ==20707== by 0x17E5D7: nautilus_directory_emit_change_signals (nautilus-directory.c:1030) ==20707== by 0x19D404: nautilus_file_changed (nautilus-file.c:8302) ==20707== by 0x20324F: dequeue_pending_idle_callback (nautilus-directory-async.c:1013) ==20707== by 0x203F33: directory_load_done (nautilus-directory-async.c:1145) ==20707== by 0x204173: more_files_callback (nautilus-directory-async.c:2102) ==20707== Address 0xb536300 is 32 bytes before a block of size 32 in arena "client" ==20707== ==20707== Invalid read of size 8 ==20707== at 0x55B8121: g_type_check_instance_is_a (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x4D378B3: gtk_widget_get_ancestor (in /usr/lib64/libgtk-3.so.0.2400.1) ==20707== by 0x1E3B27: button_data_file_changed (nautilus-pathbar.c:1430) ==20707== by 0x5593C9C: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55A7202: ??? (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0329: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0922: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x19D188: nautilus_file_emit_changed (nautilus-file.c:8350) ==20707== by 0x17E5D7: nautilus_directory_emit_change_signals (nautilus-directory.c:1030) ==20707== by 0x19D404: nautilus_file_changed (nautilus-file.c:8302) ==20707== by 0x20324F: dequeue_pending_idle_callback (nautilus-directory-async.c:1013) ==20707== by 0x203F33: directory_load_done (nautilus-directory-async.c:1145) ==20707== Address 0xb536300 is 32 bytes before a block of size 32 in arena "client" ==20707== (nautilus:20707): Gtk-CRITICAL **: 15:15:07.780: gtk_widget_get_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed ==20707== Invalid read of size 8 ==20707== at 0x4D37898: gtk_widget_get_ancestor (in /usr/lib64/libgtk-3.so.0.2400.1) ==20707== by 0x1E3B27: button_data_file_changed (nautilus-pathbar.c:1430) ==20707== by 0x5593C9C: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55A7202: ??? (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0329: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0922: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x19D188: nautilus_file_emit_changed (nautilus-file.c:8350) ==20707== by 0x17E5D7: nautilus_directory_emit_change_signals (nautilus-directory.c:1030) ==20707== by 0x19D404: nautilus_file_changed (nautilus-file.c:8302) ==20707== by 0x205771: got_filesystem_info (nautilus-directory-async.c:4021) ==20707== by 0x205771: query_filesystem_info_callback (nautilus-directory-async.c:4048) ==20707== by 0x5469F73: ??? (in /usr/lib64/libgio-2.0.so.0.5800.1) ==20707== by 0x5469FAC: ??? (in /usr/lib64/libgio-2.0.so.0.5800.1) ==20707== Address 0x1ba7ef30 is 16 bytes after a block of size 96 in arena "client" ==20707== ==20707== Invalid read of size 8 ==20707== at 0x55B8119: g_type_check_instance_is_a (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x4D378B3: gtk_widget_get_ancestor (in /usr/lib64/libgtk-3.so.0.2400.1) ==20707== by 0x1E3B27: button_data_file_changed (nautilus-pathbar.c:1430) ==20707== by 0x5593C9C: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55A7202: ??? (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0329: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0922: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x19D188: nautilus_file_emit_changed (nautilus-file.c:8350) ==20707== by 0x17E5D7: nautilus_directory_emit_change_signals (nautilus-directory.c:1030) ==20707== by 0x19D404: nautilus_file_changed (nautilus-file.c:8302) ==20707== by 0x205771: got_filesystem_info (nautilus-directory-async.c:4021) ==20707== by 0x205771: query_filesystem_info_callback (nautilus-directory-async.c:4048) ==20707== by 0x5469F73: ??? (in /usr/lib64/libgio-2.0.so.0.5800.1) ==20707== Address 0x1ba7ef30 is 16 bytes after a block of size 96 in arena "client" ==20707== (nautilus:20707): Gtk-CRITICAL **: 15:17:48.153: gtk_widget_get_ancestor: assertion 'GTK_IS_WIDGET (widget)' failed ==20707== ==20707== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==20707== General Protection Fault ==20707== at 0x4D378A3: gtk_widget_get_ancestor (in /usr/lib64/libgtk-3.so.0.2400.1) ==20707== by 0x1E3B27: button_data_file_changed (nautilus-pathbar.c:1430) ==20707== by 0x5593C9C: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55A7202: ??? (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0329: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x55B0922: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.5800.1) ==20707== by 0x19D188: nautilus_file_emit_changed (nautilus-file.c:8350) ==20707== by 0x17E5D7: nautilus_directory_emit_change_signals (nautilus-directory.c:1030) ==20707== by 0x19D404: nautilus_file_changed (nautilus-file.c:8302) ==20707== by 0x205771: got_filesystem_info (nautilus-directory-async.c:4021) ==20707== by 0x205771: query_filesystem_info_callback (nautilus-directory-async.c:4048) ==20707== by 0x5469F73: ??? (in /usr/lib64/libgio-2.0.so.0.5800.1) ==20707== by 0x5469FAC: ??? (in /usr/lib64/libgio-2.0.so.0.5800.1) ==20707== ==20707== HEAP SUMMARY: ==20707== in use at exit: 320,924,634 bytes in 968,083 blocks ==20707== total heap usage: 39,876,258 allocs, 38,908,175 frees, 3,993,846,031 bytes allocated ==20707== ==20707== LEAK SUMMARY: ==20707== definitely lost: 438,161 bytes in 1,832 blocks ==20707== indirectly lost: 15,319,132 bytes in 4,758 blocks ==20707== possibly lost: 3,546,656 bytes in 3,344 blocks ==20707== still reachable: 281,615,877 bytes in 842,436 blocks ==20707== of which reachable via heuristic: ==20707== length64 : 6,285,480 bytes in 64,562 blocks ==20707== newarray : 7,000 bytes in 82 blocks ==20707== suppressed: 0 bytes in 0 blocks ==20707== Rerun with --leak-check=full to see details of leaked memory ==20707== ==20707== For counts of detected and suppressed errors, rerun with: -v ==20707== ERROR SUMMARY: 6 errors from 4 contexts (suppressed: 0 from 0) Segmentation fault (core dumped) [stienlet@work_pc ~]$
Perhaps (just an idea) this could be an access to an already-freed object?
This morning I tried to recompile nautilus using the sources from github: git rev-parse HEAD 569c1acecbe01815a98cd42cfca5a4840b0e2754 => Apparently this bug is corrected with this version of the sources! After trying hard I wasn't able to reproduce the bug with the git version (whereas it's easily reproducible with the fedora version) What I did exactly to make a .rpm from the github sources: koji download-build --arch=src nautilus-3.30.2-1.fc29.x86_64 rpm -Uvh nautilus-3.30.2-1.fc29.src.rpm git clone https://github.com/GNOME/nautilus.git rename the nautilus directory to nautilus-3.30.2 I did some minor changes to convert the tree from github to the fedora tree: -> copy of data/icons/hicolor -> data/icons/src/ -> data/meson.build -> change the version number in top dir meson.build then tar cfJ nautilus-3.30.2.tar.xz nautilus-3.30.2 I replaced the "nautilus-3.30.2.tar.xz" from "nautilus-3.30.2-1.fc29.src.rpm" in the "SOURCES" directory. then cd SPECS rpmbuild -v -bb --target=`uname -m` nautilus.spec finally: rpm -ivh ./nautilus-3.30.2-1.fc29.x86_64.rpm --nodeps I hope I haven't forgotten any step if somebody wants to correct this bug before the corrected version gets packaged. Best regards.
*** Bug 1643791 has been marked as a duplicate of this bug. ***
Similar problem has been detected: right click -> open with -> inkscape, then crash reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=1ea97e3ffb314222b8e7dd0671c5f599;i=4214f;b=819595e69eb14914b8b04d0ed19429ef;m=5abcd42e8;t=5795db53d651a;x=b18475bceb81784f kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: i copied the file and to paste it i clicked on connected google drive in nautilus. at that time the nautilus crashed. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=100c285dbc4a490c8b14ad48fa9aa110;i=a46;b=20d8759355ff41e197743c0d2bcfec2e;m=d7e41300;t=579872b8d82d4;x=288b07c6a3a22916 kernel: 4.18.12-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Apos atulização do Fedora 28 para o 29 alguns aplicativos não abrem reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=ab6bc643c88642f0a2f1693923d2d6f8;i=166a8;b=4be4218072014abfa7475687b9c9d684;m=1591368d;t=5798c8d808206;x=2e288f3804a0458 kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I can't give steps to reproduce this crash reliably, but it seems to happen when two nautilus windows are open and I switch between them and navigate to different folders. And then, at some point, opening a folder crashes both windows. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=67f4bbd585c8424fae3de050b16c359f;i=8c6d5;b=b1449a514abd4969857eb775b4e25394;m=1fc382722;t=57972af702815;x=8334c93e84eca0f6 kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: open a folder which is a symbolic link reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=aa4396b4fd82431f89324fe8fa8e3c87;i=c5a76;b=c73528126d054cd4a20b926806458e66;m=766cb46a0;t=5799b669f8066;x=a258974a08daf3d3 kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1645194 has been marked as a duplicate of this bug. ***
*** Bug 1645302 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Sorry, not much to offer here: First time seeing this behavior. Machine had been idle for awhile, screen had gone to blanked state. After screen refreshed, there was only a X cursor, little of shell accessible (no menus, right click produced nothing, etc.). Had recently changed setting to avoid entering password after screen blanking. Logging in remotely via ssh was possible, and 'journalctl -f' showed continual failure to access the desktop background file: Nov 02 15:35:06 biggie gnome-shell[10701]: Failed to load file:///home/rolf/.themes/Gnome-OSX-IV-shell-Space-Grey/gnome-shell/misc/noise-texture.png: Error opening file /home/rolf/.themes/Gnome-OSX-IV-shell-Space-Grey/gnome-shell/misc/noise-texture.png: No such file or directory Nov 02 15:35:07 biggie gnome-shell[10701]: Failed to load file:///home/rolf/.themes/Gnome-OSX-IV-shell-Space-Grey/gnome-shell/misc/noise-texture.png: Error opening file /home/rolf/.themes/Gnome-OSX-IV-shell-Space-Grey/gnome-shell/misc/noise-texture.png: No such file or directory <snip> reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=849d1fbaad024fd284edef5c4d10dcfb;i=31228f;b=41540007b9e94afc815c9ce175121b23;m=1434d11b85;t=579aedd056bc0;x=f7d534c9ab13fedd kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1645713 has been marked as a duplicate of this bug. ***
*** Bug 1645720 has been marked as a duplicate of this bug. ***
Similar problem has been detected: i tried open text file reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: nautilus /tmp/logs-20181102-194718.zip crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=db45a09b9c6242cabcdeb2fde5895e4f;i=27cd3;b=ec297e7968624b2c83c4b80c22ba4ef9;m=24a7d00653;t=579b7ff02e6c4;x=1334169251f3d343 kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1645734 has been marked as a duplicate of this bug. ***
Similar problem has been detected: First, I tried to open the kali-linux-2018.2-amd64.iso with the proposed default application (in german it is called "Einhängen von Laufwerksabbildern"), but it did not work. After that I tried to open the same iso file with file roller, which caused this crash, closing nautilus. After uploading this bug, I could open the iso file with file roller as expected. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=0be8a034a4e341488196c8e4cb3012b9;i=50aa3;b=b5d7e839f71d4242b484fb49468e1104;m=636f175;t=579c17db7a0ac;x=16867e8bba4ba7c kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1645759 has been marked as a duplicate of this bug. ***
*** Bug 1645833 has been marked as a duplicate of this bug. ***
*** Bug 1645882 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Crashed in the background soon after copying many photos off of phone. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=dbd8ea39682f4e189848bda50a15d7f9;i=63a5b;b=b3825a71def545cfb0cc350db03ad595;m=15ab559fa5;t=579db63ee2e25;x=b976c6bc0a82ddf3 kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was clicking "Home". Looks like a random crash. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=ad62c3320021482a86bdf80b9e278644;i=493515;b=fe5d11ee82554316a9b850979e5c7dbe;m=51bbbc614;t=579c4174bad29;x=6afded6ba866a3cf kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Random crash after removing number of folders and files via nautilus. reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_type_check_instance_is_a executable: /usr/bin/nautilus journald_cursor: s=56c5f389d19045bfab6875b93e25b27f;i=1c0d4;b=9ede49ff88eb43cbbf96cf557aa3e9ca;m=12ef9ae7be;t=579e9a66a8cd0;x=4fa9729c1cb10dd kernel: 4.18.16-300.fc29.x86_64 package: nautilus-3.30.2-1.fc29 reason: nautilus killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1646621 has been marked as a duplicate of this bug. ***
*** Bug 1646827 has been marked as a duplicate of this bug. ***
*** Bug 1652787 has been marked as a duplicate of this bug. ***
*** Bug 1678352 has been marked as a duplicate of this bug. ***
*** Bug 1687029 has been marked as a duplicate of this bug. ***
*** Bug 1689268 has been marked as a duplicate of this bug. ***
F30
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.