Extra frozen / stuck mouse cursor after auto screen lock / sleep

Bug #1875528 reported by Joel Lisenby on 2020-04-28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)

Bug Description


After my computer had gone to sleep and I log in I should see only a single active mouse cursor.

What happened instead:

After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows.


I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well.

Logging out completely then logging back in again removed the extra frozen cursor.


lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04

apt-cache policy mutter
  Installed: 3.36.1-3ubuntu3
  Candidate: 3.36.1-3ubuntu3
  Version table:
 *** 3.36.1-3ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mutter 3.36.1-3ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 27 19:53:03 2020
InstallationDate: Installed on 2019-03-09 (415 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
 PATH=(custom, no user)
SourcePackage: mutter
UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago)

Joel Lisenby (sven-svenagen) wrote :
affects: ubuntu → mutter (Ubuntu)
tags: added: cursor
Changed in mutter (Ubuntu):
status: New → Confirmed
Piotr Gajdowski (p-a-gajdowski) wrote :

Experiencing same problem, in most cases displays that go into sleep modus (or you turn them off and on again) don't remove themselves from the display driver.
But some displays gets removed form the gpu(or xorg, i don't know) display driver and the re-added.
So basically this happens when you displays are re-arranging cause you added or removed a display (either manually or automatically by the display itself).

This problem is viewable in multi-monitor setup, where 1 monitor is programmed to detach himself from the gpu when going to sleep or off, and the other(s) are just turning the screen black, but stay connected to the gpu.

When you turn off you (problem) display, you actually see linux re-arranging windows/applications on the screen(s) that don't detach themselves from the gpu.
Seeing this happen, I came to this conclusion, that some display detach themselves from the gpu when going to sleep, and therefore linux thinks a display is being removed and re-arranges everything.

During this re-arrangement process a duplicate cursor is created and becomes frozen, a new cursor is created and becomes your primary cursor that behaves normally.

possible fix for this is linux resetting all cursors in xorg/gpu driver when completing such re-arrangement process.

I have zero understanding of xorg or gpu driver programming, but i do know that xorg is programmed to be able to have multiple cursors.
So my suspicion is with xorg programming.

I hope this gets fixed, It's really annoying, when you are working and have tons of apps open, you are required to log out and restart your workspace, which can be a hasle and time consuming.

Joel Lisenby (sven-svenagen) wrote :

With the latest updates installed for Ubuntu 20.04 I am no longer seeing this double mouse cursor issue after two sleeps in a row. Will report back if the issue returns.

samuelbailey (samuelbailey) wrote :

I'm having the same issue - dead cursor appears after machine has gone to sleep when I have multiple monitors connected. I'm on Ubuntu 20.04 and use Wayland, on an AMD GPU. I have updated everything with apt to the most recent version and the issue is still occurring for me.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.