On 7/7/06, Kevin O'Gorman <[EMAIL PROTECTED]> wrote:
Yesterday, I emerged cups 1.2.1-r2. Now I cannot print at all.I use KDE, and the configuration tools cannot make a connection. Even bare-bones init stuff doesn't work right: /etc/init.d/cupsd stop says it stopped the server, but /etc/init.d/cupsd start WARNING: "cupsd" has already been started but 'ps' show that it has NOT been started. lpstat -t shows confusing info about my printer: treat init.d # lpstat -t scheduler is running system default destination: lp0 device for lp0: parallel:/dev/lp0 device for lp0: /dev/null lp0 not accepting requests since Fri Jul 7 14:23:34 2006 - Paused lp0 accepting requests since Fri Jul 7 14:15:50 2006 printer lp0 disabled since Fri Jul 7 14:23:34 2006 - Paused printer lp0 is idle. enabled since Fri Jul 7 14:15:50 2006 lp0-2458 root 14336 Fri Jul 7 14:21:24 2006 lp0-2459 root 14336 Fri Jul 7 14:55:25 2006 treat init.d # SO: is it enabled or not? I guess I'll submit a bug, but I'd like to know if it's best to go back to cups-1.1.23-r7, which I had before, and for which I have a binary package. ++ kevin
I spoke too soon, it seems. I was able to get it printing, using the commands cupsenable(8) and accept(8), and with some minimal tweaking of the printers config file. However, it still will not talk to the KDE admin tools, and I have not been able to get it back to being my print server for my wife's WinXP box (using lpd services, not samba). Any help out there? ++ kevin -- Kevin O'Gorman, PhD -- [email protected] mailing list
