On 2019-12-21 04:02, David Dembrow wrote: > I use fedora with the kds plasma desktop and have been for a very long time. > Powering up today and logging in appeared to hangup while bringing up the > desktop and I noticed the plasmashell process was consuming 100% of the cpu. > I tried restarting a few times and then gave up an left the machine running > while I did an errand. When I returned, it looked like the plasma desktop > loaded because I noticed the screen lock had kicked in and when I unlocked > the screen there was a background. Then I noticed the dual screen was a > duplicate (not extended with separate backgrounds) and the kpanel was > missing. So I do not have the network manager connecting to the router as > well as no application launcher. > > Is this my own problem or has something happened to the plasma desktop > launcher? Is there a way I can reset the plasma desktop or start it manually > (i.e. from a run level 3)? > > Thanks for any suggestions,
Well, chances are it is a "local" issue. I'm running a fully updated F31/KDE system with dual monitors just fine. As a matter of fact, I just rebooted it due to having done some updates which needed a reboot. I've seen issues, at times, when my display connections (1 HDMI, 1 DP) were dislodged somewhat by a cat. Yes, you can usually do startkde from the command line if you start in run level 3. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
