On Thu, 2006-06-08 at 17:42 +0200, Uwe Storbeck wrote: > On Jun 08, Drew Parsons wrote: > > Can you check a few things? > > I have to say I don't know much about xprint, the somewhat strange > printer names (...@:64) "magically" appeared in mozilla and printing > simply works, up to now ... > > > - is XPSERVERLIST still defined? (check with "echo $XPSERVERLIST" for > > instance) > > Where should this be defined? In the user environment? It is not defined > for the old package.
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? > Supplement: I'm not able to reinstall the new ones, see below. > > > - does "xplsprinters" return anything? > > old version: > $ xplsprinters > xplsprinters: no printers found for printer spec "". > $ /etc/init.d/xprint get_xpserverlist > :64 > $ export XPSERVERLIST=':64' > $ xplsprinters > printer: xlp@:64 > printer: us@:64 > printer: lp@:64 > printer: hplj@:64 > printer: color@:64 > printer: xp_ps_spooldir_HOME_Xprintjobs@:64 > printer: xp_pdf_spooldir_HOME_Xprintjobs@:64 Yes, that means XPSERVERLIST was not set automatically for some reason. Once the rest of your X system is stabilised we'll check if it gets set when you restart X, which is what it should be doing. > > My suspicion is that you're caught in the middle of the X11R7 > > transition, which has only just hot testing this week. > > I know, never had such a lot of trouble with an update, breaking lots > of things. And some of my debian systems are running for more than > 10 years, always maintained by apt-get update/dist-upgrade over the > years and debian versions, never reinstalled. :( We're working on it... > > My guess is that > > you got the new xprint but are missing some of the new libraries, so > > Xprt is crashing at start up. This particularly seems likely since if > > you now have a full X11R7 system then you should have trouble running > > the old version of xprint. Since the old one still works normally, > > you're probably only part way through the transition. > > Shouldn't xprint depend on those libraries in this case? > It does. But you demonstrated above the problem is simply with XPSERVERLIST. Once it's set your printers are back again working fine. > > If this is the > > case then your problem should disappear over the next few days as you > > pick up the entire X11R7 system. > > I doubt about this, at the moment the nvidia-kernel-modules are missing, > even in unstable. So I cannot install the Xorg 7.0 server, most likely > for a longer time :-(. I'm starting to downgrade the X11 packages and > set them on hold. > > I more and more assume this bug is caused by an apt problem. I'm not > able to reinstall the new xprint packages by now: > > xprint-common Version: 1:1.0.2-1 Depends: x11-common (>= 1:7.0.12) > x11-common Version: 1:7.0.20 Conflicts: xserver-xorg (<< 1:7.0.12) Yes, that's what I expected, I was surprised when you said you could reinstall the old ones. You need to downgrade x11-common in particular to get back to all the old X packages. > I am stucked with xserver-xorg 6.9, so the new xprint packages never > should have been installable on my system. Not precisely. xprint needs X libraries, but does not need xserver-xorg itself. > So you may close this bug, as it probably disappears if xprint is > installed with the correct dependencies. > > Sorry for the trouble, No trouble, I'm sorry for the inconvenience. Let's check again in say a week's time, by which time your mirrors should be fully loaded with the new packages. 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. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
