Samuel Sieb wrote:
>>>> Well, I'm certainly seeking hints. The VNC session got me to a
>>>> blank screen image. I opened an xterm on it and ran startx.
>>>
>>> You what? You ran startx from within an X session?
>>
>> Well, it's been a few days. I agree that doesn't make sense. I'll
>> try it again and post a clarification.
Sorry about the confusion. There was indeed an xterm involved
but it was where I started the VNC session; it was running on the
remote deskop. VNC started directly in KDE as expected.
>Also try running "systemctl isolate graphical".
I generally run two VTs, VT1 is a text root console, VT2 is where
I run startx under my own account. In this case, startx was hung on
VT2 as I have previously described. I ran the isolate command from a
remote login. The main screen immediately switched to a sddm login --
running on VT1. Each time I entered my password, it cleared for a
moment, back to the root text console, then reappeared asking for
password again. Even killing Xorg and sddm via the remote login
did not terminate it. Meanwhile, the hung KDE on VT2 was unchanged.
The sddm login initially showed Gnome as the default desktop,
though it never got there. Changing the selection to Plasma changed
the behavior slightly. Then after entering my password, nothing
happened. Though the cursor continued to work, no selection had any
effect. I rebooted to clear it.
During this experiment, /etc/sysconfig/desktop contained,
DESKTOP="KDE"
DISPLAYMANAGER="KDE"
--
Dave Close, Compata, Irvine CA +1 714 434 7359
dave@xxxxxxxxxxx dhclose@xxxxxxxxxxxxxxxxxx
"Words are too fragile to carry ideas." -- Dick Boyd
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
