Although Mustafa says he's not well-versed, he's way smarter than me :) So his comment#26 seems to be much more relevant than what I have to say, but I'd like to reply to Daniel's comment#24/25 anyway:
I saw the details you mentioned on comment #16, and I also have fractional scaling turned off. By "having it off" I'm assuming this [1] is enough, right? Also, I noticed that by previous pasteboard wasn't too clear in showing the problem when I use 42.5-0ubuntu1vv5. I want to clarify that I get a screen as if I had 3 monitors side by side, but all in the same "client monitor". If you try to maximize the application, it picks one of the "screens" and maximizes to it, as we can see here [2]. Even without changing the fractional scale or scale setting, just by having the 42.5-0ubuntu1vv5 packages installed, I get this "triple monitor in 1" situation when I boot my VM. I had to reinstall the original packages from our archives in order to fix this. Also, I just want to make sure you're aware that these are the *mutter* packages that I have installed: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1 amd64 GObject introspection data for Mutter ii libmutter-10-0:amd64 42.5-0ubuntu1 amd64 window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1 all shared files for the Mutter window manager i.e. Just want to make clear that I don't have the "mutter" package installed, but the ones above. Back to your comment, iiuc, the "Impossible to set scaling on crtc 65 to 1.000000, error id 2" means that we're trying to use some incomplete RandR implementation in Xdcv. Isn't it the fractional scaling, that was effectively removed from your 42.5-0ubuntu1vv5 package? In this case, doesn't the errors showing up means that we're still trying to use something that isn't properly implemented in Xdcv? Just for my own information, what's the difference between the vv5 and vv4 builds? Tested with vv4 in a VM: ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.5-0ubuntu1vv4 amd64 GObject introspection data for Mutter ii libmutter-10-0:amd64 42.5-0ubuntu1vv4 amd64 window manager library from the Mutter window manager ii mutter-common 42.5-0ubuntu1vv4 all shared files for the Mutter window manager As soon as I installed it in my VM, I got that "triple monitor" situation again, and then I realized it's really just what you had described, that it automatically enables these other monitors. I can disable them and get back to 1 single monitor. With vv4, I can apply the scale 200% [3] and then revert it, but then it changes my resolution to 800x600. After realizing that, I went back to the vv5 package and re-tested and I notice it's the same behavior as in vv4. After installing it automatically enables all 4 monitors, I have to manually disable them and keep just 1. Then I test the scale to 200% + revert and it does revert, but also changes my resolution to 800x600. I can't really test that in Workspaces, because when it enables the extra monitors, I'm no longer able to access the Workspace with the AWS Workspaces client. If I try to change the scale in Workspaces, I believe it tries to enable the other monitors, and then all I get is a blank screen. And here's the output of "xrandr --verbose" from the VM [5] and the Workspace [6] [1] https://pasteboard.co/qEbvvwijUW2F.png [2] https://pasteboard.co/K9Oh9nZ8wqNk.png [3] https://pastebin.ubuntu.com/p/xkcFScZv5c/ [4] https://pastebin.ubuntu.com/p/mVwWt4Rzsr/ [5] https://pastebin.ubuntu.com/p/JC4PXwdv55/ [6] https://pastebin.ubuntu.com/p/S5bXz975Nn/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails Status in mutter package in Ubuntu: In Progress Bug description: In Amazon Workspaces running Ubuntu 22.04, when attempting to change the Scale in the Gnome Display settings, if you click on a different scale (i.e. changing from 100% to 200%) and hitting apply, it will bring up a prompt asking if you want to keep or revert the changes and there will be a timer of 20 seconds. If you try to revert the changes (either by letting the timer expire or by clicking the "revert" button), we will hit one of the following two behaviors: 1 - The setting won't revert and will keep scaled 2 - gnome-shell will show some error messages in syslog and the display will be "corrupted", where the only window you are able to click is the display setting and if you try to drag it, it will leave a "blur" throughout the window (per discussions, this seems to be https://launchpad.net/bugs/1924689) For both situations, changing the display resolution (i.e. going into and out of full screen in the workspaces client) will fix the issue When hitting situation 1, syslog shows: May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x1080 (19.958942) for monitor 'unknown unknown' When hitting situation 2, syslog shows: May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.000000, error id 2 May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label (0x557090d07de0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 0x557090bee180 == May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0 557093f00e68 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 (2cdac32b2e20 @ 105) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1 557093f00dd8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 (2cdac32a5d80 @ 27) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2 557093f00d58 i resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24) May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor is null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45 Sometimes the stack trace isn't shown, but the symptom is the same: May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on crtc 59 to 1.000000, error id 2 May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib: extension "DPMS" missing on display ":1". I'm unable to reproduce the problem if I manually install ubuntu-desktop and use the Nice DCV Server (as used by Workspaces) by following the steps from (using the xorg-x11-drv-dummy): https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up- installing-linux.html One relevant difference is that Workspaces uses a custom X11 server /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the following process being started: /usr/bin/Xdcv -output 800x600+0+0 -output 800x600+800+0 -output 800x600+1600+0 -output 800x600+2400+0 -enabledoutputs 1 vt2 -displayfd 3 -auth /run/user/541001128/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3 I'm also unable to reproduce the problem using xrdp + Xorg. While discussing this with the desktop crew, it was mentioned that we see the same problems in Xorg. And to a much lesser extent some issues in Wayland too when changing scales. mutter and gnome-shell versions being used: $ sudo apt-cache policy mutter-common mutter-common: Installed: 42.2-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 *** 42.2-0ubuntu1 100 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ sudo apt-cache policy gnome-shell gnome-shell: Installed: 42.4-0ubuntu0.22.04.1 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 *** 42.4-0ubuntu0.22.04.1 100 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
