gene heskett composed on 2023-06-20 03:13 (UTC-0400): >> Why is it Gene thinks any trouble he has has anything to do with Wayland? >> XFCE >> doesn't run in Wayland. The only Wayland XFCE users must have is the >> foundation >> Wayland requires from Xorg, which no one can be rid of (nor need to), except >> by >> running an ancient distro from before Wayland support was stuffed into Xorg, >> or by >> running MacOS, BSD, OS/2, Unix or Windows.
# grep RETT /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" # dpkg-query -W | grep wayland libwayland-client0:amd64 1.18.0-2~exp1.1 libwayland-cursor0:amd64 1.18.0-2~exp1.1 libwayland-egl1:amd64 1.18.0-2~exp1.1 libwayland-server0:amd64 1.18.0-2~exp1.1 # aptitude search wayland | grep -v libwayland | wc -l 54 # Very little "Wayland" is forced into a Bullseye installation, just 4 libs. > That needs a better explanation, Felix. As I see it, wayland can't run > as root, so no app that needs root works with wayland. Since package > managers with a gui need wayland, all the package managers that do have > a gui, are now dead except gnome packages, a poor but usable substitute > whose search function seems broken to me. The only way I've found to run > aptitude is as text with the safe-upgrade option turned on, and this is > well tested here on arm64's, but I still don't trust it on x86, its gone > wild with no way to stop it on x86, tearing down the system to the point > of having to re-install. I've run it on wintel stuff maybe 12 times, but > touching the g key has equaled a reinstall every time. It does NOT > preview what its going to do, it just does it. 4 times now. That's why I > asked if it had been tamed. You're apparently completely oblivious to my point, which is that XFCE (at least in Bullseye) /cannot/ be running on Wayland[1]. Wayland isn't even mentioned in the Bookworm release notes[2]. For Bullseye, the only mention has to do with fcitx5[3]. gene heskett composed on 2023-06-20 03:36 (UTC-0400): > from an xfce4 terminal shell, it bitches about wayland and exits, from > the pulldown menu's it asks for a passwd with a much bigger passwd > requester and when I enter my sudo pw it silently goes away. It does not > run here, ... > And when I ask why, everyone takes me to task for trying to run the only > package manager that works and has decent search function. What desktop > are you running? I'm xfce4 here. Please, if you are able without destroying the PC, provide the exact bitch message, and the exact procedure to reproduce it. Independently of whether you are able to do that without corrupting something, please provide here GUI terminal input/output from 'inxi -GSaz', but only after renaming /etc/inxi.conf and then executing 'sudo inxi -U' (which inxi.conf in Debian blocks) to update the antique broken inxi provided by Bullseye. Installing Bookworm's inxi (instead) might not help, as it was already three releases old when Bookworm was released. We need to see evidence Wayland has anything to do with Aptitude and/or Synaptic not working on your XFCE4 machine (Coyote?). Current/recent, but not Bullseye's, inxi -G* sanely reports the X window system(s) and the DE in use. [1] <https://www.linux.org/threads/xfce-wayland.43792/> [2] <https://www.debian.org/releases/stable/amd64/release-notes.en.txt> [3] <https://web.archive.org/web/20211018213418/https://www.debian.org/releases/stable/amd64/release-notes.en.txt> -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
