Molly M.B. Maclachlan

I wouldn't call FFmpeg 5.0 experimental at all. It's a major release version and was released as stable back in January. They even added a note at the end of...

> Feel free to open an issue since this might help pinning the issue down on the flatpak distribution. Done!

Also on Slackware Current with this issue, `atom --no-sandbox` makes it work. It also seems to be affecting Microsoft Teams (same symptoms, same fix), so it might not be Atom-specific?

Is there an issue for it open on the Electron repository? If not, it's probably best that one's opened there instead of us spamming the Atom devs. =)

Just want to drop in on here and say I've also run into this recently. It's a pretty big accessibility issue, since if, like with mine, the website design heavily...

I never managed to find a fix for the pip version to test if behaviour is different, but this seems to have been fixed in one of the updates to...

I also have this issue. If it helps in terms of audio server, I'm running Pipewire (with Pulse compatibility). In terms of changing audio device, the only thing I could...

On my end the relevant packages are: ``` alsa-lib-1.2.6.1-x86_64-1 alsa-plugins-1.2.6.1-x86_64-1 pipewire-0.3.50-x86_64-1 pulseaudio-15.0-x86_64-4 wireplumber-0.4.9-x86_64-1 ``` Sound works perfectly for all other applications here too.

On my system there is a `99-pulseaudio-default.conf.example`, but no actual in-use `99-pulseaudo-default.conf`. Running `aplay --list-devices --list-pcms` doesn't show any `default` entry at all. 🤔

Finally got this workaround working. It turns out on my system, there was an `/usr/share/alsa/alsa.conf.d/50-pipewire.conf` and `/usr/share/alsa/alsa.conf.d/99-pipewire-default.conf` that were missing links in `etc/asla/conf.d`. On adding those links, `aplay --list-devices --list-pcms`...