Thread: pgaccess failed, used to work

pgaccess failed, used to work

From
Eric Webber
Date:
pgaccess used to work fine, now I get this, I changed nothing,

have no idea why, anyone else see this.  only thing I did
was restart X. doesnt matter which user either

regards,
Eric streethockey@ureach.com

pgaccess &
[1] 19239
[root@gims X11]# Application initialization failed: couldn't connect to display "192.168.0.3"
Error in startup script: invalid command name "image"
    while executing
"image create bitmap dnarw -data  {
#define down_arrow_width 15
#define down_arrow_height 15
static char down_arrow_bits[] = {
        0x00,0x80,0x00,0x80,0x0..."
    (file "/usr/local/pgsql/share/pgaccess/main.tcl" line 5)



________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag

Re: pgaccess failed, used to work

From
Holger Marzen
Date:
On Wed, 13 Feb 2002, Eric Webber wrote:

> pgaccess used to work fine, now I get this, I changed nothing,
>
> have no idea why, anyone else see this.  only thing I did
> was restart X. doesnt matter which user either
>
> regards,
> Eric streethockey@ureach.com
>
> pgaccess &
> [1] 19239
> [root@gims X11]# Application initialization failed: couldn't connect to display "192.168.0.3"

Don't work as root!

It seems that you did a "su" or "telnet" to your local or another
machine and then started pgaccess. Either your DISPLAY variable isn't
correct (it should be something like 192.168.0.3:0 - ipaddress of the
machine where your X-server runs and a display number, eg 0 for the
first X-server) or you forgot to issue a "xhost +xxx" where xxx is the
name or the ip address of the machine running pgaccess.

It is no pgaccess problem. xclock won't work, either. I recommend using
ssh with enabled X11-forwarding, that does the job of setting DISPLAY
and permissions automagically.


--
PGP/GPG Key-ID:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xB5A1AFE1


Re: pgaccess failed, used to work

From
Holger Marzen
Date:
On 14 Feb 2002, tony wrote:

> On Thu, 2002-02-14 at 07:45, Holger Marzen wrote:
>
> > It seems that you did a "su" or "telnet" to your local or another
> > machine and then started pgaccess. Either your DISPLAY variable isn't
> > correct (it should be something like 192.168.0.3:0 - ipaddress of the
> > machine where your X-server runs and a display number, eg 0 for the
> > first X-server) or you forgot to issue a "xhost +xxx" where xxx is the
> > name or the ip address of the machine running pgaccess.
> >
> > It is no pgaccess problem. xclock won't work, either. I recommend using
> > ssh with enabled X11-forwarding, that does the job of setting DISPLAY
> > and permissions automagically.
>
> And via ssh? I can't ssh into the machine running pgaccess (port 22 on
> the router is forwared to my server) so I ssh into the server then into
> the workstation.
>
> Any clues on the DISPLAY variable to give for that???

It is usually done automagically. Be sure to turn X11 forwarding on, in
every ssh_config and every sshd_config.

--
PGP/GPG Key-ID:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xB5A1AFE1