LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-30-2009, 08:52 PM   #1
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-C ML
Posts: 883

Rep: Reputation: 78
Slack-Current / Dolphin-root


Slackware-Current KDE4.2
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
“/etc/rc.d/rc.messagebus reload”.
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”.

Edit:
I also have the exact same problem with Slamd64-Current KDE4.2

Last edited by slackass; 04-30-2009 at 11:49 PM. Reason: ooops!
 
Old 04-30-2009, 09:43 PM   #2
manwichmakesameal
Member
 
Registered: Aug 2006
Distribution: Slackware
Posts: 800

Rep: Reputation: 100Reputation: 100
That's weird, I just tried it on my current as of today, and it worked. It took a while to come up, but it did. Are you starting X as a normal user then trying to kdesu dolphin?

Edit: Konqueror worked as well.

Last edited by manwichmakesameal; 04-30-2009 at 09:45 PM.
 
Old 04-30-2009, 10:43 PM   #3
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-C ML
Posts: 883

Original Poster
Rep: Reputation: 78
Yep, starting x as normal user.
Never had this problem till KDE4 came along.

I think I'll do a hose & reload because I've messed with this quit a bit and no telling what I've screwed up.

Last edited by slackass; 04-30-2009 at 10:51 PM.
 
Old 05-01-2009, 10:04 AM   #4
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,408

Rep: Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834
@slackass Just wanted to say that I also see this problem as well.
I just put it down to KDE 4.2 not yet being fully ready, but if manwichmakesameal has this working then perhaps a fix can be found.
 
Old 05-01-2009, 11:19 AM   #5
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
I had this same problem when I loaded KDE4 from -current to -12.2 (back when you could do that). Posted a question here & found that it has to be called as
Quote:
kdesu dbus-launch dolphin
I made a Menu entry for it & all is well. I'm still using that earlier version of KDE4, but am wondering if I shouldn't load -current to get the newer one.
Regards,
Bill
 
Old 05-01-2009, 11:36 AM   #6
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,408

Rep: Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834Reputation: 834
@TSquaredF Thanks for the tip. It works, but I find that changing directories is slow.
At this time, 'kdesu thunar' is a better option for me.
 
Old 05-01-2009, 12:14 PM   #7
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-C ML
Posts: 883

Original Poster
Rep: Reputation: 78
TSquaredF:

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 12:14 PM. Reason: oooops!
 
Old 05-01-2009, 02:56 PM   #8
manwichmakesameal
Member
 
Registered: Aug 2006
Distribution: Slackware
Posts: 800

Rep: Reputation: 100Reputation: 100
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?
 
Old 05-01-2009, 04:20 PM   #9
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
Quote:
Originally Posted by manwichmakesameal View Post
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.
 
Old 05-01-2009, 07:44 PM   #10
slackass
Member
 
Registered: Apr 2006
Location: SE Texas
Distribution: Slack64-C ML
Posts: 883

Original Poster
Rep: Reputation: 78
Quote:
Originally Posted by manwichmakesameal View Post
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?
Mine is a Slack-Current install.
 
Old 05-03-2009, 05:41 AM   #11
Nille_kungen
Member
 
Registered: Jul 2005
Posts: 213

Rep: Reputation: 43
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.
 
Old 05-03-2009, 03:05 PM   #12
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
Quote:
Originally Posted by Nille_kungen View Post
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.
Regards,
Bill
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: How-To: Create an Open as Root Service Menu in Dolphin and Konqueror (KDE4) LXer Syndicated Linux News 0 03-31-2009 08:20 PM
updating Slack 10.2 with slack-current isos nacha Slackware 2 06-02-2006 08:52 PM
slack current pitt30 Slackware - Installation 7 12-05-2004 08:17 PM
using slack 9 CD to install slack current mr_mandrill Slackware - Installation 1 06-20-2004 01:23 AM
current Slack-Current giving troubles? r_jensen11 Slackware 5 02-02-2004 05:08 PM


All times are GMT -5. The time now is 05:53 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration