You are not logged in.

#1 Today 02:13:40

tam1138
Member
Registered: 2007-09-10
Posts: 239

some audio applications become unresponsive

On the one hand, mpv and firefox seem to work fine.  On the other hand, cmus and (some) Steam games frequently and reliably become unresponsive.  Audio chat in Discord works fine.  I say "become unresponsive" because they don't respond to input, the UI doesn't update, but they don't exit.  I attached gdb to cmus and some of its 9 threads are blocked waiting for mutexes or condition variables.  In the case of cmus, it seems like starting playback works, but then providing any input causes it to seize up.  In the case of Warframe via Steam, it initially works as long as focus remains on Warframe itself.  After a few switches to other virtual desktops, it reliably becomes unresponsive.  All unresponsive processes can be dealt with using kill -9.  I have seen nothing in journalctl, either bare or with --user, though I am not a systemd whiz, so I might be missing some special incantation to get more information.  I have no idea how to debug this.  Any guidance would be most appreciated.

Offline

#2 Today 07:40:23

killertofus
Member
Registered: 2025-02-10
Posts: 271

Re: some audio applications become unresponsive

please post a journal of the boot

sudo journalctl -b | nc termbin.com 9999 

for the previous (-1) one.

 sudo journalctl -b -1 | nc termbin.com 9999 

also the strace/gdb log


I Have Linux Perl Can i Download Gnome???

Offline

#3 Today 08:22:18

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,743

Re: some audio applications become unresponsive

I attached gdb to cmus and some of its 9 threads are blocked waiting for mutexes or condition variables.  In the case of cmus, it seems like starting playback works, but then providing any input causes it to seize up.

Dump all thread backtraces at this point, https://wiki.archlinux.org/title/Core_d … _core_dump
Ideally using https://wiki.archlinux.org/title/Debuginfod

pacman -Qi cmus # it has a lot of plugins, might be useful to know which ones are installed

Generically the most common screw-up would be colliding pipewire/pulse or deprecated pipewire-media-info or actually just using the deprecated pulsenoaudio

pacman -Qs "wire|pulse"

Offline

Board footer

Powered by FluxBB