Update to 47.2
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-5386298b3bPlease login to add feedback.
| 0 | 0 | Test Case Gnome Accessibility |
| 0 | 0 | Test Case Gnome Classic mode |
| 0 | 0 | Test Case Gnome Lock Screen |
| 0 | 0 | Test Case Gnome Login Screen |
| 0 | 0 | Test Case desktop user switching |
| 0 | 0 | Test Case gnome desktop background |
| 0 | 0 | Test Case gnome-shell activities |
| 0 | 0 | Test Case gnome-shell dash |
| 0 | 0 | Test Case gnome-shell extensions gnome org |
| 0 | 0 | Test Case gnome-shell extensions install |
| 0 | 0 | Test Case gnome-shell extensions remove |
| 0 | 0 | Test Case gnome-shell overview search |
| 0 | 0 | Test Case gnome-shell workspaces |
This update has been submitted for testing by fmuellner.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
It seems this
mutterupdate broke headless remote sessions. Once I downgrade it, i can use such a session again. Works on the bare metal though.Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@bojan, could you expand what you mean not working? Running with this update, I can still launch a headless session and connect to it via RDP.
I get a black screen on login. No top bar etc. if I reconnect, I can see the top bar, but everything is non-responsive. First thought it may have been libinput, but downgrading it did nothing. Next, I downgraded mutter and got back to normal. I went through the journal - nothing stands out. 😕
BTW, I am connecting to a Hyper-V VM running on Windows 10. Connection is from that Windows laptop to its own VM, so it's not a networking problem.
Are you connecting via gnome-remote-desktop running in the VM?
Yes, the headless one.
Collected a bit of journal when I tried connecting. It is here: https://bugzilla.redhat.com/show_bug.cgi?id=2329111
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'passed'.
hm, is it an upstream issue?
Yes, https://gitlab.gnome.org/GNOME/mutter/-/issues/3804, I discovered a work around that Bojan verified working, and am currently working on a real fix.
Awesome, good work both!
Gnome remote desktop 47.2 was just pushed, does it still happen with that one as well?
It's a race condition in the frame scheduling routines in the compositor, unrelated to gnome-remote-desktop. It just happens to (in bojan's case) hit the race more easily. Didn't ever run into it here, and had to craft a special purpose test case to replicate it.
Gotcha!
Works
works fine in a general daily usage
This update can be pushed to stable now if the maintainer wishes
FWIW, here is the upstream merge request fixing the reported regression: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4152
@jadahl, if you wanted to get broader testing of the patch that's waiting for the merge upstream, maybe roll such a build into this update and all Gnome updates-testing users can verify it.
Works great! LGTM! =)
Cool, seems upstream has merged the fix!
fmuellner edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by fmuellner.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
Works now with VM on Hyper-V. Thanks for the fix @jadahl!
This update can be pushed to stable now if the maintainer wishes
Works great! LGTM! =)
Sounds we're good to push to stable?
I've noticed f40 was pushed to stable while this was not, was f41 missed or hold back for any reason?
This update has been submitted for stable by fmuellner.
This update has been pushed to stable.