<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-15"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hi,<br>
    <br>
    A lot of KDE applications return immediately and spawn the real
    command under another pid, a bit like a deamon (but not quite).<br>
    I am not aware of any effective and seamless workaround.<br>
    You can wrap them in a script that does not exit, but then
    how/when do you choose to terminate that script...<br>
    <br>
    Cheers<br>
    Antoine<br>
    <br>
    <br>
    <br>
    On 03/02/2011 08:11 AM, Stefan Baur wrote:
    <blockquote cite="mid:4D6E41F0.6080701@stefanbaur.de" type="cite">Hi
      list,
      <br>
      <br>
      I'm having issues with sessions terminating unexpectedly when
      tring to run certain KDE applications.
      <br>
      <br>
      Server:
      <br>
      Ubuntu 10.04 LTS (Lucid Lynx) with FreeNX installed via
      <br>
      <br>
      debhttp://ppa.launchpad.net/freenx-team/ppa/ubuntu  lucid  main
      <br>
      deb-srchttp://ppa.launchpad.net/freenx-team/ppa/ubuntu  lucid 
      main
      <br>
      <br>
      Client:
      <br>
      Windows 7 Home Premium with Nomachine NXClient 3.4.0-5
      <br>
      <br>
      To debug the issue, I did the following:
      <br>
      Start xterm in rootless mode
      <br>
      Run "screen" in xterm
      <br>
      Run a regular SSH session (using PuTTY)
      <br>
      Connect the PuTTY session to the xterm-screen by issuing "screen
      -x"
      <br>
      <br>
      Run "konqueror ~" in xterm
      <br>
      NX session aborts; the screen session in PuTTY shows the
      following messages:
      <br>
      <br>
      <blockquote type="cite">surfer1@surfbox:~$ konqueror ~
        <br>
        kdeinit4: preparing to launch
        /usr/lib/libkdeinit4_klauncher.so
        <br>
        Connecting to deprecated signal
        QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
        <br>
        kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
        <br>
        kdeinit4: preparing to launch
        /usr/lib/libkdeinit4_kbuildsycoca4.so
        <br>
        kbuildsycoca4 running...
        <br>
        kdeinit4: preparing to launch
        /usr/lib/libkdeinit4_kconf_update.so
        <br>
        Connecting to deprecated signal
        QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
        <br>
        QFSFileEngine::open: No file name specified
        <br>
        konqueror(8034) OpenSearchManager::setSearchProvider: "Cannot
        open opensearch description file: "
        <br>
        konqueror(8034)/kdecore (KLibrary) kde4Factory: The library
        "/usr/lib/kde4/konq_sidebar.so" does not offer a
        qt_plugin_instance function.
        <br>
        konqueror(8034)/kdecore (KLibrary) kde4Factory: The library
        "/usr/lib/kde4/konq_shellcmdplugin.so" does not offer a
        qt_plugin_instance function.
        <br>
        konqueror: Fatal IO error: client killed
        <br>
        kdeinit4: Fatal IO error: client killed
        <br>
        klauncher: Exiting on signal 15
        <br>
        kded4: Fatal IO error: client killed
        <br>
      </blockquote>
      (here's where it crashes)
      <br>
      <br>
      If I run a full-screen KDE session, it doesn't crash:
      <br>
      <blockquote type="cite">surfer1@surfbox:~$ konqueror ~
        <br>
        QFSFileEngine::open: No file name specified
        <br>
        konqueror(10384) OpenSearchManager::setSearchProvider: "Cannot
        open opensearch description file: "
        <br>
        konqueror(10384)/kdecore (KLibrary) kde4Factory: The library
        "/usr/lib/kde4/konq_sidebar.so" does not offer a
        qt_plugin_instance function.
        <br>
        konqueror(10384)/kdecore (KLibrary) kde4Factory: The library
        "/usr/lib/kde4/konq_shellcmdplugin.so" does not offer a
        qt_plugin_instance function.
        <br>
        QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
        failed: No such file or directory
        <br>
        QFileSystemWatcher: failed to add paths:
        /home/surfer1/.config/ibus/bus
        <br>
        Bus::open: Can not get ibus-daemon's address.
        <br>
        IBusInputContext::createInputContext: no connection to
        ibus-daemon
        <br>
      </blockquote>
      (konqueror starts as requested, NX session stays active)
      <br>
      <br>
      What's going on here? Any ideas? Is this a bug? Is there a
      workaround for rootless sessions and KDE applications?
      <br>
      <br>
      Kind Regards,
      <br>
      Stefan
      <br>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
________________________________________________________________
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:

<a class="moz-txt-link-freetext" href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a>
  
         Don't forget to check the NX Knowledge Base:
                 <a class="moz-txt-link-freetext" href="http://www.nomachine.com/kb/">http://www.nomachine.com/kb/</a> 

________________________________________________________________
       FreeNX-kNX mailing list --- <a class="moz-txt-link-abbreviated" href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a>
      <a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/freenx-knx">https://mail.kde.org/mailman/listinfo/freenx-knx</a>
________________________________________________________________</pre>
    </blockquote>
    <br>
  </body>
</html>