Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
KDE5 was loaded automatically via normal system update. Fedora24. The next attempt to log in resulted in a blank screen with a cursor. Period. I cannot get past that state.
I can get to command line login using ctrl-alt-f3 but don't know where to look to try and determine what's wrong.
I was unable to get anything from the 'echo' suggestion. However I was successful downloading and installing gnome, and have been able boot and open a gnome session. Now perhaps I can look further for the KDE problem.
I had that kind of an issue some time ago with debian testing. One way I was able to get kde to launch is
ctl-alt-f2 > login as root ( then I like to launch mc {midnight comander})
cd to /var/tmp
rm kde* > and delete the kde temp files. They will be rebuilt on relaunch.
Then reboot the machine.
I have successfully resolved this issue although I still do not have ANY idea what created it in the first place.
1. I got into a command session as root.
2. I was able to download a Gnome DE as suggested by Ztcoracat. I was surprised I had a network connection since in my set-up, that is done when I log in to the KDE desktop as a user. But nevertheless, it was active.
3. I was then able to log in to the Gnome desk top/
4. Also able to switch to the "Plasma" desktop on the login screen as well. That got me back to the KDE environment where I was familiar.
I have successfully resolved this issue although I still do not have ANY idea what created it in the first place.
1. I got into a command session as root.
2. I was able to download a Gnome DE as suggested by Ztcoracat. I was surprised I had a network connection since in my set-up, that is done when I log in to the KDE desktop as a user. But nevertheless, it was active.
3. I was then able to log in to the Gnome desk top/
4. Also able to switch to the "Plasma" desktop on the login screen as well. That got me back to the KDE environment where I was familiar.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.