Dnf upgrade of wireplumber kicks the user out of KDE desktop

,

I posted in a KDE forum that I was repeatedly kicked out of the Fedora 42 KDE desktop by running an upgrade on wireplumber. See the thread here:

Upgrading Wireplumber in KDE effectively crashes Desktop

Apparently a trigger or scriptlet is somehow causing my user to be kicked out. I was thinking the SDDM was being restarted but “systemctl status sddm” shows a start time that doesn’t point to the time I was kicked out. So the KDE isn’t being killed off due to a SDDM restart.

I eventually got wireplumber upgraded by doing it logged out of KDE and from a virtual console (tty4).

As f42 is not in beta yet best place to raise this is the fedora testing mailing list.

1 Like

I’m not on the list, anyway I suspect if it’s as annoying as I’ve found (crashing you out of the desktop the instant you do a dnf upgrade of wireplumber and likely pipewire), it’s going to be “discovered” as a problem so many times it won’t matter

This is what it looks like the scriptlet does.

systemctl --user -M "yourusername@" disable --now --no-warn "wireplumber.service"

followed by

sudo systemctl --no-reload preset --global wireplumber.service

You could also just do systemctl --user disable wireplumber.service and see if it causes the same issue.

Beware that you are running code that has only just started to be stabilised. You are likely to run into many issues that will be fixed before beta. But to help get bugs found and fixed the testing list is a good place to contribute. Repots here may well not get to the right people.