Killing duplicate processes when reloading BSPWM

Hello all, new to eOS and BSPWM.

I just installed eOS+BSPWM and upon reloading BSPWM after making one change to bspwmrc (bspc monitor config), I noticed there was an extra firewall-applet icon on my polybar… and another for each subsequent time it is reloaded.

This made me open htop to observe there being an increased number of processes running each time BSPWM is reloaded.

Surely others have noticed this. Does anyone have a list of processes that are duplicated each time BSPWM is reloaded so I can add a few “killall” commands to my autostart in bspwmrc in order to stop this from occuring? I tried killall’ing the obvious ones like dunst, nm-applet, etc, but there are more processes being invoked elsewhere such as firewall-applet. So, I was hoping someone had a basic list of things I can kill that is relevant to the vanilla install of eOS+BSPWM.


1 Like

While waiting for BSPWM people to arrive, you might want to have a look at:

Perhaps you could figure out one thing or other by yourself.

And welcome to EnOS’ forum!


BSPWM autostarts apps using its config file like simple bash commands, or sh scripts (IIRC is also using dex command to run XDG autostart .desktop entries).
You should also check systemctl --user list-units -t service, in case one of them is wrongly duplicated with bspwm reload.

The results upon running the command before and after reload are the same. So that’s good right?

Thanks for the advice on the dex command running the .desktop entries. There’s 10 desktop entries in my /etc/xdg/autostart/ directory:

at-spi-debus-bus, blueberry-obex-agent, blueberry-tray, eos-update-notifier, firewall-applet, nm-applet, user-dirs-update-gtk, wallpaper-once, welcome, xapp-sn-watcher

The blueberry ones may have been my doing (I believe I installed it). I added killall commands for polybar, blueberry, picom, dunst, nm-applet, firewall-applet, nitrogen, and xapp. I know this is might be a little overboard on some of them because I think only one instance of picom can run at a time and I’m not even sure that nitrogen continues to run after its call in bspwmrc. However, I am trying to completely eliminate duplicate resources.

I think the killall commands I added has eliminated roughly most of the duplicate process upon reloading but I think I’m still getting 1-2 extra each time I reload (as opposed to the 10-12 before).

Do you know of any other commands I can run before/after reload to determine precisely what processes are duplicate?

Thanks and sorry if I’m confusing, I’m kind of a linux noob.

What commands?
Just check all autostarted executables found above in htop, to see if they are cloned instead of restarted.

Also, do some research and reading on your own. It wouldn’t help you in the long run, if I told you a command to solve all issues. You have to own your bspwm yourself. That’s the idea. Else, get khronkite with Plasma and you are king :crown: