On Fri, 2006-06-09 at 14:13 +0200, Uwe Storbeck wrote:
> On Jun 09, Drew Parsons wrote:
>
> > Yes, in the user environment. It should have be set for the old
> > package, it's automatically set
> > in /etc/X11/Xsession.d/92xprint-xpserverlist when X is started by gdm or
> > suchlike. How are you starting X? Maybe your setup has been bypassing
> > it?
>
> That's probably because I start my X server the "old" way, i.e. from
> a console with startx.
OK now we're getting somewhere :)
> > The key to your problem is XPSERVERLIST. We need to work out why it
> > hasn't been set. It should have been set under the old X, nothing's
> > changed in the new X as far as it's concerned.
>
> The environment variable seems not to be necessary with the old xprint
> version. Mozilla also has the printer information without XPSERVERLIST.
It's a bit more subtle than that. Have a look in the mozilla code (the
script which launches the binary) - you'll see that mozilla defines
XPSERVERLIST, if it hasn't already been done.
Check /usr/bin/mozilla-suite and find
if [ -z "$XPSERVERLIST" ]; then
if [ -x /etc/init.d/xprint ]; then
XPSERVERLIST=$( /etc/init.d/xprint get_xpserverlist)
export XPSERVERLIST
Next, check what happens if you run /etc/init.d/xprint get_xpserverlist
by hand. By this code, mozilla should always have access to the
printers. Are you sure it's still not working? This behaviour should
not change between old and new Xprints, and you've already checked the
new Xprint server is indeed running when you set XPSERVERLIST by hand.
Did you try closing mozilla and starting it up again to reset its value
of XPSERVERLIST.
> And btw, I don't really like the idea of yet another required
> environment variable much ... ;-)
Yeah, it's a bit of a flaw in the Xprint implementation. Sort of
designed that way upstream, and I'm a bit loathe to go against what
upstream has done. But I'll change it if I can think of a properly
reliable of doing so, but I'm not sure I can. It's sort of up to the
clients, not up to Xprint, to check if an Xprint server is available,
and I can't really change all the clients. XPSERVERLIST is designed as
the common way to inform all clients where it is. The alternative would
be to mandate a specific screen (on Debian we use :64) which always
belongs to Xprint, just as CUPS belongs to port 631.
Drew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
