Version-Release number of selected component: gnome-shell-3.23.2-3.fc26 Additional info: reporter: libreport-2.9.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _ip_get_path_for_wd executable: /usr/bin/gnome-shell global_pid: 1607 kernel: 4.10.0-0.rc6.git0.1.fc26.x86_64 runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1315318
Created attachment 1247052 [details] File: backtrace
Created attachment 1247053 [details] File: cgroup
Created attachment 1247054 [details] File: core_backtrace
Created attachment 1247055 [details] File: dso_list
Created attachment 1247056 [details] File: environ
Created attachment 1247057 [details] File: limits
Created attachment 1247058 [details] File: maps
Created attachment 1247059 [details] File: mountinfo
Created attachment 1247060 [details] File: namespaces
Created attachment 1247061 [details] File: open_fds
Created attachment 1247062 [details] File: proc_pid_status
Created attachment 1247063 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
staging openQA just ran into something that looks a lot like this on one of the upgrade tests for today's F26 compose: https://openqa.stg.fedoraproject.org/tests/125932 logs and the abrt problem dir can be downloaded from the Logs & Assets tab, the core_backtrace looks a lot like Bill's, running through raise / abort / g_assertion_message / g_assertion_message_expr / _ip_get_path_for_wd / ih_event_callback . This isn't reliably reproducible, I don't think (it hasn't happened in previous runs of the same test, or in other runs of similar tests today).
*** Bug 1474696 has been marked as a duplicate of this bug. ***
*** Bug 1483589 has been marked as a duplicate of this bug. ***
*** Bug 1488148 has been marked as a duplicate of this bug. ***
*** Bug 1494857 has been marked as a duplicate of this bug. ***
*** Bug 1499511 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.