Phew. I'll be cautious and wait until the fallout has settled.
I do like KDE a lot, but they have a tendency to need several point releases until things are smooth. Besides, for me, pipewire is a mess. On several systems a lot of applications mess up major style and I end up having no sound at all at times. Whatever is wrong there. I know it _should_ be the drop-in thing, that catches all sorts of sound and deals with it, however, in reality I got issues on nearly all my machines. (besides one, that runs 100% pulseaudio and 0% pipewire) *shrugs* No clue what's causing the mess.
And then, in the changelog, one can spot an error that was causing files to be openend with the wrong program, so the associations were wrong. Those are some basics. I wonder why something like this a) gets fixed that late before release and b) how something like this could even break in the first place. Someone must have changed something related to that part, but not even remotely tested the compiled code?
I do like KDE a lot, but they have a tendency to need several point releases until things are smooth. Besides, for me, pipewire is a mess. On several systems a lot of applications mess up major style and I end up having no sound at all at times. Whatever is wrong there. I know it _should_ be the drop-in thing, that catches all sorts of sound and deals with it, however, in reality I got issues on nearly all my machines. (besides one, that runs 100% pulseaudio and 0% pipewire) *shrugs* No clue what's causing the mess.
And then, in the changelog, one can spot an error that was causing files to be openend with the wrong program, so the associations were wrong. Those are some basics. I wonder why something like this a) gets fixed that late before release and b) how something like this could even break in the first place. Someone must have changed something related to that part, but not even remotely tested the compiled code?
Comment