#1 Today 07:03:50

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 13,357

Website

bunsen-configs-wayland-plugin available for testing

The long-promised Wayland plugin is finally ready for first trials.
There's a new package in the repos bunsen-configs-wayland-plugin and by installing that, people running BL Carbon should get a "Bunsenlabs Wayland" option at the lightdm login screen.

To get this with the minimum disruption: first do a regular apt update/upgrade so bunsen-configs gets upgraded to 13.7.
Then log out and back in. You will get some popups about overwriting user config files - if you haven't made many changes to your desktop since installing then it will probably be OK to click OK on each, otherwise give it some thought, look at the diffs and make your decision. Anyway it will make backups of your files before overwriting them.

One case though: ~/.config/bunsen/autostart: if you are starting up xfce4-clipman there then even if you decline the offer to overwrite the file you should comment out that line. The panel will be configured to use xfce4-clipman-plugin, and starting up clipman directly from autostart will break the new panel configs. The clipman plugin uses a different icon from clipman in the systray, but it works the same. The important point is that the systray clipman does not work on Wayland while the clipman panel plugin works on both X11 and Wayland. If you get in a mess over the panel configs with this then you can always go in and fix it up manually using the menu User Settings > Xfce4-panel > xfce4-panel Preferences, to add the clipman plugin.

Once bunsen-configs has upgraded to 13.7, probably best to logout/in one more time before doing 'sudo apt install bunsen-configs-wayland-plugin'.

Log out again and you should see the "Bunsenlabs Wayland" option at the lightdm login screen. Give it a try!

---
In fact, there is still work to do, in particular the session startup sequence goes through the Debian shell snippets in /etc/X11/Xsession.d and we need a new approach to that so the useful bits are still picked up but the X11-only stuff is not. (I've already got an idea how we can do that.) ~/.xsession-errors still has a log which might give you some hints. At the very least it should start "Wsession: Wayland session started for <user> at <date>..."

For now, please post any glitches you find (I'm sure there are plenty) and we can list them up here.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop