Sound dependencies stay around for hours in processes

People seem to get defensive when I criticize Linuxisms and dependencies. They're actually, GPLisms. Though, these dependencies annoy me, that they leave a residue on how my operating system behaves.

I'll turn off Waterfox or in the past Firefox, and not be on my computer for a few hours. It will have difficulty starting, so I run ps, and Pulseaudio and more than one dbus instance will be up. pkill doesn't always work on them. So, I have to use kill with the process id. OSS and Sndiod don't do this. At least, Pulseaudio and dbus are LGPL, which gives room to make improvements around these programs. I should be able to program in order to improve the way these programs work by myself.

So, if people wonder why I talk about bloat which is prevalent on Linux systems that comes here. Stuff like that is why. That's not efficient.

Maybe, I should rather be thankful that we have those programs instead, which is better than nothing, but they need to be improved, and cleaned up. Also, be thankful that these are under LGPL rather than GPL. Also, the FreeBSD userland is a lot better than it used to be.

My Android doesn't act like this, slowed down later from hanging around processes.
 
so I run ps, and Pulseaudio and more than one dbus instance will be up. pkill doesn't always work on them. So, I have to use kill with the process id.
Probably unrelated, but Thunar on Xfce seems invincible with locking drives during either smb or NTFS transfers :p


Why are you using Pulseaudio with Firefox?
 
Neither pulseaudio nor dbus are demons that are supposed to go away on their own. Once started, pulseaudio is supposed to hang around for the duration of the user's desktop session.
 
Why are you using Pulseaudio with Firefox?
That's how it comes in packages. I used to compile ports to have a better implementation, but that's too much work now.

Even with the dbus & pulseaudio processes killed, there was a segfault trying to start Waterfox, so I had to reboot. I had had to use the terminal to see the error message.

Neither pulseaudio nor dbus are demons that are supposed to go away on their own. Once started, pulseaudio is supposed to hang around for the duration of the user's desktop session.
That's what it looks like.
 
Back
Top