On 02/11/18 04:56, Dave Close wrote:
Ed Greshko wrote:
> Grasping at straws here....
> Are you running vnc server as a systemd service that gets started
> at boot time? I've never had a problem with that....but if you're
> doing that how about disabling it for a test.
No, I started it from the command line. Recall that I had the same
problem before I started using VNC. In fact, VNC is just a workaround
so I can get practical work done using this machine.
I have mixed feelings about your frustration. I'm certainly frustrated
myself. But it feels slightly good that someone else is also baffled
by the situation. I only wish there were someone who wasn't baffled
and could tell me what is wrong. Thanks for all the help.
Well, you have plasmashell running so it is a mystery as to what may be going on.
Just after login on a system I see...
[egreshko@acer ~]$ ps -eaf | grep plasma
egreshko 1561 1485 9 06:44 ? 00:00:07 /usr/bin/plasmashell
egreshko 1816 1468 0 06:44 ? 00:00:00 desktop.so [kdeinit5] desktop
egreshko 1873 1468 0 06:44 ? 00:00:00 file.so [kdeinit5] file
egreshko 1874 1468 0 06:44 ? 00:00:00 trash.so [kdeinit5] trash
egreshko 1876 1468 0 06:44 ? 00:00:00 file.so [kdeinit5] file
egreshko 1877 1468 0 06:44 ? 00:00:00 trash.so [kdeinit5] trash
I don't know of a way to restart plasmashell remotely....
So, I suppose I try strace attached to the plasmashell PID and see if anything pops out.
And I'd probably post the current status and findings to the KDE list to see if
someone there has an idea. And, of course, you may want to consider a bugzilla.
Oh, one thing has just come to mind....
This is a system which has been upgraded from F26 to F27, right? So, it still has an
F26 kernel on it. So, does KDE work if you boot the F26 kernel?
A motto of mine is: When in doubt, try it out