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.
When I try to log in to Dolphin as root using “kdesu dolphin”
It won't access anything but gives this at the bottom of the screen:
Could not start process.
Can not talk to klauncher.
The name org.kde klauncher was not provided by any .service files.
However when I log in to KDE as root and open Dolphin everything works perfect.
This made me think it was a permission thing so I after fooling around with it off an on for a couple of weeks I just added myself to all of the groups and ran
Still the same thing.
This has been happening on 2 different boxes. (AMD & Intel)
Is this just something that will be eventually fixed as Current becomes Slackware 13?
Or is there something I can do to fix it?
Thunar dose behave normally when using “kdesu thunar”.
I also have the exact same problem with Slamd64-Current KDE4.2
Last edited by slackass; 05-01-2009 at 12:49 AM.
A THOUSAND THANKS!
That fixed it on my Slamd64-Current.
And when I reinstall Slack-Current it will fix that too as they both run the same version of KDE4.
I'm doing a hose&reload on my Slack-Current because I've butchered up quite a bit of stuff and whant to start from scratch with it.
Last edited by slackass; 05-01-2009 at 01:14 PM.
Did you guys do an upgrade from 12.2 to -current? I just did a fresh install of current then used slackpkg to keep updated. Maybe that's whats causing problems?
I'm actually using 12.2. A while back, when KDE4.2.0 was put into -current, it was possible to use those packages in 12.2. Now, I can't update it (at least I don't think I can; I'm not even sure now how I can remove 4 to put 3.5 back in, there was a removal script, but I haven't seen it recently), so will probably create a new -current partition this weekend. I usually don't use -current, but like KDE4 more than 3, so will give it a go to see what happens.
TSquaredF you can use the buildscripts for kde4 from current to upgrade kde in 12.2
I did that and since the old one from current that was also for 12.2 was buggy.
Thanks. I'll give that a try. I wasn't sure whether I could upgrade or not. I installed -current yesterday, but have other issues with it, so really want to upgrade. Will let everyone know how it goes.