bunsen-configs-wayland-plugin available for testing

johnraff · 2026-09-11 04:57:10

^ kanshi as an extension of wlr-randr I guess? I don't grasp it 100% but it looks to me like automation to choose a display when it's plugged in?

Maybe it wouldn't be too hard to make a CLI wrapper for wlr-randr that lets the user choose a config set from wlr-randr's list, offer to apply it (with a confirmation timeout in case the mode setting is broken) and write it to a file that is run from the user's autostart?

Of course a pretty GUI that did all that would be better. For a moment I thought nwg-displays might be it, but it doesn't support wlroots compositors.

(wdisplays ships no man page btw )

Last edited by johnraff (2026-09-11 05:01:03)

johnraff · 2026-09-11 05:13:26

There's also something called shikane but no deb package yet.

unklar · 2026-10-27 07:38:53

^Yesterday I downloaded labwc-menu-generator from here and installed it using apt. There were no errors; the application menu was available immediately after logging out and back in.

johnraff · 2026-10-27 08:07:18

^Thanks for checking that. So for BL Nitrogen we can just use labwc-menu-generator from the regular Debian repos.

Meanwhile, for BL Carbon it might be an easy package to backport to Trixie. I'll have a look.
@unklar what Debian version are you testing on?

unklar · 2026-10-27 15:29:23

inxi-system-info

inxi -Fzxr
System:
  Kernel: 6.12.113+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
  Desktop: LabWC v: N/A Distro: BunsenLabs 13 (Carbon)
    base: Debian GNU/Linux 13
Machine:
  Type: Desktop Mobo: Shuttle model: DS50U v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: 1.07 date: 10/24/2023
CPU:
  Info: 5-core model: Intel Celeron 7305 bits: 64 type: MCP arch: Alder Lake
    rev: 4 cache: L1: 464 KiB L2: 3.2 MiB L3: 8 MiB
  Speed (MHz): avg: 500 min/max: 400/1100:900 cores: 1: 500 2: 500 3: 500
    4: 500 5: 500 bogomips: 11136
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-UP3 GT1 [UHD Graphics] vendor: Holco Enterprise
    Co /Shuttle driver: i915 v: kernel arch: Xe bus-ID: 00:02.0
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: LabWC driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7-2+deb13u1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
  Info: Tools: api: eglinfo,glxinfo wl: kanshi,wlr-randr x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio vendor: Holco
    Enterprise Co /Shuttle driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  API: ALSA v: k6.12.113+deb13-amd64 status: kernel-api
  Server-1: PipeWire v: 1.4.2 status: active
Network:
  Device-1: Intel Ethernet I219-LM vendor: Holco Enterprise Co /Shuttle
    driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Ethernet I226-LM vendor: Holco Enterprise Co /Shuttle
    driver: igc v: kernel port: N/A bus-ID: 02:00.0
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 03:00.0
  IF: wlp3s0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB
    bus-ID: 1-10:6
  Report: hciconfig ID: hci0 rfk-id: 1 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 942.7 GiB used: 56.8 GiB (6.0%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKBA512QFM-1BD1AABGB
    size: 476.94 GiB temp: 25.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    temp: 27.0 C
Partition:
  ID-1: / size: 81.24 GiB used: 10.64 GiB (13.1%) fs: ext4 dev: /dev/sda8
  ID-2: /boot/efi size: 98.8 MiB used: 6.9 MiB (7.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 29.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: 1696
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/home:antonbatenev:medit.list
    1: deb http://download.opensuse.org/repositories/home:/antonbatenev:/medit/Debian_13/ /
  Active apt repos in: /etc/apt/sources.list.d/bunsen-trixie-backports.sources
    1: deb https://pkg.bunsenlabs.org/debian/ trixie-backports main
  Active apt repos in: /etc/apt/sources.list.d/bunsen.sources
    1: deb https://pkg.bunsenlabs.org/debian/ carbon main
  Active apt repos in: /etc/apt/sources.list.d/debian-trixie-backports.sources
    1: deb https://deb.debian.org/debian/ trixie-backports main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.sources
    1: deb https://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
    2: deb https://deb.debian.org/debian-security/ trixie-security main contrib non-free non-free-firmware
    3: deb https://deb.debian.org/debian/ trixie-updates main contrib non-free non-free-firmware
Info:
  Memory: total: 32 GiB note: est. available: 30.93 GiB used: 1.33 GiB (4.3%)
  Processes: 203 Uptime: 7h 57m Init: systemd
  Compilers: N/A Shell: Bash v: 5.2.37 inxi: 3.3.38

Last edited by unklar (2026-10-27 15:42:53)

hhh · 2026-10-27 18:33:59

johnraff wrote:

For a moment I thought nwg-displays might be it, but it doesn't support wlroots compositors.

Typo? It absolutely does...
https://github.com/nwg-piotr/nwg-displays
https://packages.debian.org/trixie/nwg-displays

johnraff · 2026-10-28 00:38:23

hhh wrote:

johnraff wrote:
For a moment I thought nwg-displays might be it, but it doesn't support wlroots compositors.
Typo?

What typo?

It absolutely does...
https://github.com/nwg-piotr/nwg-displays
https://packages.debian.org/trixie/nwg-displays

I had already studied both those pages before making my claim that wlroots compositors weren't supported. Some nwg-displays github issues too as I recall.

nwg-displays-github wrote:

The program is expected to:
support sway, Hyprland, Niri and mangowm only.

nwg-displays-debian wrote:

- support sway and Hyprland only.

and: https://hypr.land/news/independentHyprland/

hyprland-news wrote:

Hyprland is no longer a wlroots-based Wayland compositor

So it looks to me like no wlroots support.

hhh · 2026-10-28 09:03:58

Huh, mangowm says it's wlroots right on its homepage...
https://mangowm.github.io/

I confess to being very confused as to what wlroots means. It's modules (or libraries) written in C that save time when building a compositor? So the compositor itself has to be written in C as well? Sway is written in C, hyrpland is now rust, niri is rust as well, and labwc is written in C but is wlroots based? Don't answer, I'm just saying it's confusing to the end user.

johnraff · 2026-10-29 02:27:50

johnraff wrote:

For a moment I thought nwg-displays might be it, but it doesn't support wlroots compositors.

hhh wrote:

mangowm says it's wlroots right on its homepage

So it does! So you win that one.

But nwg-displays looks quite firm in its list of supported compositors. I think I tested it with labwc and found it didn't work. I still have it installed so I'll log into a Wayland session and check it one more time.

PS:

$ nwg-displays
Neither sway nor Hyprland detected, terminating

So it's quite picky about which compositor is trying to run it. Maybe the Forky version is more forgiving.

Last edited by johnraff (2026-10-29 02:38:18)

hhh · Yesterday 15:24:13

@johnraff, I fired up BL Carbon LIVE today to add a partition to my computer and to check some wayland configs you've included with this package, a couple more observations...

First, OT, there's this thread here in Dev & Suggestions and there's this thread in Dev Discussions...
https://forums.bunsenlabs.org/viewtopic.php?id=9749

xwall is still not setting a wallpaper. Is this because I'm in a LIVE session or has the upgrade for bunsen-configs not avaialable yet?

No conky? -edit- Not ready for prime time...
https://forums.bunsenlabs.org/viewtopic.php?id=9854 /edit

I had to open the battery plugin's Properties and set "Show Label" to "None", otherwise the percentage hangs off of the vertical panel.

I disabled xfce4-clipman in ~/.config/bunsen/autostart but the new plugin didn't load, I had to add what's called "Clipman" from the list of panel plugins. Hmmm, doing some testing now, I'll post back.

That is all, thanks!

Last edited by hhh (Yesterday 19:10:15)

hhh · Yesterday 15:28:57

@everyone... You can get volume up/down/mute keyboard shortcuts working again by simply installing pulseaudio-utils, no logout/login required...

sudo apt install pulseaudio-utils

Thanks to @johnraff for finding this fix!

To restore the minimize/toggle maximize buttons in Firefox, right-click a toolbar>Customize Toolbar...>In the lower-left window corner check the box for 'Titlebar'

Thanks to me for finding this fix!

hhh · Yesterday 19:22:35

I'm running the BL Carbon LIVE session from a USB stick, the clipman panel plugin issue has me confused. I have upgraded the system, have not rebooted (obviously, the upgrades will not persist through a reboot) and have not install the bunsen-configs-wayland-plugin...

user@debian:~$ apt policy xfce4-clipman*
xfce4-clipman-plugin:
  Installed: 2:1.6.6-1
  Candidate: 2:1.6.6-1
  Version table:
 *** 2:1.6.6-1 500
        500 https://deb.debian.org/debian trixie/main amd64 Packages
        100 /var/lib/dpkg/status
xfce4-clipman:
  Installed: 2:1.6.6-1
  Candidate: 2:1.6.6-1
  Version table:
 *** 2:1.6.6-1 500
        500 https://deb.debian.org/debian trixie/main amd64 Packages
        100 /var/lib/dpkg/status
user@debian:~$ sudo apt purge --autoremove xfce4-clipman-plugin
REMOVING:                       
  bunsen-configs*  bunsen-configs-live*  xfce4-clipman-plugin*

Summary:
  Upgrading: 0, Installing: 0, Removing: 3, Not Upgrading: 0
  Freed space: 1,040 k

Continue? [Y/n] n
Abort.

"Add new items" in the panel shows 'Clipman", which reports the clipman daemon as already running. Continued next post after I install the BL wayland-plugin and am in a Wayland session. I'm not going to disable xfce4-clipman in autostart.

hhh · Yesterday 19:44:04

OK, I sort of get it. The carbon autostart starts the clipman daemon which gives us a panel interface via the panel's status tray plugin. If you try to add the actual clipman-plugin you get an error message that the daemon is already running,

But autostarting the daemon doesn't give you a systray clipboard interface, so you have to add the clipboard-plugin. Disabling the autostart entry is to prevent the warning in the Xorg session.

Is that right?

johnraff · Today 02:51:53

hhh wrote:

First, OT, there's this thread here in Dev & Suggestions and there's this thread in Dev Discussions...
https://forums.bunsenlabs.org/viewtopic.php?id=9749

The dev discussions thread was to discuss the technicalities, get input from other devs and try to finalise what the plugin should be like.
This thread came later, and is for everybody who wants to try out the plugin, and post feedback.

xwall is still not setting a wallpaper. Is this because I'm in a LIVE session or has the upgrade for bunsen-configs not avaialable yet?

The latter I'm afraid. I've been slow getting the updated configs out - partly because there were various other small issues I wanted to fix first, partly because other packages came up that needed fixing (eg bunsen-exit) and partly because I've been quite busy with various Real Life things. Sorry about that, but I'm hoping to get the shiny plugin out soon. I think it should get an Official Announcement so we want to get all the glitches out first...

No conky? -edit- Not ready for prime time...
https://forums.bunsenlabs.org/viewtopic.php?id=9854 /edit

The default conky should be there, looking the same as on X11, but right, most of the things that we can do with conky on X11 don't work on Wayland, except via xwayland which is still very messy and unreliable. I think on Nitrogen things will be better because both conky and labwc got a lot of improvements.

So on Carbon Wayland a basic default conky is all we can offer. Better than nothing - it's reliable at least.

I had to open the battery plugin's Properties and set "Show Label" to "None", otherwise the percentage hangs off of the vertical panel.

Thanks for finding that. Maybe we can tweak the panel xml to deal with it.

johnraff · Today 02:56:39

hhh wrote:

OK, I sort of get it. The carbon autostart starts the clipman daemon which gives us a panel interface via the panel's status tray plugin. If you try to add the actual clipman-plugin you get an error message that the daemon is already running,
But autostarting the daemon doesn't give you a systray clipboard interface, so you have to add the clipboard-plugin. Disabling the autostart entry is to prevent the warning in the Xorg session.
Is that right?

That was a tricky situation because the existing clipman functionality had to be replaced by the newer plugin for it to work on Wayland. Users who were staying on X11 only wouldn't need it, but the new plugin works on X11 too. The autostart entry has to be removed for the plugin to work. Is that consistent with what you're seeing?

MarkW · Today 09:31:16

@johnraff. Is Labwc anything to do with BL or just a huge coincidence?

unklar · Today 10:41:04

hhh wrote:

xwall is still not setting a wallpaper. Is this because I'm in a LIVE session or has the upgrade for bunsen-configs not avaialable yet?

xwwall works here.

❯ apt policy xwwall
xwwall:
  Installiert:           0.2.5-1
  Installationskandidat: 0.2.5-1
  Versionstabelle:
 *** 0.2.5-1 500
        500 https://pkg.bunsenlabs.org/debian carbon/main amd64 Packages
        100 /var/lib/dpkg/status

❯ inxi -Sxxx
System:
  Host: carbon3 Kernel: 6.12.116+deb13-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 14.2.0 clocksource: tsc
  Desktop: LabWC v: N/A with: xfce4-panel tools: xss-lock vt: 8 dm: LightDM
    v: 1.32.0 Distro: BunsenLabs 13 (Carbon) base: Debian GNU/Linux 13

Conky
when the system starts, it will open on the left, with a small window.
After "exit" and "restart" in Conky-Manager, the window is correctly placed in its rightful position.

#41 2026-09-11 04:57:10

Re: bunsen-configs-wayland-plugin available for testing

#42 2026-09-11 05:13:26

Re: bunsen-configs-wayland-plugin available for testing

#43 2026-10-27 07:38:53

Re: bunsen-configs-wayland-plugin available for testing

#44 2026-10-27 08:07:18

Re: bunsen-configs-wayland-plugin available for testing

#45 2026-10-27 15:29:23

Re: bunsen-configs-wayland-plugin available for testing

#46 2026-10-27 18:33:59

Re: bunsen-configs-wayland-plugin available for testing

#47 2026-10-28 00:38:23

Re: bunsen-configs-wayland-plugin available for testing

#48 2026-10-28 09:03:58

Re: bunsen-configs-wayland-plugin available for testing

#49 2026-10-29 02:27:50

Re: bunsen-configs-wayland-plugin available for testing

#50 Yesterday 15:24:13

Re: bunsen-configs-wayland-plugin available for testing

#51 Yesterday 15:28:57

Re: bunsen-configs-wayland-plugin available for testing

#52 Yesterday 19:22:35

Re: bunsen-configs-wayland-plugin available for testing

#53 Yesterday 19:44:04

Re: bunsen-configs-wayland-plugin available for testing

#54 Today 02:51:53

Re: bunsen-configs-wayland-plugin available for testing

#55 Today 02:56:39

Re: bunsen-configs-wayland-plugin available for testing

#56 Today 09:31:16

Re: bunsen-configs-wayland-plugin available for testing

#57 Today 10:41:04

Re: bunsen-configs-wayland-plugin available for testing

Board footer