Re: Re: Printing stopped working on Debian testing
> On 7/3/06, Chris Lale <[EMAIL PROTECTED]> wrote: > > Joshua McGee wrote: > > > Printing stopped working overnight on Debian testing, > > [ ... ] > > > > > > > > > > > May be a result of an upgrade. There is a bug report at > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351668 > > > > Check that eg lp0 exists in /dev. If not > > > > # modprobe lp > > > > If this works, add lp to /etc/modules to ensure it is loaded at next > reboot. > > > > Hth, > > Chris. > > Paul Mills: > > Changes list indicates a number of configuration changes. In my case, > > the easiest thing to do was to purge cupsys, then reinstall. Then all > > was OK. > > Thanks, I was able to get it to work by following Chris' advice, then > purging cupsys, reinstalling, then reinstalling printconf, which found > my printer. I can now print to the queue created by printconf. > Maybe some of the suggestion in a thread I sarted "/dev/lp0 rights and CUPS" might have helped. I had to add lp to /etc/modules and mess with the rights of /dev/lp0 in udev to get it working. All this purging reinstalling stuff reminds me of how I "solve" problems in Windows. Ugh. This printing/udev bug has been a really anoying experience for me, especially since no one seems to have really gotten to the bottom of it. Chris -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Printing stopped working on Debian testing
On 7/3/06, Chris Lale <[EMAIL PROTECTED]> wrote: Joshua McGee wrote: > Printing stopped working overnight on Debian testing, [ ... ] > > > May be a result of an upgrade. There is a bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351668 Check that eg lp0 exists in /dev. If not # modprobe lp If this works, add lp to /etc/modules to ensure it is loaded at next reboot. Hth, Chris. Paul Mills: Changes list indicates a number of configuration changes. In my case, the easiest thing to do was to purge cupsys, then reinstall. Then all was OK. Thanks, I was able to get it to work by following Chris' advice, then purging cupsys, reinstalling, then reinstalling printconf, which found my printer. I can now print to the queue created by printconf. - Josh http://www.mcgees.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Printing stopped working on Debian testing
Joshua McGee wrote: Printing stopped working overnight on Debian testing, [ ... ] May be a result of an upgrade. There is a bug report at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351668 Check that eg lp0 exists in /dev. If not # modprobe lp If this works, add lp to /etc/modules to ensure it is loaded at next reboot. Hth, Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Printing stopped working on Debian testing
Joshua McGee wrote: Printing stopped working overnight on Debian testing, possibly due to cron-apt running. I tried to remove and reinstall, and I am facing the following messages: /// www:~# apt-get install cupsys Reading package lists... Done Building dependency tree... Done cupsys is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 2 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up cupsys (1.2.1-2) ... Starting Common Unix Printing System: cupsdcupsd: Child exited with status 1! invoke-rc.d: initscript cupsys, action "start" failed. dpkg: error processing cupsys (--configure): subprocess post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of printconf: printconf depends on cupsys; however: Package cupsys is not configured yet. dpkg: error processing printconf (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: cupsys printconf E: Sub-process /usr/bin/dpkg returned an error code (1) /// /var/log/cups/error_log: I [29/Jun/2006:18:33:19 -0700] Listening to :::631 (IPv6) I [29/Jun/2006:18:33:19 -0700] Listening to 0.0.0.0:631 (IPv4) E [29/Jun/2006:18:33:19 -0700] Hostname lookup for "x.y.z.255" failed! E [29/Jun/2006:18:33:19 -0700] Bad BrowseAddress x.y.z.255 at line 531. E [29/Jun/2006:18:33:19 -0700] Bad netmask value 192.168.123.* on line 772. E [29/Jun/2006:18:33:19 -0700] Unknown Location directive Allow on line 772. I've looked at cupsd.conf, and to my untrained eyes lines 531 and 772 look valid, as everything is within the 192.168.123.255 netmask: 531: BrowseAddress x.y.z.255 772 with context: Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 192.168.123.* Can someone give me a pointer? Changes list indicates a number of configuration changes. In my case, the easiest thing to do was to purge cupsys, then reinstall. Then all was OK. Paul begin:vcard fn:W Paul Mills n:Mills;W Paul org:The Mills Chaos In The USA adr:;;USA email;internet:[EMAIL PROTECTED] note:Hint: remove -NOT x-mozilla-html:FALSE url:http://Mills-USA.com version:2.1 end:vcard
