Fedora 41 Crashing

[Mark_W_Gabby-Li]

Which Linux distro are you using?
Fedora KDE

Which release version?
41, updated this morning.

Which kernel are you using?
Linux 6.13.5-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 27 15:07:31 UTC 2025 x86_64 GNU/Linux

Which BIOS version are you using?
3.05

Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series)
7940HS

I can get this crash to happen by:
Opening the Discover application.
Running vulkaninfo from the command line.
Opening System Settings and going to “About This System” section.
Using the PC normally.

Here’s one callstack (I don’t know if it’s the same for each way of replicating it.):

Thread 1 (Thread 0x7fbe1728d2c0 (LWP 2008)):
[KCrash Handler]
#4 0x00007fbe20b14673 in KWin::DrmPipeline::commitPipelines(QList<KWin::DrmPipeline*> const&, KWin::DrmPipeline::CommitMode, QList<KWin::DrmObject*> const&) () from /lib64/libkwin.so.6
#5 0x00007fbe20b079dd in KWin::DrmGpu::testPipelines() () from /lib64/libkwin.so.6
#6 0x00007fbe20b07d17 in KWin::DrmGpu::checkCrtcAssignment(QList<KWin::DrmConnector*>, QList<KWin::DrmCrtc*> const&) [clone .part.0] () from /lib64/libkwin.so.6
#7 0x00007fbe20b07da6 in KWin::DrmGpu::checkCrtcAssignment(QList<KWin::DrmConnector*>, QList<KWin::DrmCrtc*> const&) [clone .part.0] () from /lib64/libkwin.so.6
#8 0x00007fbe20b0b743 in KWin::DrmGpu::testPendingConfiguration() () from /lib64/libkwin.so.6
#9 0x00007fbe20ae74ce in KWin::DrmBackend::applyOutputChanges(KWin::OutputConfiguration const&) () from /lib64/libkwin.so.6
#10 0x00007fbe20a6db09 in KWin::Workspace::applyOutputConfiguration(KWin::OutputConfiguration const&, std::optional<QList<KWin::Output*> > const&) () from /lib64/libkwin.so.6
#11 0x00007fbe20a6e1da in KWin::Workspace::updateOutputConfiguration() () from /lib64/libkwin.so.6
#12 0x00007fbe20a6eaa2 in KWin::Workspace::slotOutputBackendOutputsQueried() () from /lib64/libkwin.so.6
#13 0x00007fbe1dd5a26e in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt6Core.so.6
#14 0x00007fbe20ae7f12 in KWin::DrmBackend::updateOutputs() () from /lib64/libkwin.so.6
#15 0x00007fbe20ae9d8d in KWin::DrmBackend::handleUdevEvent() () from /lib64/libkwin.so.6
#16 0x00007fbe1dd5a26e in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt6Core.so.6
#17 0x00007fbe1dd687fd in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt6Core.so.6
#18 0x00007fbe1dd68feb in QSocketNotifier::event(QEvent*) () from /lib64/libQt6Core.so.6
#19 0x00007fbe1f03d9b8 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt6Widgets.so.6
#20 0x00007fbe1dcf3590 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt6Core.so.6
#21 0x00007fbe1deb8b06 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () from /lib64/libQt6Core.so.6
#22 0x00007fbe1deb9454 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6
#23 0x00007fbe1eacabf2 in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Gui.so.6
#24 0x00007fbe1dd00993 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt6Core.so.6
#25 0x00007fbe1dcfbf6e in QCoreApplication::exec() () from /lib64/libQt6Core.so.6
#26 0x0000564e10f67753 in main ()

[Obasav]

Which mesa version are you using? There are currently lots of issues from version 25.0, and they are fixed by downgrading to 24.3.4.

[Mark_W_Gabby-Li]

If I run dnf list installed "mesa*", I do see a lot of version 25 packages:

mesa-dri-drivers.i686          25.0.0-2.fc41                         <unknown>
mesa-dri-drivers.x86_64        25.0.0-2.fc41                         <unknown>
mesa-filesystem.i686           25.0.0-2.fc41                         <unknown>
mesa-filesystem.x86_64         25.0.0-2.fc41                         <unknown>
mesa-libEGL.i686               25.0.0-2.fc41                         <unknown>
mesa-libEGL.x86_64             25.0.0-2.fc41                         <unknown>
mesa-libGL.i686                25.0.0-2.fc41                         <unknown>
mesa-libGL.x86_64              25.0.0-2.fc41                         <unknown>
mesa-libGLU.x86_64             9.0.3-5.fc41                          anaconda
mesa-libOSMesa.i686            25.0.0-2.fc41                         <unknown>
mesa-libOSMesa.x86_64          25.0.0-2.fc41                         <unknown>
mesa-libgbm.i686               25.0.0-2.fc41                         <unknown>
mesa-libgbm.x86_64             25.0.0-2.fc41                         <unknown>
mesa-va-drivers.i686           25.0.0-2.fc41                         <unknown>
mesa-va-drivers.x86_64         25.0.0-2.fc41                         <unknown>
mesa-vulkan-drivers.i686       25.0.0-2.fc41                         <unknown>
mesa-vulkan-drivers.x86_64     25.0.0-2.fc41                         <unknown>

Is there a way to downgrade all of them at once, such as by using a meta package or do I need to do them one-by-one? And how do I downgrade?

[Zachary_Krida]

Hi @Mark_W_Gabby-Li you should find a solution in this related thread, I left a comment explaining how to downgrade mesa but also how to pin the version so you can continue to update other dependencies.

Graphical Corruption in Fedora 41 on AMD (BIOS3.06, Linux 6.13.5)

EDIT: This issue has been solved for me by downgrading mesa. There is an issue with the latest available package at time of writing. See thread for details. Issue Description I have been experiencing graphical corruption (transient colorful blocky artifacts), flickering, blank windows after recent updates to both firmware and kernel. Example of graphical artifacts under windows in GNOME overview. [Untitled] Example of graphical artifacts in Firefox (Bitwarden extension). [Screenshot From …

[Mark_W_Gabby-Li]

Thank you for the idea, but this did not fix my issue. While starting vulkaninfo does not cause a crash to occur, KWin is still crashing when I try starting games and when I navigate to About this System in the System Settings application.

[Mark_W_Gabby-Li]

I opened a bug on the KDE bug tracker about this, because KWin is what’s crashing and there are reports on Bodhi of this version of KWin being unstable.

[Mark_W_Gabby-Li]

Workaround:
Download the x86_64 6.3.2.1-1.fc41 versions of kwin, kwin-wayland, kwin-common, kwin-libs:

kwin-6.3.2.1-1.fc41 | Build Info | koji

Run this command to downgrade them:
sudo dnf downgrade ~/Downloads/kwin-wayland-6.3.2.1-1.fc41.x86_64.rpm ~/Downloads/kwin-common-6.3.2.1-1.fc41.x86_64.rpm ~/Downloads/kwin-libs-6.3.2.1-1.fc41.x86_64.rpm ~/Downloads/kwin-6.3.2.1-1.fc41.x86_64.rpm

Note that this does not pin them! So they will be updated automatically the next time you update.

[Mark_W_Gabby-Li]

The bug has been updated:

Will be fixed in 6.3.3, out on tuesday.

No idea how long it’ll take to get from there to Fedora, but at least it’s going to be addressed quickly on their end.

[inffy]

@Mark_W_Gabby-Li

The bug has been updated:

Will be fixed in 6.3.3, out on tuesday.

No idea how long it’ll take to get from there to Fedora, but at least it’s going to be addressed quickly on their end.

Fedora pushes the KDE updates pretty quickly, depending how fast the get their packaging done. So pretty surely it will be next week, maybe even next day, once it lands on Fedora “stable”

[Ro_Hefoze]

Well this sucks. I’m seeing this every time I try to launch Lutris. Hopefully we’ll get this fix same day Tues.

[Steve_Cossette]

Hello all! My name is Steve, and I’m a member of the KDE sig at Fedora, mainly dealing with packaging tasks.

This was an issue with a patch provided by KDE, which I have reverted today. The fix will be coming to F41 tomorrow: FEDORA-2025-a4ae523cd7 — bugfix update for kwin — Fedora Updates System

You can force-install it now by running the following in a terminal window:

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