<br><tt><font size=2>Stefan Baur <newsgroups.mail2@stefanbaur.de>
wrote on 02/03/2011 22:21:48:<br>
[SNIP]</font></tt>
<br><tt><font size=2>> > nxagent
:1000<br>
> > DISPLAY=:1000 konqueror ~<br>
> ><br>
> > Have a look in your ~/.xsession-errors too.<br>
> ><br>
> No errors when running nxagent locally - konqueror runs just fine
in the <br>
> nxagent window.<br>
</font></tt>
<br><tt><font size=2>Hmmm</font></tt>
<br>
<br><tt><font size=2>[SNIP]</font></tt>
<br><tt><font size=2>> Well, I had the idea to install the Nomachine
NXclient on the same <br>
> machine and connecting to 127.0.0.1.<br>
> Result: the NX session terminates unexpectedly when calling konqueror,
<br>
> just like it does on Windows.<br>
> So I can reproduce the issue under Windows (NXClient 3.4.0-5) and
Linux <br>
> (NXClient 3.4.0-7).<br>
</font></tt>
<br><tt><font size=2>So, d'you mean that if you run nxagent locally, a
rootless</font></tt>
<br><tt><font size=2>konqueror works fine, but if you run nxclient locally
rootless</font></tt>
<br><tt><font size=2>konqueror doesn't ??</font></tt>
<br>
<br><tt><font size=2>> The crash logs *nothing* in .xsession-errors<br>
> <br>
> If it's not an NX nor a FreeNX issue, what is it?<br>
> > Do you have two versions of kde installed ??<br>
> Not sure what you mean by that. My test machine is a stock install:<br>
</font></tt>
<br><tt><font size=2>Suse allowed you to keep both kde3 and kde4 but changed
the</font></tt>
<br><tt><font size=2>paths for one of them so it wasn't completely standard
. . .</font></tt>
<br>
<br><tt><font size=2>></font></tt>
<br><tt><font size=2>>kde-window-manager 4:4.4.5-0ubuntu1 KDE 4 window
manager </font></tt>
<br><tt><font size=2>>kdepimlibs5 4:4.4.5-0ubuntu1 core libraries for
KDE </font></tt>
<br>
<br><tt><font size=2>Looks like you are running 4.4.5 not 4.3.1</font></tt>
<br>
<br><tt><font size=2>I'm only on 4.3.5 so we aren't testing quite the same
thing</font></tt>
<br><tt><font size=2>and I don't know what startkde launches.<br>
</font></tt>
<br><tt><font size=2>It could just be a libraries issue, as the full kde
works OK.</font></tt>
<br>
<br><tt><font size=2>Try launching full kde4 from a remote xterm, then
exiting it as</font></tt>
<br><tt><font size=2>soon as it is running and then immediately try (a
rootless)</font></tt>
<br><tt><font size=2>konqueror from xterm and see if it can find everything
it</font></tt>
<br><tt><font size=2>needs to run.</font></tt>
<br>
<br>