Re: [SOLVED]Re: Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
On 10/05/2011 12:37 AM, Whit Hansell wrote: On 09/13/2011 07:51 AM, Gilbert Sullivan wrote: On 09/12/2011 06:36 PM, Whit Hansell wrote: I'm using Wheezy too and had the same problem w. getting a black page in the browser but it printing ok elsewhere. Now, after today's upgrade, I no longer get a black page. I get nothing. It won't print. I send the job and wait and nothing. I have to clear the print jobs but I have to disable and then enable the printer again to do that. I can however, print a printer friendly page in the browser. And I can print graphics when I right clik on the pic and do a view image, then it opens w. only the picture and that prints fine. Yes, I'm used to breakage, and don't generally mind it. But this one is such an unusual case. I usually see all of these testing systems react in the same manner when an upgrade breaks something. But this time the older installations are fine while the new ones are affected. It used to be that every CUPS upgrade would break this particular printer on every system, and all I had to do was to remove the printer and re-install it with the hp-setup script. there is a glitch somewhere in Cups or foo or something. They will get it figured out but it might take a few more days. That's the fun of Wheezy(testing). Stuff is upgraded and gets broken but in a short period of time they find the problem and fix it. That's why they tell us not to use Wheezy for production, but to stay w. stable. I've used testing since sarge mostly and have gotten used to the intermittent broken parts. I just found out that Cheese is fixed now again. It's always one thing or another but we are on the bleeding edge as they say. Just wait a few days. It'll get fixed. Regards, Whit I'm just hoping that the something in CUPS or FOOMATIC that is causing this is actually going to get fixed. If it's a change they needed to make for an important reason, and if it only broke a few oddball printers, then the driver for this printer might have to be re-written. And, IME, that usually takes a while and sometimes doesn't get done at all if there isn't enough demand for it. And I love using testing for production -- but only for me and a few others who are willing to use a work-around or two when something goes south. Thank you, Whit, for confirming that I'm not alone with this problem. Have a good one! Thanks Gilbert. Thot' I'd let you know yesterday's upgrade in Wheezy fixed my Cups problem w. MY printer(printed black page-major ink waster). An HP PSC 1500 Series AIO. Hope it fixed yours too. Regards. Whit Hi, thanks for your note on this. Unfortunately, the HP OfficeJet 6310 is still printing all-black, but only from specific types of Web pages. I use a package called Zim which has no ability to print on its own. Instead, it prints to browser, and then I print from browser to printer. It happens no matter which browser I use (Iceweasel, Midori, Chromium, Epiphany). This is the ONLY printer (out of five) which has this problem, but it happens to be the one that's most convenient to use and which has color output. I think some change in CUPS has broken this particular printer driver. Unfortunately, since it is a multi-function device, I have to install it using the hp-setup script, and that doesn't give me a choice of testing other drivers -- unless I can find one in the repositories. (My problem is partially attitude. I have made a point of not using anything from outside the main testing repository -- not even anything from contrib or non-free.) I'm glad to hear that your issue is fixed. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e8da485.8070...@comcast.net
[SOLVED]Re: Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
On 09/13/2011 07:51 AM, Gilbert Sullivan wrote: On 09/12/2011 06:36 PM, Whit Hansell wrote: I'm using Wheezy too and had the same problem w. getting a black page in the browser but it printing ok elsewhere. Now, after today's upgrade, I no longer get a black page. I get nothing. It won't print. I send the job and wait and nothing. I have to clear the print jobs but I have to disable and then enable the printer again to do that. I can however, print a printer friendly page in the browser. And I can print graphics when I right clik on the pic and do a view image, then it opens w. only the picture and that prints fine. Yes, I'm used to breakage, and don't generally mind it. But this one is such an unusual case. I usually see all of these testing systems react in the same manner when an upgrade breaks something. But this time the older installations are fine while the new ones are affected. It used to be that every CUPS upgrade would break this particular printer on every system, and all I had to do was to remove the printer and re-install it with the hp-setup script. there is a glitch somewhere in Cups or foo or something. They will get it figured out but it might take a few more days. That's the fun of Wheezy(testing). Stuff is upgraded and gets broken but in a short period of time they find the problem and fix it. That's why they tell us not to use Wheezy for production, but to stay w. stable. I've used testing since sarge mostly and have gotten used to the intermittent broken parts. I just found out that Cheese is fixed now again. It's always one thing or another but we are on the bleeding edge as they say. Just wait a few days. It'll get fixed. Regards, Whit I'm just hoping that the something in CUPS or FOOMATIC that is causing this is actually going to get fixed. If it's a change they needed to make for an important reason, and if it only broke a few oddball printers, then the driver for this printer might have to be re-written. And, IME, that usually takes a while and sometimes doesn't get done at all if there isn't enough demand for it. And I love using testing for production -- but only for me and a few others who are willing to use a work-around or two when something goes south. Thank you, Whit, for confirming that I'm not alone with this problem. Have a good one! Thanks Gilbert. Thot' I'd let you know yesterday's upgrade in Wheezy fixed my Cups problem w. MY printer(printed black page-major ink waster). An HP PSC 1500 Series AIO. Hope it fixed yours too. Regards. Whit -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e8bdefb.7030...@comcast.net
Re: Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
On 09/12/2011 06:36 PM, Whit Hansell wrote: I'm using Wheezy too and had the same problem w. getting a black page in the browser but it printing ok elsewhere. Now, after today's upgrade, I no longer get a black page. I get nothing. It won't print. I send the job and wait and nothing. I have to clear the print jobs but I have to disable and then enable the printer again to do that. I can however, print a printer friendly page in the browser. And I can print graphics when I right clik on the pic and do a view image, then it opens w. only the picture and that prints fine. Yes, I'm used to breakage, and don't generally mind it. But this one is such an unusual case. I usually see all of these testing systems react in the same manner when an upgrade breaks something. But this time the older installations are fine while the new ones are affected. It used to be that every CUPS upgrade would break this particular printer on every system, and all I had to do was to remove the printer and re-install it with the hp-setup script. there is a glitch somewhere in Cups or foo or something. They will get it figured out but it might take a few more days. That's the fun of Wheezy(testing). Stuff is upgraded and gets broken but in a short period of time they find the problem and fix it. That's why they tell us not to use Wheezy for production, but to stay w. stable. I've used testing since sarge mostly and have gotten used to the intermittent broken parts. I just found out that Cheese is fixed now again. It's always one thing or another but we are on the bleeding edge as they say. Just wait a few days. It'll get fixed. Regards, Whit I'm just hoping that the something in CUPS or FOOMATIC that is causing this is actually going to get fixed. If it's a change they needed to make for an important reason, and if it only broke a few oddball printers, then the driver for this printer might have to be re-written. And, IME, that usually takes a while and sometimes doesn't get done at all if there isn't enough demand for it. And I love using testing for production -- but only for me and a few others who are willing to use a work-around or two when something goes south. Thank you, Whit, for confirming that I'm not alone with this problem. Have a good one! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6f43c8.2030...@comcast.net
Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
Hi, I'm reluctant to even bring this up because it's so darned weird. I've got an HP OfficeJet 6310 (multi-function network device: printer, fax, scanner) that has worked flawlessly for a couple of years under Debian stable and testing. I don't make use of the fax function, but both printer and scanner have just worked after I install the printer using the hp-setup script in interactive mode. Then, recently on my Debian testing systems, there were some apparent hassles between foomatic and CUPS upgrades. Everything is back to normal after a couple of rounds of upgrades -- except for the fact that this one printer now only prints a wall of black when printing from a browser -- ANY browser. (iceweasel, midori, chromium) The scanner function works fine. All other printers work fine. All other apps print fine to this printer. But if I try to print to this particular printer *directly from* a browser, all I get is a page full of black ink. And here's the best part. If I print to file from a browser to create a PDF, and then open the PDF and print it to this printer -- that get's me a wall of black, too. (The PDF looks fine in the viewer, but it prints out all black.) But all other PDFs print out on this printer just fine. I can also copy contents of a Web page and paste them into LibreOffice Writer document, and that prints out fine -- other than the expected monkeying around with the page / text format. Is this weird, or what? I've removed the printer, purged its drivers and setup, re-installed. Nothing fixes it. I've also tried using the CUPS Web interface to modify the printer by assigning a different driver to it. I wanted to see if maybe a postscript driver would fare better. But the only OfficeJet 6300 printer driver listed in the CUPS interface now is hpcups 3.11.5. I think there used to be a slew of choices. Now only 1. And it doesn't work properly. I don't even know what to make a bug report on. There are other Debian testing systems on the network that seem print just fine to this printer. They've had the same upgrades, but they're older installations of testing. (The two computers that are doing messed up printing are from a daily build image from mid-August.) I've found other irregularities with these recent installations. I wonder if d-i did something funny to the system configuration on these two computers during installation that is causing this behavior. These two computers use Xfce and had XDM set as their default DM by the installer. (GDM had just become obsolete when this daily build was produced.) I cannot for the life of me figure this out. Can anyone suggest a way I can get this printer to work properly with browsers again? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e3bfa.8070...@comcast.net
Re: Recent Changes in CUPS and Foomatic Causing All-Black Printing from Browsers?
On 09/12/2011 01:06 PM, Gilbert Sullivan wrote: Hi, I'm reluctant to even bring this up because it's so darned weird. I've got an HP OfficeJet 6310 (multi-function network device: printer, fax, scanner) that has worked flawlessly for a couple of years under Debian stable and testing. I don't make use of the fax function, but both printer and scanner have just worked after I install the printer using the hp-setup script in interactive mode. Then, recently on my Debian testing systems, there were some apparent hassles between foomatic and CUPS upgrades. Everything is back to normal after a couple of rounds of upgrades -- except for the fact that this one printer now only prints a wall of black when printing from a browser -- ANY browser. (iceweasel, midori, chromium) The scanner function works fine. All other printers work fine. All other apps print fine to this printer. But if I try to print to this particular printer *directly from* a browser, all I get is a page full of black ink. And here's the best part. If I print to file from a browser to create a PDF, and then open the PDF and print it to this printer -- that get's me a wall of black, too. (The PDF looks fine in the viewer, but it prints out all black.) But all other PDFs print out on this printer just fine. I can also copy contents of a Web page and paste them into LibreOffice Writer document, and that prints out fine -- other than the expected monkeying around with the page / text format. Is this weird, or what? I've removed the printer, purged its drivers and setup, re-installed. Nothing fixes it. I've also tried using the CUPS Web interface to modify the printer by assigning a different driver to it. I wanted to see if maybe a postscript driver would fare better. But the only OfficeJet 6300 printer driver listed in the CUPS interface now is hpcups 3.11.5. I think there used to be a slew of choices. Now only 1. And it doesn't work properly. I don't even know what to make a bug report on. There are other Debian testing systems on the network that seem print just fine to this printer. They've had the same upgrades, but they're older installations of testing. (The two computers that are doing messed up printing are from a daily build image from mid-August.) I've found other irregularities with these recent installations. I wonder if d-i did something funny to the system configuration on these two computers during installation that is causing this behavior. These two computers use Xfce and had XDM set as their default DM by the installer. (GDM had just become obsolete when this daily build was produced.) I cannot for the life of me figure this out. Can anyone suggest a way I can get this printer to work properly with browsers again? Hey Gilbert, I'm using Wheezy too and had the same problem w. getting a black page in the browser but it printing ok elsewhere. Now, after today's upgrade, I no longer get a black page. I get nothing. It won't print. I send the job and wait and nothing. I have to clear the print jobs but I have to disable and then enable the printer again to do that. I can however, print a printer friendly page in the browser. And I can print graphics when I right clik on the pic and do a view image, then it opens w. only the picture and that prints fine. there is a glitch somewhere in Cups or foo or something. They will get it figured out but it might take a few more days. That's the fun of Wheezy(testing). Stuff is upgraded and gets broken but in a short period of time they find the problem and fix it. That's why they tell us not to use Wheezy for production, but to stay w. stable. I've used testing since sarge mostly and have gotten used to the intermittent broken parts. I just found out that Cheese is fixed now again. It's always one thing or another but we are on the bleeding edge as they say. Just wait a few days. It'll get fixed. Regards, Whit -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e6e8973.9030...@comcast.net
