Version-Release number of selected component: nautilus-3.30.1-1.fc29 Additional info: reporter: libreport-2.9.6 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=c1628fbed72546a0a3b3aa5219ff0229;i=23580;b=3e85dadd488044058ee0a60398420b69;m=8f05229;t=577f33b728dae;x=e91b0b30524bcb56 kernel: 4.18.12-300.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1492907 [details] File: backtrace
Created attachment 1492908 [details] File: cgroup
Created attachment 1492909 [details] File: core_backtrace
Created attachment 1492910 [details] File: cpuinfo
Created attachment 1492911 [details] File: dso_list
Created attachment 1492912 [details] File: environ
Created attachment 1492913 [details] File: limits
Created attachment 1492914 [details] File: maps
Created attachment 1492915 [details] File: mountinfo
Created attachment 1492916 [details] File: open_fds
Created attachment 1492917 [details] File: proc_pid_status
*** Bug 1646124 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Turned computer on and a few minutes later, this crash occured. I didn't even open Nautilus myself. reporter: libreport-2.9.6 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=b9c19a5dc68e4561a83de27a145b8ca3;i=44eac;b=fd60666c39eb4d45b944e5ccbd261adc;m=24932a7e;t=57aa195ca0f0b;x=f39d5e1932697ced kernel: 4.18.17-300.fc29.x86_64 package: nautilus-3.30.3-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1660949 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just rebooting after applying new updates including a new kernel. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=e2f7381f8a804bf9b1de225f3df17393;i=107b530;b=ce0232e511d643119b5567d971f49c71;m=2d301df;t=57da61bca2549;x=549bac583eff9ef0 kernel: 4.19.10-300.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Hi, This issue happened during the work. My computer was hanging reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=aa2abb30e2c344cab4b234b0062053d8;i=9d4;b=4de0c3c78aa94143bc0932e829f51bc3;m=25e78b4;t=57e5f132bc7bd;x=208b3e8be95d3284 kernel: 4.19.10-300.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1668887 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Searched for a file on the Overview. The file couldn't be found, and a few seconds later, this crash happened. Searches performed after this initial failure are able to work. This same crash has been happening for the past several weeks (months?) now. reporter: libreport-2.9.7 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=73de7c4090d84bffb08f853ba3da07fa;i=2fb7ce;b=b9e680b6df71468690c1d9c49e3fbe78;m=19848ea2;t=5806220bf8e51;x=abadb5b731f59075 kernel: 4.20.3-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Performed a search on the Overview shortly after booting. I was searching for a program to open, which worked, but typing in the search caused this error to be hit. reporter: libreport-2.9.7 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=73de7c4090d84bffb08f853ba3da07fa;i=3085ad;b=750c6aa1853342ff846125201fd89a76;m=ae7948b;t=580713e176b07;x=225db05475054b73 kernel: 4.20.3-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1671089 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Just after saving a newly created short text with gedit, the notification about nautilus having crashed appeared. After this occurrence I was able to save another text file with gedit without any problems. The only other observation I can add is that I've just updated my test machine overnight from Fedora 28 to 29. reporter: libreport-2.9.7 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=ddec3faa0a8749c78227a90fb50541ad;i=250142;b=322e023445164634918a6ac60467c140;m=1f6b6b7b2;t=580fabe1cf41a;x=9b47d4d7ea039c19 kernel: 4.20.5-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1672114 has been marked as a duplicate of this bug. ***
*** Bug 1672123 has been marked as a duplicate of this bug. ***
*** Bug 1673813 has been marked as a duplicate of this bug. ***
*** Bug 1673910 has been marked as a duplicate of this bug. ***
*** Bug 1677883 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I rebooted and then logged on. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=e2f7381f8a804bf9b1de225f3df17393;i=15a043a;b=0ee14ee398974f0a847424d77ed0ad4f;m=1f5bc67;t=582414a757da0;x=350af72715c4772f kernel: 4.19.15-300.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1678866 has been marked as a duplicate of this bug. ***
Similar problem has been detected: starting operating system and login reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=f4aa837037d34800a378188aa07fe769;i=6251d;b=f6707fd8d05044b19fc6a1a9d65ebad0;m=d33eb45;t=584498c0f4df0;x=8ab6759f48718f64 kernel: 4.20.14-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I typed a few letters to search. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/bin/nautilus --gapplication-service crash_function: g_local_file_query_info executable: /usr/bin/nautilus journald_cursor: s=a91b6c5f62fd48be9d59d913822f4f16;i=c597;b=e6c397ba8d564f2b9c80d7d07d813363;m=5ba82fa3a;t=5854ac9fe29f9;x=60166cd878ca1fe8 kernel: 5.0.5-200.fc29.x86_64 package: nautilus-3.30.5-1.fc29 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1694304 has been marked as a duplicate of this bug. ***
*** Bug 1694415 has been marked as a duplicate of this bug. ***
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.