Description of problem: Sp after crashing X (https://bugzilla.redhat.com/show_bug.cgi?id=1535755) by touching the Trust TB-4200 Wireless Scroll Tablet (Aiptek based) by the stylus I've decided to give Wayland a try as well - and the same thing happens as well. So it seems likely to me some common code for input handling is likely where the crash happens and takes the current graphics system down with it. Steps to reproduce the issue 1. add the following into the /etc/udev/hwdb.d/61-evdev-local.hwdb file: ######################################### # Trust ######################################### # Trust Wireless Scroll Tablet TB-4200 # (Aiptek based ?) evdev:input:b0003v08CAp0010* EVDEV_ABS_00=::26 EVDEV_ABS_01=::15 2. run as root: systemd-hwdb update udevadm trigger /dev/input/event* (alternatively just reboot - I've checked and it's not needed to run the two commands first after a reboot to trigger the crash) 3. touch the tablet with the stylus (just drawing a short line is enough) 4. Gnome Shell (which is IIRC a Wayland compositor, right ?) crashes and after a while the login screen shows up Version-Release number of selected component: gnome-shell-3.24.3-2.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: tablet_update_artpen_rotation executable: /usr/bin/gnome-shell journald_cursor: s=24a4982d27604ec2b64aad53527975d2;i=4917;b=6f69ef92530f4a97bc0a8ee1e8772ff1;m=6a3369e;t=56303984df402;x=b8f661e9251ec9e1 kernel: 4.13.5-200.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 tablet_update_artpen_rotation at ../src/evdev-tablet.c:533 #1 tablet_update_rotation at ../src/evdev-tablet.c:570 #2 tablet_check_notify_axes at ../src/evdev-tablet.c:645 #3 tablet_send_events at ../src/evdev-tablet.c:1534 #4 tablet_flush at ../src/evdev-tablet.c:1595 #5 tablet_process at ../src/evdev-tablet.c:1767 #6 evdev_device_dispatch at ../src/evdev.c:830 #7 libinput_dispatch at ../src/libinput.c:1988 #8 dispatch_libinput at evdev/clutter-device-manager-evdev.c:835 #9 clutter_event_dispatch at evdev/clutter-device-manager-evdev.c:857
Created attachment 1382712 [details] File: backtrace
Created attachment 1382713 [details] File: cgroup
Created attachment 1382714 [details] File: core_backtrace
Created attachment 1382715 [details] File: cpuinfo
Created attachment 1382716 [details] File: dso_list
Created attachment 1382717 [details] File: environ
Created attachment 1382718 [details] File: exploitable
Created attachment 1382719 [details] File: limits
Created attachment 1382720 [details] File: maps
Created attachment 1382721 [details] File: open_fds
Created attachment 1382722 [details] File: proc_pid_status
Created attachment 1382723 [details] File: var_log_messages
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.