Is /opt/trinity/bin in root's path? Try adding it to /root/.bashrc and seeing if it works then.
http://unix.stackexchange.com/questions/26047/how-to-correctly-add-a-path-to-path

On Fri, Sep 23, 2016 at 4:43 AM, <andre_debian@numericable.fr> wrote:
On Thursday 22 September 2016 21:58:50 Kate Draven wrote:
> > I open my TDE-trinity session with the user "andre".
> > If I use Konqueror as files-manager, with the user "root",
> > (to modify root text files),
> > I cannot open a text file with kedit or kwrite.
> > "TDEInit cannot launch kedit".
> > In user "andre", it works fine.
> > André

> Hi André
> When that happens to me, I usually delete the files
> .xsession-errors
> .Xauthority
> As root in konq, then close it up and start over. Works fine after that.
> If you see more than one .Xauthority, clear them all.
> I hope this helps,  Kate

I deleted ".xsession-errors" and ".Xauthority" in the "andre" account,
(/home/andre/) it worked, I could open text files with kedit.

And now, after booting my PC in the morning, I cannot do it.
 "TDEInit cannot launch kedit".

On Friday 23 September 2016 03:45:11 Dave Lers wrote:
> > If I use Konqueror as files-manager, with the user "root" :

> Do you use su Konqueror as user andre (menu > System > SuperUser >
> Konqueror)?
The two solutions :
System > SuperUser > Konqueror
and
by creating an icon on the desktop, with :
Excecute with a different user = root.

Now, the both don't work to open text files with kedit.

Thanks.

André

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting




--

John Pisini

Systems Administrator

TFCCS

617-450-3988



Disclaimer for email:


The information contained in this electronic message and any attachments to this message is intended for the exclusive use of the addressee(s) and may contain confidential or privileged information.  This e-mail is not intended to, and shall not, constitute an electronic signature giving rise to a binding legal contract, unless expressly stated otherwise in the body of the e-mail by the sender.