Liam Proven <[email protected]> writes: >On Tue, 2 Dec 2025 at 17:31, Jeffery Small <[email protected]> wrote:
>> the consensus seems to be that it is Wayland that >> is causing the problem. >I think they are wrong. >Xubuntu does not use Wayland... Because Xfce does not use Wayland. >There is _experimental_ support for labwc with Xfce but I only know of >the latest openSUSE using it so far. It is definitely not in Xubuntu >Noble. >-- >Liam Proven ~ Profile: https://about.me/liamproven ~ LinkedIn/X/FB: lproven >Email: [email protected] ~ Google: [email protected] >IoM: (+44) 7624 227612: UK: (+44) 7939-087884 >Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053 Liam: I understand that Xfce4 doesn't use Wayland, but the following packages have been pulled in by something over time: kwayland-data kwayland-integration libkf5waylandclient5 libnvidia-egl-wayland1 libqt5waylandclient5 libqt5waylandcompositor5 libqt6waylandclient6 libqt6waylandcompositor6 libqt6waylandeglclienthwintegration6 libqt6waylandeglcompositorhwintegration6 libva-wayland2 libwayland-client0 libwayland-cursor0 libwayland-egl1 libwayland-server0 qt6-wayland qtwayland5 wayland-protocols I'm not saying that Wayland proper is running, but I do wonder if some other program is using Wayland components in some way. And I'm not even saying that I have any clue that Wayland is involved at all; that's just what other have mentioned when I tried to research this problem. In any case, other people are also experiencing the same thing and if anyone does have any ideas, I'd be interested in hearing them. Regards, -- Jeffery Small -- xubuntu-users mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
