I using fedora 41 dual booting with windows 11 and turn the secure boot off. I having this issue a lot, for the first time i install, i have change from nouveau to nvidia, because i think it was the one, but it now. then i re install fedora 41. Everything still find, then it crash when i adjust ‘label spacing left’ in the extension ‘workspace indicator by open apps’ and everything is freeze, but i’m still hearing the sound of the youtube i open it on firefox. I force to turn it off and saw this problem
The bug report indicates it is a problem in the i915 driver. Since you said you are using the nvidia driver, can you disable (blacklist) the i915 driver?
Note: the “quit unexpectedly” errors are likely secondary problems that were caused when you hard-power-offed your system.
As long as you are not using the i915 driver, you should be able to blacklist it. Try adding rd.blacklist=i915 and modprobe.blacklist=i915 to your kernel parameters. Try running something like sudo grubby --args="rd.blacklist=i915 modprobe.blacklist=i915" --update-kernel /boot/<kernel> (replace <kernel> with the kernel you are using).
The linked bug report says that xorg-x11-drv-intel is tainted, which wouldn’t be true if you were using nouveau. Have you tried removing the nvidia drivers and opening a new bugzilla without the tainted component? You’ll be far more likely to get somebody working on it that way.
From your ls output, it looks like it should be /boot/vmlinuz-6.11.7-300.fc41.x86_64. Alternatively, you can change the parameters interactively at the grub boot menu (I think you have to hold the SHIFT key while booting to get it to show).
You should be able to pick the previous kernel (6.11.4-301.fc41.x86_64) if the changes didn’t work on 6.11.7-300.fc41.x86_64. Then you can undo those changes to the newer kernel by running sudo grubby --remove-args="rd.driver.blacklist=i915 modprobe.blacklist=i915" --update-kernel /boot/vmlinuz-6.11.7-300.fc41.x86_64.
Edit: If it didn’t work, it likely means that your system is using the i915 driver, not the nouveau driver.
That means the parameters I gave you didn’t work. Maybe there was a typo? Run cat /proc/cmdline to see what parameters the system was actually booted with.
Yeah, the parameter changes didn’t take. I think someone said that grubby documentation was out of date. I guess you can just try editing the command line interactively at the boot menu then. I think you press e to do that and then Ctrl+x to run with the changes, but I’m not sure. Maybe someone who is more familiar with grub could help.
