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.
OK, so I tried KDE4.x on my -current box when it was still tucked in /testing. It didn't work for me then, I thought maybe I had b0rked something up upgrading from 3.5, and decided I'd wait until it made its way into the main tree.
I recently did a Bad Thing and wound up having to reinstall Slack from scratch. So of course I now had KDE4 again ... and when I try to start it I see essentially the same behavior I saw before: I get the lovely splash screen, then when the thing is finished loading in, the screen changes to a quite hideous and striated display where everything is squished over to the left side of the screen. I can move the mouse pointer around for about 5-10 seconds and then the whole thing freezes solid.
Based on another post I saw here (I can't seem to dig it up again), I took a look at /var/log/messages and lo! there is a slew of this in there:
I also briefly scanned dmesg output and I saw a couple of anomalous lines, but I am not knowledgeable enough to know whether there is any connection. If anyone knows what I should look for there (or whether I should look there at all), I'd be happy for any guidance.
Perhaps this laptop (Dell Inspiron 4100, PIII 100MHz) is just too old to run KDE4? 3.5 ran fine on it.
I am having the same issue on a newer machine that is very capable, so I don't know if it is related to that. There is another thread about it that people have given some tips, but I haven't gotten it to work yet.
I found the post I was thinking about above, and applied RWorkman's fix to /etc/dbus-1/system.d/hal.conf, but I am still getting some KDE4-related dbus messages like the one above. And trying to start KDE4 has the same result as before.
This is not exactly a deal-breaker since I can still run KDE4 apps from, say, XFCE (which is nicer to my old machine), but I'd still be interested to know why KDE4 isn't working for me.
OK. Grissiom, I added myself to the same groups as you. I no longer get as many dbus messages when attempting to start KDE4. In fact I only get two, but they are followed by a segfault, which (I am guessing) is why my machine totally freezes:
Hmm , so we have two problem here.... At first I have to admit that I am not a guru and my way of solving problems is "try-and-fault"....
So go ahead. What video card and driver are you using? Can you run glxgears in other DE successfully? I'm using ATI X1150 with open source driver and the support is poor... If I do a lot of OpenGL the X could freeze too.... If this is your case, open ~/.kde/share/config/kwinrc when KDE is _not_ running, find the following section in it:
There are a couple of these threads about ... think you might be quoting from one of them (?)
I should have been more explicit in the first post of this one: when I reinstalled, I did so from scratch and installed -current straight in. There was no upgrading from 3.5.10 -> 4.x.x, so (unless I'm missing something else, which is always eminently possible) I should have had no old .kde stuff laying around at all.
I'm keenly interested why I am getting the dbus errors I posted above, & why my kwinrc file doesn't have any of the stuff Grissiom referenced in it ...