Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
dnf groupinstall "KDE (K Desktop Environment)"
which happily did nothing but said it was complete. From rpm -qa I see lots of kde entries. Same thing happened on my laptop. Both systems running recently updated 31. Has kde completely abandoned x11?
On 2020-01-04 12:49, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
dnf groupinstall "KDE (K Desktop Environment)"
which happily did nothing but said it was complete. From rpm -qa I see lots of kde entries. Same thing happened on my laptop. Both systems running recently updated 31. Has kde completely abandoned x11?
How are you trying to start it?
I'm running KDE perfectly fine on F31 and even Rawhide. Both under X11 since I'm not yet interested in trying Wayland.
On 1/3/20 8:49 PM, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
What was the command you tried and what was the message?
On 1/3/20 11:59 PM, Ed Greshko wrote:
On 2020-01-04 12:49, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
dnf groupinstall "KDE (K Desktop Environment)"
which happily did nothing but said it was complete. From rpm -qa I see lots of kde entries. Same thing happened on my laptop. Both systems running recently updated 31. Has kde completely abandoned x11?
How are you trying to start it?
I'm running KDE perfectly fine on F31 and even Rawhide. Both under X11 since I'm not yet interested in trying Wayland.
Typically just do
startx
from a console boot login. Tried getting a xserver with
xinit -- :0
and using startkde in the resulting xterm. Startkde is not Found, there is
startplasma-x11
which gives me the kde startup display and then drops out of xserver and back to the console
On 2020-01-04 13:37, Robert McBroom via users wrote:
On 1/3/20 11:59 PM, Ed Greshko wrote:
On 2020-01-04 12:49, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
dnf groupinstall "KDE (K Desktop Environment)"
which happily did nothing but said it was complete. From rpm -qa I see lots of kde entries. Same thing happened on my laptop. Both systems running recently updated 31. Has kde completely abandoned x11?
How are you trying to start it?
I'm running KDE perfectly fine on F31 and even Rawhide. Both under X11 since I'm not yet interested in trying Wayland.
Typically just do
startx
from a console boot login. Tried getting a xserver with
xinit -- :0
and using startkde in the resulting xterm. Startkde is not Found, there is
startplasma-x11
which gives me the kde startup display and then drops out of xserver and back to the console
I normally start my desktop environment from the GUI supplied by gdm or sddm.
The only way I know to start KDE Plasma from the command line is to have a ~/.xinitrc file containing
exec startplasma-x11
And then startx will start the KDE Plasma environment
On 1/3/20 10:49 PM, Robert McBroom via users wrote:
which happily did nothing but said it was complete. From rpm -qa I see lots of kde entries. Same thing happened on my laptop. Both systems running recently updated 31. Has kde completely abandoned x11?
The update from Plasma 5.16 to 5.17 moved the session startup script from /usr/bin/startkde (IIRC) to /usr/bin/startplasma-x11.
On 1/4/20 12:30 AM, Samuel Sieb wrote:
On 1/3/20 8:49 PM, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
What was the command you tried and what was the message?
switchdesk kde
replys
ERROR: KDE is not installed on your machine
Then suggests the group install of the KDE environment which as noted above completed with no messages of any action. Followed that with the attempts described to launch directly from a xserver.
On 2020-01-05 01:30, Robert McBroom via users wrote:
On 1/4/20 12:30 AM, Samuel Sieb wrote:
On 1/3/20 8:49 PM, Robert McBroom via users wrote:
Hadn't used kde for a few weeks. Trying to start it gave me the message that it was not installed. Curious since I've had it on my system for years. following the message suggestion ran
What was the command you tried and what was the message?
switchdesk kde
replys
ERROR: KDE is not installed on your machine
Then suggests the group install of the KDE environment which as noted above completed with no messages of any action. Followed that with the attempts described to launch directly from a xserver.
FWIW, KDE is no longer called KDE.
It is called Plasma. Enter "switchdesk" without parameters to see the choices.
Also https://wiki.archlinux.org/index.php/KDE
is a good reference in spite of the name.
https://wiki.archlinux.org/index.php/KDE
On 2020-01-05 02:00, Ed Greshko wrote:
It is called Plasma. Enter "switchdesk" without parameters to see the choices.
I should have checked this yesterday.
"switchdesk" is broken in this release. Selecting Plasma or KDE will not work as expected.
While the message displayed is
echo "Please specify one of either Plasma, GNOME, XFCE, FVWM, IceWM or WindowMaker."
There is no checking in the script for Plasma. And you'll get the error message
[egreshko@f31gq ~]$ /usr/bin/switchdesk-helper Plasma Unknown desktop requested: Plasma
With KDE, at least on a fresh F31 install, there is no "KDE (K Desktop Environment)". It is now call "KDE Plasma Workspaces".
Also, with the current plasma-workspace-5.17.4-1.fc31 there is no longer a /usr/bin/startkde.
-
Ed Greshko -
Ian Pilcher -
Robert McBroom -
Samuel Sieb