Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell
42.5-0ubuntu1:
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common
[sudo] password for fabiomirmar:
mutter-common:
Installed: 42.5-0ubuntu1
Candidate: 42.5-0ubuntu1
Version table:
*** 42.5-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main
amd64 Packages
100 /var/lib/dpkg/status
42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64
Packages
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy gnome-shell
gnome-shell:
Installed: 42.5-0ubuntu1
Candidate: 42.5-0ubuntu1
Version table:
*** 42.5-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main
amd64 Packages
100 /var/lib/dpkg/status
42.0-2ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64
Packages
And I have the same issue.
When I apply the scale change I see:
May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]:
vte-spawn-11c0b6cb-a094-4eee-9cbf-7a694348f00a.scope: Consumed 1.272s CPU time.
May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: gnome-terminal-server.service:
Consumed 1.231s CPU time.
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Impossible to set scaling on
crtc 59 to 0.615385, error id 2
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Scalig CRTC 59 at 0.615385 failed
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS"
missing on display ":1".
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor,
using scale 1
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS"
missing on display ":1".
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor,
using scale 1
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Spurious
clutter_actor_allocate called for actor
0x55a6ef3a4ba0/<dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x55a6ef3a4ba0]
which isn't a descendent of the stage!
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowGroup>:0x55a6ee826330] is on because it needs an
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowActorX11>:0x55a6f04896e0] is on because it needs an
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaSurfaceActorX11>:0x55a6f048ca30] is on because it needs an
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning:
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowGroup>:0x55a6ee826330] is on because it needs an
allocation.
May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowActorX11>:0x55a6f0488f00] is on because it needs an
allocation.
May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaSurfaceActorX11>:0x55a6f048cdb0] is on because it needs an
allocation.
When I try to revert I get:
May 25 13:30:34 U-1JSKZM4R9U78P gnome-shell[2862]: Failed to restore previous
configuration: Invalid mode 2560x984 (19.921875) for monitor 'unknown unknown'
May 25 13:30:34 U-1JSKZM4R9U78P gnome-shell[2862]: Failed to use stored monitor
configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown'
May 25 13:30:34 U-1JSKZM4R9U78P gnome-shell[2862]: Failed to use linear monitor
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 25 13:30:34 U-1JSKZM4R9U78P gnome-shell[2862]: Failed to use fallback
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 25 13:30:34 U-1JSKZM4R9U78P gnome-shell[2862]: Impossible to set scaling on
crtc 59 to 1.000000, error id 2
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib: extension "DPMS"
missing on display ":1".
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gsd-color[2980]: could not find device:
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: DING:
(gnome-control-center:3419): display-cc-panel-WARNING **: 13:30:35.541: Config
not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Monitor
mode not found
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: DING:
(gnome-control-center:3419): display-cc-panel-WARNING **: 13:30:35.567: Config
not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Monitor
mode not found
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowGroup>:0x55a6ee826330] is on because it needs an
allocation.
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowActorX11>:0x55a6f0488f00] is on because it needs an
allocation.
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaSurfaceActorX11>:0x55a6f048cdb0] is on because it needs an
allocation.
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowGroup>:0x55a6ee826330] is on because it needs an
allocation.
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaWindowActorX11>:0x55a6f0488f00] is on because it needs an
allocation.
May 25 13:30:35 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views
actor <unnamed>[<MetaSurfaceActorX11>:0x55a6f048cdb0] is on because it needs an
allocation.
--
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/2020782
Title:
Changing display scale setting and reverting it, causes gnome-shell to
error with "Failed to restore previous configuration" and other error
messages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
