GNOME Shell crashes when recording a session with fractional scaling and using a custom cursor

Bug #2077746 reported by Marco Trevisan (Treviño)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Fix Released
Medium
Marco Trevisan (Treviño)
Jammy
In Progress
Medium
Marco Trevisan (Treviño)
Noble
In Progress
Medium
Marco Trevisan (Treviño)

Bug Description

[ Impact ]

When recording a session or sharing it, and a custom cursor is used, then GNOME Shell crashes as soon as the cursor is painted

Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3978

[ Test case ]

- Enable fractional scaling to something that is not an integer scaling (e.g. 150%, 175%...)
- Start recording or sharing your session
  - E.g. Can use https://screenrecorderonline.net/
- Open this page (firefox) https://gitlab.gnome.org/Teams/Design/settings-mockups/-/commit/ff3c8fbbc1d14
  Hover on an image
- Open GIMP and use the color picker in your screen
- The custom cursor should show properly and gnome shell should record it without crashing

[ Regression potential ]

The cursor is not show or it has the wrong scaling

Tags: cursor
Changed in mutter (Ubuntu Noble):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
importance: Undecided → Medium
status: New → In Progress
description: updated
Changed in mutter (Ubuntu Jammy):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
importance: Undecided → Medium
status: New → In Progress
summary: - GNOME Shell crashes when recording a session and using a custom cursor
+ GNOME Shell crashes when recording a session with fractional scaling and
+ using a custom cursor
description: updated
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

The bug has been fixed already in GNOME 47 as part of the commit https://gitlab.gnome.org/GNOME/mutter/-/commit/422ee4515d6ee69705654f8db0dced57673f894f

Changed in mutter (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

If https://gitlab.gnome.org/GNOME/mutter/-/issues/2542 is the upstream issue then the fix went into Mutter 44.0. Noble should be "Fix Released" already.

tags: added: cursor
Changed in mutter (Ubuntu Noble):
status: In Progress → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That same fix is in 42.8 already, meaning Jammy is already fixed too.

If you think it's still not fixed then I can only assume that https://gitlab.gnome.org/GNOME/mutter/-/issues/2542 is NOT the upstream issue(?)

Changed in mutter (Ubuntu Noble):
status: Fix Released → Incomplete
Changed in mutter (Ubuntu Jammy):
status: In Progress → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh OK, it needs two separate fixes. So https://gitlab.gnome.org/GNOME/mutter/-/issues/2542 should not be listed as the upstream issue.

Changed in mutter (Ubuntu Jammy):
status: Incomplete → In Progress
Changed in mutter (Ubuntu Noble):
status: Incomplete → In Progress
description: updated
no longer affects: mutter
Revision history for this message
Robie Basak (racb) wrote :

I'm rejecting two uploads for Noble because they collide between bug 2077746 and bug 2025006 (amongst others). Please coordinate and re-upload just one SRU at once (possibly squashing multiple fixes together as you wish).

Changed in mutter (Ubuntu Noble):
status: In Progress → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in mutter (Ubuntu Noble):
status: Triaged → In Progress
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.