[SOLVED] Patch to KDE 4.10.0 causes kdm to respawn too quickly (X does not start)
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Patch to KDE 4.10.0 causes kdm to respawn too quickly (X does not start)
I upgraded kde-workspace as per Alien Bob's instructions, and now KDE won't start at all! When Slackware attempts to go to level 4, I get a message about kdm respawning too fast, and X will not start. Suggestions are welcome.
When I installed another package, I noticed that I got a lot of errors regarding ldconfig. I thought that maybe 'upgradepkg' was the wrong thing to do when replacing kde-workspace and nepomuk-core. So, I did 'removepkg' and 'installpkg' instead, and the kdm respawn problem went away. For some strange reason, the upgradepkg command did some funky things to my KDE installation. Since I found the solution to my problem, I am going to mark this thread as [SOLVED], and maybe this will serve as a warning for those doing an upgrade of the two patched packages and coming up against the kdm respawn problem.
i used --reinstall --install-all and everything works fine, both on -Current and -Stable (14.0)
i tested using Eric's and Pat's KDE packages
I guess it could've been something about my installation that caused the problem. Still, it's better to have posted about it than not. At least someone else might get some use out of it, if nothing else
I should have taken a closer look before I posted, it turns out, not all packages actually installed : ) So, once I went thru the install process completely, made sure all packages actually installed, all is good : )