This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

Alright, i can wait. Thanks for the fast reply and the downgrade tipp! Should i close the issue?

This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

I have this:

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Are you saying that one can downgrade only qt6 and the problem will go away?

I first encountered this problem immediately upon doing a "dnf update" last night.
I already did a "dnf history undo" but that did not fix the problem.

Should I be executing a different command to recover?

This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

I have this:

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Are you saying that one can downgrade only qt6 and the problem will go away?

I first encountered this problem immediately upon doing a "dnf update" last night.
I already did a "dnf history undo" but that did not fix the problem.

Should I be executing a different command to recover?

Either that, or download the -3 update that is in bodhi, waiting for a compose:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-6842ac8bfa

This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

I have this:

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Are you saying that one can downgrade only qt6 and the problem will go away?

I first encountered this problem immediately upon doing a "dnf update" last night.
I already did a "dnf history undo" but that did not fix the problem.

Should I be executing a different command to recover?

Either that, or download the -3 update that is in bodhi, waiting for a compose:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-6842ac8bfa

What is -3 please? Does that mean undo the last 3 updates, all packages?

This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

I have this:

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Are you saying that one can downgrade only qt6 and the problem will go away?

I first encountered this problem immediately upon doing a "dnf update" last night.
I already did a "dnf history undo" but that did not fix the problem.

Should I be executing a different command to recover?

Either that, or download the -3 update that is in bodhi, waiting for a compose:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-6842ac8bfa

What is -3 please? Does that mean undo the last 3 updates, all packages?

-3 is release #3 of 6.9.1, aka "6.9.1-3". You got 2, so you can either downgrade to 1, or upgrade to 3, the end result will be the same.

This is a known issue, and there is a fix in the pipeline. With Fedora's infra move though, we're "stuck" to wait.

On normal fedora, one can downgrade qt6-qtwayland. Koji is down right now because of the move, but I got the files off koji yesterday: https://farchord.fedorapeople.org/qt6-qtwayland.tar.gz (Note that this is for F42 only)

I have this:

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Are you saying that one can downgrade only qt6 and the problem will go away?

I first encountered this problem immediately upon doing a "dnf update" last night.
I already did a "dnf history undo" but that did not fix the problem.

Should I be executing a different command to recover?

Either that, or download the -3 update that is in bodhi, waiting for a compose:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-6842ac8bfa

What is -3 please? Does that mean undo the last 3 updates, all packages?

-3 is release #3 of 6.9.1, aka "6.9.1-3". You got 2, so you can either downgrade to 1, or upgrade to 3, the end result will be the same.

Ah, OK. I interpreted it as "minus 3" instead of "version 3". I did see that there was no space between the hyphen and the numeral "3" though.
;-)

I just did a "dnf check-update" but see only this:
$ dnf check-update
Updating and loading repositories:
Repositories loaded.
mozilla-openh264.x86_64 2.5.1-1.fc42 fedora-cisco-openh264
openh264.x86_64 2.5.1-1.fc42 fedora-cisco-openh264
$

Would version 3 be in there?

I also just ran this command:
$ dnf info qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
Installed packages
Name : qt6-qtwayland
Epoch : 0
Version : 6.9.1
Release : 2.fc42
Architecture : x86_64
Installed size : 5.0 MiB
Source : qt6-qtwayland-6.9.1-2.fc42.src.rpm
From repository : updates
Summary : Qt6 - Wayland platform support and QtCompositor module
URL : http://www.qt.io
License : LGPL-3.0-only OR GPL-3.0-only WITH Qt-GPL-exception-1.0
Description : Qt6 - Wayland platform support and QtCompositor module.
Vendor : Fedora Project

Available packages
Name : qt6-qtwayland
Epoch : 0
Version : 6.9.1
Release : 2.fc42
Architecture : i686
Download size : 1.3 MiB
Installed size : 4.9 MiB
Source : qt6-qtwayland-6.9.1-2.fc42.src.rpm
Repository : updates
Summary : Qt6 - Wayland platform support and QtCompositor module
URL : http://www.qt.io
License : LGPL-3.0-only OR GPL-3.0-only WITH Qt-GPL-exception-1.0
Description : Qt6 - Wayland platform support and QtCompositor module.
Vendor : Fedora Project
$

I have tried to find a good (clear) explanation of the differences between various dnf commands to "revert" installed packages, but I'm still not sure how to downgrade.

Should I do a "dnf history undo"
and would the [ARGUMENTS] be the package name, in this case qt6-qtwayland

Or should I do "dnf history rollback
and would the [ARGUMENTS] be the package name qt6-qtwayland

Or should I be executing another dnf command to revert back to version 1 of qt6-qtwayland?

I don't mind moving forward to version 3 if that would fix the screen lock problem.

If you want to absolutely install it now:

sudo dnf install bodhi-client
mkdir ~/Downloads/temp && cd ~/Downloads/temp
bodhi updates download --updateid FEDORA-2025-6842ac8bfa
sudo dnf up ./*.rpm

Should install it on your system. But it's highly likely this'll go live tomorrow. So, up to you.

If you want to absolutely install it now:

sudo dnf install bodhi-client mkdir ~/Downloads/temp && cd ~/Downloads/temp bodhi updates download --updateid FEDORA-2025-6842ac8bfa sudo dnf up ./*.rpm

Should install it on your system. But it's highly likely this'll go live tomorrow. So, up to you.

Oh, OK. I can wait and check tomorrow.

I just changed the settings on my computer to sleep after 120 minutes; I will not leave it inactive that long so the system will not sleep. And then I'll just shut down in the evening and reboot in the morning.

Here is a very good example of why I have been pushing for a good solution to the "restore window positions and sizes" upon log in. It is a real pain in the ass (in my opinion) to position all the windows and resize them each time I log in.

Thanks for the info..... I'll check tomorrow and do a "dnf check-update"

I successfully updated my laptop this morning. The screen locking issue is resolved.

However, I cannot update my main desktop system. Executing "dnf check-update" indicates that there is nothing to do:
$ dnf check-update
Updating and loading repositories:
Repositories loaded.
$

However, issuing the same "dnf update" command as I did on my laptop results in nothing.

Here is what I have on my desktop system so far (qt6-qtwayland version) :

$ dnf list | grep qt6-qtwayland
Updating and loading repositories:
Repositories loaded.
qt6-qtwayland.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.i686 6.9.1-2.fc42 updates
qt6-qtwayland-devel.x86_64 6.9.1-2.fc42 updates
qt6-qtwayland-examples.x86_64 6.9.1-2.fc42 updates
$

Other than differences related to hardware or device drivers, I have the same Fedora platform on the laptop and the desktop.

Yes that's because each mirror gets updated at different times. It really depends.

I suspected something like that.

But I don't understand how does a given computer such as my desktop (versus my laptop) get assigned a mirror?

Just for my edification (not that I need to do this now; I can wait a few days), can I configure the mirror my system uses via any settings in /etc/dnf ?

This should be fixed now.