Stop in /usr/ports/editors/staroffice52.

Matthew Seaman m.seaman at
Mon Jan 27 12:29:03 GMT 2003

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 27, 2003 at 12:00:33PM +0000, Dimitris wrote:
> On Mon, 27 Jan 2003 11:55:40 +0000 Steve Purkis <steve at> w=
> > /usr/ports/editors/staroffice52/work/office52/
n: cannot connect to X server :0.0
> > *** Error code 255
> If i remember correctly, the SO installation must be run under X (its a g=
raphical installer).
> Maybe you are running it in a shell, thus it can't connect to X.
> In case you ARE running it under X, then the problem must
> be something else... :P

If you run the StarOffice install su'd to root you won't necessarily
be able to open windows on your desktop. X defaults to locking out all
other users, even root. Try:

    xhost +local:

before you su, which will permit any user locally on your machine to
open up windows on your desktop.  Or indeed, because of the way ssh
poses as an X server if you use it to tunnel remote X sessions, it
will allow any user that you su to or login as on a remote machine
reached by ssh to open windows on your desktop.

If that level of control is too imprecise for you, you can use:

    % xauth extract /tmp/foo :0.0
    % su
    # xauth merge /tmp/foo

which copies your .Xsession credentials for your session on the local
display to /root/.Xsession, thus allowing root access to your desktop.



Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP:         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.1 (FreeBSD)



More information about the Ukfreebsd mailing list