Preview release 2.1 post #153
Conversation
|
I'll make the release announcement based on it. But making an announcement can be done only after releasing all sources — as before. |
|
It may not be complete... |
|
|
||
|  | ||
|
|
||
| As Wayland is quite different to X11 some features are not available and some settings are handled by the compositor and not anymore by LXQt, so you may see some messages like that: |
There was a problem hiding this comment.
As Wayland is quite different from X11,..., so you may see some messages like this:
|
|
||
|  | ||
|
|
||
| Similar to the window manager under X11 users can choose a Wayland compositor - any wlroots-compatible compositor should work, in addition to kwin-wayland. Hyprland, Labwc, kwin, Niri, Sway, River and Wayfire will be supported out of the box providing a basic configuration file for each of them. Using different screen lockers under Wayland including `swaylock`, `waylock` and `hyprlock` is supported too. |
There was a problem hiding this comment.
Users can choose a Wayland compositor, as they chose a window manager under X11 - ...
|
|
||
| Similar to the window manager under X11 users can choose a Wayland compositor - any wlroots-compatible compositor should work, in addition to kwin-wayland. Hyprland, Labwc, kwin, Niri, Sway, River and Wayfire will be supported out of the box providing a basic configuration file for each of them. Using different screen lockers under Wayland including `swaylock`, `waylock` and `hyprlock` is supported too. | ||
|
|
||
| At the moment there are 3 dedicated panel backends, xcb (X11), general wlroots and kwin_wayland - using the latter many features of the panel as moving windows to workspaces, workspace switcher, urgency hints, show desktop will be enabled under Wayland. Other backends can be created and added in future, enabling similar features for other compositors like sending to scratchpad instead of minimizing windows, workspace pagers and else. PRs are welcome. |
There was a problem hiding this comment.
Currently there are 3 dedicated panel backends, xcb (X11), general wlroots and kwin_wayland - with kwin_wayland supporting several features like moving windows to workspaces, workspace switcher, urgency hints, and showing desktop.
|
|
||
| At the moment there are 3 dedicated panel backends, xcb (X11), general wlroots and kwin_wayland - using the latter many features of the panel as moving windows to workspaces, workspace switcher, urgency hints, show desktop will be enabled under Wayland. Other backends can be created and added in future, enabling similar features for other compositors like sending to scratchpad instead of minimizing windows, workspace pagers and else. PRs are welcome. | ||
|
|
||
| As some applications will not work under Wayland (e.g. redshift, some clipboard manager exc) their auto starting can be limited to X11 only, while on the other side every compositor can start Wayland-only applications like `kanshi` or `xdg-desktop-portal-wlr`. |
There was a problem hiding this comment.
... while, on the other hand, every compositor can start...
|
|
||
| As some applications will not work under Wayland (e.g. redshift, some clipboard manager exc) their auto starting can be limited to X11 only, while on the other side every compositor can start Wayland-only applications like `kanshi` or `xdg-desktop-portal-wlr`. | ||
|
|
||
| Other fixes for Wayland have been applied overall, including the desktop window of `PCManFM-Qt` which has also been improved for multi monitor setups. |
There was a problem hiding this comment.
There are also general fixes and workarounds for Wayland; for example, the desktop window of PCManFM-Qt has been improved for use with multi monitor setups.
|
|
||
| For further details please consult the [Wayland Wiki](https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings). | ||
|
|
||
| The upcoming LXQt 2.1 release can already be tested installing from source, preferably using the AUR packages - as more testing feedback we get the better! |
There was a problem hiding this comment.
The upcoming LXQt 2.1 release can already be tested by installing from sources or, preferably, by making distro-specific packages and installing them (like AUR packages in Arch). The more testing feedback we get, the sooner we could find and fix probable problems!
I made some suggestions above. |
stefonarch
force-pushed
the
preview_2.1
branch
from
019643b
to
6395a57
Compare
No description provided.