This bug was fixed in the package mutter - 42.9-0ubuntu4
---
mutter (42.9-0ubuntu4) jammy; urgency=medium
* Add Revert-data-udev-Don-t-disable-KMS-modifiers-on-newer-i91.patch
to fix rendering failures on older kernels (5.15) when run on newer
hardware (Intel Alder Lake).
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:
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
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
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782
Title:
Xdcv: Changing display scale setting
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.
Actually, we're uploading a new version to jammy-proposed 42.9-0ubuntu3
so you can wait and test that version.
--
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:
Fabio, just to be clear, could you be specific about what version of
Ubuntu you were using and what version of mutter you had installed?
If this update has fixed the issue here, you can also change the bug tag
from verification-needed-jammy to verification-done-jammy
--
You received this bug
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/
Hello Fabio, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- 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
Jammy fix proposed in:
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/98
--
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
We only just noticed a similar fix was upstreamed already in mutter 43.0:
https://gitlab.gnome.org/GNOME/mutter/-/commit/16af2e407b49cd4464935a6f9b4efdc32f1339e5
** Also affects: mutter (Ubuntu Mantic)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
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
** Tags removed: xrandr-scaling
--
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
I think this is good enough Daniel. Thanks!
--
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
In the absence of ~/.config/monitors.xml (meaning the user has never
pressed the 'Keep Changes' button), Mutter will start up in a linear
layout with all monitors turned on. I think you can sometimes see this
on Xdcv login (and always see it on Xorg login), but for some reason the
secondary
I can reproduce "other monitors getting turned on at Revert" using
upstream Mutter on Xorg. Seems it's something of a feature because
Mutter only supports:
(a) An explicit monitor layout in ~/.config/monitors.xml ; or
(b) An implicit monitor layout where everything gets turned on and arranged
Also the virtual monitors turning on at revert stops happening if you
get your config file (~/.config/monitors.xml) to a state where the
secondary monitors are explicitly listed as . So there is a
difference between the default mutter config when monitors.xml doesn't
exist, and when they are
Looking at this again, I'm now testing an even smaller patch (named
vv6):
@@ -92,6 +92,9 @@ calculate_xrandr_refresh_rate (XRRModeIn
float h_total;
float v_total;
+ if (xmode->hTotal == 0 || xmode->vTotal == 0)
+return 0.0f;
+
h_total = (float) xmode->hTotal;
v_total = (float)
Great! I didn't think the black screen issue was caused by 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/2020782
Title:
Xdcv: Changing display scale setting and reverting
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]:
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.
About the following issue we can definitely take a look at it.
> - Xdcv is reporting a bogus refresh rate
That's an Xdcv bug which is probably also intentionally a design
feature. I think it should be fixed in Xdcv because this design will
break other compositors like it has broken mutter.
1. No I don't think vv5 is the final fix, which is why the upstream fix
is marked as Draft still:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3062
2. Correct. Those "logspam" bugs are just noise and can be ignored:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=logspam
3. It's not
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
Those logs from Xfce and Budgie look surprising to me. They don't prove
that the DCV viewer/server bug doesn't exist there because they seem to
have failed to turn on VNC-output-1. So the bug probably still exists in
DCV viewer/server but hasn't been triggered yet. Maybe you need to
select the
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
Also apologies - I don't have time to work on this bug every day. I
expect to get back to it some time next week.
--
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:
There's no need for a vv6 "completely disabling fractional scaling"
because that's the first thing we already tried in vv1 and it didn't
work as mentioned in comment #11. If you want to test it again then see
https://launchpad.net/~vanvugt/+archive/ubuntu/mutter/+build/26236293
> I did test that
> 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
I've also tested the "vv5" package in a fresh VM and can confirm that
zero hz is now supported, and now facing the same scenario where
multiple monitors are automatically enabled.
Another issue that still stands is the "config history" issue I've
mentioned. If you exclusively change the
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.
--
You received this bug notification because you
> 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?
For safety's sake I would recommend having Fractional Scaling disabled
before you log in, or logging in again after disabling it.
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.
Hello Daniel,
I've also been debugging this issue and noticed something weird while
reproducing it. It seems that resizing the screen via resizing the NICE
DCV client does not invoke the `meta_monitor_config_manager_set_current`
method, so the current config and the history are untouched.
Let's
BTW, what does this command return in an AWS Workspace? Any different to
the VM?
xrandr --verbose
--
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
The only relevant log messages I can see there are:
Impossible to set scaling on crtc 65 to 1.00, error id 2
Window manager warning: Scalig CRTC 65 at 1.00 failed
which is a bug in Xdcv as detailed in comment #16. Remember to keep
fractional scaling turned off.
To see if it's
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
Upstream fix proposed:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3062
You can test it in:
https://launchpad.net/~vanvugt/+archive/ubuntu/mutter/+build/26285012
Caveat:
The Settings app seems to want to turn on the three unused (usually off)
virtual monitors when revert succeeds. I
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Nevermind, "vv3" still has the bug. BTW, it seems to reproduce more
reliably if you delete ~/.config/monitors.xml before logging in.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Please try the "vv3" packages:
https://launchpad.net/~vanvugt/+archive/ubuntu/mutter/+build/26282399
--
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
Oh actually the logs you provided in comment #17 suggest that the
fractional scaling patch is trying to implement the revert using
fractional scaling (which will fail on Xdcv) even when the feature is
disabled. So it sounds like I need to make a new PPA revision that has
both the changes of vv1
Yeah I know, mentioned in comment #11:
> * I can still reproduce the failure to revert when using the PPA
version 42.5-0ubuntu1vv1 (fractional scaling support removed, so using
integer scaling).
What I was trying to say in comment #16 is not that fractional scaling
was the cause of this bug, but
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%
Yes I think when using Xdcv we just need to make sure fractional scaling
is ALWAYS DISABLED and ignore any bugs that occur if it is enabled, for
the time being. :(
While Xdcv reports its RandR version is 1.6, when you try to actually
use it (you can test with xrandr --scale or --transform) it
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
** Changed in: mutter (Ubuntu)
Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)
--
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
I've made a new patch to try:
https://launchpad.net/~vanvugt/+archive/ubuntu/mutter/+build/26240021
but can't tell if it's helping because after I installed it, the bug
stopped happening. Then after I uninstalled it, the bug still stopped
happening.
--
You received this bug notification
Also "Invalid mode 800x600 (-nan)" seems to be originating from Xdcv as
you can see it in xrandr output (800x600 0.00Hz). Xdcv is reporting a
bogus refresh rate but also Xdcv accepts that bogus refresh rate in
manual mode changes using the xrandr command. So it looks like mutter
needs to be
This is interesting:
> Impossible to set scaling on crtc 59 to 1.00, error id 2
Error 2 is BadValue and I can reproduce similar on the command line:
$ xrandr --output VNC-output-0 --scale 1x1 # or 2x2, 0.5x0.5
This works in Xorg but seems to always fail in Xdcv with error BadValue
(2).
53 matches
Mail list logo
