Re: printing problem, markdown files
On 2/1/24 15:31, Dan Ritter wrote: gene heskett wrote: On 2/1/24 12:24, Dan Ritter wrote: gene heskett wrote: pandoc -f markdown FILEIN.md -t pdf -o FILEOUT.pdf will turn markdown into PDF, which you can probably print, if by no other means than FTP to the printer itself. (Try it, Brothers come with this by default.) Thanks DSR. Scanning thru the docs I don't see anything that looks like what the print job shops of the last century called a "binding ditch". That is where the output file has say a 15mm blank space inserted on the left edge of odd numbered pages, while that same 15mm of blank space is inserted to the right of the text on even pages, leave a blank area to perfect bind the duplex pages w/o burying the text into the center crack of the opened pages. Have they adopted a new name for this? Printers (the people) still call it that. You will also want to install latex ( apt install texlive-extra-utils will get you what you need) pandoc options: -V geometry:margin=1in (all four sides) -V geometry:left=3cm,right=3cm,top=2cm,bottom=2cm (separate values for each side) and finally, what you probably want: -V geometry:twoside,left=15mm,right=30mm,top=2cm,bottom=3cm I just tested that and it did a pretty nice job. My actual command: pandoc -f markdown -t pdf -V geometry:twoside,left=15mm,right=30mm,top=2cm,bottom=3cm test.md -o foo.pdf -dsr- Downright tasty stuff, thank you dsr. . Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: printing problem, markdown files
gene heskett wrote: > On 2/1/24 12:24, Dan Ritter wrote: > > gene heskett wrote: > > pandoc -f markdown FILEIN.md -t pdf -o FILEOUT.pdf > > > > will turn markdown into PDF, which you can probably print, if by > > no other means than FTP to the printer itself. (Try it, Brothers > > come with this by default.) > > > > Thanks DSR. > > Scanning thru the docs I don't see anything that looks like what the print > job shops of the last century called a "binding ditch". That is where the > output file has say a 15mm blank space inserted on the left edge of odd > numbered pages, while that same 15mm of blank space is inserted to the right > of the text on even pages, leave a blank area to perfect bind the duplex > pages w/o burying the text into the center crack of the opened pages. Have > they adopted a new name for this? Printers (the people) still call it that. You will also want to install latex ( apt install texlive-extra-utils will get you what you need) pandoc options: -V geometry:margin=1in (all four sides) -V geometry:left=3cm,right=3cm,top=2cm,bottom=2cm (separate values for each side) and finally, what you probably want: -V geometry:twoside,left=15mm,right=30mm,top=2cm,bottom=3cm I just tested that and it did a pretty nice job. My actual command: pandoc -f markdown -t pdf -V geometry:twoside,left=15mm,right=30mm,top=2cm,bottom=3cm test.md -o foo.pdf -dsr-
Re: printing problem, markdown files
On 2/1/24 12:24, Dan Ritter wrote: gene heskett wrote: debian bookworm everting updated earlier this morning. I have an about 125 page .md file I need hardcopy of. If you don't have pandoc installed: sudo apt install pandoc then: pandoc -f markdown FILEIN.md -t pdf -o FILEOUT.pdf will turn markdown into PDF, which you can probably print, if by no other means than FTP to the printer itself. (Try it, Brothers come with this by default.) pandoc will translate all sorts of formats into many other formats; if you don't want PDF, HTML, docx, rtf and even epub are available. -dsr- Thanks DSR. Scanning thru the docs I don't see anything that looks like what the print job shops of the last century called a "binding ditch". That is where the output file has say a 15mm blank space inserted on the left edge of odd numbered pages, while that same 15mm of blank space is inserted to the right of the text on even pages, leave a blank area to perfect bind the duplex pages w/o burying the text into the center crack of the opened pages. Have they adopted a new name for this? Take care, stay well Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: printing problem, markdown files
* 2024-02-01 11:57:50-0500, gene heskett wrote: > I have an about 125 page .md file I need hardcopy of. Maybe install "okular" and "okular-extra-backends" which includes markdown backend. Open your .md file in Okular which then renders it nicely. Print. -- /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ // OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462 signature.asc Description: PGP signature
Re: printing problem, markdown files
gene heskett wrote: > debian bookworm everting updated earlier this morning. > > I have an about 125 page .md file I need hardcopy of. If you don't have pandoc installed: sudo apt install pandoc then: pandoc -f markdown FILEIN.md -t pdf -o FILEOUT.pdf will turn markdown into PDF, which you can probably print, if by no other means than FTP to the printer itself. (Try it, Brothers come with this by default.) pandoc will translate all sorts of formats into many other formats; if you don't want PDF, HTML, docx, rtf and even epub are available. -dsr-
printing problem, markdown files
debian bookworm everting updated earlier this morning. I have an about 125 page .md file I need hardcopy of. I have loaded into geany which recognizes it as an .md file but it had so 300 char lines so I've gone thru it and reformmated the long lines to a max of 72 chars. 1: Unfortunately, both printers now suddenly have no left borders so there's no "binding ditch" when printed duplex, no room for 3 hole punching the printout. So I had geany print the line numbers which will use up some damageable space used by the hole puncher. 2. I have also lost the top border, so a 90% shrink to assure the printer does not line wrap, no longer centers it on the page, a 2nd rather revolting development. 3. I am supposedly using brothers drivers (cups_browsed is not installed) which can make both printers do everything they can do. Those are NOT $49 walmart specials, but $130 and $750 printers that can and have done flawlees book length++ printouts in the past. htop says I am using the brother drivers, but I recall the print manager that pops up when you click on any editors print menu having those features until fairly recently, but that popup menu no longer has an options tab used to set that stuff. Does anyone know of a fix? Thanks for any help Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: Printing problem (was snapshot.debian.org)
On Mon 6 Jun 2022, at 20:03, Gareth Evans wrote: > On Mon 6 Jun 2022, at 17:45, Gareth Evans wrote: >> Recent message with screenshots didn't get through (at least yet) - >> text below, plus another observation. >> >> On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote: >>> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI >>> wrote: On 06/06/2022 10:48, Gareth Evans wrote: > Not sure what's happened though as it worked perfectly with both > auto-detected and manually-added printer profiles from Bullseye until a > week or two ago. My logs suggest no update to system-config-printer. I > did change the printer's hostname (on printer console) but both the > printer and laptop have been restarted several times since then, printers > re-added and re-auto-detected etc. In my case it never worked any other way. But I never dug very deep to try to find out why. > Why should adding via the command line work, but not via > system-config-printer or localhost:631? I guess adding it in CUPS web interface (localhost:631) should work, if the exact same parameters are selected: the ipp:// url and the "CUPS PPD generator" (selected by "-m everywhere" option) as opposed to "cups-filters PPD generator". That might be the explanation (at least for my case). From what I understand from https://wiki.debian.org/CUPSDriverlessPrinting , there are those two options, and "The cups-filters PPD generator is used by default with cups-browsed". In theory either should work, but there's probably some quirk in the printer and some small difference between the two methods. -- Tchurin-tchurin-tchun-clain! -- Chapolim Eduardo M KALINOWSKI edua...@kalinowski.com.br >>> >>> When adding a printer with system-config-printer, it is detected and >>> listed under "Network Printer" in the list (when expanded) (twice). I >>> currently see what's in the screenshots attached, but sometimes the >>> "IPP network printer via DNS-SD" connection option changes to something >>> involving AppSocket/... at the beginning. >>> >>> There seem to be different connections available at different times. >>> >>> Any ideas why that should be? >>> >>> It seems to me that something has changed. Given the problem was the >>> same with an identical printer on a different network, I guess it's >>> something to do with CUPS (or its config) rather than the printer >>> itself misbehaving. I had factory-reset it a couple of days ago. >>> >>> Thanks, >>> Gareth >>> >>> >>> Attachments: >>> * Screenshot at 2022-06-06 16-39-52.png >>> * Screenshot at 2022-06-06 16-40-03.png >> >> $ driverless list >> DEBUG: Started ippfind (PID 95003) >> "driverless:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en >> "Brother" "Brother MFC-L2740DW series, driverless, cups-filters 1.28.7" >> "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;" >> "driverless-fax:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" >> en "Brother" "Brother MFC-L2740DW series, Fax, driverless, cups-filters >> 1.28.7" "MFG:Brother;MDL:MFC-L2740DW >> series;CMD:PWGRaster,AppleRaster,URF,PWG;" >> DEBUG: ippfind (PID 95003) exited with no errors. >> >> The error log except attached earlier includes: >> >> [line no] log text >> [30] D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-is-accepting-jobs >> boolean true >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state enum idle >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state-reasons keyword >> none >> D [06/Jun/2022:13:32:04 +0100] [Job 6] end-of-attributes-tag >> D [06/Jun/2022:13:32:04 +0100] [Job 6] IPP/2.0 Get-Job-Attributes #22 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] operation-attributes-tag >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-charset charset utf-8 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-natural-language >> naturalLanguage en-gb >> D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-uri uri >> ipp://mfcl2740dw.local:631/ipp/faxout >> >> ^^ >> >>Fax >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] unsupported-attributes-tag >> >> D [06/Jun/2022:13:32:04 +0100] [Job 6] requested-attributes keyword >> job-media-sheets-completed >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-attributes-tag >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-impressions-completed >> integer 0 >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-name nameWithoutLanguage >> Test Page >> D [06/Jun/2022:13:32:04 +0100] [Job 6] job-originating-user-name >> nameWithoutLanguage user >> D [06/Jun/2022:13:3
Re: Printing problem (was snapshot.debian.org)
On Mon 6 Jun 2022, at 17:45, Gareth Evans wrote: > Recent message with screenshots didn't get through (at least yet) - > text below, plus another observation. > > On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote: >> On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI >> wrote: >>> On 06/06/2022 10:48, Gareth Evans wrote: Not sure what's happened though as it worked perfectly with both auto-detected and manually-added printer profiles from Bullseye until a week or two ago. My logs suggest no update to system-config-printer. I did change the printer's hostname (on printer console) but both the printer and laptop have been restarted several times since then, printers re-added and re-auto-detected etc. >>> >>> In my case it never worked any other way. But I never dug very deep to >>> try to find out why. >>> Why should adding via the command line work, but not via system-config-printer or localhost:631? >>> >>> I guess adding it in CUPS web interface (localhost:631) should work, if >>> the exact same parameters are selected: the ipp:// url and the "CUPS PPD >>> generator" (selected by "-m everywhere" option) as opposed to >>> "cups-filters PPD generator". >>> >>> That might be the explanation (at least for my case). From what I >>> understand from https://wiki.debian.org/CUPSDriverlessPrinting , there >>> are those two options, and "The cups-filters PPD generator is used by >>> default with cups-browsed". In theory either should work, but there's >>> probably some quirk in the printer and some small difference between the >>> two methods. >>> >>> -- >>> Tchurin-tchurin-tchun-clain! >>> >>> -- Chapolim >>> >>> Eduardo M KALINOWSKI >>> edua...@kalinowski.com.br >> >> When adding a printer with system-config-printer, it is detected and >> listed under "Network Printer" in the list (when expanded) (twice). I >> currently see what's in the screenshots attached, but sometimes the >> "IPP network printer via DNS-SD" connection option changes to something >> involving AppSocket/... at the beginning. >> >> There seem to be different connections available at different times. >> >> Any ideas why that should be? >> >> It seems to me that something has changed. Given the problem was the >> same with an identical printer on a different network, I guess it's >> something to do with CUPS (or its config) rather than the printer >> itself misbehaving. I had factory-reset it a couple of days ago. >> >> Thanks, >> Gareth >> >> >> Attachments: >> * Screenshot at 2022-06-06 16-39-52.png >> * Screenshot at 2022-06-06 16-40-03.png > > $ driverless list > DEBUG: Started ippfind (PID 95003) > "driverless:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en > "Brother" "Brother MFC-L2740DW series, driverless, cups-filters 1.28.7" > "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;" > "driverless-fax:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" > en "Brother" "Brother MFC-L2740DW series, Fax, driverless, cups-filters > 1.28.7" "MFG:Brother;MDL:MFC-L2740DW > series;CMD:PWGRaster,AppleRaster,URF,PWG;" > DEBUG: ippfind (PID 95003) exited with no errors. > > The error log except attached earlier includes: > > [line no] log text > [30] D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-is-accepting-jobs > boolean true > D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state enum idle > D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state-reasons keyword > none > D [06/Jun/2022:13:32:04 +0100] [Job 6] end-of-attributes-tag > D [06/Jun/2022:13:32:04 +0100] [Job 6] IPP/2.0 Get-Job-Attributes #22 > D [06/Jun/2022:13:32:04 +0100] [Job 6] operation-attributes-tag > > D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-charset charset utf-8 > D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-natural-language > naturalLanguage en-gb > D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-uri uri > ipp://mfcl2740dw.local:631/ipp/faxout > > ^^ > >Fax > > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 > > D [06/Jun/2022:13:32:04 +0100] [Job 6] unsupported-attributes-tag > > D [06/Jun/2022:13:32:04 +0100] [Job 6] requested-attributes keyword > job-media-sheets-completed > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-attributes-tag > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-impressions-completed > integer 0 > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-name nameWithoutLanguage > Test Page > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-originating-user-name > nameWithoutLanguage user > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state enum canceled > D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state-reasons keyword > job-canceled-at-device" >
Re: Printing problem (was snapshot.debian.org)
Recent message with screenshots didn't get through (at least yet) - text below, plus another observation. On Mon 6 Jun 2022, at 16:53, Gareth Evans wrote: > On Mon 6 Jun 2022, at 16:23, Eduardo M KALINOWSKI > wrote: >> On 06/06/2022 10:48, Gareth Evans wrote: >>> Not sure what's happened though as it worked perfectly with both >>> auto-detected and manually-added printer profiles from Bullseye until a >>> week or two ago. My logs suggest no update to system-config-printer. I >>> did change the printer's hostname (on printer console) but both the printer >>> and laptop have been restarted several times since then, printers re-added >>> and re-auto-detected etc. >> >> In my case it never worked any other way. But I never dug very deep to >> try to find out why. >> >>> Why should adding via the command line work, but not via >>> system-config-printer or localhost:631? >> >> I guess adding it in CUPS web interface (localhost:631) should work, if >> the exact same parameters are selected: the ipp:// url and the "CUPS PPD >> generator" (selected by "-m everywhere" option) as opposed to >> "cups-filters PPD generator". >> >> That might be the explanation (at least for my case). From what I >> understand from https://wiki.debian.org/CUPSDriverlessPrinting , there >> are those two options, and "The cups-filters PPD generator is used by >> default with cups-browsed". In theory either should work, but there's >> probably some quirk in the printer and some small difference between the >> two methods. >> >> -- >> Tchurin-tchurin-tchun-clain! >> >> -- Chapolim >> >> Eduardo M KALINOWSKI >> edua...@kalinowski.com.br > > When adding a printer with system-config-printer, it is detected and > listed under "Network Printer" in the list (when expanded) (twice). I > currently see what's in the screenshots attached, but sometimes the > "IPP network printer via DNS-SD" connection option changes to something > involving AppSocket/... at the beginning. > > There seem to be different connections available at different times. > > Any ideas why that should be? > > It seems to me that something has changed. Given the problem was the > same with an identical printer on a different network, I guess it's > something to do with CUPS (or its config) rather than the printer > itself misbehaving. I had factory-reset it a couple of days ago. > > Thanks, > Gareth > > > Attachments: > * Screenshot at 2022-06-06 16-39-52.png > * Screenshot at 2022-06-06 16-40-03.png $ driverless list DEBUG: Started ippfind (PID 95003) "driverless:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en "Brother" "Brother MFC-L2740DW series, driverless, cups-filters 1.28.7" "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;" "driverless-fax:ipp://Brother%20MFC-L2740DW%20series._ipp._tcp.local/" en "Brother" "Brother MFC-L2740DW series, Fax, driverless, cups-filters 1.28.7" "MFG:Brother;MDL:MFC-L2740DW series;CMD:PWGRaster,AppleRaster,URF,PWG;" DEBUG: ippfind (PID 95003) exited with no errors. The error log except attached earlier includes: [line no] log text [30] D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-is-accepting-jobs boolean true D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state enum idle D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-state-reasons keyword none D [06/Jun/2022:13:32:04 +0100] [Job 6] end-of-attributes-tag D [06/Jun/2022:13:32:04 +0100] [Job 6] IPP/2.0 Get-Job-Attributes #22 D [06/Jun/2022:13:32:04 +0100] [Job 6] operation-attributes-tag D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-charset charset utf-8 D [06/Jun/2022:13:32:04 +0100] [Job 6] attributes-natural-language naturalLanguage en-gb D [06/Jun/2022:13:32:04 +0100] [Job 6] printer-uri uri ipp://mfcl2740dw.local:631/ipp/faxout ^^ Fax D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 D [06/Jun/2022:13:32:04 +0100] [Job 6] unsupported-attributes-tag D [06/Jun/2022:13:32:04 +0100] [Job 6] requested-attributes keyword job-media-sheets-completed D [06/Jun/2022:13:32:04 +0100] [Job 6] job-attributes-tag D [06/Jun/2022:13:32:04 +0100] [Job 6] job-id integer 82 D [06/Jun/2022:13:32:04 +0100] [Job 6] job-impressions-completed integer 0 D [06/Jun/2022:13:32:04 +0100] [Job 6] job-name nameWithoutLanguage Test Page D [06/Jun/2022:13:32:04 +0100] [Job 6] job-originating-user-name nameWithoutLanguage user D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state enum canceled D [06/Jun/2022:13:32:04 +0100] [Job 6] job-state-reasons keyword job-canceled-at-device" ^^ ...even though it wasn't (at least not by me). Does any of this suggest it's presenting/being auto-detected as (only) a fax machine ... and cancelling the
Re: Printing problem (was snapshot.debian.org)
On 06/06/2022 10:48, Gareth Evans wrote: Not sure what's happened though as it worked perfectly with both auto-detected and manually-added printer profiles from Bullseye until a week or two ago. My logs suggest no update to system-config-printer. I did change the printer's hostname (on printer console) but both the printer and laptop have been restarted several times since then, printers re-added and re-auto-detected etc. In my case it never worked any other way. But I never dug very deep to try to find out why. Why should adding via the command line work, but not via system-config-printer or localhost:631? I guess adding it in CUPS web interface (localhost:631) should work, if the exact same parameters are selected: the ipp:// url and the "CUPS PPD generator" (selected by "-m everywhere" option) as opposed to "cups-filters PPD generator". That might be the explanation (at least for my case). From what I understand from https://wiki.debian.org/CUPSDriverlessPrinting , there are those two options, and "The cups-filters PPD generator is used by default with cups-browsed". In theory either should work, but there's probably some quirk in the printer and some small difference between the two methods. -- Tchurin-tchurin-tchun-clain! -- Chapolim Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: Printing problem (was snapshot.debian.org)
On Mon 6 Jun 2022, at 14:14, Eduardo M KALINOWSKI wrote: > On 06/06/2022 08:19, Gareth Evans wrote: >> Hello, >> >> I have a strange printing problem which can be replicated on two identical >> printers on two different networks, when printing to wireless driverless IPP >> with Brother MFC-L2740DW printers from Bullseye, whether the printer is >> auto-detected or manually added via ocalhost:631 or system-config-printer. > > I have this exact printer. Driverless printing works, but not with the > automatically generated entry included by cups-browsed (or some other > package), i have to manually add a printer queue using > > # lpinfo -v > > to get a list of URLs (the one starting with ipp:// is the one > necessary), and then something like > > # lpadmin -p Brother2740 -v IPP_URL_FROM_ABOVE -E -m everywhere > > That worked, and it's now printing normally after reboot via the added profile, thank you Eduardo. Not sure what's happened though as it worked perfectly with both auto-detected and manually-added printer profiles from Bullseye until a week or two ago. My logs suggest no update to system-config-printer. I did change the printer's hostname (on printer console) but both the printer and laptop have been restarted several times since then, printers re-added and re-auto-detected etc. HTTP_STATE_WAITING Closing for error 32 (Broken pipe) - appears in the error log for jobs it is now actually printing, so that seems to be unrelated. I don't like it when things stop working without explanation. Why should adding via the command line work, but not via system-config-printer or localhost:631? Any further debugging tips would be appreciated. Thanks, Gareth > -- > BOFH excuse #201: > > RPC_PMAP_FAILURE > > Eduardo M KALINOWSKI > edua...@kalinowski.com.br
Re: Printing problem (was snapshot.debian.org)
On 06/06/2022 08:19, Gareth Evans wrote: Hello, I have a strange printing problem which can be replicated on two identical printers on two different networks, when printing to wireless driverless IPP with Brother MFC-L2740DW printers from Bullseye, whether the printer is auto-detected or manually added via ocalhost:631 or system-config-printer. I have this exact printer. Driverless printing works, but not with the automatically generated entry included by cups-browsed (or some other package), i have to manually add a printer queue using # lpinfo -v to get a list of URLs (the one starting with ipp:// is the one necessary), and then something like # lpadmin -p Brother2740 -v IPP_URL_FROM_ABOVE -E -m everywhere -- BOFH excuse #201: RPC_PMAP_FAILURE Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: Printing problem (was snapshot.debian.org)
CUPS error log excerpt attached. G On Mon 6 Jun 2022, at 14:02, Gareth Evans wrote: > On Mon 6 Jun 2022, at 13:05, rhkra...@gmail.com wrote: >> On Monday, June 06, 2022 07:34:07 AM Gareth Evans wrote: >>> On Mon 6 Jun 2022, at 12:19, Gareth Evans wrote: >>> > I have a strange printing problem which can be replicated on two >>> > identical printers on two different networks, when printing to wireless >>> > driverless IPP with Brother MFC-L2740DW printers from Bullseye, whether >>> > the printer is auto-detected or manually added via ocalhost:631 or >>> > system-config-printer. >> >> Is there a facility to run a test print directly from the printer? If so, >> does that work? > > Hello, > > Yes, the printer prints test pages and reports from its own console, > and documents via wifi from my iphone, but not from Debian. Even 11.0 > with non-updated cups. Same issue with an identical printer on another > network - that does print from Buster. I half suspected a router > problem, but same issues when Bullseye laptop and my printer are linked > via iphone wifi hotspot. Same issue when my Bullseye laptop is linked > via EE mobile broadband router (locally) to an identical printer (in > another place, 10 miles away, so can't check for differences regularly). > > After using system-config-printer to print a test page on an > auto-detected driverless IPP profile, connected via 2.5GHz wifi to a > router, to which the Bullseye laptop is connected via 5GHz wifi, I get > no output, and: > > $ lpstat -t > scheduler is running > no system default destination > device for Brother_MFC_L2740DW_series: > implicitclass://Brother_MFC_L2740DW_series/ > Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 > 13:12:54 BST > printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun > 2022 13:12:54 BST > No suitable destination host found by cups-browsed. > Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 > 13:12:48 BST > > After changing laptop to 2.5GHz wifi... > > $ lpstat -t > scheduler is running > no system default destination > device for Brother_MFC_L2740DW_series: > implicitclass://Brother_MFC_L2740DW_series/ > Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 > 13:14:40 BST > printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun > 2022 13:14:40 BST > Printer disappeared or cups-browsed shutdown > Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 > 13:12:48 BST > > $ sudo systemctl status cups-browsed > [sudo] password for user: > ● cups-browsed.service - Make remote CUPS printers available locally > Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; > vendor > > Active: active (running) since Mon 2022-06-06 13:04:25 BST; 11min ago >Main PID: 1666 (cups-browsed) > Tasks: 3 (limit: 14146) > Memory: 3.8M > CPU: 209ms > CGroup: /system.slice/cups-browsed.service > └─1666 /usr/sbin/cups-browsed > > Jun 06 13:04:25 qwerty systemd[1]: Started Make remote CUPS printers > available > > > *I deleted 5GHz wifi profile from Network Manager Edit Connections* > $ sudo reboot > > $ sudo systemctl status cups-browsed > [sudo] password for user: > ● cups-browsed.service - Make remote CUPS printers available locally > Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; > vendor > > Active: active (running) since Mon 2022-06-06 13:27:27 BST; 3min 13s ago >Main PID: 2059 (cups-browsed) > Tasks: 3 (limit: 14146) > Memory: 2.9M > CPU: 100ms > CGroup: /system.slice/cups-browsed.service > └─2059 /usr/sbin/cups-browsed > > Jun 06 13:27:27 qwerty systemd[1]: Started Make remote CUPS printers > available > > lines 1-11/11 (END) > > > $ lpstat -t > scheduler is running > no system default destination > device for Brother_MFC_L2740DW_series: > implicitclass://Brother_MFC_L2740DW_series/ > Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 > 13:27:46 BST > printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun > 2022 13:27:46 BST > Printer disappeared or cups-browsed shutdown > Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 > 13:12:48 BST > > *Turned printer off and on again* > > $ lpstat -t > scheduler is running > no system default destination > device for Brother_MFC_L2740DW_series: > implicitclass://Brother_MFC_L2740DW_series/ > Brother_MFC_L2740DW_series accepting requests s
Re: Printing problem (was snapshot.debian.org)
On Mon 6 Jun 2022, at 13:05, rhkra...@gmail.com wrote: > On Monday, June 06, 2022 07:34:07 AM Gareth Evans wrote: >> On Mon 6 Jun 2022, at 12:19, Gareth Evans wrote: >> > I have a strange printing problem which can be replicated on two >> > identical printers on two different networks, when printing to wireless >> > driverless IPP with Brother MFC-L2740DW printers from Bullseye, whether >> > the printer is auto-detected or manually added via ocalhost:631 or >> > system-config-printer. > > Is there a facility to run a test print directly from the printer? If so, > does that work? Hello, Yes, the printer prints test pages and reports from its own console, and documents via wifi from my iphone, but not from Debian. Even 11.0 with non-updated cups. Same issue with an identical printer on another network - that does print from Buster. I half suspected a router problem, but same issues when Bullseye laptop and my printer are linked via iphone wifi hotspot. Same issue when my Bullseye laptop is linked via EE mobile broadband router (locally) to an identical printer (in another place, 10 miles away, so can't check for differences regularly). After using system-config-printer to print a test page on an auto-detected driverless IPP profile, connected via 2.5GHz wifi to a router, to which the Bullseye laptop is connected via 5GHz wifi, I get no output, and: $ lpstat -t scheduler is running no system default destination device for Brother_MFC_L2740DW_series: implicitclass://Brother_MFC_L2740DW_series/ Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 13:12:54 BST printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun 2022 13:12:54 BST No suitable destination host found by cups-browsed. Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 13:12:48 BST After changing laptop to 2.5GHz wifi... $ lpstat -t scheduler is running no system default destination device for Brother_MFC_L2740DW_series: implicitclass://Brother_MFC_L2740DW_series/ Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 13:14:40 BST printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun 2022 13:14:40 BST Printer disappeared or cups-browsed shutdown Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 13:12:48 BST $ sudo systemctl status cups-browsed [sudo] password for user: ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor > Active: active (running) since Mon 2022-06-06 13:04:25 BST; 11min ago Main PID: 1666 (cups-browsed) Tasks: 3 (limit: 14146) Memory: 3.8M CPU: 209ms CGroup: /system.slice/cups-browsed.service └─1666 /usr/sbin/cups-browsed Jun 06 13:04:25 qwerty systemd[1]: Started Make remote CUPS printers available > *I deleted 5GHz wifi profile from Network Manager Edit Connections* $ sudo reboot $ sudo systemctl status cups-browsed [sudo] password for user: ● cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor > Active: active (running) since Mon 2022-06-06 13:27:27 BST; 3min 13s ago Main PID: 2059 (cups-browsed) Tasks: 3 (limit: 14146) Memory: 2.9M CPU: 100ms CGroup: /system.slice/cups-browsed.service └─2059 /usr/sbin/cups-browsed Jun 06 13:27:27 qwerty systemd[1]: Started Make remote CUPS printers available > lines 1-11/11 (END) $ lpstat -t scheduler is running no system default destination device for Brother_MFC_L2740DW_series: implicitclass://Brother_MFC_L2740DW_series/ Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 13:27:46 BST printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun 2022 13:27:46 BST Printer disappeared or cups-browsed shutdown Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 13:12:48 BST *Turned printer off and on again* $ lpstat -t scheduler is running no system default destination device for Brother_MFC_L2740DW_series: implicitclass://Brother_MFC_L2740DW_series/ Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 13:31:39 BST printer Brother_MFC_L2740DW_series now printing Brother_MFC_L2740DW_series-6. enabled since Mon 06 Jun 2022 13:31:39 BST Waiting for job to complete. Brother_MFC_L2740DW_series-6 user 1024 Mon 06 Jun 2022 13:12:48 BST $ lpstat -t scheduler is running no system default destination device for Brother_MFC_L2740DW_series: implicitclass://Brother_MFC_L2740DW_series/ Brother_MFC_L2740DW_series accepting requests since Mon 06 Jun 2022 13:32:06 BST printer Brother_MFC_L2740DW_series is idle. enabled since Mon 06 Jun 2022 13:32:06 BST But nothing printed. /var/log/cups/erro
Re: Printing problem Sadly NOT SOLVED
This printer Brother HL-L2340DW has buggy firmware. When re-installed it killed my CUPS. . I can no longer use my local CUPS webpage, my root/admin password is not accepted. I instead use system-config-printer, which runs fine. Thanks to this program I can at least print as root. But I cannot recommend Brother On my second PC it runs OK, I never installed it here, just now after the fiaso on my main PC. So my hint is: never change a running system! The Japanese at Brother just want to sell more printers, at least, that is my assumption. Have a good New Year! PS never update your Brother laser printer and never buy them. . On Sun, 14 Jan 2018 20:30:02 +0100 arne wrote: > Hi, > > My printer suddenly didn't show up in the Print Windows > of Libre Office, Firefox and a lot of other programs. > > I can however Print to File in pdf or ps and print those with lpr > from the command line. > > The printer shows up in CUPS page and I can print the test page from > CUPS. > > I did try reinstalling its driver software, removed and added the > printer with CUPS again. > > > It is a WiFi Brother HL-L2340DW laserprinter. > > some data I collected, I can not find any error there: > ### > # lpstat -t > scheduler is running > system default destination: HLL2340D > device for BrGenML1: usb://dev/usb/lp0 > device for HLL2340D: socket://192.168.2.7 > device for PDF: cups-pdf:/ > BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET > HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET > PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET > printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM > CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 > PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 > PM CET > > > To find the available printers, at a terminal type: > # lpstat -p -d > printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM > CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 > PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 > PM CET system default destination: HLL2340D > > > Then to pick one as the default lpd printer, type: > # lpoptions -d HLL2340D > copies=1 device-uri=socket://192.168.2.7 finishings=3 > job-cancel-after=10800 job-hold-until=no-hold job-priority=50 > job-sheets=none,none marker-change-time=1515956190 > marker-colors=#00,none marker-levels=-1,97 marker-names='Black\ > Tone > > > Then type lpq to see if the printer you selected is now the default: > # lpq > HLL2340D is ready > no entries > > To show all printers that accept jobs: > # lpstat -a > BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET > HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET > PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET > > > # lpoptions -p HLL2340D -l > PageSize/Media Size: Custom.WIDTHxHEIGHT Letter Legal Executive > FanFoldGermanLegal *A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 > ISOB6 B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm > 184x260mm 197x273mm CUSTOM1 CUSTOM2 CUSTOM3 BrMediaType/MediaType: > *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK ENVTHIN RECYCLED > InputSlot/InputSlot: MANUAL *TRAY1 Duplex/Duplex: DuplexTumble > *DuplexNoTumble None Resolution/Resolution: 300dpi 600dpi *2400x600dpi > TonerSaveMode/Toner Save: *OFF ON Sleep/Sleep Time [Min.]: > *PrinterDefault 2minutes 10minutes 30minutes > > ### > Any ideas about where to look further? > > Thanks! >
Re: Printing problem
On Mon, 15 Jan 2018 23:20:52 + Brian wrote: Hi, I made a mistake, I still can not print from office, issue also not completely solved. I can print as user now with gimp, geany, firefox. Not with okular (as root yes), libreoffice writer (as root yes). Also another rights problem I guess. Below my /et/gtk* On Mon, 15 Jan 2018 23:20:52 + Brian wrote: > On Mon 15 Jan 2018 at 22:29:30 +0100, arne wrote: > > > On Mon, 15 Jan 2018 11:24:22 + > > Brian wrote: > > > > > On Sun 14 Jan 2018 at 20:30:02 +0100, arne wrote: > > > > > > > My printer suddenly didn't show up in the Print Windows > > > > of Libre Office, Firefox and a lot of other programs. > > > > > > We hope "suddenly" means that one day you went to bed and when you > > > woke up, printing from an application didn't work. No changes to > > > the printing system or the OS on your part were underaken before, > > > during or after the sleep process. > > > > > > Please give a list of all the affected programs and the output of > > > > > > dpkg -l libreoffice* > > > > > > How do you fare with okular or qpdfview? You are running under > > > GNOME? > > > > > > > > > > Hi > > > > I forgot to mention: daily updated Debian Stretch on amd64 with > > backports. > > > > In okular the printer is visible, but not printing > > In qpdfview the printer is visible and prints! > > > > In Firefox, Gimp and Geanny the printer does not appear > > > > I do not run GNOME but fluxbox. > > > > Output of dpkg -l libreoffice* below > > Thanks, > > When you say "printer" do you really mean "printers"? > > Printers are visible in the dialogs of Qt apps (okular and qpdfview) > but not in those of GTK apps. So it seems like a GTK problem. (Except > libreoffice is not a GTK app). Do you have any /etc/gtk-x.0 or > ~/.gtk-x.0 files? If so, what are their contents? /etc/gtk-2.0/im-multipress.conf # Example configuration file for the GTK+ Multipress Input Method # Authored by Openismus GmbH, 2009. # # This file follows the GKeyFile format. On the left of the equal sign goes # the key that you press repeatedly to iterate through the text items listed # on the right-hand side. The list items are separated by semicolons ";" and # consist of one or more characters each. The backslash "\" is used to escape # characters; for instance "\;" for a literal semicolon. # # The example configuration below imitates the behavior of a standard mobile # phone by a major manufacturer, with German language setting. [keys] KP_1 = .;,;?;!;';";1;-;(;);@;/;:;_ KP_2 = a;b;c;2;ä;à;á;ã;â;å;æ;ç KP_3 = d;e;f;3;è;é;ë;ê;ð KP_4 = g;h;i;4;ì;í;î;ï KP_5 = j;k;l;5;£ KP_6 = m;n;o;6;ö;ò;ó;ô;õ;ø;ñ KP_7 = p;q;r;s;7;ß;$ KP_8 = t;u;v;8;ü;ù;ú;û KP_9 = w;x;y;z;9;ý;þ KP_0 = \s;0 /etc/gtk-3.0/im-multipress.conf # Example configuration file for the GTK+ Multipress Input Method # Authored by Openismus GmbH, 2009. # # This file follows the GKeyFile format. On the left of the equal sign goes # the key that you press repeatedly to iterate through the text items listed # on the right-hand side. The list items are separated by semicolons ";" and # consist of one or more characters each. The backslash "\" is used to escape # characters; for instance "\;" for a literal semicolon. # # The example configuration below imitates the behavior of a standard mobile # phone by a major manufacturer, with German language setting. [keys] KP_1 = .;,;?;!;';";1;-;(;);@;/;:;_ KP_2 = a;b;c;2;ä;à;á;ã;â;å;æ;ç KP_3 = d;e;f;3;è;é;ë;ê;ð KP_4 = g;h;i;4;ì;í;î;ï KP_5 = j;k;l;5;£ KP_6 = m;n;o;6;ö;ò;ó;ô;õ;ø;ñ KP_7 = p;q;r;s;7;ß;$ KP_8 = t;u;v;8;ü;ù;ú;û KP_9 = w;x;y;z;9;ý;þ KP_0 = \s;0
Re: Printing problem SOLVED
Hi, It was a problem with rights. I do not know how they were changed. I could print as root, not as user. Printing with qpdfview as root worked. Firefox, Geany, Gimp I started as user, and I could not print with those. The solution for my printer with brother_lpdwrapper_HLL2340D was: /usr/lib/cups/filter/brother_lpdwrapper_HLL2340D is a link to /opt/brother/Printers/HLL2340D/cupswrapper/brother_lpdwrapper_HLL2340D Permissions (octal) should be: 100755 Owner name: root Group name: root Thanks! On Mon, 15 Jan 2018 11:24:22 + Brian wrote: > On Sun 14 Jan 2018 at 20:30:02 +0100, arne wrote: > > > My printer suddenly didn't show up in the Print Windows > > of Libre Office, Firefox and a lot of other programs. > > We hope "suddenly" means that one day you went to bed and when you > woke up, printing from an application didn't work. No changes to the > printing system or the OS on your part were underaken before, during > or after the sleep process. > > Please give a list of all the affected programs and the output of > > dpkg -l libreoffice* > > How do you fare with okular or qpdfview? You are running under GNOME? > >
Re: Printing problem
On Mon 15 Jan 2018 at 22:29:30 +0100, arne wrote: > On Mon, 15 Jan 2018 11:24:22 + > Brian wrote: > > > On Sun 14 Jan 2018 at 20:30:02 +0100, arne wrote: > > > > > My printer suddenly didn't show up in the Print Windows > > > of Libre Office, Firefox and a lot of other programs. > > > > We hope "suddenly" means that one day you went to bed and when you > > woke up, printing from an application didn't work. No changes to the > > printing system or the OS on your part were underaken before, during > > or after the sleep process. > > > > Please give a list of all the affected programs and the output of > > > > dpkg -l libreoffice* > > > > How do you fare with okular or qpdfview? You are running under GNOME? > > > > > > Hi > > I forgot to mention: daily updated Debian Stretch on amd64 with > backports. > > In okular the printer is visible, but not printing > In qpdfview the printer is visible and prints! > > In Firefox, Gimp and Geanny the printer does not appear > > I do not run GNOME but fluxbox. > > Output of dpkg -l libreoffice* below Thanks, When you say "printer" do you really mean "printers"? Printers are visible in the dialogs of Qt apps (okular and qpdfview) but not in those of GTK apps. So it seems like a GTK problem. (Except libreoffice is not a GTK app). Do you have any /etc/gtk-x.0 or ~/.gtk-x.0 files? If so, what are their contents? -- Brian.
Re: Printing problem
On Mon, 15 Jan 2018 11:24:22 + Brian wrote: > On Sun 14 Jan 2018 at 20:30:02 +0100, arne wrote: > > > My printer suddenly didn't show up in the Print Windows > > of Libre Office, Firefox and a lot of other programs. > > We hope "suddenly" means that one day you went to bed and when you > woke up, printing from an application didn't work. No changes to the > printing system or the OS on your part were underaken before, during > or after the sleep process. > > Please give a list of all the affected programs and the output of > > dpkg -l libreoffice* > > How do you fare with okular or qpdfview? You are running under GNOME? > > Hi I forgot to mention: daily updated Debian Stretch on amd64 with backports. In okular the printer is visible, but not printing In qpdfview the printer is visible and prints! In Firefox, Gimp and Geanny the printer does not appear I do not run GNOME but fluxbox. Output of dpkg -l libreoffice* below Thanks! # dpkg -l libreoffice* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---== ii libreoffice 1:5.4.4-1~bpo9+1 amd64office productivity suite (metapackage) un libreoffice-avmedia-backend (no description available) ii libreoffice-avmedia-backend-gstreamer 1:5.4.4-1~bpo9+1 amd64GStreamer backend for LibreOffice un libreoffice-avmedia-backend-vlc (no description available) ii libreoffice-base 1:5.4.4-1~bpo9+1 amd64office productivity suite -- database ii libreoffice-base-core 1:5.4.4-1~bpo9+1 amd64office productivity suite -- shared library ii libreoffice-base-drivers 1:5.4.4-1~bpo9+1 amd64Database connectivity drivers for LibreOffice un libreoffice-bundled (no description available) ii libreoffice-calc 1:5.4.4-1~bpo9+1 amd64office productivity suite -- spreadsheet ii libreoffice-common1:5.4.4-1~bpo9+1 all office productivity suite -- arch-independent files ii libreoffice-core 1:5.4.4-1~bpo9+1 amd64office productivity suite -- arch-dependent files un libreoffice-dev (no description available) un libreoffice-dev-doc (no description available) ii libreoffice-draw 1:5.4.4-1~bpo9+1 amd64office productivity suite -- drawing un libreoffice-evolution (no description available) un libreoffice-filter-binfilter (no description available) un libreoffice-filter-mobiledev (no description available) un libreoffice-gnome (no description available) un libreoffice-grammarcheck (no description available) un libreoffice-grammarcheck-nl (no description available) un libreoffice-gtk2 (no description available) un libreoffice-gtk3 (no description available) un libreoffice-help (no description available) un libreoffice-help-5.2 (no description available) ii libreoffice-help-en-us1:5.4.4-1~bpo9+1 all office productivity suite -- English_american help ii libreoffice-help-nl 1:5.4.4-1~bpo9+1 all office productivity suite -- Dutch help ii libreoffice-impress 1:5.4.4-1~bpo9+1 amd64office productivity suite -- presentation ii libreoffice-java-common 1:5.4.4-1~bpo9+1 all office productivity suite -- arch-independent Java support files un libreoffice-kde (no description available) un libreoffice-l10n (no description available) un libreoffice-l10n-4.3 (no description available) un libreoffice-l10n-4.4 (no description available) un libreoffice-l10n-en-us (no description available) ii libreoffice-l10n-nl 1:5.4.4-1~bpo9+1 all office productivity suite -- Dutch language package ii libreoffice-librelogo 1:5.4.4-1~bpo9+1 all Logo-like progamming language for LibreOffice ii libreoffice-math 1:5.4.4-1~bpo9+1 amd64office productivity suite -- equation editor un libreoffice-mysql-connector (no description available) ii libreoffice-nlpsolver 0.9+LibO5.4.4-1~bpo9+1 all "Solver for Nonlinear Programming" extension for LibreOffice un libreof
Re: Printing problem
On Sun 14 Jan 2018 at 20:30:02 +0100, arne wrote: > My printer suddenly didn't show up in the Print Windows > of Libre Office, Firefox and a lot of other programs. We hope "suddenly" means that one day you went to bed and when you woke up, printing from an application didn't work. No changes to the printing system or the OS on your part were underaken before, during or after the sleep process. Please give a list of all the affected programs and the output of dpkg -l libreoffice* How do you fare with okular or qpdfview? You are running under GNOME? -- Brian.
Re: Printing problem
arne wrote: > amd64 both systems > OS: Daily updated Linux Stretch > > After 5 hours of googling, countless unnecessary rebooting > I still can only print from thin client > , > Not from PC (Only pdf and postscript from files using lpr) > Both macines are running debian stretch updated daily > No complaints from CUPS, but their drivers don't show up > Both are running amd64 In /etc/cups/client.conf I usually put the server name #ServerName myhost.domain.com ServerName then lpstat -a $ lpstat -a HP_LaserJet_5L accepting requests since Thu 14 Dec 2017 09:40:38 PM CET HP_LaserJet_M402dn accepting requests since Sun 14 Jan 2018 11:52:07 PM CET you need 'shared' configured on the print server for the printer(s) regards
Re: Printing problem
amd64 both systems OS: Daily updated Linux Stretch After 5 hours of googling, countless unnecessary rebooting I still can only print from thin client , Not from PC (Only pdf and postscript from files using lpr) Both macines are running debian stretch updated daily No complaints from CUPS, but their drivers don't show up Both are running amd64 On Sun, 14 Jan 2018 20:30:02 +0100 arne wrote: > Hi, > > My printer suddenly didn't show up in the Print Windows > of Libre Office, Firefox and a lot of other programs. > > I can however Print to File in pdf or ps and print those with lpr > from the command line. > > The printer shows up in CUPS page and I can print the test page from > CUPS. > > I did try reinstalling its driver software, removed and added the > printer with CUPS again. > > > It is a WiFi Brother HL-L2340DW laserprinter. > > some data I collected, I can not find any error there: > ### > # lpstat -t > scheduler is running > system default destination: HLL2340D > device for BrGenML1: usb://dev/usb/lp0 > device for HLL2340D: socket://192.168.2.7 > device for PDF: cups-pdf:/ > BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET > HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET > PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET > printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM > CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 > PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 > PM CET > > > To find the available printers, at a terminal type: > # lpstat -p -d > printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM > CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 > PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 > PM CET system default destination: HLL2340D > > > Then to pick one as the default lpd printer, type: > # lpoptions -d HLL2340D > copies=1 device-uri=socket://192.168.2.7 finishings=3 > job-cancel-after=10800 job-hold-until=no-hold job-priority=50 > job-sheets=none,none marker-change-time=1515956190 > marker-colors=#00,none marker-levels=-1,97 marker-names='Black\ > Tone > > > Then type lpq to see if the printer you selected is now the default: > # lpq > HLL2340D is ready > no entries > > To show all printers that accept jobs: > # lpstat -a > BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET > HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET > PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET > > > # lpoptions -p HLL2340D -l > PageSize/Media Size: Custom.WIDTHxHEIGHT Letter Legal Executive > FanFoldGermanLegal *A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 > ISOB6 B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm > 184x260mm 197x273mm CUSTOM1 CUSTOM2 CUSTOM3 BrMediaType/MediaType: > *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK ENVTHIN RECYCLED > InputSlot/InputSlot: MANUAL *TRAY1 Duplex/Duplex: DuplexTumble > *DuplexNoTumble None Resolution/Resolution: 300dpi 600dpi *2400x600dpi > TonerSaveMode/Toner Save: *OFF ON Sleep/Sleep Time [Min.]: > *PrinterDefault 2minutes 10minutes 30minutes > > ### > Any ideas about where to look further? > > Thanks! >
Printing problem
Hi, My printer suddenly didn't show up in the Print Windows of Libre Office, Firefox and a lot of other programs. I can however Print to File in pdf or ps and print those with lpr from the command line. The printer shows up in CUPS page and I can print the test page from CUPS. I did try reinstalling its driver software, removed and added the printer with CUPS again. It is a WiFi Brother HL-L2340DW laserprinter. some data I collected, I can not find any error there: ### # lpstat -t scheduler is running system default destination: HLL2340D device for BrGenML1: usb://dev/usb/lp0 device for HLL2340D: socket://192.168.2.7 device for PDF: cups-pdf:/ BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 PM CET To find the available printers, at a terminal type: # lpstat -p -d printer BrGenML1 is idle. enabled since Sun 14 Jan 2018 06:19:20 PM CET printer HLL2340D is idle. enabled since Sun 14 Jan 2018 07:56:30 PM CET printer PDF is idle. enabled since Sun 14 Jan 2018 04:39:50 PM CET system default destination: HLL2340D Then to pick one as the default lpd printer, type: # lpoptions -d HLL2340D copies=1 device-uri=socket://192.168.2.7 finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=1515956190 marker-colors=#00,none marker-levels=-1,97 marker-names='Black\ Tone Then type lpq to see if the printer you selected is now the default: # lpq HLL2340D is ready no entries To show all printers that accept jobs: # lpstat -a BrGenML1 accepting requests since Sun 14 Jan 2018 06:19:20 PM CET HLL2340D accepting requests since Sun 14 Jan 2018 07:56:30 PM CET PDF accepting requests since Sun 14 Jan 2018 04:39:50 PM CET # lpoptions -p HLL2340D -l PageSize/Media Size: Custom.WIDTHxHEIGHT Letter Legal Executive FanFoldGermanLegal *A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm CUSTOM1 CUSTOM2 CUSTOM3 BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK ENVTHIN RECYCLED InputSlot/InputSlot: MANUAL *TRAY1 Duplex/Duplex: DuplexTumble *DuplexNoTumble None Resolution/Resolution: 300dpi 600dpi *2400x600dpi TonerSaveMode/Toner Save: *OFF ON Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes ### Any ideas about where to look further? Thanks!
Re: [SOLVED... sort of] Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sun 27 May 2012 at 08:56:04 +0200, Joost Kraaijeveld wrote: > HP > LaserJet 2200 Postscript (recommended) (en) > HP > LaserJet 2200 Postscript (recommended) (en) There are two entries for the same PPD file because two different strings for the printer model - 'HP LaserJet 2200' and 'Hewlett-Packard HP LaserJet 2200' - are given by the postscript-hp driver. CUPS+Gutenprint isn't in your list, but maybe you didn't install printer-driver-gutenprint. Not that it particularly matters if you have something which gives printing on both machines. However, it is a good quality driver. The openprinting page doesn't list any best driver because that will depend on what functionality you want. One of my print queues for the HP 2200 uses a PCL PPD file from Generic and the quality satisfies me. The speed of printing is also fine with it but any contrast with other languages amounts to a religious argument as there will too many factors (text, images, mixed text and images etc) to take account of. The HP 2200 isn't in the full flush of youth and it is doubtful HP care enough about it to keep providing a new PPD file if needed. You should be fine with the Debian packages. A benefit is that any bugs in a PPD file are more likely to fixed in Debian rather than by the printer manufacturer. -- 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/20120527151012.GV2847@desktop
Re: [SOLVED... sort of] Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sun, 27 May 2012 08:56:04 +0200, Joost Kraaijeveld wrote: > My problem is solved: I am able to print with both machines, although > graphics appear to be very slow. Then why "sort of"? I do not know which > driver I am actually using... Congrats for the solved problem :-) Then... to know what's the driver you are using, open "http:// localhost:631" and go to the printer's tab page. From there, locate your printer and look at the "Manufacturer and model" line, it should be printed there. (and yes, as I already told you, a PS driver will be slower than PCL, but you can adjust the printer's output quality and lower this value; also note the more memory has the printer, the better to speed up your printings) > After reading the discussion between Brian and Camaleón (and some > suggestions in private mail, thanks to all) which centred around "to PS > or to PCL, that's the question", I decided to remove everything on both > machines that even vaguely has something to do with printing (OK, > without removing Gnome completely). I re-installed Cups and tried all > drivers that came for the HP2000 DTN without any improvement. Then I > (accidentally) un-installed the printer-driver-postscript-hp package, > re-installed it again. After this I had two *identical entries* for the > HP LaserJet 2200 Postscript driver in the CUPS browser based > administration tool (not in the Gnome GUI btw). If I use the first entry > in the list it does NOT work. But if I use the second entry, I can print > on both machines. I always use "one" driver for my printers which I get from the manufacturer's site or visiting "http://www.openprinting.org/printers"; and I never had any problem. As the CUPS package cannot always contain the most updated file, I prefer to fetch them from upsatream, whether possible. > The source of the CUPS administration tool shows (notice the 2 entries > for HP LaserJet 2200 Postscript on line 8 and 9): (...) > LaserJet 2200 Postscript (recommended) (en) > LaserJet 2200 Postscript (recommended) (en) (...) > I do not know the difference between the two, other than the empirical > proof that the first entry does not work and the second does. According to openprinting, the best driver for your printer is "hplip" so you should be using the PS driver provided by that package, either the "0" or the "1", as they are the same. Why the first does not work? I can't tell, both are using the same PPD file, it could a "phantom" detected instance. Anyway, having different instances for the same printer pointing to different drivers is always a good idea, so you can leave whatever ppd works for you and keep as the default printer the one using a PS driver. Greetings, -- Camaleón -- 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/jpt3gi$tbr$4...@dough.gmane.org
Re: [SOLVED... sort of] Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On 2012-05-27, Joost Kraaijeveld wrote: >HP >LaserJet 2200 Series hpijs, 3.12.2 (en) >HP LaserJet >2200 Series, hpcups 3.12.2 (en) > > I do not know the difference between the two, other than the empirical > proof that the first entry does not work and the second does. You have a laser printer, right? The HP 2200 DTN is laser, isn't it? hpijs is for ink jet printers, (ij = i(nk) (j)et) so what you have seen empirically makes perfect sense because we wouldn't expect the ink jet driver to work well with a laser printer, unless I'm not understanding something (always a possibility). The PCL XL print stream corruption errors you were getting can also be caused, other than by a driver mismatch, by the hardware between the pc and printer (bad cables, etc.) but I guess the problem's fixed and you don't need to look in that direction. By the way, on my machine 'lpoptions' tells me what driver my printer's using (amongst other things). -- 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/slrnjs3vrp.20e.cu...@einstein.electron.org
Re: [SOLVED... sort of] Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
Hi, My problem is solved: I am able to print with both machines, although graphics appear to be very slow. Then why "sort of"? I do not know which driver I am actually using... After reading the discussion between Brian and Camaleón (and some suggestions in private mail, thanks to all) which centred around "to PS or to PCL, that's the question", I decided to remove everything on both machines that even vaguely has something to do with printing (OK, without removing Gnome completely). I re-installed Cups and tried all drivers that came for the HP2000 DTN without any improvement. Then I (accidentally) un-installed the printer-driver-postscript-hp package, re-installed it again. After this I had two *identical entries* for the HP LaserJet 2200 Postscript driver in the CUPS browser based administration tool (not in the Gnome GUI btw). If I use the first entry in the list it does NOT work. But if I use the second entry, I can print on both machines. The source of the CUPS administration tool shows (notice the 2 entries for HP LaserJet 2200 Postscript on line 8 and 9): HP LaserJet 2200 Foomatic/lj4dith (en) HP LaserJet 2200 Foomatic/lj5gray (en) HP LaserJet 2200 Foomatic/ljet4 (en) HP LaserJet 2200 Foomatic/Postscript (en) HP LaserJet 2200 Foomatic/pxlmono (en) HP LaserJet 2200 hpijs pcl3, 3.12.2 (en) HP LaserJet 2200 pcl3, hpcups 3.12.2 (en) HP LaserJet 2200 Postscript (recommended) (en) HP LaserJet 2200 Postscript (recommended) (en) HP LaserJet 2200 Series hpijs, 3.12.2 (en) HP LaserJet 2200 Series, hpcups 3.12.2 (en) I do not know the difference between the two, other than the empirical proof that the first entry does not work and the second does. -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1338101764.4318.21.ca...@panoramix.askesis.nl
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat, 26 May 2012 17:48:41 +0100, Brian wrote: > On Sat 26 May 2012 at 15:53:03 +, Camaleón wrote: > >> On Sat, 26 May 2012 16:26:34 +0100, Brian wrote: >> > I have a feeling you may have returned to "PostScript is a raw >> > language, no conversion is needed between the doc and the printer . . >> > . ." idea. Hope I'm wrong. >> >> No, you're not, . . . > > Taking this statement, and the previous one, it is evident you are > basing an argument on the behaviour of a filtering method in CUPS which > has not existed in Debian (and Redhat and Suse) for at least three > years. We have different understandings, which make it impossible to > compare two different conclusions in a meaningful way. Basically, a > conclusion derived from a view of reality which is wrong is without any > validity. This is not a Debian specific behavior nor related to how CUPS works in different distributions. It's about the difference between a PostScript driver/printer and PCL (or another printer languages), and the differences are *huge*. > . . . but this is not going to help the OP to solve his problem. > > He can make his own mind up on that. I'd like think there is enough in > this thread to get him started. Let's hope so. Greetings, -- Camaleón -- 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/jpr568$dh7$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat 26 May 2012 at 15:53:03 +, Camaleón wrote: > On Sat, 26 May 2012 16:26:34 +0100, Brian wrote: > > > But at least you have discarded "PostScript is a raw language, no > > conversion is needed between the doc and the printer . . . ." as a > > reason and accept the filter chain is > > > >PDF file ---> PS file ---> CUPS ---> PDF file > > > > Is it a comfort getting back to where you started? > > "No conversion is needed" because the printer understands the PostScript > language, it's not device dependant. I don't know how to express it > better but is not that hard to understand. > > > I have a feeling you may have returned to "PostScript is a raw language, > > no conversion is needed between the doc and the printer . . . ." idea. > > Hope I'm wrong. > > No, you're not, . . . Taking this statement, and the previous one, it is evident you are basing an argument on the behaviour of a filtering method in CUPS which has not existed in Debian (and Redhat and Suse) for at least three years. We have different understandings, which make it impossible to compare two different conclusions in a meaningful way. Basically, a conclusion derived from a view of reality which is wrong is without any validity. . . . but this is not going to help the OP to solve his problem. He can make his own mind up on that. I'd like think there is enough in this thread to get him started. -- 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/20120526164841.GP2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat, 26 May 2012 16:26:34 +0100, Brian wrote: > On Sat 26 May 2012 at 13:30:27 +, Camaleón wrote: > >> On Sat, 26 May 2012 13:01:16 +0100, Brian wrote: >> >> There's no "cupsFilter:" line in any of PPD files so maybe the printer >> is not a true PostScript printer or uses a slightly different >> implementation developed by HP. > > That is not relevant to the point I made but, to satisfy your curiosity: > if there no *cupsFilter line in a PPD file then CUPS assumes the printer > requires a backend to send it PostScript. Nothing to do with a 'true > PostScript printer', whatever that might be. Either the printer has a > PostScript interpreter or it doesn't. Many manufacturers implement their > own anyway. It's not that simple. There are some printes (mostly the low-end models) that can "simulate" a PostScript level in a way that only the manufacturer knows, not standarized, thus you still depend on the quality of the manufacturer's driver. >> > The standard language used for printing in Debian has been PDF for >> > over three years. There is no inherent benefit in inputting a >> > PostScript file to CUPS. >> >> I assure there is. > > But at least you have discarded "PostScript is a raw language, no > conversion is needed between the doc and the printer . . . ." as a > reason and accept the filter chain is > >PDF file ---> PS file ---> CUPS ---> PDF file > > Is it a comfort getting back to where you started? "No conversion is needed" because the printer understands the PostScript language, it's not device dependant. I don't know how to express it better but is not that hard to understand. >> > You are also confusing the input file with the file sent by a CUPS >> > backend to the printer. In the latter case, you reply completely on >> > the capabilities of the printer's interpreters whether the file >> > contains PostScript, PCL or any other language. >> >> If the printer does support PostScript and uses a PS driver, the above >> is completely irrelevant. > > I have a feeling you may have returned to "PostScript is a raw language, > no conversion is needed between the doc and the printer . . . ." idea. > Hope I'm wrong. No, you're not, but this is not going to help the OP to solve his problem. Greetings, -- Camaleón -- 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/jpqu8v$dh7$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat 26 May 2012 at 13:30:27 +, Camaleón wrote: > On Sat, 26 May 2012 13:01:16 +0100, Brian wrote: > > There's no "cupsFilter:" line in any of PPD files so maybe the printer is > not a true PostScript printer or uses a slightly different implementation > developed by HP. That is not relevant to the point I made but, to satisfy your curiosity: if there no *cupsFilter line in a PPD file then CUPS assumes the printer requires a backend to send it PostScript. Nothing to do with a 'true PostScript printer', whatever that might be. Either the printer has a PostScript interpreter or it doesn't. Many manufacturers implement their own anyway. [Snip] > > The standard language used for printing in Debian has been PDF for over > > three years. There is no inherent benefit in inputting a PostScript file > > to CUPS. > > I assure there is. But at least you have discarded "PostScript is a raw language, no conversion is needed between the doc and the printer . . . ." as a reason and accept the filter chain is PDF file ---> PS file ---> CUPS ---> PDF file Is it a comfort getting back to where you started? [Snip] > > You are also confusing the input file with the file sent by a CUPS > > backend to the printer. In the latter case, you reply completely on the > > capabilities of the printer's interpreters whether the file contains > > PostScript, PCL or any other language. > > If the printer does support PostScript and uses a PS driver, the above is > completely irrelevant. I have a feeling you may have returned to "PostScript is a raw language, no conversion is needed between the doc and the printer . . . ." idea. Hope I'm wrong. -- 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/20120526152634.GO2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat, 26 May 2012 13:01:16 +0100, Brian wrote: > On Sat 26 May 2012 at 09:58:31 +, Camaleón wrote: > >> On Fri, 25 May 2012 18:51:16 +0100, Brian wrote: >> > Not quite. The PPD file/driver combination has to produce a file >> > which, when sent to the printer, is understandable by the printer. >> > The Gutenprint driver. for example, will always send PCL to an HP2200 >> > because, even though the printer can understand PostScript, the >> > driver is designed to output only in the native language of the >> > printer. >> >> But that only happens when the printer does not natively support PS >> which does not seem to be the case; according to the printer specs¹ it >> features HP PCL 6, HP PCL 5e and HP Postscript Level 2 emulation. > > No, it happens because there is a line like this > >*cupsFilter:"application/vnd.cups-raster 100 >rastertogutenprint.5.0" > > in the PPD file. There's no "cupsFilter:" line in any of PPD files so maybe the printer is not a true PostScript printer or uses a slightly different implementation developed by HP. >> > CUPS in Debian turns any input file into PDF, apart from a PDF file, >> > of course. A PostScript file is filtered first by pstopdf, then by >> > pdftopdf. A PDF file would only be filtered by pdftopdf. If the PPD >> > file tells CUPS the printer wants PostScript it uses pdftops. >> > Otherwise, there are other filters for converting the PDF coming from >> > pdftopdf into the printer specific language. >> >> The problem still remains: the PDF file is not able to be printed >> properly, it can be either because of a corrupted file (badly-crafted), >> a problem with the driver (that is not able to interpret the code of >> the file) an error in CUPS, a problem within the application used to >> display the file... to solve the problem we have to start discarding >> all these things. > > The OP has a PCL error on one machine. It is legitimate to use a PPD > file producing PostScript to see if it resolves the problem. Converting > the input file to PostScript before sending it to CUPS is something > entirely different and of doubtful merit. Converting the file to PS with a success result when printing could be of interest for people in the know, that is, developers. It also can be a workaround to get the job done until a proper solution applies. I don't care about "merits" (dude, this is not a race!) but getting a problem resolved with a solution that can fit the user needings. >> > I wasn't concerned with speed as such but with your giving this as a >> > reason for saying '. . . no conversion is needed between the doc and >> > the printer' for a PS file. >> >> When you are using a PPD which defines the capabilities of the printer >> and how it has to behave and both (printer harwdare and printer driver) >> "speak" a standard language (like PostScript) you're reducing the >> chances for an error than when using any other emulated language such >> as PCL, simply because PS is not device-dependant, but PCL is, meaning >> -for the latter- that you completely rely on the printer's capablities >> and how your device interprets the job you are sending to it. > > The standard language used for printing in Debian has been PDF for over > three years. There is no inherent benefit in inputting a PostScript file > to CUPS. I assure there is. Again, I'm tired of seeing these kind problems with PDF, TIFF and PS files (here at the office we do fax a lot and it's very common to see a user with problems when printing hylafax produced files). We also have a set of different printers (HP Laserjet, Ricoh and Oki) so we're very accustomed to these problems, even from windows machines... > You are also confusing the input file with the file sent by a CUPS > backend to the printer. In the latter case, you reply completely on the > capabilities of the printer's interpreters whether the file contains > PostScript, PCL or any other language. If the printer does support PostScript and uses a PS driver, the above is completely irrelevant. Greetings, -- Camaleón -- 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/jpqlti$dh7$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Sat 26 May 2012 at 09:58:31 +, Camaleón wrote: > On Fri, 25 May 2012 18:51:16 +0100, Brian wrote: > > Not quite. The PPD file/driver combination has to produce a file which, > > when sent to the printer, is understandable by the printer. The > > Gutenprint driver. for example, will always send PCL to an HP2200 > > because, even though the printer can understand PostScript, the driver > > is designed to output only in the native language of the printer. > > But that only happens when the printer does not natively support PS which > does not seem to be the case; according to the printer specs¹ it features > HP PCL 6, HP PCL 5e and HP Postscript Level 2 emulation. No, it happens because there is a line like this *cupsFilter:"application/vnd.cups-raster 100 rastertogutenprint.5.0" in the PPD file. > > CUPS in Debian turns any input file into PDF, apart from a PDF file, of > > course. A PostScript file is filtered first by pstopdf, then by > > pdftopdf. A PDF file would only be filtered by pdftopdf. If the PPD file > > tells CUPS the printer wants PostScript it uses pdftops. Otherwise, > > there are other filters for converting the PDF coming from pdftopdf into > > the printer specific language. > > The problem still remains: the PDF file is not able to be printed > properly, it can be either because of a corrupted file (badly-crafted), a > problem with the driver (that is not able to interpret the code of the > file) an error in CUPS, a problem within the application used to display > the file... to solve the problem we have to start discarding all these > things. The OP has a PCL error on one machine. It is legitimate to use a PPD file producing PostScript to see if it resolves the problem. Converting the input file to PostScript before sending it to CUPS is something entirely different and of doubtful merit. > > I wasn't concerned with speed as such but with your giving this as a > > reason for saying '. . . no conversion is needed between the doc and the > > printer' for a PS file. > > When you are using a PPD which defines the capabilities of the printer > and how it has to behave and both (printer harwdare and printer driver) > "speak" a standard language (like PostScript) you're reducing the chances > for an error than when using any other emulated language such as PCL, > simply because PS is not device-dependant, but PCL is, meaning -for the > latter- that you completely rely on the printer's capablities and how your > device interprets the job you are sending to it. The standard language used for printing in Debian has been PDF for over three years. There is no inherent benefit in inputting a PostScript file to CUPS. You are also confusing the input file with the file sent by a CUPS backend to the printer. In the latter case, you reply completely on the capabilities of the printer's interpreters whether the file contains PostScript, PCL or any other language. -- 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/20120526120116.GN2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 19:45:47 +0100, Brian wrote:
> On Fri 25 May 2012 at 17:17:53 +, Camaleón wrote:
>
>> On Fri, 25 May 2012 19:02:36 +0200, Joost Kraaijeveld wrote:
>>
>> > It fails on all PDFs
>>
>> That sounds very strange...
>
> But important, do you not think, because the result is consistent.
Not sure what it means, it can point to:
1/ A problem within CUPS / drivers
2/ A problem within the program he uses to print the files
However... it makes no sense that works in one computer and fails in the
other given that both share the same configuration and print the same
files to the same printer.
>> > and I run the short test by printing page 1 of the Advanced Bas
>> > h−Scripting Guide.
>>
>> Try and put here the results of:
>>
>> 1/ Converting the PDF into a PS file (still don't?) ;-)
>
> Suppose this extra conversion works: where does he go from there?
> Condemned for ever to always convert PDF to PS for every application he
> uses. :) The Flying Dutchman of Debian printing (sorry).
He should go to bugzilla, of course, where CUPS and printer experts are
and with the results of the done tests and their results, what else? ;-)
>> 2/ Also, you can try to send the PDF job directly to the printer's
>> queue ("lp -d hp2200 your_file.pdf")
>
> This is essentially no different from the command used to print from
> most desktop applications.
You don't know what are the extra options every application adds when
sends a job to the queue... we are "testing" and that's how the tests
need to be done.
>> 3/ Use a generic PCL6 driver or try even with the latest PPD file(s)
>> coming from the upstream hplip (3.12.4), i.e., "hp-
>> laserjet_2200_series.ppd" and "hp-laserjet_2200-pcl3.ppd".
>
> Not a method to be discarded. If it works it will mask the problem but
> that may be worthwhile progress for the OP. I do wonder, though, whether
> the upstream PPD files are more up-to-date or bug-free than the ones in
> Debian.
The version of the PPD files are printed in the same files. Again, trying
won't harm.
Greetings,
--
Camaleón
--
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/jpqaok$dh7$5...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 18:51:16 +0100, Brian wrote: > On Fri 25 May 2012 at 16:56:51 +, Camaleón wrote: > >> On Fri, 25 May 2012 17:22:11 +0100, Brian wrote: >> >> > I suggest you have a look at how CUPS works. This statement is >> > exactly the opposite of what happens when a PostScript job is >> > submitted. >> >> How is that? Both, printer and driver, share the same language. > > Not quite. The PPD file/driver combination has to produce a file which, > when sent to the printer, is understandable by the printer. The > Gutenprint driver. for example, will always send PCL to an HP2200 > because, even though the printer can understand PostScript, the driver > is designed to output only in the native language of the printer. But that only happens when the printer does not natively support PS which does not seem to be the case; according to the printer specs¹ it features HP PCL 6, HP PCL 5e and HP Postscript Level 2 emulation. > CUPS in Debian turns any input file into PDF, apart from a PDF file, of > course. A PostScript file is filtered first by pstopdf, then by > pdftopdf. A PDF file would only be filtered by pdftopdf. If the PPD file > tells CUPS the printer wants PostScript it uses pdftops. Otherwise, > there are other filters for converting the PDF coming from pdftopdf into > the printer specific language. The problem still remains: the PDF file is not able to be printed properly, it can be either because of a corrupted file (badly-crafted), a problem with the driver (that is not able to interpret the code of the file) an error in CUPS, a problem within the application used to display the file... to solve the problem we have to start discarding all these things. >> I've always understood (and that's also my own experience) is the >> opposite. Even in windows, a PS driver it takes longer to proceed with >> the job because PS uses a very descriptive and detailed language. > > I wasn't concerned with speed as such but with your giving this as a > reason for saying '. . . no conversion is needed between the doc and the > printer' for a PS file. When you are using a PPD which defines the capabilities of the printer and how it has to behave and both (printer harwdare and printer driver) "speak" a standard language (like PostScript) you're reducing the chances for an error than when using any other emulated language such as PCL, simply because PS is not device-dependant, but PCL is, meaning -for the latter- that you completely rely on the printer's capablities and how your device interprets the job you are sending to it. ¹http://h2.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=28861&prodTypeId=18972&prodSeriesId=28861&objectID=bpl10417#A3 Greetings, -- Camaleón -- 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/jpq9g6$dh7$3...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 17:17:53 +, Camaleón wrote:
> On Fri, 25 May 2012 19:02:36 +0200, Joost Kraaijeveld wrote:
>
> > It fails on all PDFs
>
> That sounds very strange...
But important, do you not think, because the result is consistent.
> > and I run the short test by printing page 1 of the Advanced Bas
> > h−Scripting Guide.
>
> Try and put here the results of:
>
> 1/ Converting the PDF into a PS file (still don't?) ;-)
Suppose this extra conversion works: where does he go from there?
Condemned for ever to always convert PDF to PS for every application he
uses. :) The Flying Dutchman of Debian printing (sorry).
> 2/ Also, you can try to send the PDF job directly to the printer's queue
> ("lp -d hp2200 your_file.pdf")
This is essentially no different from the command used to print from
most desktop applications.
> 3/ Use a generic PCL6 driver or try even with the latest PPD file(s)
> coming from the upstream hplip (3.12.4), i.e., "hp-
> laserjet_2200_series.ppd" and "hp-laserjet_2200-pcl3.ppd".
Not a method to be discarded. If it works it will mask the problem but
that may be worthwhile progress for the OP. I do wonder, though, whether
the upstream PPD files are more up-to-date or bug-free than the ones in
Debian.
--
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/20120525184547.GL2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 18:40:52 +0200, Joost Kraaijeveld wrote: > On vr, 2012-05-25 at 16:52 +0100, Brian wrote: > > What do you mean by 'machine-dependent file'? > > A file that is generated install-time, that adapts an installation to > the machine. E.g. whether a certain machine has or has not installed > packages. I do not think there is anything of that nature in the cups-filters and cups packages, but I haven't looked at the preinst and postinst files. -- 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/20120525180547.GK2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 16:56:51 +, Camaleón wrote: > On Fri, 25 May 2012 17:22:11 +0100, Brian wrote: > > > I suggest you have a look at how CUPS works. This statement is exactly > > the opposite of what happens when a PostScript job is submitted. > > How is that? Both, printer and driver, share the same language. Not quite. The PPD file/driver combination has to produce a file which, when sent to the printer, is understandable by the printer. The Gutenprint driver. for example, will always send PCL to an HP2200 because, even though the printer can understand PostScript, the driver is designed to output only in the native language of the printer. CUPS in Debian turns any input file into PDF, apart from a PDF file, of course. A PostScript file is filtered first by pstopdf, then by pdftopdf. A PDF file would only be filtered by pdftopdf. If the PPD file tells CUPS the printer wants PostScript it uses pdftops. Otherwise, there are other filters for converting the PDF coming from pdftopdf into the printer specific language. > I've always understood (and that's also my own experience) is the > opposite. Even in windows, a PS driver it takes longer to proceed with > the job because PS uses a very descriptive and detailed language. I wasn't concerned with speed as such but with your giving this as a reason for saying '. . . no conversion is needed between the doc and the printer' for a PS file. -- 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/20120525175116.GJ2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 19:02:36 +0200, Joost Kraaijeveld wrote:
> On vr, 2012-05-25 at 16:56 +, Camaleón wrote:
>> Running the test won't hurt and anyway, he still did not say if the
>> file is the same in both computers nor if all the PDFs are failing, or
>> maybe I missed that reply.
> It fails on all PDFs
That sounds very strange...
> and I run the short test by printing page 1 of the Advanced Bas
> h−Scripting Guide.
Try and put here the results of:
1/ Converting the PDF into a PS file (still don't?) ;-)
2/ Also, you can try to send the PDF job directly to the printer's queue
("lp -d hp2200 your_file.pdf")
3/ Use a generic PCL6 driver or try even with the latest PPD file(s)
coming from the upstream hplip (3.12.4), i.e., "hp-
laserjet_2200_series.ppd" and "hp-laserjet_2200-pcl3.ppd".
Greetings,
--
Camaleón
--
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/jpoes1$4v3$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On vr, 2012-05-25 at 16:56 +, Camaleón wrote: > Running the test won't hurt and anyway, he still did not say if the file > is the same in both computers nor if all the PDFs are failing, or maybe I > missed that reply. It fails on all PDFs and I run the short test by printing page 1 of the Advanced Bash−Scripting Guide. -- Met vriendelijke groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1337965356.4896.6.ca...@asterix.askesis.nl
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 17:22:11 +0100, Brian wrote: > On Fri 25 May 2012 at 15:59:55 +, Camaleón wrote: > >> On Fri, 25 May 2012 16:45:06 +0100, Brian wrote: >> >> > The native language of the printer is PCL but it also has a >> > PostScript interpreter. It is happy to be given a file in either >> > language. >> >> PostScript is a raw language, no conversion is needed between the doc >> and the printer, > > I suggest you have a look at how CUPS works. This statement is exactly > the opposite of what happens when a PostScript job is submitted. How is that? Both, printer and driver, share the same language. > >> that's why is better that PCL (should the printer >> includes >> native support for it) although I use the latter because is faster. > > No. Please see above. I've always understood (and that's also my own experience) is the opposite. Even in windows, a PS driver it takes longer to proceed with the job because PS uses a very descriptive and detailed language. >> > The first thing CUPS will do when it sees the PS file is convert it >> > to PDF, so I'm not sure that will tell us anything interesting. >> > However, it would be good to know whether the same difference in >> > behaviour happens with other files. >> >> I have experienced a similar problem when printing PDF files that were >> badly or poorly encoded. Converting the files to a different "language" >> (thus avoinding the source of the error) solved the problem. But that >> can happen only for specific-crafted PDF files so YMMV depending on the >> application it was used to generate the PDF files. > > The OP has no problem with printing the file from one machine. It is the > other, 'identical' machine which is troubling him in a particular way. > Anecdotal evidence may not help him reach a solution. Running the test won't hurt and anyway, he still did not say if the file is the same in both computers nor if all the PDFs are failing, or maybe I missed that reply. Greetings, -- Camaleón -- 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/jpodki$4v3$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On vr, 2012-05-25 at 16:52 +0100, Brian wrote: > What do you mean by 'machine-dependent file'? A file that is generated install-time, that adapts an installation to the machine. E.g. whether a certain machine has or has not installed packages. Although the packages on the machines are the same, the installations and updates did not occur in the same order and may not be done with the same answers to upgrade questions. And both machines started as a Debian SARGE TESTING somewhere in time... I will try your debug tip shortly. Thanks. -- Met vriendelijke groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1337964052.4896.4.ca...@asterix.askesis.nl
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 15:59:55 +, Camaleón wrote: > On Fri, 25 May 2012 16:45:06 +0100, Brian wrote: > > > The native language of the printer is PCL but it also has a PostScript > > interpreter. It is happy to be given a file in either language. > > PostScript is a raw language, no conversion is needed between the doc and > the printer, I suggest you have a look at how CUPS works. This statement is exactly the opposite of what happens when a PostScript job is submitted. > that's why is better that PCL (should the printer includes > native support for it) although I use the latter because is faster. No. Please see above. > > The first thing CUPS will do when it sees the PS file is convert it to > > PDF, so I'm not sure that will tell us anything interesting. However, it > > would be good to know whether the same difference in behaviour happens > > with other files. > > I have experienced a similar problem when printing PDF files that were > badly or poorly encoded. Converting the files to a different > "language" (thus avoinding the source of the error) solved the problem. > But that can happen only for specific-crafted PDF files so YMMV depending > on the application it was used to generate the PDF files. The OP has no problem with printing the file from one machine. It is the other, 'identical' machine which is troubling him in a particular way. Anecdotal evidence may not help him reach a solution. -- 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/20120525162211.GI2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 16:45:06 +0100, Brian wrote: > On Fri 25 May 2012 at 15:18:50 +, Camaleón wrote: > >> On Fri, 25 May 2012 17:05:15 +0200, Joost Kraaijeveld wrote: >> >> > And I am not sure, but I seem to remember that it used to be PS that >> > was the default. >> >> A postscript printer will be happier with a postcript driver though in >> linux you will experience a noticeable delay when using a PS driver for >> printing complex documents. > > The native language of the printer is PCL but it also has a PostScript > interpreter. It is happy to be given a file in either language. PostScript is a raw language, no conversion is needed between the doc and the printer, that's why is better that PCL (should the printer includes native support for it) although I use the latter because is faster. >> > Anyway, with PS I have the same problem. I suspect that some machine >> >-dependent file is not correct. I have compared (the size of) the >> >files >> > on both disks that are in the deb files and they seem to be the same. >> >> Have you tried by converting the PDF file to a PS? And what happens >> with a different PDF file or the error happens with *any* PDF file? > > The first thing CUPS will do when it sees the PS file is convert it to > PDF, so I'm not sure that will tell us anything interesting. However, it > would be good to know whether the same difference in behaviour happens > with other files. I have experienced a similar problem when printing PDF files that were badly or poorly encoded. Converting the files to a different "language" (thus avoinding the source of the error) solved the problem. But that can happen only for specific-crafted PDF files so YMMV depending on the application it was used to generate the PDF files. Greetings, -- Camaleón -- 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/jpoa9r$4v3$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 17:05:15 +0200, Joost Kraaijeveld wrote: > On Fri, 2012-05-25 at 14:53 +, Camaleón wrote: > > > > Are you sure that's the recommended driver for your device? The printer > > seems to support PS as well as PCL6 so using lj5gray can make the job > > output slower and has less options available to configure :-? > > It is the driver that the GUI says that it is the default. And I am not > sure, but I seem to remember that it used to be PS that was the default. > Anyway, with PS I have the same problem. I suspect that some > machine-dependent file is not correct. I have compared (the size of) the > files on both disks that are in the deb files and they seem to be the > same. Generic PostScript and Generic PCL are other drivers which work - you don't have to use something which says 'default'. There is also a Gutenprint driver. If they can clear up your issue, well and good. What do you mean by 'machine-dependent file'? -- 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/20120525155217.GH2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 15:18:50 +, Camaleón wrote: > On Fri, 25 May 2012 17:05:15 +0200, Joost Kraaijeveld wrote: > > > And I am not sure, but I seem to remember that it used to be PS that > > was the default. > > A postscript printer will be happier with a postcript driver though in > linux you will experience a noticeable delay when using a PS driver for > printing complex documents. The native language of the printer is PCL but it also has a PostScript interpreter. It is happy to be given a file in either language. > > Anyway, with PS I have the same problem. I suspect that some machine > >-dependent file is not correct. I have compared (the size of) the files > > on both disks that are in the deb files and they seem to be the same. > > Have you tried by converting the PDF file to a PS? And what happens with > a different PDF file or the error happens with *any* PDF file? The first thing CUPS will do when it sees the PS file is convert it to PDF, so I'm not sure that will tell us anything interesting. However, it would be good to know whether the same difference in behaviour happens with other files. -- 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/20120525154506.GG2847@desktop
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 17:05:15 +0200, Joost Kraaijeveld wrote: > On Fri, 2012-05-25 at 14:53 +, Camaleón wrote: >> On Fri, 25 May 2012 14:39:01 +0200, Joost Kraaijeveld wrote: >> >> > I have 2 identical Wheezy machines: they both have the same packages >> > and the same versions for those packages Wheezy, up to date as of >> > this morning). The configuration files in /etc/cups and /etc/foomatic >> > are exactly identical. Both machines should print to a network >> > printer (HP2200 DTN). I use Cups and Foomatic, and the recommended >> > "HP LaserJet 2200 Foomatic/lj5gray" driver (the postscript driver has >> > the same behaviour). >> >> Are you sure that's the recommended driver for your device? The printer >> seems to support PS as well as PCL6 so using lj5gray can make the job >> output slower and has less options available to configure :-? > It is the driver that the GUI says that it is the default. GUIs can lie... I mean, they try to do their best but often they offer to the user what they have, not what's the best. > And I am not sure, but I seem to remember that it used to be PS that > was the default. A postscript printer will be happier with a postcript driver though in linux you will experience a noticeable delay when using a PS driver for printing complex documents. > Anyway, with PS I have the same problem. I suspect that some machine >-dependent file is not correct. I have compared (the size of) the files > on both disks that are in the deb files and they seem to be the same. Have you tried by converting the PDF file to a PS? And what happens with a different PDF file or the error happens with *any* PDF file? Greetings, -- Camaleón -- 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/jpo7sq$4v3$1...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 2012-05-25 at 14:53 +, Camaleón wrote: > On Fri, 25 May 2012 14:39:01 +0200, Joost Kraaijeveld wrote: > > > I have 2 identical Wheezy machines: they both have the same packages and > > the same versions for those packages Wheezy, up to date as of this > > morning). The configuration files in /etc/cups and /etc/foomatic are > > exactly identical. Both machines should print to a network printer > > (HP2200 DTN). I use Cups and Foomatic, and the recommended "HP LaserJet > > 2200 Foomatic/lj5gray" driver (the postscript driver has the same > > behaviour). > > Are you sure that's the recommended driver for your device? The printer > seems to support PS as well as PCL6 so using lj5gray can make the job > output slower and has less options available to configure :-? It is the driver that the GUI says that it is the default. And I am not sure, but I seem to remember that it used to be PS that was the default. Anyway, with PS I have the same problem. I suspect that some machine-dependent file is not correct. I have compared (the size of) the files on both disks that are in the deb files and they seem to be the same. -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1337958315.4419.32.ca...@panoramix.askesis.nl
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 14:39:01 +0200, Joost Kraaijeveld wrote: > I have 2 identical Wheezy machines: they both have the same packages and > the same versions for those packages Wheezy, up to date as of this > morning). The configuration files in /etc/cups and /etc/foomatic are > exactly identical. Both machines should print to a network printer > (HP2200 DTN). I use Cups and Foomatic, and the recommended "HP LaserJet > 2200 Foomatic/lj5gray" driver (the postscript driver has the same > behaviour). Are you sure that's the recommended driver for your device? The printer seems to support PS as well as PCL6 so using lj5gray can make the job output slower and has less options available to configure :-? > Both machines print the Linux test page without problems. But one > machine cannot print PDFs while the other one prints them without > problem, be it a little slow (i.e. compared to the Windows machines that > use the same printer). Are you testing with the same PDF file? Do other PDF files fail in the same way? > The problematic machine prints a PDF file as an almost empty pages with > the following text: "PCL CL error > Subsystem: IMAGE > Error: ExtraData > Operator: ReadImage > Position: 7" > I have re-installed/purged/rebooted etc. and nothing helped so far. > > Does anyone recognises this problem? Which *machine-dependent* files > exist and in which directory are there, after an > installation/configuration? Anyone any ideas? Try to convert the PDF to a PS file (from the GNOME or KDE virtual printer service), open the PS and print from there. Some PDF files are badly encoded and thus more prone to make the printer to "halt". Greetings, -- Camaleón -- 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/jpo6dt$4v3$8...@dough.gmane.org
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 25 May 2012 14:39:01 +0200 Joost Kraaijeveld wrote: [...] > use the same printer). The problematic machine prints a PDF file as an > almost empty pages with the following text: > "PCL CL error > Subsystem: IMAGE > Error: ExtraData > Operator: ReadImage > Position: 7" > I have re-installed/purged/rebooted etc. and nothing helped so far. > > Does anyone recognises this problem? Which *machine-dependent* files > exist and in which directory are there, after an > installation/configuration? Anyone any ideas? > > TIA Could it be a corrupted file on that machine ? -- keith -- 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/20120525141753.9280647e9df355198c2d2...@gmail.com
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri 25 May 2012 at 14:39:01 +0200, Joost Kraaijeveld wrote: > I have 2 identical Wheezy machines: they both have the same packages and > the same versions for those packages Wheezy, up to date as of this > morning). The configuration files in /etc/cups and /etc/foomatic are > exactly identical. Both machines should print to a network printer If there is problem with one machine not printing correctly I'd be tempted to think the machines are not identical. > (HP2200 DTN). I use Cups and Foomatic, and the recommended "HP LaserJet > 2200 Foomatic/lj5gray" driver (the postscript driver has the same > behaviour). Coincidence! I have the same machine. > > Both machines print the Linux test page without problems. But one > machine cannot print PDFs while the other one prints them without > problem, be it a little slow (i.e. compared to the Windows machines that > use the same printer). The problematic machine prints a PDF file as an > almost empty pages with the following text: > "PCL CL error > Subsystem: IMAGE > Error: ExtraData > Operator: ReadImage > Position: 7" > I have re-installed/purged/rebooted etc. and nothing helped so far. Edit /etc/cups/cupsd.conf and put 'LogLevel debug' at the end. Delete or move /var/log/cups/error_log and restart cups. Print the same PDF from each machine and compare the logs. -- 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/20120525130924.GE2847@desktop
OT: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 2012-05-25 at 14:53 +0200, Joost Kraaijeveld wrote: > And for those thinking about sacrificing a goat: done that already. It > made the first machine work, not the second one. Two machines, but one goat only? A second goat? A virgin? At a special time, e.g. at full moon only? And so on and so forth ;) -- 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/1337950792.2251.105.camel@precise
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
On Fri, 2012-05-25 at 14:48 +0200, Juan Sierra Pons wrote: > Hi, > > I had a similar problem long time ago I don't remember if the error > message was the same > > But I solved it stopping and unplugging the printer for a while > (30 sec should be enough) > > Its sound silly but it worked. :) In effect that is what I do every day every day (the problem exist for some time already and now it is getting in my way). And for those thinking about sacrificing a goat: done that already. It made the first machine work, not the second one. -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1337950404.4419.22.ca...@panoramix.askesis.nl
Re: Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
2012/5/25 Joost Kraaijeveld : > Hi, > > I have 2 identical Wheezy machines: they both have the same packages and > the same versions for those packages Wheezy, up to date as of this > morning). The configuration files in /etc/cups and /etc/foomatic are > exactly identical. Both machines should print to a network printer > (HP2200 DTN). I use Cups and Foomatic, and the recommended "HP LaserJet > 2200 Foomatic/lj5gray" driver (the postscript driver has the same > behaviour). > > Both machines print the Linux test page without problems. But one > machine cannot print PDFs while the other one prints them without > problem, be it a little slow (i.e. compared to the Windows machines that > use the same printer). The problematic machine prints a PDF file as an > almost empty pages with the following text: > "PCL CL error > Subsystem: IMAGE > Error: ExtraData > Operator: ReadImage > Position: 7" > I have re-installed/purged/rebooted etc. and nothing helped so far. > > Does anyone recognises this problem? Which *machine-dependent* files > exist and in which directory are there, after an > installation/configuration? Anyone any ideas? > > TIA > > -- > Groeten, > > Joost Kraaijeveld > Askesis B.V. > Molukkenstraat 14 > 6524NB Nijmegen > tel: 024-3888063 / 06-51855277 > fax: 024-3608416 > web: www.askesis.nl > > > -- > 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/1337949541.4419.19.ca...@panoramix.askesis.nl > Hi, I had a similar problem long time ago I don't remember if the error message was the same But I solved it stopping and unplugging the printer for a while (30 sec should be enough) Its sound silly but it worked. :) Best regards -- Juan Sierra Pons j...@elsotanillo.net Linux User Registered: #257202 http://www.elsotanillo.net GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -- -- 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/CABS=y9s3ujk6e0jgozq9dgo9pcmawpekn4ng3a6pytxyp9u...@mail.gmail.com
Wheezy printing problem: 2 identical (?) machines and 1 does not print PDFs
Hi, I have 2 identical Wheezy machines: they both have the same packages and the same versions for those packages Wheezy, up to date as of this morning). The configuration files in /etc/cups and /etc/foomatic are exactly identical. Both machines should print to a network printer (HP2200 DTN). I use Cups and Foomatic, and the recommended "HP LaserJet 2200 Foomatic/lj5gray" driver (the postscript driver has the same behaviour). Both machines print the Linux test page without problems. But one machine cannot print PDFs while the other one prints them without problem, be it a little slow (i.e. compared to the Windows machines that use the same printer). The problematic machine prints a PDF file as an almost empty pages with the following text: "PCL CL error Subsystem: IMAGE Error: ExtraData Operator: ReadImage Position: 7" I have re-installed/purged/rebooted etc. and nothing helped so far. Does anyone recognises this problem? Which *machine-dependent* files exist and in which directory are there, after an installation/configuration? Anyone any ideas? TIA -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl -- 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/1337949541.4419.19.ca...@panoramix.askesis.nl
Cups Printing problem with USB to Parallel printer Cable
Debian Users I have been plagued with an annoying problems with cups lately. I have to unplug the usb cable every time I try to print from X and then the console. I finally found what is causing this but not where the problem is. This is on Sid and on Wheezy/Testing. Here is what I found. On boot-up the lp looks like this: wtopa@dj:~$ ls -lR /dev/bus/usb/003 crw-rw-r-T 1 root root 189, 256 Feb 27 04:22 001 crw-rw-r-T 1 root lp 189, 261 Feb 27 16:43 002 Printing from the console works for a while then doesn't print. Unplug then pluging the usb shows a change to; wtopa@dj:~$ ls -lR /dev/bus/usb/003 crw-rw-r-T 1 root root 189, 256 Feb 27 04:22 001 crw-rw-r-T 1 root lp 189, 261 Feb 27 16:43 003 If I go to the cups printer page and then click on jobs then select reprint Job, the page sent to the printer from the console will be printed. If I go to mrxvt I can use a2ps to print pages as well. This is a good work-around but not a fix. Repeated unplug/plug of the usb cable shows that the lp perimeter changes fron the starting 002 all the way to 007 before returning to the initial 002. So the 002-004-006 work for printing from the CLI and the odd numbers for X. I suspect the problems is with cups but I am not sure. I am not a udev guru but am trying to see if I can create a rule to correct this PITA problem. Anyone with with udev rule experience have any ides as to how to do this? -- 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/4f4c05cb.4080...@gmail.com
Re: Printing problem in Icedove
Oops, perhaps I confused debian-user-dig...@lists.debian.org with debian-user@lists.debian.org 1. I once claimed that printings were better years ago, but I was mistaken, using Gimp with Gutenprint and some tricks (I'll send those again if I should have randomly send to digest ;) everything is ok here, excepted of this ... On Sun, 2011-07-17 at 14:04 +0200, Ralf Mardorf wrote: > > * To: debian-backpo...@lists.debian.org > > * Subject: Printing problem in Icedove > > * From: Paul van der Vlis > > * Date: Fri, 15 Jul 2011 21:05:56 +0200 > > * Message-id: <4e208f94.2000...@vandervlis.nl> > > > > __ > > Hello, > > > > I am using Icedove with the nl_NL locale. But Icedove wants to use > > "letter" paper. That's wrong, we use "A4" here. My printer does not > > print then, because it has no letter paper. So I have to change the > > setting for every e-mail I print. > > > > With regards, > > Paul. > > Dunno if the mail I've written to Debian user list some minutes ago (not > backports) came through the list. I lauded the Linux printing, but > anyway, I can confirm that I need to manually change to "A4" too, for > any app and btw. I also need to do it for "grayscale" too. > > I forgot to do it for a printing I did some minutes ago and a beautiful > women lost some cm of hear head :D. > > I'm using testing without backports. > > - Ralf -- 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/1310904588.7440.13.camel@debian
Re: Printing problem jpeg file size gets multiplied???
On Mon, 11 Jul 2011 16:25:48 -0500, Jack Schneider wrote: > I have two jpeg files on my desktop. Both show correct file sizes in > Properties. Running Debian Squeeze Up2date. Printer is Lexmark C540 > Xl, printer properties shows connected to printer. via my local network. > > Using Gthumb to print, it sends to queue and hangs... never prints... > Lexmark printer eventually goes to "powersave mode" top of list is > "processing" > Looking at queue for one image shows a file size of > 25megs for a 2.2 > meg jpeg file. Both file sizes seem to be up by a factor of 10 > > Where can I look for a start??? Don't go nuts :-) The real size of your jpeg file does not have nothing to do with the size it turns when you send it to the printer and then queued. What you see in the printer queue is the result of the job processing that depends to the printer driver in use, the complexity of the file (text renders faster than images), selected quality setting (300 dpi goes faster than 1200 dpi), and all that. Try by reducing the output quality and if you can or test with another driver (i.e., if you have a PS printer and currently using a PS driver, try with PCL6, Poscript is very very slw in linux :-P). Also, check if there is any PPD updated file available for your printer model. Greetings, -- Camaleón -- 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/pan.2011.07.12.17.53...@gmail.com
Printing problem jpeg file size gets multiplied???
Hi, All I have two jpeg files on my desktop. Both show correct file sizes in Properties. Running Debian Squeeze Up2date. Printer is Lexmark C540 Xl, printer properties shows connected to printer. via my local network. Using Gthumb to print, it sends to queue and hangs... never prints... Lexmark printer eventually goes to "powersave mode" top of list is "processing" Looking at queue for one image shows a file size of > 25megs for a 2.2 meg jpeg file. Both file sizes seem to be up by a factor of 10 Where can I look for a start??? TIA, Jack -- 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/20110711162548.71aa765f@Speeduke
Printing problem, lenny, xfce, galeon, gnome, xprint
I'm having difficulty getting Galeon to print web pages. (I can print from Iceweasel and Emacs, so this can't be something grossly stupid like failure to start CUPS.) I am running Lenny with the 'alternative' windowing/desktop environment Xfce4, which was installed by using netinstall CD. Galeon complained that environment variable XPSERVERLIST contains no print servers, and it appeared in my simple investigation that this variable was undefined. I found a print-setup link in the xfce settings menu and set it to CUPS, and I have installed the package xprint, but still have a problem. Galeon still gives the same error message, but now there is an XPSERVERLIST variable and it contains the string ':64 ' This doesn't look like a print server selection to me, so I suppose I have some configuration to do, but where? (Remember printing is working for Iceweasel and Emacs, both running in the windowing/desktop environment.) I could try typing in may own definition of XPSERVERLIST, but I can't find documentation of the precise format of a server selection line. I think something should have been set up automagically by one of the packages that I have installed, but which one should be responsible? Many gnome packages were automatically installed when I installed Galeon, but I am not running Gnome and don't see a way to access the Gnome configuration system. (also I don't really want to run Gnome) Suggestions, please. -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
panasonic kxp-1123 printing problem
A friend and me used linuxprinting.org and openprinting.org and have foomatic and cups and the ppd file for this printer on my machine. I got new ink cartridges for this printer from databaazar.com and we can make the printer do the self-test externally but even after foomatic is given the location of my new ppd file and foomatic updated configurations to what's in that file there two things this printer won't do. You can't print a test page within linux g.u.i. interface and while trying to print garden variety text pages the printer only prints garbage none of which is in the files being printed. So where to go from here? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem(s) (SOLVED)
Andrew Malcolmson wrote: Wayne Topa-4 wrote: Has anyone got a clue as to where I should look? Perhaps: sudo aptitude purge cups #check for any cups packages left and purge them if any are found sudo aptitude search cups~i #Search your user's home folder for any remaining cups settings sudo aptitude clean sudo aptitude update sudo aptitude install cups Thank you Andrew! After deleting the cups packages and running update/locate to see if there were any cups files around, I found 2 .cups dirs. One on /root and one on ~user. In those dir,s there was a client.conf file which had the Old print server address. This box was built, by a vendor, in 2006 and it must have been there all this time. They specialized in Red Hat so maybe that is a RH thingy. I rgreped both of those dirs and never had that directory come up. Thanks for the suggestion to remove the cups packages otherwise I would still be pulling my hair out. Many Thanks a Best Regards Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem(s)
Wayne Topa-4 wrote: > > > Has anyone got a clue as to where I should look? > Perhaps: sudo aptitude purge cups #check for any cups packages left and purge them if any are found sudo aptitude search cups~i #Search your user's home folder for any remaining cups settings sudo aptitude clean sudo aptitude update sudo aptitude install cups -- View this message in context: http://www.nabble.com/Strange-printing-problem%28s%29-tp23855660p23902246.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem(s)
andmalc wrote:
Wayne Topa-4 wrote:
...
I gave attached the cupsd.conf & client.conf files.
...
LogLevel warning
...
Try changing the log level in cupsd.conf to debug and follow the log while
printing. You may also turn on debug logging by running
sudo cupsctl --debug-logging
More info:
On SID my user is not able to connect to the server, but root can, using
lpstat -t. Root get the list of printers but the user gets
strace lpstat -t
[ends with]
ensocket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
setsockopt(4, SOL_TCP, TCP_NODELAY, [1], 4) = 0
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
connect(4, {sa_family=AF_INET, sin_port=htons(631),
sin_addr=inet_addr("192.168.1.3")}, 16) = -1 EHOSTUNREACH (No route to host)
close(4)= 0
write(2, "lpstat: Unable to connect to ser"..., 36lpstat: Unable to
connect to server
) = 36
exit_group(1)
The addr=inet_addr("192.168.1.3" WAS the old print server. Its gone now
and this box (192.168.1.11) has the printer now.
I have [erz]greped the system and removed/changed all the 192.168.1.3
references to 192.168.1.11 but the strace still shows lpstat trying to
connect to the .3 address. I
On Testing (Squeeze) both the user and root get the above error.
I am not able to find any files with 192.168.1.3 in them, yet the lpstat
command keeps looking for it.
Has anyone got a clue as to where I should look?
TIA
Wayne
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem(s)
andmalc wrote: Wayne Topa-4 wrote: ... I gave attached the cupsd.conf & client.conf files. ... LogLevel warning ... On Sid for these tests Thanks for the reply! Changed the loglevel to debug No entries in the error_log when my user tries to print. There are no errors show there at all regarding a failure to print. (???) Changed the lever to debug 2 and restarted cups. More info in the log but still no errors shown. Tried something different. wt...@dj:~$ sudo a2ps zim_pages.txt [zim_pages.txt (plain): 1 page on 1 sheet] /usr/bin/lp: Error - scheduler not responding! [Total: 1 page on 1 sheet] sent to the default printer Maybe something new added in the 3 months I didn't use this box and I haven't loaded it. Try changing the log level in cupsd.conf to debug and follow the log while printing. You may also turn on debug logging by running sudo cupsctl --debug-logging wt...@dj:~$ sudo cupsctl --debug-logging cupsctl: Unable to connect to server: No route to host It seems that might be why the error_log doesn't show any error. The user account can't get to the cups server. Now to figure out why! I'm going to start a root X session and see if the X apps will print. That should narrow down the problems if that works. Will report back when I get more data. Thanks again!! Wayne -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem(s)
Wayne Topa-4 wrote: > > ... > > I gave attached the cupsd.conf & client.conf files. > ... > LogLevel warning > ... > Try changing the log level in cupsd.conf to debug and follow the log while printing. You may also turn on debug logging by running sudo cupsctl --debug-logging -- View this message in context: http://www.nabble.com/Strange-printing-problem%28s%29-tp23855660p23872115.html Sent from the Debian User mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Strange printing problem(s)
I am having a problem with cups, again, and hope that someone here may be able to save my sanity. I had my AMD64 box die about 3 months ago and have just recently revived it. It is a 3 dist box with squeeze and sid up to date so far but having different printing problems. Printing was working normally when this box went down. Below is what upgrading introduced. I must have screwed up something but am unable to figure out what has changed. The hardware interface changed from serial db9 to a usb/rs232 converter SID Did an aptitude update/upgrade yesterday. Using cups I can print using 'Print Test Page" Ok but can not print from Iceweasel, IceDove, adobe/Xpdf as a user. Root can print from the CLI using a2ps or lpr but I can not print from my user account or get lpstat -t to show the installed printers that it shows when root runs it, ie: r...@dj:/home/wtopa# lpstat -t scheduler is running system default destination: HP6P device for 6P: usb://HP/LaserJet%206P device for Cups-Pdf: cups-pdf:/ device for HP6P: usb://HP/LaserJet%206P 6P accepting requests since Wed 03 Jun 2009 12:41:33 PM EDT Cups-Pdf accepting requests since Sun 17 May 2009 02:20:56 PM EDT HP6P accepting requests since Sun 31 May 2009 07:31:51 PM EDT printer 6P is idle. enabled since Wed 03 Jun 2009 12:41:33 PM EDT printer Cups-Pdf is idle. enabled since Sun 17 May 2009 02:20:56 PM EDT printer HP6P is idle. enabled since Sun 31 May 2009 07:31:51 PM EDT The user is in the lp and lpadmin groups. wt...@dj:~$ lpstat -t lpstat: Unable to connect to server SQUEEZE Using the same cupsd.conf and client.conf that SID is using, the X print problems are the same as on Sid. On the console lpstat-t does not work for anyone. I gave attached the cupsd.conf & client.conf files. Any pointers appriciated. Wayne ServerName 127.0.0.1 LogLevel warning SystemGroup lpadmin # Allow remote access Port 631 Listen localhost:631 #Listen 192.168.1.11:631 Listen /var/run/cups/cups.sock # Enable printer sharing and shared printers. Browsing On BrowseOrder allow,deny BrowseAllow @LOCAL BrowseAddress @LOCAL DefaultAuthType Basic #DefaultEncription IfRequested # Allow shared printing... Order allow,deny Allow all Allow wtopa #Encryption Required # Restrict access to the admin pages... Order allow,deny Allow root allow wtopa Allow localhost AuthType Default Require user @SYSTEM # Restrict access to the configuration files... AuthType Basic Require user @SYSTEM Order allow,deny Allow root Allow wtopa Allow localhost Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow Require user @OWNER @SYSTEM Order deny,allow Order deny,allow
Strange printing problem(s)
I am having a problem with cups, again, and hope that someone here may be able to save my sanity. I had my AMD64 box die about 3 months ago and have just recently revived it. It is a 3 dist box with squeeze and sid up to date so far but having different printing problems. Printing was working normally when this box went down. Below is what upgrading introduced. I must have screwed up something but am unable to figure out what has changed. The hardware interface changed from serial db9 to a usb/rs232 converter SID Did an aptitude update/upgrade yesterday. Using cups I can print using 'Print Test Page" Ok but can not print from Iceweasel, IceDove, adobe/Xpdf as a user. Root can print from the CLI using a2ps or lpr but I can not print from my user account or get lpstat -t to show the installed printers that it shows when root runs it, ie: r...@dj:/home/wtopa# lpstat -t scheduler is running system default destination: HP6P device for 6P: usb://HP/LaserJet%206P device for Cups-Pdf: cups-pdf:/ device for HP6P: usb://HP/LaserJet%206P 6P accepting requests since Wed 03 Jun 2009 12:41:33 PM EDT Cups-Pdf accepting requests since Sun 17 May 2009 02:20:56 PM EDT HP6P accepting requests since Sun 31 May 2009 07:31:51 PM EDT printer 6P is idle. enabled since Wed 03 Jun 2009 12:41:33 PM EDT printer Cups-Pdf is idle. enabled since Sun 17 May 2009 02:20:56 PM EDT printer HP6P is idle. enabled since Sun 31 May 2009 07:31:51 PM EDT The user is in the lp and lpadmin groups. wt...@dj:~$ lpstat -t lpstat: Unable to connect to server SQUEEZE Using the same cupsd.conf and client.conf that SID is using, the X print problems are the same as on Sid. On the console lpstat-t does not work for anyone. I gave attached the cupsd.conf & client.conf files. Any pointers would surly be appreciated. Wayne ServerName 127.0.0.1 LogLevel warning SystemGroup lpadmin # Allow remote access Port 631 Listen localhost:631 #Listen 192.168.1.11:631 Listen /var/run/cups/cups.sock # Enable printer sharing and shared printers. Browsing On BrowseOrder allow,deny BrowseAllow @LOCAL BrowseAddress @LOCAL DefaultAuthType Basic #DefaultEncription IfRequested # Allow shared printing... Order allow,deny Allow all Allow wtopa #Encryption Required # Restrict access to the admin pages... Order allow,deny Allow root allow wtopa Allow localhost AuthType Default Require user @SYSTEM # Restrict access to the configuration files... AuthType Basic Require user @SYSTEM Order allow,deny Allow root Allow wtopa Allow localhost Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow Require user @OWNER @SYSTEM Order deny,allow Order deny,allow
Re: Strange printing problem in iceweasel -pelase help.
Thank you. But my trouble has nothing to do with printer as I cannot print to a file either. It seems to be a iceweasel problem in printing selected pages. Ramesh Andrew Malcolmson wrote: On Fri, May 8, 2009 at 6:46 PM, Ramasubramanian Ramesh wrote: Can you please tell me why this might be happening and what experiments I can do to further investigate? I tried googling and got nowhere. Take a look at the Ubuntu wiki page on debugging printing issues: https://wiki.ubuntu.com/DebuggingPrintingProblems -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem in iceweasel -pelase help.
On Fri, May 8, 2009 at 6:46 PM, Ramasubramanian Ramesh wrote: > Can you please tell me why this might be happening and what experiments I > can do to further investigate? I tried googling and got nowhere. > Take a look at the Ubuntu wiki page on debugging printing issues: https://wiki.ubuntu.com/DebuggingPrintingProblems -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Strange printing problem in iceweasel -pelase help.
Can you please tell me why this might be happening and what experiments I can do to further investigate? I tried googling and got nowhere. Ramesh Ramasubramanian Ramesh wrote: I run lenny amd64 and standard iceweasel package. I am having difficulty in printing *some* secure (https) pages. I am not sure what causes it, but I think it does not print if there is only one page to print. Th result is the same regardless of whether I print to the printer directly or to a file. When I print to a file, the resulting postscript file has basic control text but nothing to display. The same with pdf file. Can any one help? Ramesh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Strange printing problem in iceweasel
I run lenny amd64 and standard iceweasel package. I am having difficulty in printing *some* secure (https) pages. I am not sure what causes it, but I think it does not print if there is only one page to print. Th result is the same regardless of whether I print to the printer directly or to a file. When I print to a file, the resulting postscript file has basic control text but nothing to display. The same with pdf file. Can any one help? Ramesh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
On Jan 1, 4:50 pm, Ken Irving wrote: > On Thu, Jan 01, 2009 at 08:07:55AM -0500, Zach Uram wrote: > > I have exhausted every solution I could find :( As a last resort I > > tried running lpadmin to set the printer manually and I get that > > stupid ambiguous error message again, same one I got in the cups web > > interface. Does anyone know what this error message means and how I > > can get my printer (HP Deskjet 960C hooked up to parallel port) setup > > using lpadmin: > > > z...@hal9000:~$ sudo lpadmin -h localhost -p HP -D printer -u > > allow:zu22 -P /rofs/usr/share/cups/model/hpijs/HP/HP-DeskJet_960C-hpijs.ppd > > lpadmin: Request Entity Too Large > > I haven't been following this thread, but just to toss out a few > random thoughts... > > Googling that error message seems to indicate it's from the web server; > adding CUPS to the google query gives some possible hints, e.g., > > ... CUPS - Request Entity Too Large. If you get this CUPS error, > it may mean that you don't have write permission to your CUPS spool > directory ... > > If you add your user to the lpadmin group it won't take effect until > you log in again. > > In some cases running commands under sudo is not sufficient to give > root privileges to some of the arguments. I don't know why that is, > but suppose it's a matter of how/when the command line is parsed. > In such cases it might work to become root and remove all doubt. > > Here's a look at my cups spool on a working system: > > k...@denali:~$ sudo ls -ld /var /var/spool /var/spool/cups > /var/spool/cups/tmp > drwxr-xr-x 14 root root 4096 2008-08-27 13:03 /var > drwxr-xr-x 6 root root 4096 2008-12-05 14:36 /var/spool > drwx--x--- 3 root lp 4096 2008-12-29 15:42 /var/spool/cups > drwxrwx--T 2 root lp 4096 2008-08-29 14:12 /var/spool/cups/tmp Hi Ken, Here is the output on mine: drwxr-xr-x 10 root root 160 2009-01-01 02:35 /var drwxr-xr-x 6 root root 80 2009-01-01 02:30 /var/spool drwx--x--- 5 cupsys lp60 2008-12-31 18:09 /var/spool/cups drwxrwx--T 4 cupsys lp40 2006-05-17 08:46 /var/spool/cups/tmp Before I ran the lpadmin program I ran "groups" and verified my normal user was in the lpadmin group. I also tried running lpadmin as root and same error occurs. Zach -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
On Jan 1, 3:10 pm, andmalc wrote: > > Did you see/try the suggestion I made in the original thread? > > "Install the printer by running 'hp-setup' as root. Choose the option > for a parallel connection. " There is no hp-setup installed. There is an hp-toolbox but that requires python-qt3 which needs 20MB of disk space which I don't have so I can't try it. Zach -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
On Thu, Jan 01, 2009 at 08:07:55AM -0500, Zach Uram wrote: > I have exhausted every solution I could find :( As a last resort I > tried running lpadmin to set the printer manually and I get that > stupid ambiguous error message again, same one I got in the cups web > interface. Does anyone know what this error message means and how I > can get my printer (HP Deskjet 960C hooked up to parallel port) setup > using lpadmin: > > z...@hal9000:~$ sudo lpadmin -h localhost -p HP -D printer -u > allow:zu22 -P /rofs/usr/share/cups/model/hpijs/HP/HP-DeskJet_960C-hpijs.ppd > lpadmin: Request Entity Too Large I haven't been following this thread, but just to toss out a few random thoughts... Googling that error message seems to indicate it's from the web server; adding CUPS to the google query gives some possible hints, e.g., ... CUPS - Request Entity Too Large. If you get this CUPS error, it may mean that you don't have write permission to your CUPS spool directory ... If you add your user to the lpadmin group it won't take effect until you log in again. In some cases running commands under sudo is not sufficient to give root privileges to some of the arguments. I don't know why that is, but suppose it's a matter of how/when the command line is parsed. In such cases it might work to become root and remove all doubt. Here's a look at my cups spool on a working system: k...@denali:~$ sudo ls -ld /var /var/spool /var/spool/cups /var/spool/cups/tmp drwxr-xr-x 14 root root 4096 2008-08-27 13:03 /var drwxr-xr-x 6 root root 4096 2008-12-05 14:36 /var/spool drwx--x--- 3 root lp 4096 2008-12-29 15:42 /var/spool/cups drwxrwx--T 2 root lp 4096 2008-08-29 14:12 /var/spool/cups/tmp Ken -- Ken Irving -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
On Thu, Jan 1, 2009 at 9:20 AM, Javier Barroso wrote: > Hi, Hi, > Which solutions have you tried ? I tried gnome-cups-manager which calls gnome-cups-add, I tried lpadmin, I tried the cups web interface. > I suppose this is a silly question, but .. has you got free space in > your /var/spool/cups partition ? Yes. I even posted a question on cups.org forum asking what that error means but no one has replied, I asked also in #debian on freenode and no one knows. Zach -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
On Jan 1, 8:30 am, "Zach Uram" wrote: > I have exhausted every solution I could find Did you see/try the suggestion I made in the original thread? "Install the printer by running 'hp-setup' as root. Choose the option for a parallel connection. " -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: update on printing problem
Hi, On Thu, Jan 1, 2009 at 2:07 PM, Zach Uram wrote: > I have exhausted every solution I could find :( Which solutions have you tried ? > z...@hal9000:~$ sudo lpadmin -h localhost -p HP -D printer -u > allow:zu22 -P /rofs/usr/share/cups/model/hpijs/HP/HP-DeskJet_960C-hpijs.ppd > lpadmin: Request Entity Too Large I suppose this is a silly question, but .. has you got free space in your /var/spool/cups partition ? Regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
update on printing problem
I have exhausted every solution I could find :( As a last resort I tried running lpadmin to set the printer manually and I get that stupid ambiguous error message again, same one I got in the cups web interface. Does anyone know what this error message means and how I can get my printer (HP Deskjet 960C hooked up to parallel port) setup using lpadmin: z...@hal9000:~$ sudo lpadmin -h localhost -p HP -D printer -u allow:zu22 -P /rofs/usr/share/cups/model/hpijs/HP/HP-DeskJet_960C-hpijs.ppd lpadmin: Request Entity Too Large Zach -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: GNOME faint printing problem.
On Sun February 10 2008 08:58:15 am Matt Gracie wrote: > I'm running Debian sid on an ia32 computer, with everything up to date, > and printing via CUPS to an HP Laserjet 4m. When I print from GNOME > applications, like evince or epiphany, the output is too faint to read. > But if I print the same document or web page from xpdf or iceweasel, it > prints normally. > > This leads me to believe that the issue is something in the GNOME > environment, but as a recent convert from Windowmaker, I'm not that > familiar with the byzantine underpinnings of a modern desktop > environment. Also, I didn't see anything recent about this problem in > the bug tracker. Is this a known issue? Is there some simple setting > that I'm missing? I get that on a printer at work also. In my case I can set the resolution to 600x600 or 1200x1200 and I get better results. The default 300x300 is ok but if anything is highlighted the color is to light. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
GNOME faint printing problem.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm running Debian sid on an ia32 computer, with everything up to date, and printing via CUPS to an HP Laserjet 4m. When I print from GNOME applications, like evince or epiphany, the output is too faint to read. But if I print the same document or web page from xpdf or iceweasel, it prints normally. This leads me to believe that the issue is something in the GNOME environment, but as a recent convert from Windowmaker, I'm not that familiar with the byzantine underpinnings of a modern desktop environment. Also, I didn't see anything recent about this problem in the bug tracker. Is this a known issue? Is there some simple setting that I'm missing? Thanks for any help, - --Matt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHry0n6wBqCH7pnjIRAqCJAKDEyaG8KKiigb929IvXHLdM5TOpqwCgws1s 4cPSBs3avbyYBewDpEoP2Ss= =/BQg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cups printing problem
On Sun, Sep 02, 2007 at 14:47:52 -0600, Robert Jerrard wrote: > On Sun, 2007-09-02 at 22:03 +0200, Florian Kulzer wrote: > > On Sat, Sep 01, 2007 at 11:43:18 -0600, Robert Jerrard wrote: > > > I have just installed Debian etch from scratch. In attempting to set up > > > the printing the cups printer section tells me: > > > > > > "/usr/lib/cups/backend/http failed" > > > > > > and /var/log/cups/error_log gives: > > > > > > E [01/Sep/2007:10:22:33 -0600] [Job 1] Destination printer does not exist! > > > E [01/Sep/2007:10:22:33 -0600] PID 27798 (/usr/lib/cups/backend/http) > > > stopped with status 4! > > > > > > when using http://localhost:631/ipp/9100 > > > > > > If I try socket://localhost:9100 cups tells me: > > > > > > "Network host 'localhost' is busy; will retry in 5 seconds..." > > > > > > and /var/log/cups/error_log gives: > > > > > > E [01/Sep/2007:11:40:59 -0600] CUPS-Add-Modify-Printer: Unauthorized > > > > > > Any ideas what to try next to get printing to work? > > > > Tell us what printer this is (maker/model) and how it is connected to > > your computer (parallel port, USB, network). > > I have a Xerox Phaser 8500 for which I had a ppd file from Xerox > originally but did not think to save it for the install. Now Xerox no > longer makes it available so I have been trying with a UNIX ppd file and > just a generic postscript printer ppd. I think the correct ppd file is available here: http://www.support.xerox.com/go/getfile.asp?objid=61334 You need to download CupsPrinterPkg2007_May_10.tar and extract XRX_Phaser_8500n.ppd from this archive. This file should replace /etc/cups/ppd/Xerox.ppd. > The printer is connected with an > ethernet connection to a small hub which is connected to my computer > with a network card with address 10.10.11.3, the printer has address > 10.10.11.10. I have another network card connecting my computer to the > internet using dhcp. Can you ping the printer at this address? (10.10.11.10) > > Also, post your /etc/cups/printers.conf. > > # Printer configuration file for CUPS v1.3.0 > # Written by cupsd on 2007-09-02 14:34 > > Info Xerox 8500 > Location home > DeviceURI socket://localhost:9100 > State Idle > StateTime 1188765273 > Accepting Yes > Shared Yes > JobSheets none none > QuotaPeriod 0 > PageLimit 0 > KLimit 0 > OpPolicy default > ErrorPolicy stop-printer > I would expect that one of these DeviceURIs should work: DeviceURI ipp://10.10.11.10 DeviceURI ipp://10.10.11.10/ipp/ DeviceURI socket://10.10.11.10 DeviceURI socket://10.10.11.10:9100 DeviceURI http://10.10.11.10:631 DeviceURI http://10.10.11.10:631/ipp/ Your CUPS server runs on "localhost", but the DeviceURI should point to the network address of the printer. You have to restart cupsys if you change the configuration file. You can also use the "add printer" function of the CUPS frontend (http://localhost:631) to add a new printer with the correct DeviceURI and to select the ppd file from Xerox. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cups printing problem
On Sun, 2007-09-02 at 22:03 +0200, Florian Kulzer wrote: > On Sat, Sep 01, 2007 at 11:43:18 -0600, Robert Jerrard wrote: > > I have just installed Debian etch from scratch. In attempting to set up > > the printing the cups printer section tells me: > > > > "/usr/lib/cups/backend/http failed" > > > > and /var/log/cups/error_log gives: > > > > E [01/Sep/2007:10:22:33 -0600] [Job 1] Destination printer does not > > exist! > > E [01/Sep/2007:10:22:33 -0600] PID 27798 (/usr/lib/cups/backend/http) > > stopped with status 4! > > p > > > > when using http://localhost:631/ipp/9100 > > > > If I try socket://localhost:9100 cups tells me: > > > > "Network host 'localhost' is busy; will retry in 5 seconds..." > > > > and /var/log/cups/error_log gives: > > > > E [01/Sep/2007:11:40:59 -0600] CUPS-Add-Modify-Printer: Unauthorized > > > > Any ideas what to try next to get printing to work? > > Tell us what printer this is (maker/model) and how it is connected to > your computer (parallel port, USB, network). I have a Xerox Phaser 8500 for which I had a ppd file from Xerox originally but did not think to save it for the install. Now Xerox no longer makes it available so I have been trying with a UNIX ppd file and just a generic postscript printer ppd. The printer is connected with an ethernet connection to a small hub which is connected to my computer with a network card with address 10.10.11.3, the printer has address 10.10.11.10. I have another network card connecting my computer to the internet using dhcp. > Also, post your /etc/cups/printers.conf. (This file can contain clear > text passwords of network printers; remove those from your mail if > necessary.) # Printer configuration file for CUPS v1.3.0 # Written by cupsd on 2007-09-02 14:34 Info Xerox 8500 Location home DeviceURI socket://localhost:9100 State Idle StateTime 1188765273 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Thanks for any help or suggestions. Bob Jerrard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cups printing problem
On Sat, Sep 01, 2007 at 11:43:18 -0600, Robert Jerrard wrote: > I have just installed Debian etch from scratch. In attempting to set up > the printing the cups printer section tells me: > > "/usr/lib/cups/backend/http failed" > > and /var/log/cups/error_log gives: > > E [01/Sep/2007:10:22:33 -0600] [Job 1] Destination printer does not > exist! > E [01/Sep/2007:10:22:33 -0600] PID 27798 (/usr/lib/cups/backend/http) > stopped with status 4! > p > > when using http://localhost:631/ipp/9100 > > If I try socket://localhost:9100 cups tells me: > > "Network host 'localhost' is busy; will retry in 5 seconds..." > > and /var/log/cups/error_log gives: > > E [01/Sep/2007:11:40:59 -0600] CUPS-Add-Modify-Printer: Unauthorized > > Any ideas what to try next to get printing to work? Tell us what printer this is (maker/model) and how it is connected to your computer (parallel port, USB, network). Also, post your /etc/cups/printers.conf. (This file can contain clear text passwords of network printers; remove those from your mail if necessary.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Cups printing problem
I have just installed Debian etch from scratch. In attempting to set up the printing the cups printer section tells me: "/usr/lib/cups/backend/http failed" and /var/log/cups/error_log gives: E [01/Sep/2007:10:22:33 -0600] [Job 1] Destination printer does not exist! E [01/Sep/2007:10:22:33 -0600] PID 27798 (/usr/lib/cups/backend/http) stopped with status 4! p when using http://localhost:631/ipp/9100 If I try socket://localhost:9100 cups tells me: "Network host 'localhost' is busy; will retry in 5 seconds..." and /var/log/cups/error_log gives: E [01/Sep/2007:11:40:59 -0600] CUPS-Add-Modify-Printer: Unauthorized Any ideas what to try next to get printing to work? Bob Jerrard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Network printing problem.
On 19/07/07 20:37:22, Florian Kulzer wrote: > On Thu, Jul 19, 2007 at 10:58:13 +0100, Barry Samuels wrote: > > I have two computers at home on a small network both of which are > > connected to a router. Both computers are running Debian Testing. > > Computer A has two ethernet ports one of which is connected to the > > router and one is connected to a network printer. Computer B sends > > its printing jobs to the network printer via the router. > > > > Everything was working well until I upgraded the kernel on computer > > A from 2.6.20.1 to 2.6.22. After that upgrade network printing from > > computer B would no longer work with the message 'waiting for > address> to come up'. The odd thing is that I could ping the > > ethernet port on computer A to which the printer is connect but not > > the printer itself. > > > > Reverting to kernel 2.20.1 on computer A cured the printing problem > > but means that the sensors temperatures that have worked properly > > for the first time with 2.6.22 now cannot be displayed (bother!). > > > > That seems to mean either a bug in kernel 2.6.22 or a new setting > > that I have not set. I did copy my 2.6.20.1 config to 2.6.22 and > > did a make oldconfig. > > > > Any comments, suggestions or revalations please? > > Maybe there was a network-related change in some kernel configuration > options and "make oldconfig" did not take that into account properly. > For example, a missing netfilter module might make your firewall on > Computer A unduly restrictive. Do you see any network or firewall > related error messages in dmesg? > > I would simply try a stock Debian 2.6.22 kernel image (available in > Sid); if that works then you know the problem is the configuration of > your custom kernel. > > -- > Regards,| http://users.icfo.es/Florian.Kulzer > Florian | Florian Thanks for your suggestion. Computer A is normally running 24 hours each day and the last time it would have been re-booted would have been when the new (2.6.22) kernel was installed. Computer B is turned on and off each day. This morning I decided to revert to the 2.6.22 kernel, having been running the 2.6.20.1 kernel since this problem appeared, to try some more investigation. Having re-booted computer A and turned on computer B I find that the printing is now working perfectly again. When the problem first appeared I also tried printing from my laptop which connects via wireless and that couldn't print either so I'm assuming the problem was with computer A. I have no idea what it might have been but it has gone away. Thanks for trying to help. -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: Network printing problem.
On Thu, Jul 19, 2007 at 10:58:13 +0100, Barry Samuels wrote: > I have two computers at home on a small network both of which are > connected to a router. Both computers are running Debian Testing. > > Computer A has two ethernet ports one of which is connected to the > router and one is connected to a network printer. Computer B sends its > printing jobs to the network printer via the router. > > Everything was working well until I upgraded the kernel on computer A > from 2.6.20.1 to 2.6.22. After that upgrade network printing from > computer B would no longer work with the message 'waiting for address> to come up'. The odd thing is that I could ping the ethernet > port on computer A to which the printer is connect but not the printer > itself. > > Reverting to kernel 2.20.1 on computer A cured the printing problem but > means that the sensors temperatures that have worked properly for the > first time with 2.6.22 now cannot be displayed (bother!). > > That seems to mean either a bug in kernel 2.6.22 or a new setting that > I have not set. I did copy my 2.6.20.1 config to 2.6.22 and did a make > oldconfig. > > Any comments, suggestions or revalations please? Maybe there was a network-related change in some kernel configuration options and "make oldconfig" did not take that into account properly. For example, a missing netfilter module might make your firewall on Computer A unduly restrictive. Do you see any network or firewall related error messages in dmesg? I would simply try a stock Debian 2.6.22 kernel image (available in Sid); if that works then you know the problem is the configuration of your custom kernel. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Network printing problem.
I have two computers at home on a small network both of which are connected to a router. Both computers are running Debian Testing. Computer A has two ethernet ports one of which is connected to the router and one is connected to a network printer. Computer B sends its printing jobs to the network printer via the router. Everything was working well until I upgraded the kernel on computer A from 2.6.20.1 to 2.6.22. After that upgrade network printing from computer B would no longer work with the message 'waiting for to come up'. The odd thing is that I could ping the ethernet port on computer A to which the printer is connect but not the printer itself. Reverting to kernel 2.20.1 on computer A cured the printing problem but means that the sensors temperatures that have worked properly for the first time with 2.6.22 now cannot be displayed (bother!). That seems to mean either a bug in kernel 2.6.22 or a new setting that I have not set. I did copy my 2.6.20.1 config to 2.6.22 and did a make oldconfig. Any comments, suggestions or revalations please? -- Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
Re: printing problem - spurious "d" characters, bad pixels,spurious form feeds - SOLVED
IB. wrote: charles norwood wrote: On Thu, 2006-07-06 at 10:27 -0400, Daniel B. wrote: ... Also, given that the spurious characters appear at different places in the printout when I try again suggests that something random is going on (dropped or extra characters in the output stream), which doesn't sound like having the wrong PPD file. Oh--another thing is that since upgrading to Sarge and 2.6.8 (2.6.8-2-k7-smp), trying to print occasionally hangs the entire system. That suggests a problem with the parallel port driver or something closer to that later. Daniel I don't have an answer, but my experience is "random" errors are due to hardware failing. No, I'm pretty sure it's not failing hardware: The hardware worked fine with Woody, kernel 2.4, and the pre-CUPs printing system. And it still works fine when I boot into Windows and print. I found the technical problem. As I hypothesized, it was a problem with the kernel in the parallel port driver. CONFIG_PARPORT_PC_FIFO was enabled. The fact that CONFIG_PARPORT_PC_FIFO is experimental leads to another question: Why the hell did a Debian kernel for the _stable_ release (Sarge) use an _experimental_ kernel option?! Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel parallel-post printing problem - spurious characters printed randomly interspersed in printout - since kernel (and Sarge) update
I wrote: Since I upgraded to Debian Sarge and kernel 2.6.8 (2.6.8-2-k7-smp), I've been getting lots of errors in my printouts. The error pattern is that at multiple, seemingly random positions in the middle of the printout, there is a spurious "d" character... ... Because plain-text documents (seem to) print fi[n]e, it doesn't seem to be a kernel problem with the parallel port. Actually, it DOES seem to be a problem in the kernel (or downstream) after all. If data is written slowly enough to device file /dev/lp0, the printout is fine; otherwise, the printout is corrupted at random locations, seemingly by extra or missing bytes, as I described before [ http://lists.debian.org/debian-user/2006/10/msg00133.html ]. That strongly suggests a problem with handshaking or interrupt handling in the kernel (and not with the parallel port and printer since printing worked fine with Woody and kernel 2.4 and still works fine under Windows). I configured lpd to write to a file instead of /dev/lp0. I printed a Postscript file, and after having it rastered for my printer, lpd wrote the print data to the specified file. Then I copied the file's contents to /dev/lp0 in a way that slowed things down, like this (subject to typos and any "rememberos"): cat x.dat | ( while dd bs=1 count=1 ; do : ; done ) | cat >/dev/lp0 When the block size was 1 or maybe also when it was 2, the printout would be fine. When the block size was 3 or more, I'd almost always get errors in random locations. (Repeated attempts with the same block size would get errors in different positions.) Does anyone know what's going on? Does the kernel have a bug in its parallel-port handshaking or interrupted-handling logic? Do I have something configured wrong? Is my hardware (Asus A7M266-D motherboard (AMD 768 chip)) buggy near the parallel port? Thanks, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: printing problem - spurious characters printed randomly interspersed in printout - since Sarge/kernel update
Marty wrote: Daniel B. wrote: [With] Debian Sarge and kernel 2.6.8 ... I've been getting lots of >> errors in my printouts. ... at multiple, seemingly random positions >> ... there is a spurious "d" character... ... This applies to files that go through the magicfilter/gs rasterizer, but does not seem to apply to text files (which get written directly to the printer). It seems as if ... something got out of sync between the stream of >> printer commands from the rasterizer and the printer itself >> ... Re-printing the same document the same way ... yields errors in >> different locations. >> It does not seem to be a cabling or printer unreliability problem: >> ... Because plain-text documents (seem to) print fi[n]e, it doesn't seem to be a kernel problem with the parallel port. Therefore, it seems to be a printing software problem--except that the randomness ... doesn't make sense. I first noticed this problem when I upgraded to Sarge and kernel 2.6 _and_ switched from lpr to CUPS. >> ... I removed CUPS and re-created my previous setup that used lpr and >> magicfilter for printing. Unfortunately the problem still remains ... >> ... [I suspect] that the "d" characters ... were supposed to be part of the frame around bitmap data ... as if [extra bytes], or a bad >> count, is being generated by the Postscript-to-bitmap renderer or an >> extra byte or bytes are being written out to the printer). Has anyone seen a problem like this? I haven't seen this but I also have a BJ-series printer and mine has DIP switches which I used to experiment with different emulation modes and other settings. I think one emulation mode was Epson compatible, and the other native. What might be causing the random variation in the errors? One guess is that you are using the wrong emulation mode, or the right emulation with the wrong DIP switch setting. I doubt having wrong dip-switch settings is the problem since it worked fine with Woody, kernel 2.4, and lpr/magicfilter/gs, and it still works fine under Windows. (Well, I guess it's possible that the gs filter changed assumptions about the dip-switch settings, but that doesn't seem to fit the randomness.) > Also I tried different BJ series .ppd files and I ended up using a .ppd file for a different model, but never understood why it seemed to work better. I'm not using PPD files. I'm using the lpr package and the magicfilter package (and not using any PPD files with the lpr package). How can I intercept the bytes that are being sent by lpd You mean cupsd? Are you trying to run both together? No and no. I mean lpd from package "lpr". I'm not running them together: >> ... I removed CUPS and re-created my previous setup that >> used lpr and magicfilter for printing. (I switched back because I thought that would get me back to having a working printer. Of course, it ended up telling me that the problem was not in CUPS, and is somewhere else in Sarge (in gs?) or kernel 2.6 (or something else?).) to the printer device (to see the the errors are being injected before that point)? The only way I know to intercept parallel port data ... By "device" there I meant the character device /dev/lp0 (as opposed to the parallel port hardware). > is gdb (possibly with ddd or other front end) or a logic analyzer, but these seem like massive overkill. Definitely. Would pointing lpd to a pipe (or maybe even a file) instead of /dev/lp0 work. Does lpd do anything with ioctls such that it would fail or refuse to work a device file that's not a character device? (In that case, is there any way to log the data that's written to a character device?) The reason I'm thinking about intercepting the data at different points is to see if I can find where the randomness first shows up. For example, if it first shows up in the output of the gs filter, then pretty surely gs is buggy; if it first shows up in what lpd writes to /dev/lp0, then lpd is buggy; etc. How can I check the bytes that are actually being send out from the kernel to the parallel port (to see [i]f the errors are being injected after the byte stream gets to the parallel port device (/dev/lp0)? The simplest way is so swap out the suspect device, but why or how do you think this could happen? Which level of "device" do you mean here? (I thought you meant the hardware, but that can't be swapped out.) (I meant between the file-system-level device /dev/lp0 and probably the point in the kernel where it's writing out the sequence of bytes to the hardware, or possibly at the level of what the hardware actually got from the kernel.) I was thinking that if the kernel wasn't handling parallel port interrupts correctly, it could be dropping bytes or sending extra bytes. (Of course, that theory (seemingly) is shot down by the fact that plain text (seemingly) prints fine.) Any other ideas? ... Other than that, you might try to see if you can track down what changed t
Re: printing problem - spurious characters printed randomly interspersed in printout - since Sarge/kernel update
Daniel B. wrote: Since I upgraded to Debian Sarge and kernel 2.6.8 (2.6.8-2-k7-smp), I've been getting lots of errors in my printouts. The error pattern is that at multiple, seemingly random positions in the middle of the printout, there is a spurious "d" character, and frequentlyright after the "d" there sometimes is a column or two of erroneous dots. (Sometimes after the "d" the printer jumps to the next page; sometimes the printer beeps a lot as if it is rendering ASCII BEL characters.) The printed "d" seems to be in the printer's native font for plain- ASCII(+) printing. (It's not in the same Postscript font of any text in the middle of which the error occurs.) This applies to files that go through the magicfilter/gs rasterizer, but does not seem to apply to text files (which get written directly to the printer). It seems as if: - the (non-Postscript) printer (a Canon BubbleJet BJ-200ex) had correctly executed a printer command to print out a packet of the bitmap generated by magicfilter, magicfilter's bj200 filter, and/or gs (gs-gpl) - the printer was ready for another character (to print plainly) or bitmap printing command - something got out of sync between the stream of printer commands from the rasterizer and the printer itself - the next byte in the stream was an ASCII "d" (a 0x64 byte), - the printer, being back in plain-text mode, printed a "d" - the printer recognized a bitmap-printing command, and got back into bitmap-printing mode, but something wasn't quite synchronized (thus the the next column or so of dots got messed up) - things got synchronized again for a while (since the printout's fine for somtimes several printer lines worth of bitmap dots until the next error). The location of the errors seems to be random. Re-printing the same document the same way (e.g., printing a text document through enscript or printing a web page from a browser) yields errors in different locations. It does not seem to be a cabling or printer unreliability problem: - I haven't even unplugged the printer or printer cable (parallel) since I upgraded from Woody and kernel 2.4 to - Printing still prints fine from Windows. - Plain-text documents print fine (lpr xxx.txt), with no known errors. Because plain-text documents (seem to) print file, it doesn't seem to be a kernel problem with the parallel port. Therefore, it seems to be a printing software problem--except that the randomness (the non-repeating position and the varying quantity of the errors) doesn't make sense. I first noticed this problem when I upgraded to Sarge and kernel 2.6 _and_ switched from lpr to CUPS. Thinking the problem was something in CUPS or foomatic (the PPDs files?), today I removed CUPS and re-created my previous setup that used lpr and magicfilter for printing. Unfortunately the problem still remains (except that plain-text files print fine, since they are printed directly to the printer). The errors always involve a "d" character. That makes me think that the "d" characters I see are 0x64 bytes that were supposed to be part of the frame around bitmap data, and that some count of bitmap-data bytes is getting out of sync with the stream of bitmap-data bytes (e.g., as if an extra bytes or bytes, or a bad count, is being generated by the Postscript-to-bitmap renderer or an extra byte or bytes are being written out to the printer). Has anyone seen a problem like this? I haven't seen this but I also have a BJ-series printer and mine has DIP switches which I used to experiment with different emulation modes and other settings. I think one emulation mode was Epson compatible, and the other native. What might be causing the random variation in the errors? One guess is that you are using the wrong emulation mode, or the right emulation with the wrong DIP switch setting. Also I tried different BJ series .ppd files and I ended up using a .ppd file for a different model, but never understood why it seemed to work better. How can I intercept the bytes that are being sent by lpd You mean cupsd? Are you trying to run both together? to the printer device (to see the the errors are being injected before that point)? The only way I know to intercept parallel port data is gdb (possibly with ddd or other front end) or a logic analyzer, but these seem like massive overkill. How can I check the bytes that are actually being send out from the kernel to the parallel port (to see of the errors are being injected after the byte stream gets to the parallel port device (/dev/lp0)? The simplest way is so swap out the suspect device, but why or how do you think this could happen? Any other ideas? Might be worth trying different parallel port modes (ECP, EPP, etc.) by reconfiguring the kernel or BIOS. Other than that, you might try to see if you can track down what changed to cause the problem. If you have backups and a spare drive, you mi
printing problem - spurious characters printed randomly interspersed in printout - since Sarge/kernel update
Since I upgraded to Debian Sarge and kernel 2.6.8 (2.6.8-2-k7-smp), I've been getting lots of errors in my printouts. The error pattern is that at multiple, seemingly random positions in the middle of the printout, there is a spurious "d" character, and frequentlyright after the "d" there sometimes is a column or two of erroneous dots. (Sometimes after the "d" the printer jumps to the next page; sometimes the printer beeps a lot as if it is rendering ASCII BEL characters.) The printed "d" seems to be in the printer's native font for plain- ASCII(+) printing. (It's not in the same Postscript font of any text in the middle of which the error occurs.) This applies to files that go through the magicfilter/gs rasterizer, but does not seem to apply to text files (which get written directly to the printer). It seems as if: - the (non-Postscript) printer (a Canon BubbleJet BJ-200ex) had correctly executed a printer command to print out a packet of the bitmap generated by magicfilter, magicfilter's bj200 filter, and/or gs (gs-gpl) - the printer was ready for another character (to print plainly) or bitmap printing command - something got out of sync between the stream of printer commands from the rasterizer and the printer itself - the next byte in the stream was an ASCII "d" (a 0x64 byte), - the printer, being back in plain-text mode, printed a "d" - the printer recognized a bitmap-printing command, and got back into bitmap-printing mode, but something wasn't quite synchronized (thus the the next column or so of dots got messed up) - things got synchronized again for a while (since the printout's fine for somtimes several printer lines worth of bitmap dots until the next error). The location of the errors seems to be random. Re-printing the same document the same way (e.g., printing a text document through enscript or printing a web page from a browser) yields errors in different locations. It does not seem to be a cabling or printer unreliability problem: - I haven't even unplugged the printer or printer cable (parallel) since I upgraded from Woody and kernel 2.4 to - Printing still prints fine from Windows. - Plain-text documents print fine (lpr xxx.txt), with no known errors. Because plain-text documents (seem to) print file, it doesn't seem to be a kernel problem with the parallel port. Therefore, it seems to be a printing software problem--except that the randomness (the non-repeating position and the varying quantity of the errors) doesn't make sense. I first noticed this problem when I upgraded to Sarge and kernel 2.6 _and_ switched from lpr to CUPS. Thinking the problem was something in CUPS or foomatic (the PPDs files?), today I removed CUPS and re-created my previous setup that used lpr and magicfilter for printing. Unfortunately the problem still remains (except that plain-text files print fine, since they are printed directly to the printer). The errors always involve a "d" character. That makes me think that the "d" characters I see are 0x64 bytes that were supposed to be part of the frame around bitmap data, and that some count of bitmap-data bytes is getting out of sync with the stream of bitmap-data bytes (e.g., as if an extra bytes or bytes, or a bad count, is being generated by the Postscript-to-bitmap renderer or an extra byte or bytes are being written out to the printer). Has anyone seen a problem like this? What might be causing the random variation in the errors? How can I intercept the bytes that are being sent by lpd to the printer device (to see the the errors are being injected before that point)? How can I check the bytes that are actually being send out from the kernel to the parallel port (to see of the errors are being injected after the byte stream gets to the parallel port device (/dev/lp0)? Any other ideas? Thanks. Daniel -- Daniel Barclay [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: printing problem - spurious "d" characters, bad pixels, spuriousform feeds
charles norwood wrote: On Thu, 2006-07-06 at 10:27 -0400, Daniel B. wrote: ... Also, given that the spurious characters appear at different places in the printout when I try again suggests that something random is going on (dropped or extra characters in the output stream), which doesn't sound like having the wrong PPD file. Oh--another thing is that since upgrading to Sarge and 2.6.8 (2.6.8-2-k7-smp), trying to print occasionally hangs the entire system. That suggests a problem with the parallel port driver or something closer to that later. Daniel I don't have an answer, but my experience is "random" errors are due to hardware failing. No, I'm pretty sure it's not failing hardware: The hardware worked fine with Woody, kernel 2.4, and the pre-CUPs printing system. And it still works fine when I boot into Windows and print. Besides, "random" errors are also easily due to bugs in concurrent code (e.g., the kernel and interrupt handlers (device drivers)). > My lockups have been due to hw/sw misconfiguration e.g. irqs colliding. What kind of configuration? (BIOS settings? auto-detected Linux configuration? manual Linux configurations?) Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: printing problem - spurious "d" characters, bad pixels, spuriousform feeds
On Thu, 2006-07-06 at 10:27 -0400, Daniel B. wrote: > Felipe Sateler wrote: > > Daniel B. wrote: > > > >> Can anyone help with this? I got absolutely no replies when I > >> posted it before. Now the problem is much worse, with dozens > >> of errors per page, maybe evening averaging one error per line > >> of text (when printing a plain-text file). > > > > I'm taking a _very_ wild guess here: perhaps you are using the wrong PPD > > file. Have you tried with alternative ones (perhaps downloading a new one > > from linuxprinting.org)? > > I'll double check. However, I'm pretty sure I've got the right PPD > file. > > Also, given that the spurious characters appear at different places in > the printout when I try again suggests that something random is going > on (dropped or extra characters in the output stream), which doesn't > sound like having the wrong PPD file. > > Oh--another thing is that since upgrading to Sarge and 2.6.8 > (2.6.8-2-k7-smp), trying to print occasionally hangs the entire system. > > That suggests a problem with the parallel port driver or something > closer to that later. > > Daniel I don't have an answer, but my experience is "random" errors are due to hardware failing. My lockups have been due to hw/sw misconfiguration e.g. irqs colliding. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: printing problem - spurious "d" characters, bad pixels, spuriousform feeds
Felipe Sateler wrote: Daniel B. wrote: Can anyone help with this? I got absolutely no replies when I posted it before. Now the problem is much worse, with dozens of errors per page, maybe evening averaging one error per line of text (when printing a plain-text file). I'm taking a _very_ wild guess here: perhaps you are using the wrong PPD file. Have you tried with alternative ones (perhaps downloading a new one from linuxprinting.org)? I'll double check. However, I'm pretty sure I've got the right PPD file. Also, given that the spurious characters appear at different places in the printout when I try again suggests that something random is going on (dropped or extra characters in the output stream), which doesn't sound like having the wrong PPD file. Oh--another thing is that since upgrading to Sarge and 2.6.8 (2.6.8-2-k7-smp), trying to print occasionally hangs the entire system. That suggests a problem with the parallel port driver or something closer to that later. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: printing problem - spurious "d" characters, bad pixels, spuriousform feeds
Daniel B. wrote: > Can anyone help with this? I got absolutely no replies when I > posted it before. Now the problem is much worse, with dozens > of errors per page, maybe evening averaging one error per line > of text (when printing a plain-text file). I'm taking a _very_ wild guess here: perhaps you are using the wrong PPD file. Have you tried with alternative ones (perhaps downloading a new one from linuxprinting.org)? -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
printing problem - spurious "d" characters, bad pixels, spuriousform feeds
Can anyone help with this? I got absolutely no replies when I posted it before. Now the problem is much worse, with dozens of errors per page, maybe evening averaging one error per line of text (when printing a plain-text file). Thanks. --- Since I upgraded to Debian Sarge and switched to CUPS for printing, I've been getting lots of errors in my printouts. The error pattern is that somewhere in the middle of the printout, there is a spurious "d" character, and right next to the "d" (I think after it) there is a column or two of erroneous dots. (Sometimes after the "d" the printer jumps to the next page.) The printed "d" seems to be in the printer's built-in font for plain-ASCII(+) printing. (It's not in font of any text in the middle of which the error occurs.) It seems as if: - the (non-Postscript) printer (a Canon BubbleJet 200-ex) has going along happily printing out the bitmap generated by gs or whatever my Postscript-to-printer-commands filter is, - something got out of sync (e.g., the printer thought the bitmap data ended), - the next byte was an ASCII "d", - the printer, being back in plain-text mode, printed a "d" - the printer got back into bitmap-printing mode, but something wasn't quite synchronized (thus the the next column or so of dots got messed up) - things got synchronized again for a while (since the printout's fine until the next error.) The location of the errors seems to be random. Re-printing the same document the same way (e.g., printing a text document through enscript or printing a web page from a browser) yields errors in different locations. I'm pretty sure it's not a cabling or printer unreliability problem. I haven't even unplugged the printer or printer cable (parallel) since I upgraded from woody to sarge, and (I think) printing still prints fine from Windows.) I think it's a printing software problem (although I guess it could theoretically be a kernel problem with the parallel port). When I upgraded from Woody to Sarge, I also switched to using CUPS from whatever I had before, which I think involved magicfilter and using gs as the Postscript engine. The errors always involve a "d" character. That makes me think that the "d" characters I see are "d" bytes that were supposed to be partof the frame around bitmap data, and that some count of bitmap-data bytes is getting out of sync with the stream of bitmap-data bytes (e.g., as if an extra bytes or bytes, or a bad count, is being generated by the Postscript-to-bitmap renderer or an extra byte or bytes are being written out to the printer). Has anyone seen a problem like this? Thanks. Daniel -- Daniel Barclay [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
printing problem - spurious "d" characters, bad pixels, spuriousform feeds
Since I upgraded to Debian Sarge and switched to CUPS for printing, I've been getting lots of errors in my printouts. The error pattern is that somewhere in the middle of the printout, there is a spurious "d" character, and right next to the "d" (I think after it) there is a column or two of erroneous dots. (Sometimes after the "d" the printer jumps to the next page.) The printed "d" seems to be in the printer's built-in font for plain-ASCII(+) printing. (It's not in font of any text in the middle of which the error occurs.) It seems as if: - the (non-Postscript) printer (a Canon BubbleJet 200-ex) has going along happily printing out the bitmap generated by gs or whatever my Postscript-to-printer-commands filter is, - something got out of sync (e.g., the printer thought the bitmap data ended), - the next byte was an ASCII "d", - the printer, being back in plain-text mode, printed a "d" - the printer got back into bitmap-printing mode, but something wasn't quite synchronized (thus the the next column or so of dots got messed up) - things got synchronized again for a while (since the printout's fine until the next error.) The location of the errors seems to be random. Re-printing the same document the same way (e.g., printing a text document through enscript or printing a web page from a browser) yields errors in different locations. I'm pretty sure it's not a cabling or printer unreliability problem. I haven't even unplugged the printer or printer cable (parallel) since I upgraded from woody to sarge, and (I think) printing still prints fine from Windows.) I think it's a printing software problem (although I guess it could theoretically be a kernel problem with the parallel port). When I upgraded from Woody to Sarge, I also switched to using CUPS from whatever I had before, which I think involved magicfilter and using gs as the Postscript engine. The errors always involve a "d" character. That makes me think that the "d" characters I see are "d" bytes that were supposed to be partof the frame around bitmap data, and that some count of bitmap-data bytes is getting out of sync with the stream of bitmap-data bytes (e.g., as if an extra bytes or bytes, or a bad count, is being generated by the Postscript-to-bitmap renderer or an extra byte or bytes are being written out to the printer). Has anyone seen a problem like this? Thanks. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Printing problem 750C
Hello There, I am trying to print a .pdf file to an HP Designjet 750C roll feed plotter.The length of the plot is equal to 3.5 x A0 sheets but I cannot get it to print the whole thing as I wish, it only does a single A0 sheet taken from the middle of the plot window. I have set the plotter to 'Inked Area' as this looks as though it should then set the plot size accordingly. On the PC, when I go into print set-up I can select 'custom size' but then when going into the Printer wizard/set-up window on the PC I am not able to select anything other than standard sheet sizes! why is this? Would a latest version of the printer driver allow this command or does it need some special code tweaking? A quick response would be very much appreciated Best regards Ken Clark Chief Mechanical Engineer Thales Underwater Systems Ocean House Templecombe Somerset BA8 0DH Tel 01963 372515 Fax 01963 372747 email [EMAIL PROTECTED] Many Thanks Ken This email, including any attachment, is a confidential communication intended solely for the use of the individual or entity to whom it is addressed. It contains information which is private and may be proprietary or covered by legal professional privilege. If you have received this email in error, please notify either the sender or telephone ++ 44 (0) 1963 370551 upon receipt, and immediately delete it from your system. Anything contained in this email that is not connected with the businesses of Thales Naval is neither endorsed by nor is the liability of this company. Whilst we have taken reasonable precautions to ensure that any attachment to this email has been swept for viruses, we cannot accept liability for any damage sustained as a result of software viruses, and would advise that you carry out your own virus checks before opening any attachment. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
