While I'm dropping by,
This may already be fixed on TDE, but openSUSE's KDE3 has an issue where running discord in FF captures socket used by ALSA and kills the KDE3 system sounds. Closing the tab releases the socket and restore everything as it should be.
Instead of using the discord web-interface, using the Linux desktop app, has no problem and the KDE3 sounds continue right on playing.
If you want to test on TDE, just open the discord web-app in firefox. You can confirm the issue (well, your sound-theme would die...) by checking with aplay, e.g.
$ aplay somefile.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
I note here as I don't know if this is FF, or a base ALSA or KDE/TDE issue. If you patched for it, we may need to cherry-pick the commit.
Keep up the great work all!
пт, 3 нояб. 2023 г., 09:10 David C. Rankin drankinatty@suddenlinkmail.com:
While I'm dropping by,
This may already be fixed on TDE, but openSUSE's KDE3 has an issue where running discord in FF captures socket used by ALSA and kills the KDE3 system sounds. Closing the tab releases the socket and restore everything as it should be.
I tend to use apulse with Slackware's build of Firefox (currently mozilla-firefox-115.4.0esr-i686-1_slack15.0 )
https://github.com/i-rinat/apulse.git
but not tried Discord (web version) there in years ...
Instead of using the discord web-interface, using the Linux desktop app, has no problem and the KDE3 sounds continue right on playing.
If you want to test on TDE, just open the discord web-app in firefox. You can confirm the issue (well, your sound-theme would die...) by checking with aplay, e.g.
$ aplay somefile.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
I note here as I don't know if this is FF, or a base ALSA or KDE/TDE issue. If you patched for it, we may need to cherry-pick the commit.
Keep up the great work all!
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
please by add support refresh rate monitors 144hz, 120hz , and 165 hz
Em sex., 3 de nov. de 2023 às 03:10, David C. Rankin < drankinatty@suddenlinkmail.com> escreveu:
While I'm dropping by,
This may already be fixed on TDE, but openSUSE's KDE3 has an issue where running discord in FF captures socket used by ALSA and kills the KDE3 system sounds. Closing the tab releases the socket and restore everything as it should be.
Instead of using the discord web-interface, using the Linux desktop app, has no problem and the KDE3 sounds continue right on playing.
If you want to test on TDE, just open the discord web-app in firefox. You can confirm the issue (well, your sound-theme would die...) by checking with aplay, e.g.
$ aplay somefile.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
I note here as I don't know if this is FF, or a base ALSA or KDE/TDE issue. If you patched for it, we may need to cherry-pick the commit.
Keep up the great work all!
-- David C. Rankin, J.D.,P.E.
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Andrew Randrianasulu -
carlos alberto
-
David C. Rankin