While upgrading to kernel 6.11.11-200.fc40.x86_64 today, after reboot I could login. Then I just could move with the mouse and nothing I clicked worked. Appeared to be dead.
While moving the mouse to the bottom it showed me the hover-text from the extension dash to dock.
Opening Settings worked but i could not click anything (same as after login).
After power off the restart in kernel 6.11.10 worked and a downgrade from mutter helped me to use the newest kernel again.
sudo dnf history info 326
Transaction ID : 326
Begin time : 2024-12-12 11:23:51
Begin rpmdb : cb22f2f14024eeac3bcb1ff1d4360d44666c72a4996cfe1f1e4a59254a3948f3
End time : 2024-12-12 11:25:56
End rpmdb : 4312347b51497bae6cf3fbcefb8260a49d32f71165ee61594c9eb429a8501fed
User : 1000 *************
Status : Ok
Releasever : 40
Description : dnf5 upgrade
Comment :
Packages altered:
Action Package Reason Repository
Install kernel-modules-extra-0:6.11.11-200.fc40.x86_64 External User updates
Install kernel-modules-0:6.11.11-200.fc40.x86_64 External User updates
Install kernel-core-0:6.11.11-200.fc40.x86_64 External User updates
Install kernel-modules-core-0:6.11.11-200.fc40.x86_64 External User updates
Install kernel-0:6.11.11-200.fc40.x86_64 External User updates
Upgrade gnome-shell-0:46.7-1.fc40.x86_64 Group updates
Upgrade gvisor-tap-vsock-6:0.8.1-1.fc40.x86_64 Dependency updates
Upgrade gvisor-tap-vsock-gvforwarder-6:0.8.1-1.fc40.x86_64 External User updates
Upgrade kernel-tools-0:6.11.11-200.fc40.x86_64 Weak Dependency updates
Upgrade kernel-tools-libs-0:6.11.11-200.fc40.x86_64 Dependency updates
Upgrade mutter-0:46.7-1.fc40.x86_64 Dependency updates
Upgrade mutter-common-0:46.7-1.fc40.noarch Dependency updates
Upgrade virtiofsd-0:1.13.0-1.fc40.x86_64 External User updates
Remove kernel-0:6.11.7-200.fc40.x86_64 User @System
Remove kernel-core-0:6.11.7-200.fc40.x86_64 User @System
Remove kernel-modules-0:6.11.7-200.fc40.x86_64 User @System
Remove kernel-modules-core-0:6.11.7-200.fc40.x86_64 User @System
Remove kernel-modules-extra-0:6.11.7-200.fc40.x86_64 User @System
Replaced gnome-shell-0:46.6-2.fc40.x86_64 Group @System
Replaced gvisor-tap-vsock-6:0.8.0-1.fc40.x86_64 Dependency @System
Replaced gvisor-tap-vsock-gvforwarder-6:0.8.0-1.fc40.x86_64 External User @System
Replaced kernel-tools-0:6.11.10-200.fc40.x86_64 Weak Dependency @System
Replaced kernel-tools-libs-0:6.11.10-200.fc40.x86_64 Dependency @System
Replaced mutter-0:46.6-1.fc40.x86_64 Dependency @System
Replaced mutter-common-0:46.6-1.fc40.noarch Dependency @System
Replaced virtiofsd-0:1.10.1-1.fc40.x86_64 External User @System
Downgrade:
sudo dnf history info 327
Transaction ID : 327
Begin time : 2024-12-12 12:56:07
Begin rpmdb : 4312347b51497bae6cf3fbcefb8260a49d32f71165ee61594c9eb429a8501fed
End time : 2024-12-12 12:56:11
End rpmdb : f924a422e8caed642b68963942e690f8a22a8756d855eddc712480ecb2aada4b
User : 1000 ***********
Status : Ok
Releasever : 40
Description : dnf downgrade mutter
Comment :
Packages altered:
Action Package Reason Repository
Downgrade mutter-0:46.0-1.fc40.x86_64 Dependency fedora
Downgrade mutter-common-0:46.0-1.fc40.noarch Dependency fedora
Replaced mutter-0:46.7-1.fc40.x86_64 Dependency @System
Replaced mutter-common-0:46.7-1.fc40.noarch Dependency @System
As far as I have seen, the tests of 6.12 have been positive since 6.12.3, it was just waited for the bpftool maintainer since then (don’t know what this was about), and it seems this has happened already:
6.12.4 is now in bodhi’s testing and the bodhi tests are so far mostly positive as well (the one with negative karma refers to two bugs of around 2006, so I am not sure if I take that report serious).
So you might try to test 6.12.4 the way it was pushed to bodhi-testing and see if your issue is still present with that one. If this is a kernel issue, we can say for sure that it will be only processed if it still occurs on 6.12:
If it still occurs on 6.12, you might increase the amount of kernels that remain installed in advance to further updates, in order to ensure that you still keep 6.11.10 installed (default is 3 kernels).
Now we can change the default kernel by using the index number:
sudo grubby --set-default-index=1
Verify the default kernel
Verify that the right kernel has been set as default:
sudo grubby --default-title
The output will be the default kernel title:
Fedora Linux (6.11.10-200.fc40.x86_64) 40 (Workstation Edition)
I just related the issue because I was reading other topic with 6.11.11 issues.
Yes 6.13 I will test with my RPI5 when it is ready to install, it is still rc2 on kernel.org . Till then I just use the 6.11.10 kernel as a workaround and will test 6.12 when available.
It might be added for other users that using 6.11.10 is not a long term solution because this kernel is no longer supported.
So if the update to 6.12.X does not solve the problem once any 6.12 has been pushed to stable, we need to actively evaluate the issue and likely file a bug report to ensure it gets solved
Hard to foresee. It is also possible that a mutter update uses some new functions in the kernel, while these functions have a bug. If I get it right, the mutter update has not caused issues in 6.10.10. Hopefully, we will not need to evaluate that issue after 6.12 is in stable.
I not changed any thing on the login. Since long I use Wayland only. On purpose I not changed anything.
Before I wrote this topic I tested twice to be sure if I can reproduce. I could reproduce.
Then I removed mutter , history you can see above. After that I tried to reproduce and I could not anymore. Login was normally.
Then I was upgrading to the 6.12 Kernel as proposed by chris.
$ sudo dnf history info 328
Transaction ID : 328
Begin time : 2024-12-12 19:56:41
Begin rpmdb : f924a422e8caed642b68963942e690f8a22a8756d855eddc712480ecb2aada4b
End time : 2024-12-12 19:58:30
End rpmdb : 6a23cfafd062c02ab5078cc3f73a647026d8743a594cb9619de8a6a74cc33f7f
User : 1000 ***********
Status : Ok
Releasever : 40
Description : dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-811cffc4ef
Comment :
Packages altered:
Action Package Reason Repository
Install kernel-modules-extra-0:6.12.4-100.fc40.x86_64 External User updates-testing
Install kernel-modules-0:6.12.4-100.fc40.x86_64 External User updates-testing
Install kernel-core-0:6.12.4-100.fc40.x86_64 External User updates-testing
Install kernel-modules-core-0:6.12.4-100.fc40.x86_64 External User updates-testing
Install kernel-0:6.12.4-100.fc40.x86_64 External User updates-testing
Upgrade kernel-headers-0:6.12.4-100.fc40.x86_64 Dependency updates-testing
Upgrade kernel-tools-0:6.12.4-100.fc40.x86_64 Weak Dependency updates-testing
Upgrade kernel-tools-libs-0:6.12.4-100.fc40.x86_64 Dependency updates-testing
Remove kernel-0:6.11.8-200.fc40.x86_64 User @System
Remove kernel-core-0:6.11.8-200.fc40.x86_64 User @System
Remove kernel-modules-0:6.11.8-200.fc40.x86_64 User @System
Remove kernel-modules-core-0:6.11.8-200.fc40.x86_64 User @System
Remove kernel-modules-extra-0:6.11.8-200.fc40.x86_64 User @System
Replaced kernel-headers-0:6.11.3-200.fc40.x86_64 Dependency @System
Replaced kernel-tools-0:6.11.11-200.fc40.x86_64 Weak Dependency @System
Replaced kernel-tools-libs-0:6.11.11-200.fc40.x86_64 Dependency @System
Upgraded the mutter package and since then my computer works as before with kernel 6.11.10 while using also 6.11.11 and 6.12