Help Understanding the Project's Direction and Target Audience

[arraybolt3]

@questionnaire

From what I’ve researched, it seems fair to say that most distributions use Mutter or KWin. Kicksecure, however, takes a different approach by using labwc because of its lightweight design, which offers security advantages, and that makes sense. That said, I suspect labwc might be causing additional bugs when paired with LXQt, leaving distributions like Kicksecure to inherit and work around those issues/bugs.

labwc was chosen because it was the only Wayland compositor reasonably suitable for use with LXQt in a VM. See:

Wayland only or Noland

For the Trixie port, removing Xwayland does not look possible without switching to a resource-heavy desktop environment or using hacks: There seem to be very few desktops that are fully ready for Wayland in Debian Trixie. GNOME is ready, KDE is ready, LXQt is ready enough (still some rough edges but they can mostly be papered over). XFCE is missing critical functionality and is too buggy. Cinnamon and Budgie are likely too immature and are potentially resource-heavy anyway. So in practical ter…

@questionnaire

labwc-tweaks when? and is there any other GUI tools that integrate with controlling labwc in the works (configuring keyboard shortcuts)?

Probably not until the release of Debian Forky at the earliest, possibly never if Debian doesn’t package it. Upstream doesn’t sign their releases or Git commits, and we try to not package architecture-specific code for the sake of supporting multiple processors without complicated build infrastructure. It’s possible we will introduce graphical tools of our own for configuring labwc in the future, but this isn’t planned at the moment.