Same Sound Issue - With a twist after pipewire install.
All, The .xsession-error and sound drop-out that occurs on Leap 15.4 kde3 has a slight twist after installing pipewire a month ago or so. Sound for the desktop (ksound theme, minimize, maximize, etc.. sounds) randomly just stop working. Other sounds like those from browser audio, etc.. continue to work. Once the kde sounds stop, they are dead until you restart the desktop. Checking xsession-errors there are a few messages I don't recognize after 15 years of looking at them... Maybe something that provides a clue for fixing? Repeating errors: jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave auto_sink: Could not load oss auto_sink: Could not load sun akode: Could not open auto-sink jack_client_new: deprecated Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave auto_sink: Could not load oss auto_sink: Could not load sun akode: Could not open auto-sink KNotify::playTimeout jack_client_new: deprecated Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave auto_sink: Could not load oss auto_sink: Could not load sun akode: Could not open auto-sink jack_client_new: deprecated Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave auto_sink: Could not load oss auto_sink: Could not load sun akode: Could not open auto-sink KNotify::playTimeout Anybody else notice any change in the sound bug after pipewire? -- David C. Rankin, J.D.,P.E.
On 10/28/23 19:20, David C. Rankin wrote:
All,
The .xsession-error and sound drop-out that occurs on Leap 15.4 kde3 has a slight twist after installing pipewire a month ago or so. Sound for the desktop (ksound theme, minimize, maximize, etc.. sounds) randomly just stop working. Other sounds like those from browser audio, etc.. continue to work. Once the kde sounds stop, they are dead until you restart the desktop.
Hah, In the past both play and aplay would continue to work. Now play works but aplay (alsa) is dead: 19:25 wizard:~/.../tmp/debug/cs50> play volume/input.wav volume/input.wav: File Size: 353k Bit Rate: 1.41M Encoding: Signed PCM Channels: 2 @ 16-bit Samplerate: 44100Hz Replaygain: off Duration: 00:00:02.00 In:100% 00:00:02.00 [00:00:00.00] Out:88.2k [ | ] Clip:0 Done. 19:25 wizard:~/.../tmp/debug/cs50> aplay volume/input.wav ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave aplay: main:831: audio open error: Device or resource busy -- David C. Rankin, J.D.,P.E.
On 10/28/23 19:28, David C. Rankin wrote:
Hah,
In the past both play and aplay would continue to work. Now play works but aplay (alsa) is dead:
19:25 wizard:~/.../tmp/debug/cs50> play volume/input.wav
volume/input.wav:
File Size: 353k Bit Rate: 1.41M Encoding: Signed PCM Channels: 2 @ 16-bit Samplerate: 44100Hz Replaygain: off Duration: 00:00:02.00
In:100% 00:00:02.00 [00:00:00.00] Out:88.2k [ | ] Clip:0 Done. 19:25 wizard:~/.../tmp/debug/cs50> aplay volume/input.wav ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave aplay: main:831: audio open error: Device or resource busy
Problem found, but not understood: The issue was konqueror --profile filemanagement. The circumstance is odd, but explains somewhat the "unable to open slave" part of the error -- but why is a mystery. What happened. I created $HOME/tmp/recipes and created/edited a file with vim in that directory. In konqueror I navigated to the directory and previewed the file to do a copy/paste into an email and closed the file, but left the directory open in konqueror. Then later came back in konsole and moved the file to another directory and deleted the directory (leaving konqueor holding a reference to the directory inode -- which should be irrelevant, but wasn't) Later sound dropped out, I don't know how much later, but the next time that a desktop sound would have been played, ALSA rolled-over and died with the errors shown in .xsessions-errors and above. I had no clue that konqueror holding a reference to a deleted directory would cause ALSA issues -- it shouldn't, but preparing to log out/in to restart the desktop I moved the directory to something else -- and sound started working again as soon as konqueror released the inode reference! 21:25 wizard:~/.../tmp/debug/cs50> aplay volume/input.wav Playing WAVE 'volume/input.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo No problems. I know this isn't the cause of all the KDE3 sound gremlins -- but it points to a potential cause. If part of kde maintains a reference to a temporary file or directory that is deleted -- that could have the same effect as what I did above. Though I have no clue how repeatable this is or how to track down what is KDE is freaking out on a stale directory reference. If I can reproduce it, I'll look at open files with lsof before changing what is open in konqueror. Then if repeatable, we can file a bug report. -- David C. Rankin, J.D.,P.E.
On 10/28/23 21:29, David C. Rankin wrote:
I know this isn't the cause of all the KDE3 sound gremlins -- but it points to a potential cause. If part of kde maintains a reference to a temporary file or directory that is deleted -- that could have the same effect as what I did above. Though I have no clue how repeatable this is or how to track down what is KDE is freaking out on a stale directory reference. If I can reproduce it, I'll look at open files with lsof before changing what is open in konqueror. Then if repeatable, we can file a bug report.
The problem is discord in Firefox. When discord is loaded in firefox, it claims the alsa device and KDE sounds cannot play, e.g. $ aplay cs50/volume/input.wav ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave aplay: main:831: audio open error: Device or resource busy Closing the discord tab in Firefox solves the issue completely: $ aplay cs50/volume/input.wav Playing WAVE 'cs50/volume/input.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo The open directory file-descriptor was a coincidence -- discord in Firefox is the issue. Is there any way to keep discord from claiming the sound device as its own so this doesn't happen? -- David C. Rankin, J.D.,P.E.
I've had to deal with similar problems before, a web-based platform claiming the sound device. In my case, if I remember correctly, I instructed my users to go to web-based application settings and disable the sound. If this discord app you're using has a similar option, you could try that. Rafael On Wed, Nov 1, 2023 at 6:30 AM David C. Rankin < drankinatty@suddenlinkmail.com> wrote:
On 10/28/23 21:29, David C. Rankin wrote:
I know this isn't the cause of all the KDE3 sound gremlins -- but it points to a potential cause. If part of kde maintains a reference to a temporary file or directory that is deleted -- that could have the same effect as what I did above. Though I have no clue how repeatable this is or how to track down what is KDE is freaking out on a stale directory reference. If I can reproduce it, I'll look at open files with lsof before changing what is open in konqueror. Then if repeatable, we can file a bug report.
The problem is discord in Firefox.
When discord is loaded in firefox, it claims the alsa device and KDE sounds cannot play, e.g.
$ aplay cs50/volume/input.wav ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave aplay: main:831: audio open error: Device or resource busy
Closing the discord tab in Firefox solves the issue completely:
$ aplay cs50/volume/input.wav Playing WAVE 'cs50/volume/input.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
The open directory file-descriptor was a coincidence -- discord in Firefox is the issue. Is there any way to keep discord from claiming the sound device as its own so this doesn't happen?
-- David C. Rankin, J.D.,P.E.
On 2023-11-01 14:24, Rafael H. B. wrote:
I've had to deal with similar problems before, a web-based platform claiming the sound device. In my case, if I remember correctly, I instructed my users to go to web-based application settings and disable the sound.
If this discord app you're using has a similar option, you could try that.
Firefox can disable or mute the sound in a tab; I don't remember which. Ah, mute. Right click on tab. Maybe that is not enough. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))
On 11/1/23 08:29, Carlos E. R. wrote:
Firefox can disable or mute the sound in a tab; I don't remember which. Ah, mute. Right click on tab. Maybe that is not enough.
Thank you Carlos and Rafeal, I'll try in firefox. I'll also see how the discord app behaves compared to running it in a firefox tab. I know just muting sound in the discord web-interface inside firefox doesn't make any difference, but I haven't tried granting/revoking sound access though the privacy settings in firefox. Will report back. -- David C. Rankin, J.D.,P.E.
On 11/1/23 19:02, David C. Rankin wrote:
I'll try in firefox. I'll also see how the discord app behaves compared to running it in a firefox tab.
I know just muting sound in the discord web-interface inside firefox doesn't make any difference, but I haven't tried granting/revoking sound access though the privacy settings in firefox.
Will report back.
Using the discord app is fine. There is no sound conflict with ALSA as there is when running discord from the web-interface in firefox. It's a bug somewhere, but whose bug is it? Firefox, KDE3? -- David C. Rankin, J.D.,P.E.
participants (3)
-
Carlos E. R. -
David C. Rankin -
Rafael H. B.