LXQt 2.1 Released With New Wayland Session Component

[phoronix]

Phoronix: LXQt 2.1 Released With New Wayland Session Component

LXQt 2.1 is now available as the latest feature release to this Qt-based lightweight desktop environment. Most significant with LXQt 2.1 is the introduction of the lxqt-wayland-session component...

https://www.phoronix.com/news/LXQt-2.1-Released

[Danny3]

Nice!
And good to have more Qt-based DEs so the Qt project gets more testing and bug reports!

[schmidtbag]

Nice!
And good to have more Qt-based DEs so the Qt project gets more testing and bug reports!

I've given LXQt a shot a few times, but ultimately gave up on it due to it breaking every time Qt updated. Could've just been bad maintainers for Arch though.

[pWe00Iri3e7Z9lHOX2Qx]

I still need to play with this again. Do the different window management / compositor options in lxqt-wayland-session introduce any weird issues with window decorations / theming etc.?

[Blisterexe]

Lxqt lets you choose what wayland compositor you want, like any xorg desktop, whic is *extremely* cool.

[Vistaus]

I've given LXQt a shot a few times, but ultimately gave up on it due to it breaking every time Qt updated. Could've just been bad maintainers for Arch though.

I've been using LXQt for a while now and it survived the Qt 6.7 to 6.8 upgrade on CachyOS (Arch).

[elbar]

When QT switch happened its memory usage grows, now it is under QT6 but problem is not QT but its KDE bindings and uncommon nature to common desktop today's users. XFCE has a lot of love but is also ugly and not behave the way it should, but XFCE is commonly used in virtual machines so there is corporate development with little memory footprint required. But lxqt is not so ugly but missing something crucial for desktop needs, and compositors even like i3 and similar don't solve this, it is something different...

And when switch to wayland happens, from GIMP long standing issues not backed by sponsor needs it is also a long story not only memory disaster...

But when resources are limited it could be the way and could be p(l)easant, but problem is that even KDE today has such drive for limitness comparable with LXQT and not backed by their libs only limiting composition of frugal IDE, but nice one but without (american) drive.

[Veto]

The Wayland support is considered optional and experimental with LXQt planning to continue supporting the X11 session indefinitely.

At this point it seems the LXDE based PIXEL desktop is probably a better bet going forward: https://www.phoronix.com/news/Raspbe...ayland-Default

[ahrs]

I've given LXQt a shot a few times, but ultimately gave up on it due to it breaking every time Qt updated. Could've just been bad maintainers for Arch though.

I've noticed something similar myself, on Gentoo. I run testing though, I'm sure it's better on the stable channel. LXQt really needs to start using the CI features of Github to catch these breakages early instead of waiting for distro reports and then fixing things up later.

[ahrs]

When QT switch happened its memory usage grows, now it is under QT6 but problem is not QT but its KDE bindings and uncommon nature to common desktop today's users.

LXQt only uses KDE Frameworks if they make sense for them. They try to use core Qt for everything and when they do use a KDE Framework they keep to the tiers for core frameworks only, that aren't going to pull in the entire Plasma desktop just to use them.

EDIT: By the way elbar that bug you linked it two years old and about the KF5 version of KWin. KDE frameworks and Kwin are all on version 6 now. Furthermore, LXQt doesn't have a default window manager or compositor, KWin is just a suggestion that some distributions use (it's the default on Gentoo, and probably other distros but some still configure it differently).