30 Jul
2015
30 Jul
'15
10:55 a.m.
On Thursday 30 July 2015 11:42:09 E. Liddell wrote:
On Thu, 30 Jul 2015 11:02:02 +0100
Lisi Reisz <lisi.reisz(a)gmail.com> wrote:
It now looks as though the real one was not functioning, and has somehow been
stirred into functioning. Unless this is right, and all the stirring around
has moved the real one up the pecking order?
Anything I can do to find out? If there is a rogue one floating around, I
should perhaps get rid of it.
I am baffled but delighted. I do love this list!!
Lisi
On Thursday 30 July 2015 10:45:39 Lisi Reisz
wrote:
Maybe you've got a rogue nonfunctional tdesu installed somewhere earlier in
your $PATH? Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because
KWrite launches fine as $USER.) It works here on R14.0.1 and tdesu is installed
by
tdebase-trinity-bin so I assume it's installed on your computer. But
if /opt/trinity/bin is not in your path that command will fail more
or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes
about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my
paths.