Skip to main content ↑ ↓
Topic: experimenting with lxqt 2.1 (Read 373 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

experimenting with lxqt 2.1

I used latest lxqt-runit iso and made a vm. After that lxqt opened in X11 mode. I updated packages in the vm and latest lxqt was installed ie version 2.1.

After reboot the 2.1 version was working fine and I was able to configure it mostly. Thei is X11 version. I was able to get the panel almost like I prefer. Seems lxqt-panel always leaves a small window height in place even when autohiding. I was able to remove the grey line by using my standard background colur and setting opacity==1. I was not able (as yet) to change the tasks background to match so my buttons still have a grep bg.

To get a wayland session I had to install labwc from AUR and the arch linux package lxqt-wayland-session. Neither of these require systemd, but build from aur rquires that base-devel is present.

After this I rebooted and see that the sddm login now has extra sessions labwc and LXQt (wayland).

The labwc session is completely minimal it just has a primitive right button menu with options Reconfigure and Exit. I imagine it can be used to setup an openbox style configuration.

The LXQt (Wayland) session works pretty well and seemed to be identical in layout and operation of the panel/taskbar and styling.

It seems that the lxqt-panel can show the gvim icon etc in wayland, I suppose that's because of gtk3, but I am not an expert.

This is the best experience I've had so far with wayland. However, I imagine it will be hard to duplicate my openbox setup as it's using older gtk styles.

I forgot to say that intially the wayland session would not start, I think that's because the autostart was trying to iuse connman which I don't think is installed in lxqt-runit by default. At login there was a session configuration window shown.

Re: experimenting with lxqt 2.1

Reply #1 –
Thanks for the helpful review.

Re: experimenting with lxqt 2.1

Reply #2 –
Fresh install, working fine with no big issues, made me happy to see that.

A note: just run "startlxqtwayland" with something like greetd since it's not only possible now, but also some DM's like sddm with it's default config seem to be buggy with xorg/xwayland, at least i had a weirdness with it.

Kwin_wayland is eating memory for lunch, got to 600 something mb. Labwc sits at around 300 on the main pc with amdgpu, which is still more than a composited xorg session, no idea why it's behaving bloaty with it. On an intel igpu it's just around 100.

Is libsfdo missing from the repos here? i installed it by hand for labwc.

For the sake of reference, the previous thread. Part of the environment and kanshi/config remain good: https://forum.artixlinux.org/index.php/topic,6185.msg38166.html

Re: experimenting with lxqt 2.1

Reply #3 –
To accommodate for the LXQT/Labwc combination the following packages were added to the Galaxy repository a few days ago:
- lxqt-wayland-session
- labwc
- libsfdo

As per the LXQt Wayland Session section on https://github.com/lxqt/lxqt/releases/tag/2.1.0 multiple Wayland compositors are supported:
This is a new component that allows choosing a Wayland LXQt session in LXQt Session Settings. It supports Labwc, KWin, Wayfire, Hyprland, Sway, River and Niri. It adds "LXQt (Wayland)" to the items of your desktop display manager (e.g., SDDM). If you want to use it, make sure to choose a Wayland compositor from the drop-down menu of LXQt Session Settings → Wayland Settings → Wayland compositor. Optionally, a supported Wayland screenlocker command may also be selected if available.

artist

Re: experimenting with lxqt 2.1

Reply #4 –
libsfdo still doesn't seem to be in the repos.
Congrats for the rest of the packages anyway, it's a bliss not longer having to build them.

Re: experimenting with lxqt 2.1

Reply #5 –
libsfdo was already in the galaxy repo dir, but not in the database somehow; fixed

artist