Missing default cursor

Bug #2063869 reported by Alistair Cunningham
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mutter
Fix Released
Unknown
dmz-cursor-theme (Ubuntu)
Won't Fix
Undecided
Unassigned
mutter (Ubuntu)
Status tracked in Oracular
Noble
Fix Committed
Medium
Daniel van Vugt
Oracular
Fix Released
Medium
Daniel van Vugt

Bug Description

[ Impact ]

In a Wayland session, changing the desktop cursor theme to anything other than Yaru or Adwaita results in a pale grey square as the cursor.

[ Test Plan ]

1. Log into a Wayland session.
2. sudo apt install gnome-tweaks
3. In the Tweaks app under Appearance, select DMZ-white or Redglass cursor theme.
4. Move the cursor over various window edges such that the cursor shape should change.
5. Move the cursor over the top panel.
6. Verify the cursors you see are the expected ones and not just a grey square.

[ Where problems could occur ]

Since the entire cursor selection stack changed both in the lead up to this bug and in fixing it, any aspect of the mouse pointer (cursor) selection logic could be affected. In any app, in both Xorg and Wayland sessions.

[ Other Info ]

The Xorg version of this issue is bug 2062377.

[ Original description ]

After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem:

1. cd /usr/share/icons/DMZ-White/cursors
2. ln -s left_ptr default
3. In gnome-tweaks change to some other mouse pointer.
4. In gnome-tweaks change back to DMZ-White.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: dmz-cursor-theme 0.4.5ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 18:39:40 2024
Dependencies:

InstallationDate: Installed on 2020-07-14 (1382 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: dmz-cursor-theme
UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago)

Revision history for this message
Alistair Cunningham (acunningham) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in dmz-cursor-theme (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
status: New → Won't Fix
Changed in mutter (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in dmz-cursor-theme (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
Changed in mutter (Ubuntu):
importance: Undecided → Medium
status: New → In Progress
milestone: none → noble-updates
Changed in mutter:
status: Unknown → New
tags: added: cursor
Changed in mutter:
status: New → Fix Released
Changed in mutter (Ubuntu):
status: In Progress → Fix Committed
tags: added: fixed-in-mutter-47 fixed-upstream
Changed in mutter (Ubuntu):
milestone: noble-updates → ubuntu-24.10
Changed in mutter (Ubuntu Noble):
assignee: nobody → Daniel van Vugt (vanvugt)
importance: Undecided → Medium
status: New → Triaged
no longer affects: dmz-cursor-theme (Ubuntu Oracular)
no longer affects: dmz-cursor-theme (Ubuntu Noble)
description: updated
Changed in mutter (Ubuntu Noble):
milestone: none → ubuntu-24.04.1
description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 46.2-1ubuntu2

---------------
mutter (46.2-1ubuntu2) oracular; urgency=medium

  [ Marco Trevisan ]
  * Add place-Always-center-initial-setup.patch to always center the
    initial setup window (LP: #2016013)

  [ Daniel van Vugt ]
  * Add backends-Handle-null-views-instead-of-creating-dummy-view.patch
    to prevent "clutter_frame_clock_notify_presented: code should not be
    reached" log spam in some Nvidia Wayland sessions (LP: #1967707)
  * Add backends-Restore-support-for-X11-cursor-themes.patch to restore
    support for X11 cursor themes, which was lost in Mutter 46.0
    (LP: #2062377, LP: #2063869)

 -- Daniel van Vugt <email address hidden> Tue, 25 Jun 2024 15:26:37 +0800

Changed in mutter (Ubuntu Oracular):
status: Fix Committed → Fix Released
Changed in mutter (Ubuntu Noble):
status: Triaged → In Progress
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Alistair, or anyone else affected,

Accepted mutter into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/46.2-1ubuntu0.24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Noble):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-noble
Revision history for this message
Alistair Cunningham (acunningham) wrote :

On that page, I see various packages listed in the "Binary packages built by this source" section. Which one(s) should we download and install for testing?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Alistair Cunningham (acunningham) wrote :

Thank you Daniel. Unfortunately this doesn't seem to fix the problem. I upgraded the packages, and now have:

> root@albatross:/usr/share/icons/DMZ-White/cursors# dpkg -l | grep mutter
> ii gir1.2-mutter-14:amd64 46.2-1ubuntu0.24.04.1 amd64 GObject introspecti
> on data for Mutter
> ii libmutter-14-0:amd64 46.2-1ubuntu0.24.04.1 amd64 window manager libr
> ary from the Mutter window manager
> ii mutter-common 46.2-1ubuntu0.24.04.1 all shared files for th
> e Mutter window manager
> ii mutter-common-bin 46.2-1ubuntu0.24.04.1 amd64 shared programs for
> the Mutter window manager

but there's still no "default" file:

> root@albatross:/usr/share/icons/DMZ-White/cursors# ls -l default
> ls: cannot access 'default': No such file or directory

and if I change the cursor to "Adwaita (default)", and back to "DMZ-White", I still see the grey square when moving the mouse pointer over the desktop or top bar.

As a side note, changing the cursor to "Adwaita (default)", and then switching virtual desktop to my Firefox window seems to crash all my gnome-terminal windows and gnome-tweaks. Going the other direction doesn't. Probably a separate problem. I'll report it if it still happens once we fix this.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There isn't meant to be a "default" file. The dmz-cursor-theme task is marked as "Won't fix" at the top of the page.

Maybe I shouldn't have linked the upstream bug to this one... Can you try the test case written in the Bug Description?

Also crashes should be reported in separate bugs, not here.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Did you reboot after installing the new packages? It seems I forgot to mention that.

Revision history for this message
Alistair Cunningham (acunningham) wrote :

Thank you Daniel. After rebooting, this seems to be working correctly.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Great! In that case the crash you mentioned may have been bug 2062377 which should also be fixed now.

tags: added: verification-done-noble
removed: verification-needed-noble
tags: added: fixed-in-mutter-46.3
removed: fixed-in-mutter-47
tags: added: verification-done
removed: verification-needed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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