Update - kwin 6.3.2.1-2.fc41 - disaster

Ask Fedora
, ,
1

This morning my system (Fedora 41 KDE) receive some updates:

kwin 6.3.2.1-2.fc41
kwin-wayland 6.3.2.1-2.fc41
kwin-libs 6.3.2.1-2.fc41
kwin-common 6.3.2.1-2.fc41

Well, that was a start of painful morning.
System rebooted normally, and i was ready to dive in my work.
I started launching my apps.
The picture disappeared, a completely black screen. Then it came back with a KWIN crash message.
I did some reports.
And I returned the old versions so I could work.
After I finished my work I started investigating.
It turned out that KWIN crashes when starting CHROME BROWSER which is a FLATPAK app.
Then I tried to start FLATSEAL - it also didn’t work and crashed KWIN.
I decided to restore their old versions so I could work.
Are there others with similar problems related to this KWIN update?

2

Same problem. Kwin-wayland crashed every time i tried to open Chrome. Downgrading to the previous version solved it for me:

sudo dnf downgrade https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/1.fc41/x86_64/kwin-6.3.2.1-1.fc41.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/1.fc41/x86_64/kwin-common-6.3.2.1-1.fc41.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/1.fc41/x86_64/kwin-libs-6.3.2.1-1.fc41.x86_64.rpm https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/1.fc41/x86_64/kwin-wayland-6.3.2.1-1.fc41.x86_64.rpm
4 Likes
3

Same here, thank you for the downgrade command

1 Like
4

I made an account just to thank you for the downgrade command. This would happen with any app I opened, including chrome. Withint 30s of starting, segfault.

2 Likes
5

No problem at all for me, and I use several Flatpak apps.

I wonder what the difference is here that’s causing the very different behaviour we see?

fwiw I’m on kernel 6.12.15-200.fc41.x86_64 and using nVidia driver 570.86.16.

6

Kernel 6.13.5-200.fc41.x86_64, using AMD graphics.

7

I would suggest filing a bug.

8

Thanks for this. I was having the same issue, this fixed it for now.

9

Agreed, and if someone does have the time to do so, please link the bug here.
I wonder if this is an AMD GPU + kwin issue.
I too am using AMD (RX 7700s and 7900 XTX, both with the same issue)
My issue wasn’t with flatpak though, native apps too. Konsole would trigger it after a few seconds, as would chrome (native install, not flatpak)
I had to switch to console to downgrade without logging in to fix it.

I wonder what the difference is here that’s causing the very different behaviour we see?

I suspect, anecdotally, that it’s a kwin+amd issue.

Relevant hardare:

VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 33 [Radeon RX 7600/7600 XT/7600M XT/7600S/7700S / PRO W7600] (rev c1)
Linux fw16 6.13.5-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Feb 27 15:07:31 UTC 2025 x86_64 GNU/Linux

I tried earlier kernels, didn’t fix it. Only the downgrade did. So it’s one of those 4 packages with the issue.

Message: Process 9123 (kwin_wayland) of user 1000 dumped core.
_ZN4KWin11DrmPipeline15commitPipelinesERK5QListIPS0_ENS0_10CommitModeERKS1_IPNS_9DrmObjectEE

Seems to lead me to believe it’s an AMD issue, since this is rendering related.

10

I filed it:
https://bugzilla.redhat.com/show_bug.cgi?id=2350883

1 Like
11

FYI I have amd gpu and no crashes.

The bug report is missing hardware details by the way.

12

I didn’t want to wait for the full testing, so I simply fixed my Fedora 42 with this:

dnf upgrade
 https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/3.fc42/x86_64/kwin-6.3.2.1-3.fc42.x86_64.rpm
 https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/3.fc42/x86_64/kwin-common-6.3.2.1-3.fc42.x86_64.rpm
 https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/3.fc42/x86_64/kwin-libs-6.3.2.1-3.fc42.x86_64.rpm
 https://kojipkgs.fedoraproject.org//packages/kwin/6.3.2.1/3.fc42/x86_64/kwin-wayland-6.3.2.1-3.fc42.x86_64.rpm
13

I put a dump of lshw on there? Am I missing something?

14

Sorry I missed the attachement. I expecting to see details in the report itself.

I’ve add my hardware details so that there is a reference for a working configuration to compare.