Asking for input on Root Actions Service Menu

[kubicle]

1. Why don't we have an Utopic dev forum yet?

2. Now to the beef:

dbus 1.8 with dbus-run-session just landed on utopic and I was going to fix a long standing issue with my Root Actions servicemenu (well, more of a general kde issue) when launching dolphin with kdesudo (as root). The issue was that you could open a text file as root within the dolphin instance only in the first dolphin instance per session. subsequent times you'd only get an error along the lines of "kdeinit could not launch kate" or something similar (can't remember exactly).

I was about to go fix it by using dbus-run-session, but decided to try again just to make sure the issue was still there (and it wasn't...go figure).

So, is anyone else seeing this issue anymore?

Don't know whether it was fixed in KDE, in dbus or somewhere else, but I'd greatly appreciate any and all input on the issue:

So, if you have time, perform these steps:
1. start dolphin as root:
"kdesudo dolphin"
2. click on a text file to open it on kate
3. close kate and dolphin
4. repeat steps 1-3
5. Report results, including KDE and Dbus versions.

Thanks

[vinnywright]

issue still present in Kubuntu-14.04 KDE-4.13.3

dbus/trusty-updates,trusty-security,now 1.6.18-0ubuntu4.1 amd64 [installed]
simple interprocess messaging system (daemon and utilities)

VINNY

EDDIT: I can however open a text file in say /etc with my root actions service menu from a regular dolphin several times .

just not in a kdesudo (root) dolphin

[GreyGeek]

kdesudo dolphin

$ kdesudo dolphin
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
Object::connect: No such signal org::freedesktop::UPower:eviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower:eviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus:pen: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
QPixmap::scaled: Pixmap is a null pixmap

I was able to open a txt file using kate the first time but not the second. It gave me "KDEInit could not launch: /usr/bin/kate"

However, I could open a text file twice using KWrite.

[Qqmike]

Previously, I said this: Not very helpful here. I can't open a text file (as you specified) even ONCE:

CORRECTION: I did a Ctrl-Alt-Backspace, then I WAS able to open the text file once; but not twice.

I get this:
Sorry - Dolphin
KDEInit could not launch /user/bin/kate

Probably too old a system, anyway:
In 12.04,
dbus installed: 1.4.18-1ubuntu1.5
KDE 4.8.5

[kubicle]

Thanks for the input guys, I REALLY appreciate it.

@vinnywright:
Yeah, the root actions menu works fine multiple times, the issue is only with dolphin launched with kdesudo (or with the menu)

@GreyGeek:
The problem only rears it's head with some programs (like kate)...as you noticed kwrite seems unaffected

@Qqmike:
You probably had already used your one "free lunch" of the kde session, and once you started a fresh session, it worked once as expected.

I think the issue is a problem is connecting to the already existing root's dbus-daemon...and that causes the error (one can circumvent that by using dbus-launch, but that's a bit hackish with issues of it's own...dbus 1.8 has dbus-run-session which would be a better solution, but seems like it's not necessary anymore).

Anyway, like I said, I'm not seeing the error anymore on utopic (dbus 1.8.x) so it might finally be solved (you seem to all be using <=1.6.x dbus).

So now I only need some one running dbus 1.8.x to confirm it's fixed.

[GreyGeek]

I'm running dbus (1.6.18-0ubuntu4.1), so the problem exists in that version on my Trusty Tahr, fully updated.

[MoonRise]

Here:

After 1. I went to open a text file (double click) and received "KDEInit could not launch: /usr/bin/kate". Then did Right Click --> Open With Kate and it produced the same result. However, if I used the Root Actions Service Menu (Right Click --> Root Actions ... Open as Text) it opens right up.


Kubuntu 14.04.

[vinnywright]

Thanks for the input guys, I REALLY appreciate it.

So now I only need some one running dbus 1.8.x to confirm it's fixed.

K I was going to put some ver of sid on the old 13.10 partition this weekend but will do utopic first ,,,,,,,,,unless someone else or2 confirms it first

VINNY

[Snowhog]

1. Why don't we have an Utopic dev forum yet?

Because you asked, now we do.

[kubicle]

K I was going to put some ver of sid on the old 13.10 partition this weekend but will do utopic first ,,,,,,,,,unless someone else or2 confirms it first

You don't have to go out of your way to test it (although I don't mind if you do ), someone with Utopic will pick it up...provided they catch the thread.

Because you asked, now we do.

Along those lines, could this thread be moved there, thanks

[verndog]

...
2. Now to the beef:

dbus 1.8 with dbus-run-session just landed on utopic and I was going to fix a long standing issue with my Root Actions servicemenu (well, more of a general kde issue) when launching dolphin with kdesudo (as root). The issue was that you could open a text file as root within the dolphin instance only in the first dolphin instance per session. subsequent times you'd only get an error along the lines of "kdeinit could not launch kate" or something similar (can't remember exactly).

I was about to go fix it by using dbus-run-session, but decided to try again just to make sure the issue was still there (and it wasn't...go figure).

So, is anyone else seeing this issue anymore?

Don't know whether it was fixed in KDE, in dbus or somewhere else, but I'd greatly appreciate any and all input on the issue:

So, if you have time, perform these steps:
1. start dolphin as root:
"kdesudo dolphin"
2. click on a text file to open it on kate
3. close kate and dolphin
4. repeat steps 1-3
5. Report results, including KDE and Dbus versions.

Thanks

Yes, I have that same issue. Used root once and on the second try, it fails.

edit: I'll have to try again to get #5 results.

[kubicle]

Yes, I have that same issue. Used root once and on the second try, it fails.

edit: I'll have to try again to get #5 results.

Are you using trusty (or earlier) with dbus 1.6.x (or lower)...or utopic with dbus 1.8.x?
Your bugged result is expected behavior in the former, should be fixed in the latter.

[Rog132]

With Utopic

1. start dolphin as root:
"kdesudo dolphin"
2. click on a text file to open it on kate
3. close kate and dolphin
4. repeat steps 1-3
5. Report results, including KDE and Dbus versions.

Still there...

rog132@fox6u:~$ apt-cache policy dbus
dbus:
Installed: 1.8.6-1ubuntu1
Candidate: 1.8.6-1ubuntu1
Version table:
*** 1.8.6-1ubuntu1 0
500 http://fi.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
100 /var/lib/dpkg/status

rog132@fox6u:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10
Codename: utopic

rog132@fox6u:~$ kde4-config --version
Qt: 4.8.6
KDE Development Platform: 4.14.0
kde4-config: 1.0

[kubicle]

Thanks Rog, I just noticed it myself (I upgraded another host to utopic and saw the issue back again...still no idea why it seemed to work fine on the laptop)

Luckily, dbus-run-session works as expected (on both machines), so I can fix it in the menu (although only on machines with dbus 1.8) even if the issue is still there.

[kubicle]

Uploaded Root Actions 2.8.2 (http://kde-look.org/content/show.php...?content=48411)

This version hopefully fixes the "KDEInit coul not launch" issue, although only with dbus 1.8.x onwards (Utopic) and only when using the menu to launch dolphin.

I'd happily hear any usage experiences from Utopic users (to make sure it's really fixed)...if you're not using Utopic, you can still try it out and see that there aren't any new bugs caused by the fix (there shouldn't be), but the issue will still be there if you don't have dbus 1.8.x.

Thanks again to you all for your activity.