*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
I don't think there is an official solution to this yet, however, in my
Ubuntu 20.04 (and then also 20.10) installation I was able to
automatically fix it every login by using this very small program I
devel
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
Travis solution worked however after the next reboot the problem
reappears. Any idea how to fix it permanently?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
I was able to get rid of this by changing the display scaling back to
100% and than I resumed the display scale that I had wanted.
--
You received this bug notification because you are a member of Ubuntu
D
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052
** This bug is no longer a duplicate of bug 1827428
Mouse cursor left frozen copy of itself
** This bug has been marked a duplicate of bug 1873052
GNOME 3.36 Lands Scaled/Transformed Hardware Cursors S
*** This bug is a duplicate of bug 1827428 ***
https://bugs.launchpad.net/bugs/1827428
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 1827428 ***
https://bugs.launchpad.net/bugs/1827428
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1827428, so it is being marked as such. Please look
** No longer affects: gnome-session (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1829221
Title:
second, dead, mouse pointer left on screen after login, x11 session
To ma
It does appear to be related to the xrandr scaling experimental feature,
after all. Revert that to default and the issue disappears. Guessing
that probably makes it a mutter bug, and being of an experimental
feature at that is hopefully of interest to someone but not urgent. In
view of that didn't
