From kde-linux Wed Jan 30 09:26:16 2002 From: "C. Drechsle" Date: Wed, 30 Jan 2002 09:26:16 +0000 To: kde-linux Subject: [kde-linux] dcopserver - problem with sharing an kde-desktop X-MARC-Message: https://marc.info/?l=kde-linux&m=101238281525982 MIME-Version: 1 Content-Type: multipart/mixed; boundary="------=_NextPart_000_0015_01C1A978.8CAE7E20" This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C1A978.8CAE7E20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For our network-project I'm testing a thin client that has no harddisk = and should work with the applications of a linux server through an = embedded Liunx named eLux. From this thin client it is possible to start = a kde on a remote server with the XDM-protocol. That works. But if the KDE on the server is already in use, the remote-user receives = the message: could not read network connection list // .DCOPserver_kch145_TC148:1 check... "dcopserver" ...runing. Now Im looking for documentation to the dcopserver.=20 ------=_NextPart_000_0015_01C1A978.8CAE7E20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

For our network-project I'm = testing a thin=20 client that has no harddisk and should work with the applications of a = linux=20 server through an embedded Liunx named eLux. From this thin client it is = possible to start a kde on a remote server with the = XDM-protocol.
That=20 works.
But if the KDE on the server is already in use, the = remote-user=20 receives the message:

could not read network connection = list
//=20 .DCOPserver_kch145_TC148:1

check... "dcopserver" = ...runing.

Now Im looking for documentation to the = dcopserver.=20

------=_NextPart_000_0015_01C1A978.8CAE7E20-- ___________________________________________________ This message is from the kde-linux mailing list. Account management: http://mail.kde.org/mailman/listinfo/kde-linux. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.