This problem was the same as another problem reported elsewhere.
Quote:
From: Thomas Leonard
<http://groups.google.com/groups?hl=en&q=author:tal00r%40ecs.soton.ac.uk+>
([EMAIL PROTECTED] <mailto:tal00r%40ecs.soton.ac.uk>)
Subject: Bug#109344: gimp1.2: 'gimp-remote -n' often fails
Newsgroups: debian.bugs.dist
<http://groups.google.com/groups?hl=en&group=debian.bugs.dist>
View: (This is the only article in this thread) | Original Format
<http://groups.google.com/groups?selm=E15Ypze-0003bh-00%40everest.ecs.soton.ac.uk&output=gplain>
Date: 2001-08-20 07:45:18 PST
Package: gimp1.2
Version: 1.2.2-1
Severity: normal
When using 'gimp-remote -n FILE', when the gimp is not loaded, I often get
this error:
everest:~>gimp-remote -n Icon.xpm
Xlib: connection to ":0.0" refused by server
Xlib: *XDM **authorization **key **matches* an *existing **client*!
Gtk-WARNING **: cannot open display: :0
I think the problem is that gimp-remote connects to the X server and then
Gimp tries to connect with the same PID very soon afterwards. I've reported
this against the X server too, but a possible workaround might be to fork()
before running the new process (not tried).
>From what I see the error message pattern (randomly occuring and worse for faster
>machines),
I believe what Thomas described applies here.
Min
