OK, followed the tips outlined in
https://wiki.ubuntu.com/DebuggingPrintingProblems
First, this is a parallel port printer:
tomman@saki:~$ lsmod | grep lp
lp 12797 0
parport 31375 3 lp,ppdev,parport_pc
tomman@saki:~$ lsmod | grep ppdev
ppdev 12651 0
parport 31375 3 lp,ppdev,parport_pc
tomman@saki:~$ lsmod | grep parport
parport_pc 22036 1
parport 31375 3 lp,ppdev,parport_pc
tomman@saki:~$ dmesg | grep par
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.008990] AppArmor: AppArmor disabled by boot time parameter
[ 61.046513] ppdev: user-space parallel port driver
[ 61.183747] parport_pc 00:0b: reported by Plug and Play BIOS
[ 61.186640] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[ 61.319153] lp0: using parport0 (interrupt-driven).
tomman@saki:~$ sudo lpinfo -v
file cups-pdf:/
network ipp
network http
network socket
network beh
network ipps
direct hp
network https
network lpd
network smb
direct parallel:/dev/lp0
direct hpfax
tomman@saki:~$ /usr/lib/cups/backend/parallel
tomman@saki:~$ sudo /usr/lib/cups/backend/parallel
direct parallel:/dev/lp0 "Canon BJC-250" "Canon BJC-250 LPT #1"
"MFG:Canon;CMD:BJ,LQ,BJL,BJRaster,BSCC;MDL:BJC-250;C$
tomman@saki:~$
The printer is detected OK (and even prints with the gutenprint drivers,
either locally or from the network), so this is not the issue here.
I've tried changing the printer settings (this time, using the
Foomatic/bjc250gs driver which is giving me the problems), and noticed
something odd: I only get the foomatic-rip segfaults under the following
conditions:
- Set "Color Mode" on Default Settings to "Color (Draft Quality)"
- All other General settings are set to the following:
* Page Size: US Letter
* Manual Feed of Paper: Off
* Resolution: 360x360 DPI
* Printout Quality: Draft
* Compose Black: On
- Use the web management UI to print a CUPS test page.
It will fail with the already mentioned segfault on CUPS debug logs.
However, other applications will print just fine, and if the Color Mode
is set to "Color (High Quality)" the test page will also print. When
redirecting the print data to a file, I get the following results:
Case 1: Color (Draft Quality) + CUPS test page
- Data to print queue: This:
#PDF-BANNER
Template default-testpage.pdf
Show printer-name printer-info printer-location printer-make-and-model
printer-driver-name printer-driver-version paper-size imageable-area
job-id options time-at-creation time-at-processing
(seems to be default CUPS test print commands)
- Data to printer: Nothing (a zero-byte file is created
Case 2: Color (High Quality) + CUPS test page
- Data to print queue: Same as Case 1
- Data to printer: ~700KB raster data
Case 3: Color (Draft Quality) + another application (say, a text
document on gedit)
- Data to print queue: ~12KB PDF
- Data to printer: ~400KB raster data
Given that there is already a "Printout quality" setting, the "Color
(Draft Quality)" on Color Mode seems to be redundant, plus it leads to
troubles whenever the user attempts to test its CUPS setup, failing the
quintessential test page.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
