Bug 1716771
| Summary: | Interacting with a wacom pen triggers gnome shell crashes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Peter Hutterer <peter.hutterer> |
| Component: | gnome-shell | Assignee: | Carlos Garnacho <cgarnach> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | Apurva Bhide <abhide> |
| Priority: | unspecified | ||
| Version: | 8.0 | CC: | abhide, bperkins, cgarnach, cschalle, fmuellner, jadahl, jkoten, mboisver, mclasen, rstrode, tpelka, wchadwic |
| Target Milestone: | rc | Flags: | tpelka:
mirror+
|
| Target Release: | 8.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
.Interacting with a `wacom` pen works on the gnome shell
Previously, interacting with the shell frequently triggered the backtrace and the gnome shell was unresponsive. As a consequence, the stylus tip was not working, the stylus cursor was hidden whenever scrolled over a window, and the mouse button stopped working. With this update, `gnome-shell-3.32.2-9.el8` package is added in RHEL 8.1. As a result, interacting with the `wacom` does not make the gnome shell unresponsive.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-05 22:14:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1678350 | ||
|
Description
Peter Hutterer
2019-06-04 05:43:16 UTC
upstream fix: https://gitlab.gnome.org/GNOME/gnome-shell/issues/540 I cannot reproduce this issue on gnome-shell-3.32.2-9.el8. I can't reproduce this anymore either, thanks! gnome-shell-3.32.2-9.el8.x86_64 mutter-3.32.2-10.el8.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3553 |