[gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[Wolfgang Liebich]

Hi,
This is probably partiallay OT, but google didn't help me much until
now.
I'm logged in on my new computer, Machine N. I have setup ssh to connect
by DSA key to my old computer, Machine O. Now i want to use the dcop
program on O to give me a list of all open konqueror sessions on O. At
first I just want to do something like:
<new machine>:ssh <old machine> '/usr/kde/3.5/bin/dcop'
But I always get "ERROR: Couldn't attach to a DCOP server'"
What gives?
puzzled in Vienna,
Wolfgang
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[Boyd Stephen Smith Jr.]

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

On Tuesday 26 September 2006 03:50, Wolfgang Liebich 
<Wolfgang.Liebich@siemens.com> wrote about '[gentoo-user] Question about 
the dcop utility: How to use it from a remote computeR?':
> I'm logged in on my new computer, Machine N. I have setup ssh to connect
> by DSA key to my old computer, Machine O. Now i want to use the dcop
> program on O to give me a list of all open konqueror sessions on O. At
> first I just want to do something like:
> <new machine>:ssh <old machine> '/usr/kde/3.5/bin/dcop'
> But I always get "ERROR: Couldn't attach to a DCOP server'"

I've never used DCOP, but I figured this was probably related to 
environment variables, so I did an strace on a simple dcop invocation to 
try and figure out why it can't find the (presumably) running dcop server 
on "O".

On my system communication with the local DCOP server is via 
~/.DCOPserver_<hostname>__0, and I'm fairly sure the _0 at the end 
corresponds to part of my DISPLAY setting, ":0", indicating a local X 
server.  You may need to set your DISPLAY environment variable on "O" 
before you do the dcop invocation.

Assuming "O" is a standard desktop machine and you are the only one logged 
on to it, you should be able to do something like:
ssh O env DISPLAY=:0.0 dcop
to get the standard dcop output.

The only sure-fire way to determine the correct DISPLAY setting is to pull 
it from the X session you want to connect to. E.g.:
$ env | grep ^DISPLAY
DISPLAY=:0.0

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[Alan McKinnon]

On Tuesday 26 September 2006 10:50, Wolfgang Liebich wrote:
> Hi,
> This is probably partiallay OT, but google didn't help me
> much until now.
> I'm logged in on my new computer, Machine N. I have setup ssh
> to connect by DSA key to my old computer, Machine O. Now i
> want to use the dcop program on O to give me a list of all
> open konqueror sessions on O. At first I just want to do
> something like:
> <new machine>:ssh <old machine> '/usr/kde/3.5/bin/dcop'
> But I always get "ERROR: Couldn't attach to a DCOP server'"
> What gives?

dcop will only work properly in the same session as the kdeinit 
that launched it. So, if you start konsole from KDE and run 
dcop it will work. The ssh session is not attached to kdeinit 
in any way so won't contact the dcop server.

I've never had to do what you want to accomplish so I don't have 
a definitive answer. I'd read the docs for dcop and see if 
there's an answer there. Alternatively (thinking out the box 
here), maybe try launch screen from a kde session and attach it 
to an ssh session...

alan
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[Mike Myers]

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

Hi!
You need to use either the --all-sessions or --all-users switch, or just use
--user or --session and specify which you want to work with.  Since several
instances of KDE can run on the same computer, dcop needs to know which one
to use if you aren't runnign the dcop command from the KDE session.

On 9/26/06, Wolfgang Liebich <Wolfgang.Liebich@siemens.com> wrote:
>
> Hi,
> This is probably partiallay OT, but google didn't help me much until
> now.
> I'm logged in on my new computer, Machine N. I have setup ssh to connect
> by DSA key to my old computer, Machine O. Now i want to use the dcop
> program on O to give me a list of all open konqueror sessions on O. At
> first I just want to do something like:
> <new machine>:ssh <old machine> '/usr/kde/3.5/bin/dcop'
> But I always get "ERROR: Couldn't attach to a DCOP server'"
> What gives?
> puzzled in Vienna,
> Wolfgang
> --
> gentoo-user@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1303 bytes --]

AW: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR?

[Liebich, Wolfgang]

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

Hi,

>Von: Boyd Stephen Smith Jr. [mailto:bss03@volumehost.net]
>Gesendet: Di 9/26/2006 3:56
>An: gentoo-user@lists.gentoo.org
>Betreff: Re: [gentoo-user] Question about the dcop utility: How to use it from a remote computeR?
<snip>

>I've never used DCOP, but I figured this was probably related to 
>environment variables, so I did an strace on a simple dcop invocation to 
>try and figure out why it can't find the (presumably) running dcop server 
>on "O".

>On my system communication with the local DCOP server is via 
>~/.DCOPserver_<hostname>__0, and I'm fairly sure the _0 at the end 
>corresponds to part of my DISPLAY setting, ":0", indicating a local X 
>server.  You may need to set your DISPLAY environment variable on "O" 
>before you do the dcop invocation.

>Assuming "O" is a standard desktop machine and you are the only one logged 
>on to it, you should be able to do something like:
>ssh O env DISPLAY=:0.0 dcop
>to get the standard dcop output.

THANK YOU! That worked like a charm!
Problem solved..
The only sure-fire way to determine the correct DISPLAY setting is to pull 
it from the X session you want to connect to. E.g.:
$ env | grep ^DISPLAY
DISPLAY=:0.0

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 3697 bytes --]