On Wed, 2021-06-30 at 22:27 +0100, Patrick O'Callaghan wrote:
On Wed, 2021-06-30 at 12:24 -0700, Jonathan Ryshpan wrote:
> > Most if not all these issues are related to Wayland (other than
> > Discover, which is something else). Try KDE under Xorg.
>
> Not so easy to do. The login screen allows a choice between Wayland
> and Xorg; but the change is not sticky. The only instructions I can
> find on the web are for Gnome and require editing a file
> /etc/gdm/custom.conf that does not exist on my system; in fact there
> is no directory /etc/gdm/ .
Not in my experience. I've used both sddm and gdm, and in both cases
the choice is remembered across sessions, i.e. sticky. I didn't have to
edit anything.
Gdm is not available on my system (by default) since I run KDE. Sddm
works, except that I had to change SDDM > Behavior from "Plasma (X11)"
where I found it to "Plasma (Wayland)" and back in order to get
sessions to start using X11 rather than Wayland.
Now that I am running X11, sddm behaves strangely: It runs properly
when invoked in System Settings but when I run it from the command line
($ sddm), I see this:
$ sddm
[06:49:24.239] (EE) DAEMON: Failed to open VT master: Permission denied
[06:49:24.243] (EE) DAEMON: Failed to read display number from pipe
[06:49:24.243] (WW) DAEMON: Attempt 1 starting the Display server on vt -1 failed
[06:49:26.348] (EE) DAEMON: Failed to read display number from pipe
[06:49:26.348] (WW) DAEMON: Attempt 2 starting the Display server on vt -1 failed
[06:49:28.352] (EE) DAEMON: Failed to read display number from pipe
[06:49:28.352] (WW) DAEMON: Attempt 3 starting the Display server on vt -1 failed
[06:49:28.352] (EE) DAEMON: Could not start Display server on vt -1
Running sddm using "$ sudo sddm" starts a completely new session. I
don't remember this happening under Wayland.
--
Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net>
If one foot is on fire and the other is frozen
to the floor on the average you are doing OK.