Bug 1747985 - Mouse cursor disappearing when activities is activated and when using the desktop in Gnome
Summary: Mouse cursor disappearing when activities is activated and when using the des...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mousetweaks
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-02 11:49 UTC by David Walther
Modified: 2019-10-25 14:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-25 14:35:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Walther 2019-09-02 11:49:53 UTC
Description of problem:
Mouse cursor disappear when toggling between open programmes.

Version-Release number of selected component (if applicable):
Fedora 30 Linux 5.2.9-200

How reproducible:
In my Dell optiplex 7010 the error is on and off but with the above mentioned kernel something that happens every day. This did not happen before Kernel 5.2.

Steps to Reproduce:
1. Upgrade from kernel 5.1* to 5.2*
2. Activate the Activities "corner" to toggle between programmes.
3.

Actual results:
Occasional mouse cursor disappearance 

Expected results:
Occasional mouse cursor disappearance 

Additional info:
When opening a new program the error temporarily quits.

Comment 1 David Walther 2019-09-04 20:55:48 UTC
I got a kernel update the day after this bug was filed. And for now the bug has not returned.
I'm now on kernel 5.2.11-200.fc30.x86_64

Regards
David Walther

Comment 2 David Walther 2019-09-05 12:32:27 UTC
And now the problem is back again. Still on kernel 5.2.11-200.

Comment 3 David Walther 2019-10-25 13:00:58 UTC
The bug has completely gone after upgrade from kernel 5.2* to 5.3*.
So it was probably not a Gnome error. But it was not present i KDE under 5.2*


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