Bug 225780 - kdesu - Unable to Browse Files when App Started with Root Authority
Summary: kdesu - Unable to Browse Files when App Started with Root Authority
Status: RESOLVED DUPLICATE of bug 217620
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
Depends on:
Reported: 2010-02-07 00:25 UTC by David Rankin
Modified: 2010-11-06 23:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2010-02-07 00:25:53 UTC
Version:            (using Devel)
Installed from:    Compiled sources


    Another problem that has appeared in 4.4 beta shapshots is that any time you run an app with elevated privileges such as running 'kdesu systemsettings' you cannot access any files on the filesystem. When you click on a setting that requires you to find a files on your system like login manager -> themes -> install new theme, the file open dialog appears, but then as soon as you try to change directories, etc. you get the error:

Could not start process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files.

    You can move through your directories, but the file window pane of the file open dialog remains empty.

    EVEN if you navigate to the proper directory, use xterm to copy the exact file name to the file open dialog, you CANNOT access the file. All of which makes much of systemsettings useless.

    That's it. Let me know if you need anything else. Thanks.
Comment 1 David Rankin 2010-02-07 02:51:03 UTC
Here is a bit more info that might help:

Say for example, you click on 'Install New Theme' from login manager in system settings, you first get an awkward little dialog box that just has a place to type a file name and only the little 'floppy disk' icon that allows you to bring up the normal file-open dialog. You bring up the normal file-open dialog and then try browsing to an opening any file causing the error. After you dismiss the error message and then hit cancel to close the file-open dialog (it's the only way you can close it) a dbus-launch process is left running and eating up CPU (a lot).

I found this error because the fans on my laptop started screaming and just stuck on full flow. At first I thought it was just nepomuk or something, but it never went away. Looking closer, it looked like the file-open dialog had left the launcher associated with the file-open dialog running and the stray process was really hitting the CPU. I had to kill this set of processes manually and then the system returned to normal:

5588 ?        S      0:00 dbus-launch --autolaunch 7a0501a6c921a52616ec2e64484e7035 --binary-syntax --close-stderr
 5591 ?        Ss     7:21 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session
21054 ?        R      0:00  \_ /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session

I don't know if this will help or not, but I thought I would pass it along. Thanks.
Comment 2 Oswald Buddenhagen 2010-11-06 23:26:04 UTC

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