FS#54152 - [mesa] Strange pixelated line follows cursor in GNOME Shell areas

Attached to Project: Arch Linux
Opened by Deactivated account (TechnicalTotoro) - Sunday, 21 May 2017, 21:41 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 10:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I have found that since I upgraded from the previous version to 17.0.5-1 and now to 17.1.0-1 that some times when my cursor goes over the top bar or is in the Activities Overview that it has a strange pixelated line following it. I can't seem to take a screenshot of it since the GNOME screenshot utility doesn't capture the cursor nor this strange long pixelated line which is thin but not completely solid and made of many seemingly random colours. I have GNOME version 3.24.2.

I don't know that this was the case before, but just now it happened because one of my VMs was using 100% of my RAM and my Swap space started filling up. The strange line disappeared after I clicked the Firefox icon from the dock and it launched. The strange line didn't appear on the desktop though, nor in any other application, just the top-bar, AO, and the dock which I have not just in the AO due to the Dash To Dock GNOME extension.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 10:12 GMT
Reason for closing:  No response
Comment by Deactivated account (TechnicalTotoro) - Saturday, 27 May 2017, 14:19 GMT
It seems that they don't have to always follow the cursor around, but in my case their normally do, I have attached an example of when they are just on one part of the screen. The weird pixelation is just on top of the "Processes" tab button in the System Monitor.
Comment by Laurent Carlier (lordheavy) - Saturday, 02 June 2018, 07:12 GMT
Is it fixed with current mesa/xorg-server ?
Comment by mattia (nTia89) - Wednesday, 06 November 2019, 15:08 GMT
I cannot reproduce this issue;
I propose to close the bug

Loading...