On Wed, Nov 22, 2006 at 03:02:11PM +0100, Dr. Edgar Alwers wrote: > Hi Ken, > > On Wednesday 22 November 2006 12:57, Ken Moffat wrote: > > > I'm pretty sure your cups *isn't* 2.6.7, so please check which > > version it really is. > Sorry, Typo. It is 1.2.7
Blimey, they're releasing quickly these days. > > > What do you mean by 'the tests local are all OK' ? > Print Test Page from http://localhost:631/printers is OK. The same from > KDE->control Center->Peripherals->printers->instances->test. but in this last > case, I only see the printer pointing the "print system currently used" to > LPR/LPRng Print System, as pointing to cups does not show the printer. > > > > For me, cups-1.2.2 (and kde-3.5.5) seem to work fine. > > behaviour: > A is the client, B the server. B is running with KDE 3.5.2 with cups 1.2.7, > kernel 2.6.18. LAN connection, no routers in between, no firewalls. > > If A runs under the old system BLFS 6.1, KDE 3.4.0 and cups 1.1.23, A see > the > printer list and prints remote > > If A is running under the new BLFS svn 20061028, KDE 3.5.2 and cups 1.2.7, A > does not see the printer list and consequently cannot print. > > B see the printer list _only_ under LPR/LPRng but prints than nice > Possibly, configuration issues on both A and B. I don't run cups on a server (I attach the printer to my chosen desktop machine) so I can't really advise about the client. For A running the new system it might be an error in authorisation (it was tightened up for 1.2), but I think you need to concentrate on the server until it can see its own printer. > > > > Anything in the cups log ? > mhmm.. It says "Listening to 0.0.0.0:631 on fd 0... > Unable to open listen socket for address :::631 - Address family not > supported > by protocol. > Does this tell you anything ? > Edgar > No. I'm back on x86, with cups 1.2.2 and my error_log shows I [22/Nov/2006:15:54:07 +0000] Listening to 0:631 - note that the format of where it is listening has changed, perhaps the code itself has altered. If you haven't already done so, check the README and any other docs in the tarball. OTOH, maybe it always shows 0:0:0:0 in full if an error happens. The error message perhaps indicates an error in /etc/hosts (for localhost) or even in cupsd.conf, might be worth double checking those on the server. If you also have an old build of the server, you could compare the contents of cupsd.conf. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
