Description of problem: Second logon crash after visiting command line to edit a non relevant file. Version-Release number of selected component: gnome-shell-3.26.1-2.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: clutter_input_device_xi2_get_current_tool executable: /usr/bin/gnome-shell journald_cursor: s=b90cec314c8a4c71a81c89e583170ee3;i=4058d;b=40d3730b60d64e6789bd2b403df670e5;m=da493a83;t=55d175fe15086;x=de52fa56dc43ada0 kernel: 4.13.9-300.fc27.x86_64+debug rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 clutter_input_device_xi2_get_current_tool at x11/clutter-input-device-xi2.c:197 #1 clutter_device_manager_xi2_translate_event at x11/clutter-device-manager-xi2.c:1594 #2 clutter_backend_real_translate_event at clutter-backend.c:596 #3 clutter_x11_handle_event at x11/clutter-event-x11.c:200 #4 handle_host_xevent at backends/x11/meta-backend-x11.c:317 #5 x_event_source_dispatch at backends/x11/meta-backend-x11.c:370 #10 meta_run at core/main.c:648 Potential duplicate: bug 1470160
Created attachment 1347479 [details] File: backtrace
Created attachment 1347480 [details] File: cgroup
Created attachment 1347481 [details] File: core_backtrace
Created attachment 1347482 [details] File: cpuinfo
Created attachment 1347483 [details] File: dso_list
Created attachment 1347484 [details] File: environ
Created attachment 1347485 [details] File: exploitable
Created attachment 1347486 [details] File: limits
Created attachment 1347487 [details] File: maps
Created attachment 1347488 [details] File: open_fds
Created attachment 1347489 [details] File: proc_pid_status
Created attachment 1347490 [details] File: var_log_messages
Similar problem has been detected: virt-manager became unresponsive, followed by a curious partial unresponsiveness of the rest of the gnome shell. I switched to a text virtual terminal and ran gnome-session-logout --no-prompt, with the plan of logging out and back in to recover. Upon switching back to the graphical terminal, rather than being logged out, I see the gnome-shell crashed error reporter, along with all the other windows. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: clutter_input_device_xi2_get_current_tool executable: /usr/bin/gnome-shell journald_cursor: s=e0b405faab47496e985742118651e7d1;i=da0c5;b=4d1e18fb135e4598b52c3e7be02410e9;m=20a354644bc;t=565fef2656e95;x=877f7950c5eb7295 kernel: 4.14.14-300.fc27.x86_64 package: gnome-shell-3.26.2-4.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
This problem was reported in November. The bug may be a collateral problem caused by some other problem. In any event, the problem appears to have disappeared from my use of F27, and i use F27 daily. Twbeckum, has this problem reoccurred for you or can I close this with a Works for me now?
*** Bug 1557618 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.