foomatic-rip assert failure: printer: options.c:763: build_foomatic_custom_command: Assertion `choice' failed. (printing a short file with lpr filename)

[John S. Gruber]

Binary package hint: foomatic-filters

Could not print by using: lpr filename

Got this error when trying. Print job is in queue saying "processing"

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: foomatic-filters 4.0.7-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
AssertionMessage: printer: options.c:763: build_foomatic_custom_command: Assertion `choice' failed.
CrashCounter: 1
Date: Sun Mar 13 21:29:06 2011
ExecutablePath: /usr/bin/foomatic-rip
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110305)
Lpstat: device for printer: ipp://192.168.1.6/printers/S600
MachineType: TOSHIBA Satellite L355D
Papersize: letter
PpdFiles: printer: Canon S600 Foomatic/bj8XXYYZ.upp (recommended)
ProcCmdline: printer 9 gruber control 1 job-originating-user-name=gruber\ finishings=3\ job-priority=50\ job-sheets=none,none\ number-up=1\ outputorder=reverse\ job-uuid=urn:uuid:65e0a9b1-fa85-3daf-48b2-cd1901a26eb4\ job-originating-host-name=localhost\ time-at-creation=1300066143\ time-at-processing=1300066143\ job-id=9\ job-state=5\ job-media-sheets-completed=0\ job-k-octets=1\ AP_D_InputSlot=
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=61f2ed95-8418-48c1-a681-7825f4278341 ro i2c-algo-bit.bit-test=1
Signal: 6
SourcePackage: foomatic-filters
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 ?? ()
Title: foomatic-rip assert failure: printer: options.c:763: build_foomatic_custom_command: Assertion `choice' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/04/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.90
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvr1.90:bd06/04/2009:svnTOSHIBA:pnSatelliteL355D:pvrPSLE0U-01000R:rvnTOSHIBA:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Satellite L355D
dmi.product.version: PSLE0U-01000R
dmi.sys.vendor: TOSHIBA

[Apport retracing service (apport)]

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __assert_fail (assertion=0x805aa7b "choice", file=0x805a92f "options.c", line=763, function=0x805ae37 "build_foomatic_custom_command") at assert.c:81
 build_foomatic_custom_command (cmd=0x8863848, opt=0x8761d98, values=0x8761498 "None") at options.c:763

[Till Kamppeter (till-kamppeter)]

I cannot reproduce this bug. Can you attach the follwoing files:

/etc/cups/ppd/printer.ppd
/etc/cups/printers.conf
~/.cups/lpoptions

Also attach the file which you tried to print and create an error_log as described in the "CUPS error_log" section on https://wiki.ubuntu.com/DebuggingPrintingProblems. Thanks.

[John S. Gruber (jsjgruber)]

There is no ~/.cups directory

[John S. Gruber (jsjgruber)]

The job seems stuck in the "processing" state on my machines printer queue. The actual printer is on a lucid computer on my LAN.

Thanks for looking at this problem. Please let me know if I can provide any additional information.

[Till Kamppeter (till-kamppeter)]

Can you attach your /etc/cups/cupsd.conf file? Thanks.

[John S. Gruber (jsjgruber)]

There it is. Thanks, Till.

[John S. Gruber (jsjgruber)]

This problem happened a couple more time, but not in a way that I could reproduce. Furthermore I couldn't print plain text files no matter what I tried, with the queue status listing "empty file" and foomatic errors.

I tried adding an additional printer specifying the same remote printer. That printer worked. Comparing /etc/cups/printers.conf I saw that they had few fields different. Changing the non-working printer's Type to match the working definition got it to work, too. (Changed Type from 8433678 to 8433676--is this clearing CUPS_PRINTER_REMOTE?) Both defined printers at the same location--ipp://192.168.1.6/printers/S600.

Everything was printing except for chromium browser print-outs.

With either printer type the gutenburg ppd does work, and it prints chromium browser output as well.

[John S. Gruber (jsjgruber)]

Marked as incomplete as I can't reproduce this particular problem. If someone else does please mark it again as "new".

[Till Kamppeter (till-kamppeter)]

John, "Incomplete" is not correct here. Set s bug which you have reported and cannot reproduce any more to "Invalid". "Incomplete" means that there is still info needed from the reporter of the bug. Setting to "Invalid"...