You are not logged in.
Unfortunately I have to be out all day today, but your symptoms are so similar to what I was getting trying to run Wayland on a qemu VM (switching to QXL video fixed it) that I was sure that's what you were doing. But I haven't yet tested installing to the VM, still playing with live sessions. The plus is that every reboot gives you a fresh start but the minus is that you have to go through the upgrading etc every time.
I'll get back to this tomorrow. But, to repeat, I don't get any issues with the BL Wayland session running on real hardware.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky and Mastodon, there's also some GitStuff )
Offline
@johnraff. Is Labwc anything to do with BL or just a huge coincidence?
I have enjoyed a simple setup with openbox and tint2 for a long time. Initially I used Arch Linux, but then moved to bunsenlabs as I found enjoyed the community and found the pre-configured setup convenient. I joined the team and was an active contributor to the project.
Then, a few years ago, I wanted to move to Wayland. I found that there weren't many options that didn't require me to re-wire my brain. I have tried tiling managers like i3 many times over the years, but can't quite get used to them. Sometimes I've stuck with them for a month or so, but always reverted back to the stacking paradigm. So, I knew sway wouldn't be right on that basis.
There weren't many options around then. Ignoring a few small hacky projects on top of tinywl (the wlroots example compositor), it fundamentally came down to mutter, kwin, hikari, weston and wayfire.
So, I decided to have a go at re-writing openbox for wayland, and here we are, six years on. Maybe it's just me, but when I'm developing I find I don't have much time for forums and such like. It's not that I'm not interested (cos I am) it's just a choice of where I spend spare time.
Interestingly, I find that there still aren't many options for stacking compositors. If we ignore those that aren't mature enough - or popular enough to be packaged by common distros, and if we ignore kwin and mutter as too integrated with their respective stacks, I think it comes down to labwc, cosmic and wayfire.
Offline
@Malm, thanks for the reply! I'm always glad when I see you check in.
re: stacking Wayland compositors, Joey Snedden at omg.ubuntu recently did an article on a new project, Polo, a wayfire rewrite of Marco (MATE). I tested it and offered some feedback, thought you might be interested...
https://github.com/KeremSoke/polo/issues/5
I've been doing some preliminary live-builds for BL Nitrogen using labwc and xfce4-panel, we might offer a second ISO that is Wayland-only. Expect to see me posting some issues on github! ![]()
Why why why why?!!???
Offline
@hhh Great to see you too!
I did notice polo the other day. Looks interesting, will have a deeper look.
I think cinnamon have been working on a fork of mutter in a similar sense.
There is another mate spin here using labwc: https://github.com/labwc/labwc/discussions/3791
I think there is a lot to be said for doing a Wayland-only iso.
Offline
I think there is a lot to be said for doing a Wayland-only iso.
+1 Absolutely agree! ![]()
Offline