Taking the plunge into the world of Wayland from X11 and well its been a interesting plunge. I had to learn how to make a kanshi config file so that I can get use out of both monitors. I had to create a script to split my dual screen wallpapers in half as swaybg doesn’t support multi-monitor and from what I searched not much does. They say there is an unsupported version with the `-m multi monitor`version however I decided to just split the wallpapers as making a script I wrote gave me more confidence than downloading something that may or may not work. A bit of trial and error with the script but in the end it works well.
I also had to update my screen brightness script to work on wayland. It was a bit of a pain as I had to use two different programs for the monitors I have(now I have two different scripts for the WM I’m in). The display port uses one program and the hdmi uses another. Makes it seem kinda bloatish however I have plenty of space.I did get A.I to help with the scripts as it doesn’t suffer dyslexia like I do and just wanted something to look over it and make sure things were set correctly without having ill affects on the system. Yes it made adjustments and yes I understand what each adjustment was for and what it does.
I had to adjust my rc.xml file from the openbox. I was able to recreate most of my keybinds. I left a few out as I will do things on a trial basis of what I actually use and need.I also had to update and change a few things in my Conky. A few of the X11 window settings no longer work under wayland and multi monitor support isn’t really supported however gap_x and gap_y can be set to where you want it just set the alignment to none.
One of the best things was being able to keep Thunar. I keep pcmanfm as a backup however I’ve just never really like it. I can’t seem to however set up my Open as Root custom action. I have to read up and see if and what the change is to get it to work in wayland.
There has been a few pains such as getting GTK and QT to use dark themes I had to end up running a gsettings command to set the themes for GTK. LXQT has worked wonderfully on both systems just another reason to love it
I’m really liking the labwc and have spent most of this last week playing in it and most of the day just using it like I do my daily with a few exceptions. I am getting ready to install on my main system (no os reinstall) since both are on the other setup anyway and there is no interference issues and it will be good to have a backup for my WM.
Overall its been a fun terrible experience I have no regrets jumping head first into it. There was hair pulling thank God the neighbor had hair (This is a joke no one was actually harmed during this experiment ) and lots of cursing. It was also fun taking the experiment from a VM to a physical Test install. I do look forward to the install on this system. Which really at this point is just installing from a package list the programs I need to get it fully operational and then a little setup. I just now have all the confidence I need to know I can get it to be as I pretty much want it to be.
I also used this experiment to test out Trouble shooting with A.I and I think it still has a way to go while it was helpful with trouble shooting and my scripts once I fixed it’s errors. So I still had to make sure I was able to go find and fix their errors. I can say though it’s much better than it was just a couple years ago when I tried to do a simple script and it was a disaster to say the least. I thought then well A.I has years to go before its ready for something like that. While still no where near perfect it has improved. What that means in the over all beats me.
Sorry for the long winded thread of the experience however I wanted to share to hopefully encourage those who may be sitting on the fence on something they want to do. Doing new things can be fun and exciting as well as painful. However if you are willing to just push past the pain you will relish in your success. Good Luck to you in your Endeavour’s
I suppose technically LXQT can use labwc without any WM configuration however I like a right click menu on the desktop Openbox ruined me with that lol. I also wanted to put in my key binds that i have been using for the past 5 plus years. Since I had learned to read the xml format when I first started using openbox I got used to it.
Its not the same is it? I mean you just had to install KDE and there Wayland is. I had to look up and learn the programs and how to configure and use said programs then install them and manually do it.
Here it is on my daily. Only issue with transfer was of course my conky however I was finally able to solve that issue. And Now here it is in its glory
As it turns out, Brave is not working for me on my Wayland side. I can run it under X11 but for somereason it wont find the “Wayland” session I’ve installed Xwayland however that had no affect either. The only way Brave works right now is if I go into an X11 session and use it. Every other app I have seems to work just as it did it the test environment. Since I don’t use brave very much and only for a few accounts I suppose I can just do that in X11.
here is the error I get
brave
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb
Everything else seems to work pretty good. I had a few keybinds that for some reason didn’t work at first but a reboot and it fixed it.
brave
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
[0929/082529.640916:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aborted (core dumped) brave
env -u QT_QPA_PLATFORM brave
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
[0929/084436.379924:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Aborted (core dumped) env -u QT_QPA_PLATFORM brave
Ok installed qt6-wayland rebooted and still not glory. No need to post the same error message again. Thanks but like I said I don’t use it enough anymore so the rare occasion I do need it I can just go to the X side. I think I’m going to go sit out and enjoy the remainder of my morning now.
(This is a joke no one was actually harmed during this experiment 
) and lots of cursing. It was also fun taking the experiment from a VM to a physical Test install. I do look forward to the install on this system. Which really at this point is just installing from a package list the programs I need to get it fully operational and then a little setup. I just now have all the confidence I need to know I can get it to be as I pretty much want it to be.
But it runs without configuration in Atrium.
however I was finally able to solve that issue. And Now here it is in its glory 
