kdesudo - process for the file protocol died unexpectedly

[SteveK]

Binary package hint: kdesudo

When running kdesudo or kdesudo dbus-launch dolphin or another app that uses file protocol, the following message is received: "The process for the file protocol died unexpectedly" and the relevant folder shows no contents. Gksudo dbus-launch seems to work OK after any previous kdesudo attempts have "timed-out".

I have also posted about this at the Kubuntu forums (http://kubuntuforums.net/forums/index.php?topic=3109260.0) where some have confirmed the issue and others not. It seems to be inconsistent.

Regards,

Steve

ProblemType: Bug
Architecture: i386
Date: Tue Jan 12 10:57:33 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: kdesudo 3.4.2.2-0ubuntu1
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
SourcePackage: kdesudo
Uname: Linux 2.6.31-18-generic i686
XsessionErrors:
 (polkit-gnome-authentication-agent-1:2207): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
 (<unknown>:2692): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed

[The Recorder (arthurbm)]

I have had the same exact problem, and have also found that using "gksudo dbus-launch ......." works, while kdesu, kdesudo, and gksu (with or without dbus-lauch) do not.

[nerdy_kid (nerdy-kid)]

gksu dbus-launch.... works for me. I really hope that this issue gets fixed before the release. I like the terminal and all, but......
Maybe RC2?

[vmc (vmclark)]

None of the examples or fixes work for me.

[SteveK (stevekej)]

Hmm, the bug is still present in 4.4 final.

You can lead a horse to water...

[BigcityCat (pshomeexpress)]

Yes I have this issue and I have talked to several others who do as well.

[Jonathan Thomas (echidnaman)]

Hi,

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: https://bugs.kde.org/show_bug.cgi?id=165268
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

[SteveK (stevekej)]

Thanks for taking the time to look at this Jonathan.

The bug you linked to in fact seems to be about using kdesudo or kdesu without dbus-launch, which was specified there as a workaround. In this bug adding dbus-launch makes no difference.

However, the good news is that the other specified workaround there i.e.

kdesudo 'dolphin --nofork' &

Does appear to work in this case, although I haven't tested it extensively.

No doubt it's all related even if it isn't exactly the same issue.

Best regards,

Steve

[Leo Milano (lmilano)]

Hi All,

FWIW, in Lucid, just running "sudo dolphin" works fine for me, whereas "kdesudo dolphin" doesn't.

[Intrepido (intre-pido-poco)]

Same in karmic when update to KDE 4.4

[Robert McKee (bertmanphx)]

Same problem here.

see attached file, when trying to run from Konsole.

bertmanphx

[Robert McKee (bertmanphx)]

This is the output when trying to run dolphin as root from konsole

[molecule-eye (niburu1)]

Both "sudo dolphin" and "kdesudo dolphin" don't work for me. However, the workaround command "kdesudo 'dolphin --nofork' &" did work for me. I'm using Kubuntu 9.10 Karmic with KDE 4.4.1 installed via the backports repository.

[michael (reeves-87)]

Using "kdesudo 'dolphin --nofork' &" works for me. This issue seems to happen with any program launched via kdesudo that attempts to open a navigation dialog for the file system. Kubuntu 9.10 Karmic with KDE 4.4.x.

[Thomas Sisson (thomas-sisson-1)]

It's back and it's valid! Perhaps the issue is improperly listed, but the issue is real.

[Thomas Sisson (thomas-sisson-1)]

Also, the nofork option does not work anymore because it was removed from Dolphin. Sorry I couldn't edit my own comment, so I had to make a new comment.

[eugenez (eugene-zvyagintsev)]

"kdesudo dbus-launch dolphin" works fine (workaruund from https://bugs.kde.org/show_bug.cgi?id=165268#c19).

You can define an alias in ~/.bashrc: alias kdesudo='kdesudo dbus-launch' and (after re-login) just use "kdesudo blablabla"

(Kubuntu 16.10 with Plasma 5.8.5)