I've been using the KDE dragonized version for about two months now and everything was mostly fine, however, two days ago all of a sudden audio stopped working while I was watching some videos. When I checked the audio settings, the output device had "analog stereo duplex" profile, changing it to "analog stereo output" fixed the problem, but introduced constant popping, buzzing and crackling sound. I tried both reinstalling pipewire and switching to pulseaudio through garuda assistant but nothing worked and now my system doesn't even detect any output devices and also there's no "port" options for any device in the settings.
please help, everything worked great out of the box for my system and I wasn't doing anything unusual when it broke
Without it, you will not receive any help from the Garuda team or your topic is likely to be closed without notice.
Before you open a new help request, read relevant sections of the Arch and Garuda wiki.
Thoroughly search your issue and any error messages in the forum and on the web.
Report everything you have already attempted to solve your problem.
This thread sounds kind of similar to your problem. There are a lot of good troubleshooting efforts in there as well, although it looks like a few folks are actually going to reinstall a fresh ISO for the fix.
none of those troubleshooting methods worked. and I opened this topic after reading and trying everything about this issue that I could find here.
I tried switching to PulseAudio, this resulted in still no audio, no devices being detected. then somehow yesterday, while not doing anything related to audio (just work-related browsing), the notification that audio device was found popped up, but it started to buzz and hiss every second, then after about an hour the system started changing profiles by itself from analog stereo audio output to digital stereo audio output to some random ones for about 10 seconds and then the sound just fcking died again, back to no nothing at all.
Since the problem started in the morning of January 29, I tried rolling back (no effect), I tried downgrading pipewire (no effect). The weirdest part of the whole issue is how it happened without anything being updated or changed in the system.
If I have to reinstall the system completely, how much of my settings would I lose, provided I use separate hdd for home folder and would install same flavor of garuda?
Is garuda not a live-system? I'm asking because I tried booting into fresh iso to check for sound and it shows no devices at all, whereas in manjaro I can at least open up something in browser to verify that there is sound
For software, delete local configuration folders, depending on audio server used.
If there was a system failure, restoring a snapshot should have solved it.
After another update today, the configs for kde got messed up, plasma/latte won't load on boot, I can't do anything with my pc anymore, restoring snapshots doesn't do anything, in every restored state this travesty persists. what the hell is happening with the distro, how come it went from rock-solid stable to complete mess in a matter of couple days?
Update: I randomly stumbled into a key combination that opens latte settings, there I found out that the profile for my panels and docks layout contains nothing, but at least I can switch to duplicate profile to get latte back.
Still no sound, no devices, no options for ports in sound settings. I think this might me of some importance for troublesooting:
This is not a criticism, and this is by no means a fix, simply my observations on ways to avoid these types of problems. Running a rolling distro is very different from running a fixed point release model, so other methodologies are sometimes helpful.
Timeshift/snapper is an excellent system rollback feature, but it is in no way a complete backup solution. I would highly advise users to start making incremental backups of their home directory on an external drive. Back In Time is a good utility for ensuring your home directory and all its config files can be easily restored if you ever need to.
If you are too lazy to create proper backups, I'd suggest you become
even lazier.
By this I mean if you are reading about serious ongoing issues on the forum skip doing updates until these posts die off. Generally, if a serious bug has occurred that is affecting users it will generally be ironed out before too long with new updates. You will not learn how to correct problems by doing this, but you may avoid some serious problems that require correcting by being extra lazy.
I'm not talking about skipping updates for months, but a couple of weeks is no big deal if you want to side step an ongoing issue.
Just some observations, from someone who has never had to reinstall Garuda since the day I first installed it.
Thanks for pointers, getting familiar with snapshots is definitely something I should educate myself further on, being that this exact feature is one of the things that pulled me towards Garuda on this new PC in the first place. Btw, is there a way to give snapshots names in Garuda? Like, if I want to manually create a good one before major updates and have it named/commented. I recently found out that I accidentally got stuck in "restore backup" subvolume of snapper, lol.
On the topic of sound issue – I checked for sound in both Manjaro and the exact Garuda iso that I first installed – no sound in both of those, so it is definitely a hardware issue and now I contacted the manufacturer's service center to get it sorted under warranty. Thanks guys for good talk and decent pointers to various useful things. <3
