Re: MIT-SCREENT-SAVER
I'll try it, I can't right now since I won't be at school till tommorow.
And for your information I was on IRIX at school connecting with xterm
via ssh to my home linux/debian box and ssh sets the DISPLAY variable
stuff for me.
I tried running licq the same way on my friends machine and I did not
get those messages. Also, I use WindoMaker and I use potato with all
new packages.
Thanks
Ramiel Givergis, webmaster@relm.net, http://www.relm.net
--------------------------~~~===<[^]>===~~~------------------------------
This mail is a natural product. The slight variations in spelling and
grammar enhance its individual character and beauty and in no way are to
be considered flaws or defects.
On Tue, 16 Mar 1999, Noah L. Meyerhans wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Tue, 16 Mar 1999, Branden Robinson wrote:
>
> > On Tue, Mar 16, 1999 at 10:16:13AM -0800, Ramiel Givergis wrote:
> > > When I use ssh and run licq remotly I keep getting
> > > Xlib: extension "MIT-SCREEN-SAVER" missing on display "host:10.0".
> >
> > That's bizarre. I think that means something on the remote end is trying
> > to start a screen saver on your local hardware.
>
> No, it's just looking for the screen saver extension (definied in libXext
> as I recall). What X server are you running on your machine? When you
> log in to the remote machine, do you set your DISPLAY variable yourself,
> or do you let ssh set it up for you? (The error message indicates that
> it's the latter.) I suspect this is actually a problem with ssh's X11
> forwarding.
> Try setting the DISPLAY variable yourself when you log in. If you're in
> the bash shell, run 'export DISPLAY="<your hostname>:0"'. On your local
> machine, you'll now need to explicitly give the remote host access to your
> X server. Run 'xhost <remote machine>' on your local machine. Now try
> running licq and see what happens.
>
> > That could be a bug in licq. I have no idea why licq would have anything
> > to do with a screen saver, though.
> >
>
> I'd say it's highly unlikely that it's a bug in licq. Most likely it's
> got to do with ssh. Less likely it has something to do with the version
> of Xlib that licq has been linked with...
>
> noah
>
> PGP public key available at
> http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html
> or by 'finger -l frodo@ccs.neu.edu'
>
> This message was composed in a 100% Microsoft free environment.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBNu7LLodCcpBjGWoFAQHOawP/eLrdqC8Jl4fGxn7vDiBalNTMDnX0sMBc
> yJRjpP1Ys2xOwesMwRdHrJLMAcui7LgmWGuRVQSBGuJY9EVF9bkrBXsToNNek7oS
> e95kVz3d4cVgI65SUBvPogZH4oFcbeBmVRILfM6PU4Dlnn/jenEImmZcWpgKPX58
> 8xwWEoiSip4=
> =MeNZ
> -----END PGP SIGNATURE-----
>
Reply to: