The adventure continue!
I managed to find the solution to the absence of audio devices right after the fresh install of CachyOS (and on any kernel).
The solution is simple but requires the commandment of several languages: cussing, swearing, cursing, and damnation of every kind. Well, I guess it’s the same language. ) The point is the KDE-Wayland couple is still buggy and unstable. I log out of Wayland session (after the newly fresh install) and log in under X11. Miracle happened! All sound devices and sound itself are back! I reload KDE Wayland session, and everything works! Note it! But the bug, some bug, is still somewhere between KDE and Wayland.
The solution is not a solution. Sometimes it works, sometimes - not!
Good question. It works after reboot into Wayland.
BUT!
I noted, it not working again. Maybe because I logged out of session, but I’m not sure. I rebooted, and it works again. I mean, no X11, just Wayland. So the issue persists. Sometimes works, sometimes - not
My installation is fresh new. I use default kernel. I just don’t like the idea of changing default settings. Maybe developers fix the issue (maybe not).
No. It is really fresh install and on the different HDD.
And the solution is not a solution because it sometimes works, and sometimes not.
And I cannot install gstreamer plugins or they are not seen by the player.
So - pipewire works bad for me on CachyOS. I posted a bug report on Forum, but not sure if it will be addressed. Sad!
I did not create log. I installed linux zen kernel, it seems to me, it works. But I need to watch.
OK, I choose a default kernel and make log.
sudo cachyos-bugreport.sh
I uploaded the log here:
It seems the issue doesn’t depend on a kernel: cachyos or linux native.
One more interesting event.
The task panel loads too long on cachyos kernels and almost at once on linux-zen kernel. Strange things can be seen in CachyOS kingdom.
To be fair to them, I’d consider CachyOS “experimental”…
It’s so niche and so ambitious, I would really, really advise against using it to do “actual work”.
No matter how much creative work you do, you should depend on your hardware to handle the work just fine without needing to run some custom pet-project kernel…
Performance should simply and objectively not matter more than stability, because if you’re OS crashes mid-work (eg rendering something), you already spent more time than you saved through optimization. And if for some weird reason it does, then simply upgrading your hardware will do way more than optimizations might…
Personally, I decided to not use it even for non-work related tasks, because I simply don’t trust that its community is big enough for me to not have to worry about enough eyes being on the project…
Should definitely add that to the cachyos forum thread too.
When this happens, can you post the output of journalctl --user -b -xu wireplumber.service please.
Scratch that, it would be really nice to see the full log from that session ala journalctl -b > ~/Desktop/journal.log. Something kills wireplumber for whatever reason. That looks very odd.
systemd[669]: wireplumber.service: Main process exited, code=killed, status=9/KILL
systemd[669]: wireplumber.service: Failed with result 'signal'.
So wireplumber - the media manager service that is necessary for pipewire - gets killed.
I’m blank here why this would happen, but it’s a good datapoint. Post the log over at the cachy forum, maybe someone else has an idea.
PS: Also maybe take off the “resolved” tag from the forum post. Because people may assume it’s just social chatter after that and don’t click on the issue anymore.
These days I’m at idle. No load. I have plenty of time to study new software and to tame some Linux distros. ) When it comes back to work, there would be no jokes and no experiments. But who knows, when it comes back to work.
On the other hand maybe they do something that hits a bug early that eventually everybody is going to encounter. Fixing that can be a benefit to everybody. Who knows.
