Fedora Account System
Red Hat Associate
Red Hat Customer
This is a tracking bug for the Blocker review process. Do not add comments about the issue here, but use the upstream tracker at https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/307. Reproducible: Always
Proposed as a Blocker for 44-final by Fedora user lruzicka using the blocker tracking app because: Basic application functionality
Note, this seems to have started affecting the installer RDP interface, but more recently. In Rawhide, the earliest case I can find is Fedora-Rawhide-20260220.n.0: https://openqa.fedoraproject.org/tests/4319703 . In 44, the earliest case is just two days ago: https://openqa.fedoraproject.org/tests/4398111 . On both 44 and Rawhide it's been affecting the GNOME tests for much longer. So, that's a bit of a conundrum. Why would it happen on GNOME for weeks, then start happening to installs on Rawhide around Feb 20, then start happening to installs on 44 around March 7?
Discussed in a blocker review meeting [1] on 2026-03-09. The outcome was: !agreed 2444824 - punt (delay decision) - we decided to delay the decision on this for more manual investigation into the various facets (different clients, GNOME case vs. installer case, getting more logs about what's going on when there's a failure) [1] https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/
Aha, https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/5162 might be why it started happening recently to the installer. I'm going to do a Rawhide build of pipewire with that backported; in some initial testing it looks like that makes things much more reliable. I'll send a PR to propose the same for F44.
AGREED AcceptedFinalFreezeException / Delayed final blocker decision. Discussed at the 2026-03-16 (blocker / freeze exception) review meeting: This is accepted as a freeze exception issue as the GNOME remote desktop case is definitely heavily broken and we want that fixed for release if possible. Blocker status decision is delayed as the blocker case (RDP install) seems to fail much less often, but we want to investigate more thoroughly before deciding. https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-16/f44-blocker-review.2026-03-16-16.01.log.txt
FEDORA-2026-86d8944272 (pipewire-1.6.2-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-86d8944272
I think we can treat the pipewire update as mostly addressing this, it at least fixes most instances of the bug as described here. I will keep on eye on the RDP install test results and file a new bug if it looks like we're seeing an unacceptable failure rate there.
FEDORA-2026-86d8944272 (pipewire-1.6.2-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
This was a proposed blocker, we need at least some form of verification that the RDP installs are fine. Reopening for that case.
Well, my thought was commetn #7...pipewire has clearly improved the situation for GNOME remote desktop, and that's what this bug was initially for. I checked and there've been no further failures in install_rdp since the blocker meeting. Out of the last 200 runs on F44 across aarch64 and x86_64 there are only 3 failures, so I think it's fine. If we see more failures I'll open a new bug, as noted.
I opened https://bugzilla.redhat.com/show_bug.cgi?id=2464127 two months ago, no activity whatsoever, and we've been without remote desktop access since we've upgraded our virtual desktops to F44, rendering them unusable.