Bug 1598077 - [abrt] gnome-shell: clutter_input_device_xi2_get_current_tool(): gnome-shell killed by SIGSEGV
Summary: [abrt] gnome-shell: clutter_input_device_xi2_get_current_tool(): gnome-shell ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:60351fc1ce8bc9654350ad03fa9...
: 1639768 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-04 09:46 UTC by Arthur S.
Modified: 2019-05-28 22:56 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:56:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (100.98 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: cgroup (331 bytes, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: core_backtrace (34.03 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: cpuinfo (1.76 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: dso_list (9.83 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: environ (3.30 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: exploitable (112 bytes, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: limits (1.29 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: maps (104.96 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: mountinfo (4.38 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: open_fds (6.23 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details
File: var_log_messages (6.37 KB, text/plain)
2018-07-04 09:46 UTC, Arthur S.
no flags Details

Description Arthur S. 2018-07-04 09:46:29 UTC
Description of problem:
The desktop froze suddenly. This happens about once or twice a day (though I can't be certain it is the same issue as this is the first time I get a crash report), seemingly at random, and more frequently when heavily loaded. 
If I can switch to a tty and kill some apps it usually fixes it (this is what I did here), but most of the time even that doesn't work and I have to reset the machine - and there is nothing that looks useful in the logs after rebooting.

Version-Release number of selected component:
gnome-shell-3.28.2-1.fc28

Additional info:
reporter:       libreport-2.9.5
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=aa3066ec12e845e09fb4531f56017617;i=184f;b=339dde364125406c8d4d323b40223cc5;m=1148160e11;t=5702884c14566;x=98bee2b4e0c5e6cb
kernel:         4.17.2-200.fc28.x86_64
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:292
 #1 clutter_device_manager_xi2_translate_event at x11/clutter-device-manager-xi2.c:1497
 #2 clutter_backend_real_translate_event at clutter-backend.c:597
 #3 clutter_x11_handle_event at x11/clutter-event-x11.c:200
 #4 handle_host_xevent at backends/x11/meta-backend-x11.c:383
 #5 x_event_source_dispatch at backends/x11/meta-backend-x11.c:436
 #10 meta_run at core/main.c:664

Potential duplicate: bug 1509406

Comment 1 Arthur S. 2018-07-04 09:46:34 UTC
Created attachment 1456447 [details]
File: backtrace

Comment 2 Arthur S. 2018-07-04 09:46:35 UTC
Created attachment 1456448 [details]
File: cgroup

Comment 3 Arthur S. 2018-07-04 09:46:37 UTC
Created attachment 1456449 [details]
File: core_backtrace

Comment 4 Arthur S. 2018-07-04 09:46:38 UTC
Created attachment 1456450 [details]
File: cpuinfo

Comment 5 Arthur S. 2018-07-04 09:46:39 UTC
Created attachment 1456451 [details]
File: dso_list

Comment 6 Arthur S. 2018-07-04 09:46:41 UTC
Created attachment 1456452 [details]
File: environ

Comment 7 Arthur S. 2018-07-04 09:46:42 UTC
Created attachment 1456453 [details]
File: exploitable

Comment 8 Arthur S. 2018-07-04 09:46:43 UTC
Created attachment 1456454 [details]
File: limits

Comment 9 Arthur S. 2018-07-04 09:46:45 UTC
Created attachment 1456455 [details]
File: maps

Comment 10 Arthur S. 2018-07-04 09:46:46 UTC
Created attachment 1456456 [details]
File: mountinfo

Comment 11 Arthur S. 2018-07-04 09:46:47 UTC
Created attachment 1456457 [details]
File: open_fds

Comment 12 Arthur S. 2018-07-04 09:46:49 UTC
Created attachment 1456458 [details]
File: proc_pid_status

Comment 13 Arthur S. 2018-07-04 09:46:50 UTC
Created attachment 1456459 [details]
File: var_log_messages

Comment 14 Leslie Satenstein 2018-08-02 15:36:08 UTC
Similar problem has been detected:

Installed new gnome extensions from Florian M.

reporter:       libreport-2.9.5
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=e1116363aa4a4089a6140c0eaf719a20;i=ef6c;b=c285737a25c34542a27227f205488742;m=1ec10e2d0;t=572755e26ab2f;x=d4f9477f45ba3d82
kernel:         4.17.9-200.fc28.x86_64
package:        gnome-shell-3.28.3-1.fc28
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Leslie Satenstein 2018-08-05 14:37:52 UTC
Similar problem has been detected:

Black screen.  Could be caused by an extension, but I think not. No extension is doing any waits or related actions.

reporter:       libreport-2.9.5
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=72e1c4abffb245a0b49a0d57836623f7;i=91db;b=0b1fd05c3b2e41e88ac3a1277d938d39;m=85fba8f;t=572b0e46f9435;x=bc1058078d117dff
kernel:         4.17.11-200.fc28.x86_64
package:        gnome-shell-3.28.3-1.fc28
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Matt Burgess 2018-10-16 14:44:43 UTC
*** Bug 1639768 has been marked as a duplicate of this bug. ***

Comment 17 Ben Cotton 2019-05-02 20:37:31 UTC
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.

Comment 18 Ben Cotton 2019-05-28 22:56:38 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.