So far, the only thing I know for sure that I would consider using it for is to use JoiPlay to play RPG Maker games that I can’t get working with my normal methods but at least on my current computer/distro, I’m having issues with audio crackling.

I might find other apps to use later but for the most part, I just kind of keep android apps to android.

I am, wireplumber is part of pipewire.

While I have already found a working solution, I think the issue wasn’t that it was selecting the wrong device. it was almost as if my normal audio devices didn’t exist for some reason because nothing could see them, even my input devices were missing.

Ok, even though I said I’d wait until tomorrow, I decided to try it again. It seemed to boot more or less normally but I did try someone else’s suggestion and it got audio working again. I did undo the edit I made to the modprobe blacklist and I did keep fluidsynth and pulseaudio uninstalled but I tried using the wireplumber ppa, like someone else suggested and my audio is working again. Granded, I have no idea what actually fixed the issue, so I don’t know who to fully credit but thanks for helping.

Ok, I installed it and restarted my computer (even though I said I’d wait until tomorrow) and everything is working again. Thank you.

Ok, so a lot of them are old messages, none of the messages from this session are labeled as busy. I did just try logging out and back in and that was pretty much instantaneous, so whatever it was that caused my computer to boot slowly just effect the boot itself. But yeah, I tried restarting pipewire and everything related to it and it’s still just showing the dummy output device and audio isn’t working. Thanks for trying though.

I would like to just use pipewire, as it’s what was preinstalled in Linux Mint, so I have already removed pulseaudio. pipewire-pulse was already installed but pipewire-alsa wasn’t, so I’ve installed that and I’ve restarted pipewire and reloaded alsa but it’s still not working.

Ok well, pipewire is what’s pre-installed and as of now neither pipewire nor pulseaudio are working. I have already uninstalled pulseaudio, as I would like to just use what’s preinstalled if I can get it working again.

I have already uninstalled pulseaudio since I only installed it because pipewire stopped working and now neither of them are working. I have also already seen that pipewire-pulse was installed and it was actually running. But before I install that ppa, the last time I installed a ppa, I had to completely reinstall Linux Mint so I just want to make sure that that is actually an official version of wireplumber.

Ok and that command doesn’t list anything.

For some reason the the “stop” command didn’t work as it thought pulseaudio wasn’t running but I was able terminate it through htop. Also, that didn’t work, it did restart pipewire but my normal audio devices are still missing and I still don’t have working audio. I did, just in case, also check the journalctl and fuser commands you gave me previously, and fuser still just lists pipewire and journalctl stil gives the same error messages as before.

I just saw you edit and I did just remove pulseaudio.

I’m not sure how long everything takes normally but systemd-udev-settle.service took over two minutes. When running it with --user the longest was xdg-desktop-portal.service, which took 6 seconds. The third command gives:

UNIT LOAD ACTIVE SUB DESCRIPTION ● casper-md5check.service loaded failed failed casper-md5check Verify Live ISO checksums ● systemd-udev-settle.service loaded failed failed Wait for udev To Complete Device Initialization ● vboxdrv.service loaded failed failed VirtualBox Linux kernel module Also, no I did check and fluidsynth was the only thing removed. I think it did for some reason add some of Wine’s dependencies to autoremove but I’ll deal with those later.

Nope, that didn’t work. In fact, it made the issue worse because now I can’t get audio to work at all because my normal audio devices are missing again. I also tried running the commands again and the journalctl command is still giving me the same error messages and fuser states that the only thing running is pipewire.

Also, for some reason, my computer took a longer time to boot than normal and it made me input my password at startup, which I have Linux Mint configured to just automatically log me in without it. So if you have any further suggestions that require a restart, I don’t feel comfortable restarting my computer again and I will try them tomorrow.

I thought that it was a kernel update too but the last time it was updated was two weeks ago and nothing else relevant to audio was updated either.

I’ve restarted my computer and the fuser command does show mutiple instances of fluidsynth. I also ran the journalctl command and I’m getting a bunch of the same error messages over and over again. They are:

mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files

spa.alsa: 'front:0': playback open failed: Device or resource busy

mod.adapter: 0x5794b3a2b2a0: can't get format: Device or resource busy

I restarted my computer to check and if I run pavucontrol after starting, the only audio device listed is the dummy device. So I don’t know if that’s possible.

When I run that command, I get: $ fuser -fv /dev/snd/* USER PID ACCESS COMMAND /dev/snd/controlC0: j 2002 F.... wireplumber j 11734 F.... pulseaudio /dev/snd/seq: j 1998 F.... pipewire

I know pulseaudio is only running because I manually ran it, so could it be wireplumber that’s causing the issue?

I actually installed pulseaudio to fix this issue, pipewire is still installed it just doesn’t work for me anymore. I can try configuring pipewire and see if I can get it working again but I’m looking at the conf file and I have no idea how to configure it without breaking it further.

I tried looking into configuring alsa and pulseaudio but the only configuration they seem to have aren’t applicable to my issue. I would just switch to wayland but none of my currently preferred desktop environments have full wayland support.

I’m using the Cinnamon edition of Linux Mint 22.1. I was going to mention this in the post but I wasn’t sure if I needed to, seeing that this issue seems to be present in other distros as well and I’m not the only person to experience this issue with this sound card.