bspwm Issues

Around September 2021 I built a new PC. I decided this would be my first main machine running Linux, and Linux only1, so I also decided I should make it look a little pretty.
So, out with dwm and it’s default statusbar and in with bspwm and Polybar. I’ve been using this setup (mirrored on my ThinkPad E4702) since then, but lately I’ve been running into the issue described here. It’s the kind of issue that makes me want to rip my hair out, since I have no clue why it appears and how to fix it.

Since it started appearing more often I’ve thought about switching back to dwm. I’m actually kind of missing it, really. There are some minor things in bspwm I find too complicated, and I miss the simple stack layout of dwm.

What I’ll be missing in dwm is Polybar. Sure, I can just use it, but Polybar (without any patches) will be unable to show information about tags in dwm which irritates me a bit (and actually is the primary reason I decided to switch to bspwm in the first place).

The reason I want Polybar is because of statusbar icons. There is a patch for dwm but I’ve never managed to patch dwm with it.
Looks like it’s time to try again, as bspwm is (sadly) really getting on my nerves now.


  1. I had to install Windows as well because of gaming, but Linux is still the primary way I use my Desktop. 

  2. Back when I bought the E470 I didn’t know any better. I should have gotten a different model, and one without a GPU because what do I need a GPU in a Laptop for? 

Do you have a comment on one of my posts? Feel free to send me an E-Mail: witcher@wiredspace.de
To participate in a public discussion, use my public inbox: ~witcher/public-inbox@lists.sr.ht (Archive)
Please review the mail etiquette.

Posted on: March 12, 2022

Articles from blogs I read

Alpine 3.24.1 released

Alpine 3.24.1 released

via Alpine Linux News June 13, 2026

syslogd(8) privileged and non-privileged parts now separate binaries

In OpenBSD, the syslogd(8) system logger has already for a while now fork(2)ed the privileged from the non-privileged parts. Now Alexander Bluhm (bluhm@) decided it's time to split these parts into separate binaries in order to provide even better sep…

via OpenBSD Journal June 12, 2026

Introducing µlock

Last weekend I sat down and set into code a project that has been living in my head rent-free for some time: µlock (a.k.a: ulock). ulock is a minimal Wayland screen-locker, designed to work without relying on any setuid binary on Linux. This is done by relyi…

via Hugo's weblog on WhyNotHugo (雨果) June 6, 2026

Generated by openring