Re: Problems with cups/printconf on Squeeze and Sid
On Sun, 21 Nov 2010 10:05:05 -0500, Wayne Topa wrote:
> On 11/21/2010 07:20 AM, Camaleón wrote:
>> Uh? That is not normal. You should be able to add/manage your printer
>> from web interface. What do logs say?
>>
>>
> Sorry, I forgot the log entries. After purging all of the cups packages
> as well as all of the dependices, and re-install of version 1.4.4-3, the
> problem remains. The log is interesting.
>
> /var/log/cups/error_log
>
> W [21/Nov/2010:09:14:17 -0500] [CGI] Missing Product in
> /usr/share/ppd/hp-ppd/HP/HP_DeskJet_630C.ppd!
That seems just a (W)arning message.
> E [21/Nov/2010:09:17:53
> -0500] PID 355 (/usr/lib/cups/cgi-bin/printers.cgi) crashed on signal 6!
> E [21/Nov/2010:09:18:24 -0500] PID 662 (/usr/lib/cups/cgi-bin/admin.cgi)
> crashed on signal 6!
> E [21/Nov/2010:09:21:04 -0500] Unable to bind socket for address ::1:631
> - Cannot assign requested address.
Those entries are more serious (E)rrors and for me worth for bug
reporting because Cups is just crashing :-/
> BTW I am trying to get an HP Laser HP-6P installed, not a "Deskjet"
>
> Odd that I can connect to localhost:631, the cups home page OK though. I
> then upgraded to the sid version 1.4.4-7 and the error_log shows
>
> Unable to bind socket for address ::1:631 - Cannot assign requested
> address. PID 21560 (/usr/lib/cups/cgi-bin/admin.cgi) crashed on signal
> 6!
I would not install the sid version while running squeeze, unless
explicitly recommended.
> Cups has not worked on this AMD64 system for over a year and if I recall
> correctly, this error is the what made me set up the 686 system as the
> print server.
And why not reporting the error? A year is so much time for leaving Cups
crashing without reporting the bug. Printing facility is a must in any
system.
> This box, squeeze partition, is updated 3-4 times a week and the sid
> partition at least once a week. They both have the same problem.
>
> Strange.....
Yep, strange. I have squeeze (32 bits) installed and cups works fine.
>> Also, have you tried with "lpadmin"? Is the command line utility for
>> managing printers in Cups.
>
> lpadmin : cannot connect to server
Wow... but expected if Grub is in the state you have reported.
Greetings,
--
Camaleón
Reply to: