When dolphin opened using " su-to-root -X -c dolphin and/or Alt + F2 and then kdesu dolphin" as advised. I still cannot right click on a text file and edit, say with kwrite.

Code:

The error is now an error box
- Sorry dolphin -
KDEInit could not launch '/usr/bin/kwrite'.

The same error occurs opening a file from Krusader root-mode.

I'm new to forums so not sure if I should open a new topic or continue?

Thanks again for help and advice.

blackhole

Post subject:Posted: 10.10.2010, 13:06

Joined: 2010-09-12
Posts: 110

Status: Offline

It happens sometimes. Normally a reboot will fix the problem (longtime bug).
However, in krusader, you can edit without problems hitting F4 (edit).

somerset

Post subject:Posted: 10.10.2010, 14:19

Joined: 2010-10-09
Posts: 8

Status: Offline

Thankyou edhunter and blackhole for your help and time.

More info.

After dolphin opened using " su-to-root -X -c dolphin" and edit a text file.

error
- Sorry dolphin -
KDEInit could not launch '/usr/bin/kwrite'.

After closing this box the computer runs slow with cpu time constantly at approx 70%.
In System activity viewer there are 4 or 5 greyed out processes constantly flicking on and off. There are several knotify4 and a dbus-daemon, that have constantly changing PID's.

The easiest way to recover cpu is to change runlevel by init 2 and then init 5.

However krusader root-mode and edit with F4 does seem to work, but it is a lot of extra effort just to edit a few text files in root mode.

Thanks again for help.

devil

Post subject:Posted: 10.10.2010, 19:14

Joined: 2010-08-26
Posts: 491
Location: Berlin
Status: Offline

you could resort to using mc or mcedit <path>
vi is another possibility but needs some getting-used-to
(some people say vi is a operating system, not an editor)

greetz
devil

devil

Post subject:Posted: 11.10.2010, 11:19

Joined: 2010-08-26
Posts: 491
Location: Berlin
Status: Offline

somerset,
could you please report your version of sux.
there is a new version out today: 1.0.1-6
could you try that please with kde and gtk apps and report any errors.
i am trying to give useful input to the maintainer.
thxx.

greetz
devil

somerset

Post subject:Posted: 17.10.2010, 20:04

Joined: 2010-10-09
Posts: 8

Status: Offline

Sorry for delay - I've been offline for a while.

I'm using apttosid 10 2 dvd in 32bit live mode.

sux version is 1.0.1-5

After loading sux 1.0.1-6 with apt-get (i'm in live mode). The result is still the same.

On a friends dual core laptop htop shows both cores shoot up to about 70% after trying to open a text file from root mode "su-to-root -X -c dolphin", but wont launch kwrite.
-error- KDEInit could not launch '/usr/bin/kwrite'

apt-get'ed gedit plus about 40MB dependencies.
From root mode dolphin text file "open with gedit" - Does not open - no error box this time but again cpu both cores shoot up to about 70% until processes killed again.

I've got the same problem from the beginning I use sidux/aptosid. I can't start an application to open something out of an application like dolphin or konqueror, wich I have started with su rights (sudo, su-to-root, kdesu, sux - it's everytime the same). I always right-klick on an object I want to open with another application, select open with and than select... (I have set the configuration on german so the entrys I have listed here might differ). In the following window you can select the application that should open your document - enter kdesu [application].
It normally works, so I think the, for example, kdesu dolphin accesses it's fixed configuration (here a .desktop file somewhere around ~/.kde/…/servicemenus) wich tells itto execute the standard kwrite, not the root-kwrite, but dolphin is (partly) in root-mode so KDEInit and klaunch are getting a bit confused. I think that the real problem is in sudo on wich kdesu and sux are based on (not really, but theey all use the same parts like the sudoers-list and have similar libraries) that just simulates a root environment, but not completely. Another ugly thing can happen when using kdesu/sudo/sux: If you start a programm like dolphin the first time, but you do this with root-rights, the configuration is saved in your home environment, but is owned by root, because sudo gives root-powers, stays in your normal home-folder (if you haven't changed it in the commandline), what causes that the next start of dolphin doesn't work properly, because you have no write access to the config. So you have to get root again and change all ownership of all data in your home-folder to your username.
I think I'll try to bugfix the "can't run an application out of root-mode"Problem.

Do you know where the servicemenu folder in KDE4 is (Still working with KDE3 on an USB-Drive - never have done a d-u there )?
You can add this script to /usr/bin/rootlauncher and modify all servicemenu scripts so that they execute rootlauncher [command]
Example: