Re: is Wayland/Weston mature enough to be the default desktop choice in Buster?
- Date: Sat, 6 Apr 2019 21:48:57 +0200
- From: Bastian Blank <waldi@xxxxxxxxxx>
- Subject: Re: is Wayland/Weston mature enough to be the default desktop choice in Buster?
On Sat, Apr 06, 2019 at 08:47:51PM +0200, Guillem Jover wrote:
> I don't use GNOME at all, but I tried to switch to Wayland last month
> (from i3 to sway), and sadly the experience lasted only a couple of days.
You changed display manager implementations and are trying to compare
that? How can you differentiate between problems causes by the i3 to
sway switch from problems caused by xorg to wayland?
> I noticed that not all big desktop programs support Wayland natively
> (such as Chromium), or do so out of the box (such as Qt or KDE), this
> implies you need to have XWayland running most of the time, which
> consumes around 100 MiB of resident memory.
My gnome-shell consumes a multiple of that usualy. But much more
important: why is the qt wayland support not installed?
> Wayland also uses libinput
> which I've found to be subpar compared to the synpatics input drivers.
xorg only installs the libinput and the separate wacom input by default:
| Package: xserver-xorg-input-all
| Depends: xserver-xorg-input-libinput
| Recommends: xserver-xorg-input-wacom
> There seems to be also some issue with Qt/KDE programs and text DPI.
I don't see such problems, and I use it in HiDPI mode, which becomes
increasingly more common. wireshark is now a Qt application and looks
fine, apart from the fact that it's Qt and the design choices of this
I could add a number of problems I found myself, but none of them are
relevant for Joe Random user.
It is a human characteristic to love little animals, especially if
they're attractive in some way.
-- McCoy, "The Trouble with Tribbles", stardate 4525.6