[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I just tested Ubuntu 22.04 and I can confirm it fixes the issue. First, used 22.04 with the current mutter version available in jammy- updates: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 libmutter-10-0: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 gir1.2-mutter-10: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 And I do hit the error when trying to revert after changing the scale: Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:03:38 U-20CG3JVH1ALS3 gnome-shell[3048]: Xlib: extension "DPMS" missing on display ":1". Then, I upgraded to package from -proposed: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And now the error is no longer logged and I can successfully revert: Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 59 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 61 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 61 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 63 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 63 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 65 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 65 at 1.00 failed Scalig CRTC 65 at 1.00 failed (The errors above can be ignored for now as their are a known problem with Xdcv, which is further explained in comment #16) Marking as verification-done ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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: Xdcv:
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi, Thank you for the package in -proposed. I just tested Ubuntu 22.04 and I can confirm it fixes the issue. First, used 22.04 with the current mutter version available in jammy- updates: user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 mutter-common: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 libmutter-10-0: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 gir1.2-mutter-10: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-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 And I do hit the error when trying to revert after changing the scale: Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:40:40 U-2RVWD6LKXR3GE gnome-shell[3186]: Xlib: extension "DPMS" missing on display ":1". Then, I upgraded to package from -proposed: user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user0: mutter-common: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu3 Candidate: 42.9-0ubuntu3 Version table: *** 42.9-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And now the error is no longer logged and I can successfully revert: Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 59 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 61 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 61 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 63 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 63 at 1.00 failed Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on crtc 65 to 1.00, error id 2 Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: Scalig CRTC 65 at 1.00 failed (The errors above can be ignored for now as their are a known problem with Xdcv, which is further explained in comment #16) Marking as verification-done ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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: Xdcv: Changing
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2 with Jammy. I'll test again when 42.9-0ubuntu3 is available in -proposed. -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I've tested the mutter packages from -proposed in an AWS Workspace: https://pastebin.ubuntu.com/p/9Yvgfs7yZr/ And I'm able to successfully change the scale to 200% and then revert the setting. The following messages are logged when changing to 200%: https://pastebin.ubuntu.com/p/Y5QdXSqcsW/ And then when you try to revert: https://pastebin.ubuntu.com/p/cYP7JKryx9/ -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
For completeness: re: the Lunar issue that I mentioned in comment #22 and that Andreas suggested me to file a separate bug (on comment #28): I tested a freshly installed Lunar VM, and also did 'apt upgrade' everything in my previous Lunar VM (where I was originally hitting the problem I mentioned) and I'm no longer seeing an issue on switch user, so I'm going to hold on filing another bug. I believe that problem is already resolved with newer Xorg version. I'll file a different bug in case I hit the problem again in the future. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Thank you very much for the great job narrowing this, Daniel! -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Daniel, Regarding 3 (the blank screen issue when enabling a monitor): I can confirm that the issue happens when you're using Workspaces client 5.9.0.4129 (Windows client version) and no longer happens (even with Xdcv + Gnome) in 5.10.0.4196. And, by checking the client release notes [1]: "Resolved black screen issue when using multiple monitors with Ubuntu WorkSpaces" [1] https://docs.aws.amazon.com/workspaces/latest/userguide/amazon- workspaces-windows-client.html#windows-release-notes Regards, Fabio Martins -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you will also need to look at the details shared by Daniel in his comment #16. Otherwise, even if we fix the zero hz issue, you will be able to change/revert scale, but will also need to make sure fractional scaling is disabled. -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Daniel, A few items to make sure I'm on the same page: 1. So, IIUC, you're saying that the "final fix" should be the vv5 package, which contains the fix to the zero hz bug (loosening mutter to accept zero-Hz, as this is the bogus refresh rate being reported by Xdcv) + the caveat for AWS to either fix Xdcv or never try to enable Fractional scaling in the instance (details in your comment#16), is that so? 2. Regarding your comment on bug 1857392 and bug 2007742 being present, iiuc they do not have a noticeable impact (other than spamming the log). 3. Also, I need to mention that I went ahead and tried once more the vv5 package on a AWS Workspace, and I can no longer reproduce the blank screen. Now I see these logs [1] and the scale does get reverted from 200% to 100%. https://pastebin.ubuntu.com/p/JpVsjbQzsQ/ 4. If 1 above is correct, then where (if anywhere) we are going to investigate the situation where vv5 causes the other monitors to get automatically enabled? Regards, Fabio Martins -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1 --auto" to enable another
monitor using Budgie and Xfce (I believe none of them use mutter), and I
can't reproduce the "blank screen". It doesn't really do anything, but
also doesn't reproduce the blank screen issue.
This is what I see in Xfce:
https://pastebin.ubuntu.com/p/BNs9KJqbHz/
And Budgie:
https://pastebin.ubuntu.com/p/pKTGzJb8bN/
My previous suggestion (patch with zero hz fix + no fractional scaling)
was because I thought vv1 was also exposed to the issue you mentioned on
comment #19 ("fractional scaling patch is trying to implement the revert
using fractional scaling"), but I guess not, and it still fails with the
"Invalid mode 800x600 (-nan)" errors, which is the zero hz issue, and
led us to vv2 and then vv4.
So, the current situation is that either with vv4 (zero hz patch + no
fractional scaling) OR vv5 with fractional scaling disabled (zero hz
patch included) we get to the situation where the extra monitors are
automatically enabled and the resolution is changed to 800x600:
https://pastebin.ubuntu.com/p/k822YMHM5v/
And IIUC this is what needs to be investigated next.
And no need to apologize if not able to respond this daily, completely
understandable and you're already doing a lot for this bug. Thank you
very very much for that!
I'll also be OoO for the next couple of days, back on Monday anyway.
Cheers,
Fabio Martins
--
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:
Xdcv: Changing display scale setting and reverting it fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
> Try logging into a non-GNOME Xorg session on Workspaces > if you can. Then use the 'xrandr' command to set a mode > to turn on one of the unused virtual monitors. If that > causes the DCV client to go blank then we have proven > it's not mutter's fault. I did test that with a Cinnamon session and confirmed it. I basically did: xrandr --output VNC-output-1 --auto and it immediately goes to a blank screen OK, so saying out loud my understanding of this issue so far, so as to check it's correct. The problems are: - Fractional scaling is supported in RandR 1.3 or newer - Xdcv reports its RandR version is 1.6, but when you try to use fraction scaling it errors (error id 2) - The corruption bug 1924689 may be caused by the fractional scaling patch (or a side effect of the "error id 2"?) - Xdcv is reporting a bogus refresh rate - There's a "config history" issue identified by Mustafa in comments #26 and #30 What we've been doing now to try to narrow it down is: A - The "Zero Hz" fix is basically loosening mutter to accept zero-Hz, as this is the bogus refresh rate being reported by Xdcv B - vv4 fix = no fractional scaling + "zero Hz" fix C - vv5 fix = re-adds fractional scaling + "zero Hz" fix And out of it, we've confirmed in local VM / Workspaces tests that 1 - Without fractional scaling patch (vv4) / with fractional scaling disabled, we can't reproduce the "Failed to restore previous configuration: Invalid mode" / "Impossible to set scaling on crtc" errors 2 - The "Zero Hz" fix causes a side-effect of enabling the unused monitors (tbd if this is a bug) 2a. If you manually disable 3 monitors (keeping only one) and then try to apply / revert 200% scale, it errors [1] and sets resolution back to 800x600 3 - When enabling unused monitors in Workspaces, we get a blank screen (which I've confirmed through cinnamon / xrandr that it must be a problem with the Workspaces client when enabling a monitor) For the "zero Hz" problem, if I understand correctly, it is a bogus issue without a noticeable impact in usage. On the other hand, due to the "zero Hz" fix introducing problems 2 and 2a above, I'm skeptical on validating that avoiding fractional scaling fixes our issue (item 1 above). If the "zero hz" issue is really just bogus, should we try a "vv6" build completely disabling fractional scaling for the Xdcv use case (on apply and revert), but not including the "zero hz" fix? This way we would be able to validate item 1 above (even if we see the zero hz bogus messages, which we can ignore for now). If this succeeds, we can investigate the item 3 above separately, so we can then re-introduce the "zero hz" fix. [1] https://pastebin.ubuntu.com/p/Xtyfvb3CV2/ -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
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 amd64GObject introspection data for Mutter ii libmutter-10-0:amd6442.5-0ubuntu1 amd64window 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.00, 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 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.5-0ubuntu1vv4 amd64window 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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020782 Title: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Daniel, For when you have a chance, we've discussed this bug a bit in #ubuntu- release in Libera.Chat. The SRU team would like to hear your opinion on SRU'ing this fix for lunar, and your comments above on mentioning that it's unlikely to be useful vs. what you mentioned previously of this being a general bug. I would appreciate it if you can chime in and add your comments, so we can unblock this SRU. Regards, Fabio Martins -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Hi Daniel, Thanks again. Tested 42.5-0ubuntu1vv5 When I apply the 200% scale: https://pastebin.ubuntu.com/p/MfS9vpT6KB/ When I revert it: https://pastebin.ubuntu.com/p/SHtvrXyPkY/ And then I get this situation (possibly due to what you mentioned on the settings app attempting to enable the 4 monitors): https://pasteboard.co/kLUbb5XWlwAQ.png The tests above were in a qemu VM in my laptop + DCV. I also tested it in an AWS Workspace and I believe the situation is similar. When I change scale to 200%: https://pastebin.ubuntu.com/p/DgkB3rngvj/ When I revert it: https://pastebin.ubuntu.com/p/H4nJC4MmKW/ And the screen in the Workspaces client gets all blank and there's no place to click. Even if I try to resize the client screen (which would force Xdcv to change the resolution) I can't get back to the workspace. Only way to fix it is to close and reopen the client. -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Daniel, Thanks for chiming in. I've tried reproducing this bug outside of DCV, but no lucky. What I tried last is to launch a baremetal instance on AWS (g4dn.metal) with the same Nvidia GPUs as the instance type where we are consistently able to reproduce this problem, and then I: 1. Installed KVM 2. Created a Jammy VM (just to see if I would be able to reproduce it, and then I would do the same for Lunar) 3. Added an Nvidia GPU to the VM with PCI passthrough 4. Installed the nvidia driver 5. Setup desktop with Xorg (and gdm3 with Xorg) the same way we've been doing with the AWS VM 6. Tried to reproduce the problem by installing skype snap or running 'sudo udevadm trigger' However, I'm unable to reproduce this problem, even in a Jammy VM (when not using DCV). You mentioned "then simply verifying the patch is present would suffice", how would I do that? Just showing tha gdm3 from -proposed is enough? If so, I did setup a Lunar VM the same way (also with the same Nvidia GPU) and did the basic tests: One thing to notice is that "apt install gdm3" wouldn't upgrade the package to the one in -proposed: https://pastebin.ubuntu.com/p/FDdFfcPHDd/ So, I had to specify the version: https://pastebin.ubuntu.com/p/Kq7Zj9wxH2/ Not sure if this is a problem. Anyway, after that I rebooted the VM and did the basic tests: Packages installed from -proposed: https://pastebin.ubuntu.com/p/ZTxYTSQD3v/ - Logged in as ubuntu user and launched Firefox, LibreOffice and gedit: https://pastebin.ubuntu.com/p/xBJXTG6NgP/ - Switched user to fabiomirmar and opened Thunderbird, skype and gnome- calculator: https://pastebin.ubuntu.com/p/RSCxqCGcrH/ - Switched back to the ubuntu user and I see its apps are still running: https://pastebin.ubuntu.com/p/j4kBKF3bXp/ - Once again, switched back to fabiomirmar, and the processes are also running: https://pastebin.ubuntu.com/p/q9TJFJhQgp/ Also tested the "init 3" / "init 5" tests you mentioned. After the tests mentioned above, I switched to multi-user.target: https://pastebin.ubuntu.com/p/VkrkdwXcbt/ Then went back to graphical.target: https://pastebin.ubuntu.com/p/7X8VyydPGz/ Another feedback that I have to share, is that although it's not consistent, on Lunar sometimes the session (gnome?) crashes when you are logging back in after switching user. i.e.: you login as ubuntu, open one or more apps (such as firefox), hit "switch user" and try to login again. Most of the times, it will work and firefox will be running, but sometimes the session crashes and you are brought back to gdm and have to login again. After logging back in, Firefox is no longer there. The logs during the crash are available here: https://pastebin.ubuntu.com/p/bfRQnrhFNG/ However, I don't think this is related to the GDM patch from Ghadi, as I'm able to reproduce the very same problem with gdm from lunar/main from a fresh installation: https://pastebin.ubuntu.com/p/bSH7mwVTtB/ I think this might need its own launchpad bug, but leaving my comment with the details here, so that others can share their feedback. Also, not marking this as verification-done for lunar, but I think it's done :) Regards, Fabio Martins -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I was getting some inconsistent and confusing results on my tests, so I decided to start from scratch with a fresh VM (qemu) and also a fresh Workspace (AWS). In a freshly installed Jammy VM (on qemu, not AWS), out of the box we have factional scaling disabled, so I tried changing scale to 200% and I do hit the error (but the scale DOES change): https://pastebin.ubuntu.com/p/yVwnmqbTTJ/ When I try to revert, I hit the error again and gnome freezes: https://pastebin.ubuntu.com/p/nYpqJDmr5x/ I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the VM When I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/V7MmKCjc4W/ And also when trying to revert it (gnome freezes): https://pastebin.ubuntu.com/p/dbWZFQGr9t/ Package versions: https://pastebin.ubuntu.com/p/c4WsgPVnxr/ Also did the same tests with a fresh Workspace: Tested the very same thing in a Workspace: Out of the box fractional scaling is disabled, so I tried changing scale to 200% and I hit the error (but it does change): https://pastebin.ubuntu.com/p/gSZ5rfm7vF/ When I try to revert, I hit the error and then it causes the problem reported in https://launchpad.net/bugs/1924689: https://pastebin.ubuntu.com/p/NHY62YvxCG/ (So both Workspaces and local VM hit the same problem, but when reverting Workspaces will hit LP#1924689 and the local VM will freeze gnome) I then rebooted the Workspace without upgrading any package and tried the same steps again, and I still have the same problem. I then upgraded the packages in the PPA: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade Rebooted the Workspace, and I still hit the error both when trying to change the scale to 200% (still does change it, though): https://pastebin.ubuntu.com/p/977wzx6sxW/ And when I try to revert: https://pastebin.ubuntu.com/p/D2VZv2J7QV/ Packages: https://pastebin.ubuntu.com/p/mDKy4wWyWZ/ So, unless I'm missing something, apparently the same problem happens with fractional scaling disabled and also with the packages from the PPA. -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
I'm not sure how can we verify lunar. There's no DCV available for non- LTS releases, and there's no known way of reproducing this issue without DCV. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Hi Andreas, I'm sorry, I missed your request for the additional tests. Just did them for Jammy. Adding here: - Logged in as ubuntu user and launched Firefox, LibreOffice and gedit: https://pastebin.ubuntu.com/p/H3WVmVkgJh/ - Switched user to fabiomirmar and opened Thunderbird, skype and gnome-calculator: https://pastebin.ubuntu.com/p/By3q2kf8Nq/ - Switched back to the ubuntu user and I see its apps are still running, and so are the processes for the fabiomirmar user: https://pastebin.ubuntu.com/p/DxMtJ2MVnN/ Also tested the "init 3" / "init 5" tests you mentioned. After the tests mentioned above, I switched to multi-user.target: https://pastebin.ubuntu.com/p/DXPjRYsfQC/ Then went back to graphical.target: https://pastebin.ubuntu.com/p/3ghpd2VtVZ/ Marking verification-done-jammy. Let me know if I missed anything. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020641] Re: Installing or removing apps through snap-store launches another gdm session
Hi, I've been able to verify that the package in -proposed fixes the issue for Jammy: Before applying the patch we have: https://pastebin.ubuntu.com/p/KphZJjZRsb/ when attempting a "sudo snap disconnect skype:opengl :opengl" we can see the gdm session being launched: https://pastebin.ubuntu.com/p/hSk3xRWxnz/ After installing gdm3 from proposed: https://pastebin.ubuntu.com/p/MGcQmf6gzs/ Attempted the same "snap disconnect skype:opengl :opengl": and I no longer see another gdm session being launched: https://pastebin.ubuntu.com/p/f4qWHtrzxN/ Also tested with "udevadm trigger" (which is ultimately called by snap connect/disconnect and triggers the issue) and I can't reproduce the problem anymore: https://pastebin.ubuntu.com/p/4zdmPd5bSH/ Marking verification-done-jammy. I'll verify lunar tomorrow. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2020641 Title: Installing or removing apps through snap-store launches another gdm session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020641/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
Thanks for the investigation Daniel. Indeed my inability to change the scale with the first patch was due to low resolution in my client machine. Interesting enough, I tried reproducing this in a Local VM with Xdcv (with just regular mutter packages, straight from our archives, no PPA), and I'm unable to reproduce the problem when I disable fractional scaling. I'm able to change to 200% and then revert properly. Given that I'm unable to reproduce there, I went back to an AWS Workspace and installed your new 42.5-0ubuntu1vv2 package and I'm still able to reproduce the problem when reverting it: May 31 20:17:42 U-3JQHCWI1WR5QW geoclue[2660]: Service not used for 60 seconds. Shutting down.. May 31 20:17:42 U-3JQHCWI1WR5QW systemd[1]: geoclue.service: Deactivated successfully. May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Impossible to set scaling on crtc 59 to 1.00, error id 2 May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Xlib: extension "DPMS" missing on display ":1". May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-0' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-1' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-2' does not exist May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: property match 'XRANDR_name'='VNC-output-3' does not exist -- 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: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
I also tested Daniel's mutter package with: sudo add-apt-repository ppa:vanvugt/mutter sudo apt update sudo apt upgrade And rebooted the Workspace just in case. I know Mustafa mentioned he was still able to reproduce the issue. In my case, I wasn't but on the other hand, I can't do the action that would allow me to reproduce it. When I go to display settings, I don't have an option to change the scale, but I do have the option to enable "Fractional Scaling", but if I enable it, I don't have an apply button to enable it, so this never gets enabled and doesn't get to a situation where I can change/revert the scale to see if I would be able to reproduce the issue or not. -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Hi Daniel, I'm not with the SEG team and I would need assistance from someone building that and providing the debs or a ppa. I've also subscribed Mustafa, from SEG, to this bug, as he's assisting me investigating this issue. Regards, Fabio Martins -- 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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
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/[: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 [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [:0x55a6f04896e0] is on because it needs an allocation. May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views actor [: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 [:0x55a6ee826330] is on because it needs an allocation. May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]:
[Bug 2020782] [NEW] Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages
Public bug reported: 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.00, 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.00, 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.
[Bug 683725] Re: When I format an usb key, after remount it opens the empty device twice.
Thank you for filing this bug. I tried to reproduce it in Xenial, but it seems this behavior is no longer happening and very likely is already fixed, so I'm closing this bug as invalid. This is also a duplicate of 686780. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/683725 Title: When I format an usb key, after remount it opens the empty device twice. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/683725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 686780] Re: USB format opens two nautilus windows
Thank you for filing this bug. I tried to reproduce it in Xenial, but it seems this behavior is no longer happening and very likely is already fixed, so I'm closing this bug as invalid. This is also a duplicate of 683725. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/686780 Title: USB format opens two nautilus windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/686780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334806] Re: nautilus disappear desktop icons and freeze open folders on jaunty
We are closing this bug report as it is related to a no longer supported version of Ubuntu + Kernel + Nautilus and this issue has not been observed in any recent and supported releases. ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/334806 Title: nautilus disappear desktop icons and freeze open folders on jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/334806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
