* Jos van Kan [07-08-04 16:23]:

Op donderdag 8 juli 2004 22:37, schreef Patrick Shanahan:

...

* Jos van Kan [07-08-04 15:09]:

...

which is correct However, all lpq, lpc and lpr commands as well as print commands from KDE apps hang.

post results from: lpstat -a

lpstat -a hangs :-(

open Yast2 and delete the printer instance and reinstall the printer. Or do it with http://localhost:631/ but make sure that you have set your password for lp. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

* Stanley Long [07-08-04 22:54]:

Request for clarification: Do you mean that the User Name should be "lp"? ie, that the User entered into lppasswd should be "lp"?

No, you must have a <user-name> with a <password> in passwd.md5 belonging to cups or you cannot make/delete printers. read: man lppasswd

I chose to use my own username, as in /home/"username" for cups. Is that why the localhost:631 and YAST2 might not synchronize?

Not in my opinion. Another suggestion, that you restart cups, rccups restart, and try again, should also be attempted. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Op vrijdag 9 juli 2004 00:23, schreef Patrick Shanahan:

* Jos van Kan [07-08-04 16:23]:

...

Op donderdag 8 juli 2004 22:37, schreef Patrick Shanahan:

...

* Jos van Kan [07-08-04 15:09]:

...

which is correct However, all lpq, lpc and lpr commands as well as print commands from KDE apps hang.

post results from: lpstat -a

lpstat -a hangs :-(

open Yast2 and delete the printer instance and reinstall the printer.

Or do it with http://localhost:631/ but make sure that you have set your password for lp.

SOLVED! That is, the problem has been solved but the mystery has not. Yast hung in the printer section. So I set an lppassword for myself with lppasswd, and went to the above url. Nothing spectacular happened. Konq said "connection to localhost broken" and Firefox said nothing at all and just sat there. Nosing in /var/log/cups/error.log learned, that tcp_wrappers was not allowed from 127.0.0.1! "Look in /etc/hosts.allow and /etc/hosts.deny" it helpfully said. Ugh! Just shows you that it does not always pay to be a paranoiac. So after relaxing hosts.allow a bit the printer configuration screen duly showed up at localhost:631. Before deleting the printer I couldn't resist to try "Print Testpage". Now two miracles happened: 1. The testpage duly printed. You can't imagine how it feels to hear that humming sound again after a couple of days of mulish silence! 2. The ban on cups had been lifted. lp, lpq and lpstat all were in perfect working order again. I'm still wondering what could have caused this behaviour. A software lock? I looked around in /var/spool/cups and /var/log/cups but could find nothing remotely resembling a lock. (I suddenly realize it may have been hidden.) I did not try "rccupsd restart" because I already had rebooted (remember I tried to print in WXP find out whether it was a hardware error) and that hadn't helped either. Thanks all who participated and Patrick in particular. Best regards, -- Jos van Kan