DCOP problem when running a kde app remotely (withDISPLAY redirect)

[Com Pegasus-CC-Hotline]

Hello,

> Wouldn't it be better to use a commandline mixer like alsamixer?

This would be my next (and last) chance, as I need to switch
off something called "externel something" or so, but all other mixers
I have tried so far do not handel this switch, except kmix.
So that's probably my last chance to get my vinyl into this computer.

And anyway: If it isn't possible to just run a kde app without beforehand
starting a bunch of servers (I have read about some further, which might 
be needed), then I am really a bit "upset" of kde.

As the -dopcserver switch is already standard to all kde apps, then
shouldn't it be standard to have something like "-dcopserver none"
to switch it off, for any unforseable situations like this one?

cu,
Thomas
 
 

-----Ursprüngliche Nachricht-----
Von: Kevin Krammer [mailto:kevin.krammer at gmx.at] 
Gesendet: Donnerstag, 24. August 2006 12:32
An: kde at mail.kde.org
Betreff: Re: [kde] DCOP problem when running a kde app remotely (withDISPLAY redirect)

On Wednesday 23 August 2006 17:56, Com Pegasus-CC-Hotline wrote:
> Hello,
>
> I have to run a kde application (kmix) remotely on a non-X, non kde
> system.
> I don't want to install big packets there, as I want to run this kmix
> one-time only,
> and the system shall actually stay damm small.

Wouldn't it be better to use a commandline mixer like alsamixer?

> Result: kmix didn't start due to missing DCOPserver. Then I found
> the -dcopserver switch available for all kde applications, but the
> proposed syntax (first line from ~/.DCOPserver*) doesn't address
> the need to use a remote one.
>
> However, I have read, that a different dcop server is needed for each
> display,
> so it should be possible to use a remote dcop server in order to use a
> remote
> display. But how to do it, or in other words:
>
> What is the syntax for the -dcopserver argument to contact a remote dcop
> server,
> and are there any other things I should take into account?

DCOP handles it transport through the ICE library, which might be able to 
handle remote connections as well. However I guess DCOP registers a local 
connection, i.e. libICE creates a unix socket, very likely for security 
reasons.

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer at gmx.at>
Qt/KDE Developer, Debian User
Moderator: www.mrunix.de (German), www.qtcentre.org
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.