Created attachment 133157 [details] bspwm config file SUMMARY Starting with the previous version of Plasma, I configured my system to start the graphics session without using KWin, replacing it with bspwm. Obviously I am aware that, operating this replacement, it is not possible to have a perfect compatibility, however until now I have been able to make everything I needed to work. The problem I'm experiencing occurred yesterday for the first time, after installing the latest version of Plasma from the Manjaro stable repositories: the new volume pop-up, which should appear when editing the latter, hasn't been seen anymore despite being correctly enabled in the settings (this is proved by the fact that it appears when I start a session with KWin enabled). If necessary, I am available to provide any kind of log while I attach my bspwm configuration, if it is useful. STEPS TO REPRODUCE 1. Open Plasma along with bspwm 2. Enable the volume pop-up and try to increment/decrement the audio level 3. See that the pop-up is not shown OBSERVED RESULT The pop-up is not shown EXPECTED RESULT The pop-up should appear (even if in the wrong position or in tiled mode) SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux: Manjaro 20.2 (Kernel 5.9.3-1MANJARO) KDE Plasma: KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION bspwm Version: 0.9.10-1
I believe the OSD is built into kwin. It's not part of Plasma.
No, I don't think so. Today I used my computer without plugging-in the external monitor and the volume pop-up appeared as expected. So I thought that the problem was caused by wrong positioning by bspwm and I tried to set the WM to not manage the pop-up (by setting the flag 'manage=off' to the window class 'plasmashell'), but when I connected the second monitor, the problem occurred again.
It's in Plasma, not KWin. KWin shouldn't be strictly speaking required here.
The OSDs come from Plasma, but they're positioned by the window manager. If KWin is the window manager, KWin does it. If something else is the window manager, that something else is responsible. We adhere to the spec for OSD windows here, so I'd say it's most likely an issue in bspwm.