On Thu, Apr 13, 2023 at 10:18:12AM +0200, Thomas Schmitt wrote: > Hi, > > tomas@tuxteam.de wrote: > > Perhaps the browser is trying to do some kind of notification via > > audio? > > There are some "notification" entries in about:config worth > > investigating. > > None of them looks to me like being related to audio. Well, only indirectly: this was what I was trying to illustrate. The browser tells your DE/X session/whatever "go annoy the user", and the latter decides to yell at her. That's why my audio-incapacitated browser instance is able to make noises anyway. > There would be many combinations of on-off. So i did not play with them > but rather went on to notifications and loudspeaker test. Browsers are exponential hells, yes. > There are three web sites listed in "settings - Notification Permissions" > Two are "Allow" one is "Block". None of them was involved in my > experiments. I removed them all. > But the page > https://support.mozilla.org/en-US/kb/push-notifications-firefox?as=u&utm_source=inproduct > (linked by "learn more" in the setings page) says > While Firefox is open, websites which have been granted permission can > send notifications to your browser, which displays them on the screen. > Sound is not mentioned. This may or may not be the source. I was talking about "desktop notifications", which the browser might/would trigger. Of course, I may be totally wrong. > I dug out a pair of loudspeakers and attached it to the "Line Out" socket > at the mainboard backplane (lime color, matches color of plug and > description of the mainboard). > Then i hopped around between the browser tabs until pulseaudio showed > activity in top(1) (again on a Gitlab site). > Nothing is to hear. > > Google found me a hopefully harmless site to test the speakers > https://www.onlinemictest.com/de/lautsprecher-test/ > Clicking on its "<" and ">" buttons indeed plays a beep-bup-boop sound. > > When rebooting after this adventure i saw a delay of 1:30 minutes at > "A stop job is running Make remote CUPS printer available locally" > (Copied to paper and toggled into this mail. Possibly not 100% exact.) > This happened only once. Further reboots went swiftly. > > Frustrated i disabled pulseaudio globally again und put the speakers back > into their dungeon. If you don't need it, this seems like the wise thing to do. And if you want to give your browser sound, there's thankfully apulse, which fakes a Pulseaudio interface via LD_PRELOAD tricks. Cheers -- t
Attachment:
signature.asc
Description: PGP signature