dolphin shows an error message if started with kdesu

Version: (using KDE 4.0.5)
Installed from: Fedora RPMs
OS: Linux

Description of problem:
Dolphin, launched by command "kdesu dolphin" does not work.

Version-Release number of selected component (if applicable):
kdebase-4.0.5-3.fc9.i386

Steps to Reproduce:
1.Press "Alt+F2". Enter "kdesu dolphin", where /usr/bin/kdesu - symbolic link to
/usr/libexec/kde4/kdesu.
2.Enjoy.

Actual results:
Dolphin write strange message:"Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files". And does not
show contents of any folder.

Expected results:
It must work.

Additional info:
It strange, but if you enter "su", your root password and then from root run
"sudo dolphin" its work. And also then you can run dolphin by "Alt+F2" command
"kdesu dolphin" and now it is work! Very strange.

Created attachment 25685
Message, which write dolphin

Message, which write dolphin.

Same Problem with KDE 4.1 (OpenSuse 11.0)

Problem confirmed on Bluewhite64 12.1 (KDE 4.1.0) and Slackware 12.1 (KDE 4.1.0)

OK, after talking to sandsmark on #kde I found out the issue is related to Xorg security. If I run "xhost +localhost:root" before trying "kdesu dolphin" everything goes OK, both in Bluewhite64 and Slackware. Don't know about OpenSuse and Fedora.

Sure, but nonetheless, kdesu dolphin from prompt should launch Dolphin as root. That's the point of kdesu, I thought.

Well, now I remember that on the same distro I am having that problem with KDE 4.1.0, I had KDE 3.5.9 installed. Back then I could run "kdesu konqueror" and it would work without any problems.

So, if now a "kdesu dolphin" doesn't work as it should, I don't think it is really a Xorg security problem, it is indeed a KDE problem.

I can confirm this is for me too. OpenSuse 11.0

Box: Linux 2.6.25.18-0.2 x86_64 | OS 11.0 | (KDE4.1.2) "49.1" | M2N4-SLI | AMD 64 X2 5200+ | nVidia 8500GT | 2GB RAM

Lap: OS 11.0 | Celeron 550 | (KDE4.1.2)"49.1" | Intel 965 GM | Lenovo R61e | 1GB RAM

Work around for me is just to use kde3 for su mode. Maybe there is a fix on the way, as I see 4.1.3 is due in a few days

*** Bug 175214 has been marked as a duplicate of this bug. ***

Confirmed on KDE 4.2 trunk, revision 888223. Konqueror still completely unaffected. Also works using kdesu -u <anyone but root> dolphin. Only running Dolphin as root is broken, on OpenSuSE 11.0, self compiled using kdesvn-build

@David: I guess you know within 5 seconds what's the root cause of this ;-) Could you maybe provide a rough hint where I can take a look to solve this? Thanks!

Same problem on KDE 4.1.2 onFedora 9 (2.6.27.5-41) but none of the workarounds here seem to work. kdesu is not recognised and only seems to be a stub Neither Dolphin nor Konqueror can be made to work in SU mode.Guess I'll have to wait for 4.1.3 and hope it fixes things.

Interestingly, the Dolphin - Super User Mode, works fine. What is going on inside Dolphin?

Dolphin - Super User Mode was supplied by SuSE, in case any of you are still searching. However it no longer works, running latest Trunk.

I'm reassigning it to kdelibs, I have no clue about the root cause. Maybe someone with the necessary knowledge of kdesu has some hints.

I am running KDE 4.1.3 (on Bluewhite64 12.2) and the problem is still here.

I ran into this same bug using openSUSE 11.1 with KDE 4.1.3. Running dolphin as root (File Manager Super User Mode, provided by openSUSE apparently) causes the same problem.

I hope this gets fixed soon, I actually like Dolphin. Guess I'll have to use Konqueror for now, as that works fine with kdesu.

Same error message ("The name org.kde.klauncher was not provided by any .service files") after launching systemsettings using kdesu and try to change the login screen's background image.

Hi all,
I just wanted to share a GUI-based work-around that solved the problem for me and I haven't seen it before in the forums.

1) Create a new entry for Dolphin on KDE Menu editor (you can copy-paste the normal one and label the new one as "Dolphin (SU)" or something similar).
2) Clic on it and, on the "Advanced" tab, select "Run as a different user --> root"

When runing it, you'll most likely get the same problem that has been repported here. The trick is in the following steps.
1) Left-clic on any folder --> properties
2) On the "General" tab, clic the small "key" right from "Type - folder".
3) A new window pops-up, where you can read "Application Preference Order". Just clic on "Add" and enter the "Dolphin (SU)" you've created previously.

Hope that does it for you.

PS: There is a chance that "Dolphin (SU)" may be added directly to the top of that list, which may be an inconvenient if you have any desktop shortcuts to folders. Just play with the "preference order" as you wish, as long as the "Dolphin (SU)" application is on the list it should work.

workaround "kdesu dbus-launch dolphin" from discusion on forum.kde.org

(In reply to comment #19)
> workaround "kdesu dbus-launch dolphin" from discusion on forum.kde.org
>

Workaround works for me, thanks! A bit of a pain to have to do this everytime I wanna access the other partition, but I'm sure it won't be too long until this is fixed. At least, I hope not...

*** Bug 181537 has been marked as a duplicate of this bug. ***

Workaround works for me, thank you. I confirm this for KDE 4.2 under Kubuntu 8.10.

The workaround shouldn't be necessary if you have DBUS with autolaunch support (it was added to dbus at some point, no idea in which version).

"kdesu dolphin" works fine here, and for Andras Mantia.
We both see a dbus-daemon running as root (with --autolaunch).

If dbus autolaunch doesn't work for you, I have to blame either a too old DBUS version, or a distribution with a bad dbus setup possibly.

In reply to comment #23)
> The workaround shouldn't be necessary if you have DBUS with autolaunch support
> (it was added to dbus at some point, no idea in which version).
>
> "kdesu dolphin" works fine here, and for Andras Mantia.
> We both see a dbus-daemon running as root (with --autolaunch).
>
> If dbus autolaunch doesn't work for you, I have to blame either a too old DBUS
> version, or a distribution with a bad dbus setup possibly.
>

if I am running Dolphin Version 1.2 Using KDE 4.2.00 (KDE 4.2.0) "release 82.5"
under openSuse and others are using Fedora, Kubuntu, etc then it's a bit hard to understand how the distro is the problem

I am still having the problem and have a root dbus-daemon running and running dbus-1-1.2.4-5.1

Strange, indeed. I tested and worked with opensuse, same dbus and svn trunk.
Now I did a reboot and it doesn't work anymore.

David, when I run kdesu dolphin, it starts the dbus session bus for root, but not kdeinit4.
root 6451 0.0 0.0 21128 860 ? Ss 01:33 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root 6452 0.0 0.0 30224 820 ? S 01:33 0:00 dbus-launch --autolaunch d2f223773c984c89331a62fa493ee8fd --binary-syntax --close-stderr

I wonder why it started at previous test. It was also clear that at that time kdesu dolphin took some seconds to start, and now it is almost instant.

This bug still happens with me, so I beleive it should not be marked at resolved

Reopening then. Anyone with the bug, please look at the output in the terminal and the running processes, in order to find out 1) if dbus autostart works, and 2) if kdeinit4 starts (as root).
Double-check that the environment (PATH etc.) allows root to find kdeinit4, of course.......

Some tests:
- the problem isn't dbus, that is autolaunched, even if I kill the dbus processes, I will get new dbus processes, like:
root 12355 0.0 0.0 21128 904 ? Ss 11:09 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root 12356 0.0 0.0 30224 844 ? S 11:09 0:00 dbus-launch --autolaunch d2f223773c984c89331a62fa493ee8fd --binary-syntax --close-stderr

- kdeinit4 will not start, that's the problem:
ps ux | grep kde
root 13136 0.5 1.0 211816 22192 ? Sl 11:11 0:00 /opt/kde4/bin/dolphin
root 13870 0.0 0.0 5284 812 pts/10 S+ 11:13 0:00 grep kde

The PATH contains kdeinit4.

Now the interesting is that "kdesu konqueror" works, it starts the kdeinit4 for root and after that kdesu dolphin works as well.Probably sometime in the past I run a root process that started kdeinit4, this is why it worked. Sorry for confusing you David.

Here is what I have after starting kdesu konqueror:

ps ux | grep kde
root 13888 0.5 0.0 50012 1544 pts/15 Ss+ 11:14 0:00 /bin/su root -c /opt/kde4/lib64/kde4/libexec/kdesu_stub -
root 13891 0.0 0.0 12232 736 pts/15 S+ 11:14 0:00 /opt/kde4/lib64/kde4/libexec/kdesu_stub
root 13894 20.6 1.5 398900 31908 ? Ssl 11:14 0:00 /opt/kde4/bin/konqueror
root 13898 0.7 0.2 142744 5308 ? Ss 11:14 0:00 kdeinit4: kdeinit4 Running... de
root 13902 3.2 0.5 175252 12004 ? S 11:14 0:00 kded4
root 13910 0.0 0.3 147784 6792 ? S 11:14 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-root/klauncherT13899.slave-socket local:/tmp/ksocket-root/konquerorT13894.slave-socket
root 13911 0.0 0.3 147784 6788 ? R 11:14 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-root/klauncherT13899.slave-socket local:/tmp/ksocket-root/konquerorX13894.slave-socket
root 13912 0.0 0.3 147784 6792 ? S 11:14 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-root/klauncherT13899.slave-socket local:/tmp/ksocket-root/konquerorw13894.slave-socket
root 13914 0.0 0.0 5284 812 pts/10 S+ 11:14 0:00 grep kde
root 13916 0.0 0.3 147704 6804 ? S 11:14 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-root/klauncherT13899.slave-socket local:/tmp/ksocket-root/konquerorb13894.slave-socket

"kdesu dolphin" doesn't output anything on the terminal...

I confirm the results András has posted. I did the very same tests. When I issue "kdesu dolphin" there is no kdeinit4.

I am running Bluewhite64-12.2, KDE-4.2.0 and dbus-1.2.6 (but we already know it isn't dbus fault ;)

I tried that workaround (kdesu dbus-launch dolphin) and it really worked.

Does
   kdesu dolphin --nofork
work?

Then it's a KUniqueApplication-related problem.

(In reply to comment #30)
> Does
> kdesu dolphin --nofork
> work?
>
> Then it's a KUniqueApplication-related problem.
>

yes in openSuse 11.1 kde4.2

What am I missing?

[kenjiro@coruscant:~]$ kdesu dolphin --nofork
kdesu: Unknown option 'fork'.
kdesu: Use --help to get a list of available command line options.

(In reply to comment #32)
> What am I missing?
>
> [kenjiro@coruscant:~]$ kdesu dolphin --nofork
> kdesu: Unknown option 'fork'.
> kdesu: Use --help to get a list of available command line options.
>
try: kdesu 'dolphin --nofork' &

OK dokey. Tried: kdesu 'dolphin --nofork'

It really worked (not only the whole command). I could see folders and files.

The problem is not limited to Dolphin. I was using kdesudo to run some programs with a separate account. Try creating another user, then do kdesudo -u OTHER_USER konsole. While konsole starts, opening X programs from that console will fail:

test@doppelholz:~$ konsole
<unknown program name>(8518)/: KUniqueApplication: Cannot find the D-Bus session server

<unknown program name>(8517)/: KUniqueApplication: Pipe closed unexpectedly.

test@doppelholz:~$ konqueror
No protocol specified
konqueror: cannot connect to X server :0.0
test@doppelholz:~$ dolphin
<unknown program name>(8679)/: KUniqueApplication: Cannot find the D-Bus session server

<unknown program name>(8678)/: KUniqueApplication: Pipe closed unexpectedly.

As you can see, Dolphin and Konsole complain about a missing D-Bus server, while Konqueror does not.
kdesudo -u OTHER_USER Konqueror works and Konqueror can start other programs, including Dolphin and konsole.

Here's ps aux | grep test for kdesudo -u test dolphin:
test 9137 4.4 1.0 75704 21456 pts/1 Sl 11:44 0:00 dolphin
test 9141 0.0 0.0 3124 712 pts/1 S 11:44 0:00 dbus-launch --autolaunch 3e2e1f278702bf5637da71e94989a957 --binary-syntax --close-stderr
test 9142 0.0 0.0 2640 812 ? Ss 11:44 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session

And here for kdesudo -u test konqueror:
test 9171 2.7 1.6 112180 33372 pts/1 Sl+ 11:45 0:00 konqueror
test 9175 0.0 0.0 2640 848 ? Ss 11:45 0:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
test 9176 0.0 0.0 3124 716 pts/1 S+ 11:45 0:00 dbus-launch --autolaunch 3e2e1f278702bf5637da71e94989a957 --binary-syntax --close-stderr
test 9179 0.1 0.2 33340 4868 ? Ss 11:45 0:00 kdeinit4: kdeinit4 Running...
test 9180 0.1 0.4 35836 8892 ? S 11:45 0:00 klauncher
test 9183 0.8 0.5 58412 10544 ? S 11:45 0:00 kded4
test 9191 0.0 0.3 36096 7052 ? S 11:45 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-test/klauncherMT9180.slave-socket local:/tmp/ksocket-test/konquerorbw9171.slave-socket
test 9193 0.0 0.3 35868 6836 ? S 11:45 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-test/klauncherMT9180.slave-socket local:/tmp/ksocket-test/konquerorcF9171.slave-socket
test 9194 0.0 0.3 35868 6832 ? S 11:45 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-test/klauncherMT9180.slave-socket local:/tmp/ksocket-test/konquerorbh9171.slave-socket
test 9195 0.0 0.3 36096 7024 ? S 11:45 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-test/klauncherMT9180.slave-socket local:/tmp/ksocket-test/konquerortQ9171.slave-socket

As you can see, in both cases D-Bus has been started with the same arguments (BTW: The D-Bus processes do not terminate when the sudo session ends and accumulate. Argh!). However, there are no kded, klauncher and kdeinit processes when starting Dolphin or Konsole.

I'm running KDE 4.2.00 under Kubuntu Intrepid.

I can confirm comment#35
It's exactly the same on Gentoo running 4.2.0.

This makes most applications completely useless when they're run using 'kdesu'.

Opening file dialogs just shows:
"Could not start process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files."

Trying to send a mail via KMail shows:
Sending failed:
Unable to create SMTP job.
The message will stay in the 'outbox' folder until you either fix the problem (e.g. a broken address) or remove the message from the 'outbox' folder.
The following transport was used:
 <email address hidden>

D-Bus has autolaunch support, the running D-Bus session is even started with the '--autostart' argument.

*** Bug 187340 has been marked as a duplicate of this bug. ***

The bugs #189450, #189267, #186017 and #173697 might be duplicates/related.

I can also confirm comment #35 on gentoo running kde 4.2.2 on qt 4.5.

kdesu 'dolphin --nofork' (or any other command, like kdesu 'systemsettings --nofork') works fine. Otherwise I get errors.

I'm on Arch Linux with latest KDEmod packages.

This bug also affects System Settings.
https://bugs.kde.org/show_bug.cgi?id=189997

*** Bug 189997 has been marked as a duplicate of this bug. ***

I had a problem possibly similar to this bug but after asking the suse factory list, I tried altering kdesurc and the problem disappeared and I couldn't reproduce it anymore.
see https://bugzilla.novell.com/show_bug.cgi?id=511480.
Don't know if this sheds any light.

Looks like this bug has been fixed in KDE-4.3.0rc2. I just tested running dolphin and systemsettings by means of kdesu and it work nicely. I forgot to test it on KDE-4.3.0rc1.

Oh, I am running Bluewhite64-12.2.

Unfortunately I still get the error message with RC2 and 3 :(

Using kdesudo to launch an application 'as root' launches the application but results in the statement "The process for the file protocol died unexpectedly." The application is usable, and with root privileges. So something 'minor' is wrong, or is this symptomatic of a bigger problem?

(In reply to comment #45)
> Using kdesudo to launch an application 'as root' launches the application but
> results in the statement "The process for the file protocol died unexpectedly."
> The application is usable, and with root privileges. So something 'minor' is
> wrong, or is this symptomatic of a bigger problem?

Sorry. Running:
Distro Ubuntu 9.10 karmic
KDE 4.4.0
Kernel 2.6.31-19-generic i686 (32 bit)

Just launched Ark via kdesudo as soon as a dialog requiring file:// access opens it appears blank. I got the following konsole output

ark(2585)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-root/ksycoca4"
ark(2585)/kdecore (trader) KMimeTypeTrader::query: query for mimeType "application/x-tar" , "Kerfuffle/Plugin" : returning 1 offers
ark(2585)/kio (bookmarks) KBookmarkManager::KBookmarkManager: starting KDirWatch for "/root/.local/share//user-places.xbel"
ark(2585)/kio (KDirListerCache) KDirListerCache::listDir: Listing directory: KUrl("trash:/")
ark(2585)/kio (KDirListerCache) KDirListerCache::listDir: Listing directory: KUrl("file:///")
ark(2585)/kio (KDirListerCache) KDirListerCache::forgetDirs: Killing update job for "file:///"
ark(2585)/kio (KDirListerCache) KDirListerCache::listDir: Listing directory: KUrl("file:///")
ark(2585)/kio (KIOJob) KDirModel::indexForUrl: KUrl("file:///usr/src/gcc-4.2") not found
ark(2585)/kio (KDirModel) KDirModel::expandToUrl: Remembering to emit expand after listing the root url
ark(2585)/kio (KIOJob) KDirModel::indexForUrl: KUrl("file:///usr/src/gcc-4.2") not found
ark(2585)/kio (KDirModel) KDirModel::expandToUrl: Remembering to emit expand after listing the root url
ark(2585)/kio (KDirListerCache) KDirListerCache::listDir: Entry currently being listed: KUrl("trash:/") by (KDirLister(0xb1ced90) )
ark(2585)/kio (Slave) KIO::Slave::createSlave: createSlave "trash" for KUrl("trash:/")
ark(2585)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-root/arkNY2585.slave-socket"
ark(2585)/kio (Slave) KIO::Slave::createSlave: createSlave "file" for KUrl("file:///")
ark(2585)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-root/arkZK2585.slave-socket"
ark(2585)/kio (KDirListerCache) KDirListerCache::slotResult: finished listing KUrl("trash:/")
ark(2585)/kio (Slave) KIO::Slave::timeout: slave failed to connect to application pid= 2589 protocol= "file"
ark(2585)/kio (Slave) KIO::Slave::timeout: Houston, we lost our slave, pid= 2589
ark(2585)/kio (Slave) KIO::Slave::timeout: slave died pid = 2589
ark(2585)/kio (KDirListerCache) KDirListerCache::slotResult: finished listing KUrl("file:///")

I have Kubuntu 9.10 Karmic with KDE 4.4.x. Using "kdesudo dolphin --nofork &" causes dolphin to work for me.

I'm running Fedora 13 with KDE 4.4.5. I typed in "kdesu dolphin" and dolphin opened as expected. Anyone else having issues?

It still doesn't work for me using KDE 4.5.0 on Gentoo.

Hi all,

After few month to work under macosx with macports and KDE 4,5,3 install, without any problem, upgrating to KDE 4,5,4, i can see the same problem.

There is an entry in Macports :

https://trac.macports.org/ticket/25178

As you can see my comments in this thread, DBUS run fine. Also, as QT4 4.7.1 is aqua version not X11 based, what's happen ?

Gilles Caulier

Confirmed on KDE 4.5.4, Kubuntu 10.10 x64.
Besides what's been mentioned here, this also seems to affect me in Dolphin randomly when I double click files to open then inside Kate/any other process. Dolphin appears to freeze up for like 30 seconds, then finally shows this message, along with the other program saying the same thing. It happens so often and randomly I'm sick of it.

Oh, and if it helps, it also seems to do that on when opening files from browsing a network (using Samba for example), but I don't think it's restricted to that. Also took forever while opening pictures while browsing my sisters camera. As another side note, "kdesu dolphin" seemed to work.. One time it took forever to open when I tried though, tried it after and it worked normally fast. I've also gotten the "file://" protocol failed, or whatever message it was, someone mentioned earlier. I can't seem to reproduce the behavior, and it just happens whenever it feels like it. If you need anything else more specific, just ask.

I switch this file to Major because none KDE application can be used properly.

Somebody can guide us to resolve this issue ? Where is the problem exactly ? From DBUS ? A shared lib binary compatibility broken with KDELibs ?

Gilles Caulier

Can anyone suffering this bug check

1) the dbus-launch workaround described at https://bugs.kde.org/show_bug.cgi?id=199209

2) whether configuring oxygen as the widget style for *root*

prevents this bug?

Has the root cause of this issue been discovered?

openSUSE is having an issue which is apparently related to this one, so does anyone know the status of this bug?

A large number of applications appear to be unable to launch as root. openSuSE 11.4 has these issues (though they were first reported in openSuSE 11.2). This bug report may be related: https://bugs.kde.org/show_bug.cgi?id=199209

Additionally, openSuSE has a number of related bug reports:

https://bugzilla.novell.com/show_bug.cgi?id=656144 (this is what Will Stephenson above is referring to I believe, when he mentions the Widget Style for root)

https://bugzilla.novell.com/show_bug.cgi?id=514056

ALT+F2 -> kdesu dolphin works for me on openSUSE 11.4

The style dolphin comes up with looks nothing like oxygen, so it's not not using oxygen for root that causes this either.

The different theme is the workaround that is applied to avoid this bug.

https://bugzilla.novell.com/show_bug.cgi?id=656144#c21

Maybe it works for now because of the workaround? I'm not by my Linux box, so I will have check tomorrow. Either way, this workaround is not user friendly :(

(In reply to comment #59)
> ALT+F2 -> kdesu dolphin works for me on openSUSE 11.4
>
> The style dolphin comes up with looks nothing like oxygen, so it's not not
> using oxygen for root that causes this either.

Works for me too in in openSUSE 11.4
Strangely it uses the same style as my user, though I have never logged in as root or configured qtconfig as root.

(In reply to comment #60)
> The different theme is the workaround that is applied to avoid this bug.
>
> https://bugzilla.novell.com/show_bug.cgi?id=656144#c21
>
> Maybe it works for now because of the workaround? I'm not by my Linux box, so I
> will have check tomorrow. Either way, this workaround is not user friendly :(

What's not user-friendly about not using oxygen for root? One should not work as root anyway and hanging apps are certainly a lot less user-friendly than having them in some style.

Anyway. This is an oxygen bug and has nothing to do with openSUSE or kdesu etc. So the component of this bug has to be either changed or this one closed as "worksforme" and a new one opened against oxygen – in case the bug is still reproducible with KDE 4.7.

I meant "not user-friendly" because the workaround does not respect the users choice in theme, and it counters KDE's belief in beauty and KDE's style. Bad choice of words on my part.

I will create a new bug report against Oxygen since Oxygen is the only thing showing this issue.

More information available here: https://bugs.kde.org/show_bug.cgi?id=277249

On Kubuntu 11.4 (kde 4.6.4) this works just fine. I can not confirm.
Notice that the command is 'kdesudo' there.

The command "kdesu dolphin" fails silently in openSUSE 12.1 Milestone 3. The command "kdesu kwrite" fails providing no feedback, though Kwrite displays a crash dialogue. This issue is reliably reproducible.

i'm having issues launching kde apps with the sudo command

for example

sudo dolphin
http://paste.kde.org/140059/

kdesu dolphin
http://paste.kde.org/140065/

the only way to launch it with root privileges is kdesu dbus-launch dolphin

*** This bug has been marked as a duplicate of bug 199209 ***