Version-Release number of selected component: nautilus-3.28.1-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: __libc_sigaction executable: /usr/bin/nautilus journald_cursor: s=ae0fe2b4e4ff45ec876d963e49d7dff1;i=d15b3;b=4c32c4ca7c9f42ef943df870f8b4a75a;m=6b72a3ba0;t=57160d6b9c2b7;x=a9dea6ec85ff530a kernel: 4.17.6-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1462810 [details] File: backtrace
Created attachment 1462811 [details] File: cgroup
Created attachment 1462812 [details] File: core_backtrace
Created attachment 1462814 [details] File: cpuinfo
Created attachment 1462815 [details] File: dso_list
Created attachment 1462816 [details] File: environ
Created attachment 1462817 [details] File: limits
Created attachment 1462818 [details] File: maps
Created attachment 1462819 [details] File: mountinfo
Created attachment 1462820 [details] File: open_fds
Created attachment 1462821 [details] File: proc_pid_status
Created attachment 1462822 [details] File: var_log_messages
*** Bug 1609232 has been marked as a duplicate of this bug. ***
A little piece of info: When I experienced the problem reported in bug 1609232, I tried to connect the same HDD to a USB2 port after the crash. That worked without problems. So, the difference between connecting via USB2 (OK) and USB3 (crash) could mean something?
Similar problem has been detected: When I show the column star , and star a folder (outside documents) reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/nautilus --gapplication-service crash_function: __libc_sigaction executable: /usr/bin/nautilus journald_cursor: s=4250ff6447584229b50fa9f72acd6ee4;i=1a8f;b=f5fa019cf75a4cf891fda068d94b98c5;m=2370968e0;t=5749488826df4;x=614161d7d5cd06e5 kernel: 4.17.14-202.fc28.x86_64 package: nautilus-3.28.1-1.fc28 reason: nautilus killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.