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 ()
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.
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.
Workaround:
Download the x86_64 6.3.2.1-1.fc41 versions of kwin, kwin-wayland, kwin-common, kwin-libs:
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.
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”