my printer does not print LBP2900

[fool]

In addition to bug #200263:

My printer does not work if I connect the LBP 2900 after booting the system to usb. The printer only works if I connect it to usb AND turn it on before booting the computer. This bug started with the new update of cups in the first days of april 2008.

The following output was made if my printer is started before booting the system(the printer works fine):

lpinfo -v

network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_4a9_2676_0000A376H0YZ_if0_printer_noserial
direct ccp:/var/ccpd/fifo0
direct ccp:/var/ccpd/fifo1
direct ccp:/var/ccpd/fifo2
direct ccp:/var/ccpd/fifo3
direct ccp:/var/ccpd/fifo4
direct ccp:/var/ccpd/fifo5
direct ccp:/var/ccpd/fifo6
direct ccp:/var/ccpd/fifo7
direct canon:/dev/usb/lp0
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
direct scsi
network smb

user@desktop:~$ lpstat -v
Gerät für LBP2900: ccp:/var/ccpd/fifo0
Gerät für tp0: lpd://192.168.xxx.xxx/

The following output was made after disconnecting the printer within a running system:

user@desktop:~$ lpinfo -v
network socket
network beh
direct ccp:/var/ccpd/fifo0
direct ccp:/var/ccpd/fifo1
direct ccp:/var/ccpd/fifo2
direct ccp:/var/ccpd/fifo3
direct ccp:/var/ccpd/fifo4
direct ccp:/var/ccpd/fifo5
direct ccp:/var/ccpd/fifo6
direct ccp:/var/ccpd/fifo7
direct hal
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
direct scsi
network smb

user@desktop:~$ lpstat -v
Gerät für LBP2900: ccp:/var/ccpd/fifo0
Gerät für tp0: lpd://192.168.xxx.xxx/

The following output was made after reconnecting the printer in the running system:

user@desktop:~$ lpinfo -v
network socket
network beh
direct hal:///org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_printer_noserial
direct usb://Canon/LBP2900
direct ccp:/var/ccpd/fifo0
direct ccp:/var/ccpd/fifo1
direct ccp:/var/ccpd/fifo2
direct ccp:/var/ccpd/fifo3
direct ccp:/var/ccpd/fifo4
direct ccp:/var/ccpd/fifo5
direct ccp:/var/ccpd/fifo6
direct ccp:/var/ccpd/fifo7
direct canon:/dev/usb/lp0
direct hpfax
direct hp
network http
network ipp
network lpd
direct parallel:/dev/lp0
file cups-pdf:/
direct scsi
network smb

user@desktop:~$ lpstat -v
Gerät für LBP2900: ccp:/var/ccpd/fifo0
Gerät für tp0: lpd://192.168.xxx.xx/

[fool (write-me)]

I am using Ubuntu Gutsy on a desktop system.

[firmit (firmit)]

I followed the guide on
https://help.ubuntu.com/community/HardwareSupportComponentsPrinters/CanonPrinters/Canon_LBP_2900

If you did too - the package you assigned the bug to may be wrong as the canon ppd-file are proprietary, and that the ccpd-daemon is the cause of this error, not hal-cups-utils. I have not changed everything in the bug-header as I need to get this confirmed.

I have the same kind of trouble. What I am getting is that the ccpd-daemon crashes upon startup whenever the printer is turned off. Apport pops up and askes me to report. But fails to do so when opening Firefox...something about memory...

I simply need to start the daemon manually:

sudo /etc/init.d/ccpd start

This works for me. It should be easy to fix this - simply add a Ifup-thingy - "check if printer is turned-on" - in the start of ccpd and exit and print to log that printer is not on or something. Or even better - add a deamon monitoring if the printer gets turned on later, and start the ccpd deamon.

[fool (write-me)]

Thanks a lot for your help, it works fine with the above solution.

[Pascal De Vuyst (pascal-devuyst)]

Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!

[fool (write-me)]

To get an automatic startup for the LBP 2900 I added simply looked in

/etc/udev/rules.d/

and searched for a rule file containing "lp" to indicate there is already something about printers in it.
In this case it was the file

/etc/udev/rules.d/85-hpjl10xx.rules

I simply added after the last line

KERNEL=="lp*", RUN+="/etc/init.d/ccpd restart"

and it works.

Output of /etc/udev/rules.d/85-hpjl10xx.rules

#Own udev rule for HP Laserjet 1000
KERNEL=="lp*", SUBSYSTEMS=="usb", SYSFS{idVendor}=="03f0", SYSFS{product}=="hp LaserJet 1000", SYMLINK+="hplj1000", RUN+="/usr/sbin/hplj1000"
#Own udev rule for HP Laserjet 1005
KERNEL=="lp*", SUBSYSTEMS=="usb", SYSFS{idVendor}=="03f0", SYSFS{product}=="hp LaserJet 1005 series", SYMLINK+="hplj1005", RUN+="/usr/sbin/hplj1005"
#Own udev rule for HP Laserjet 1018
KERNEL=="lp*", SUBSYSTEMS=="usb", SYSFS{idVendor}=="03f0", SYSFS{product}=="HP LaserJet 1018", SYMLINK+="hplj1018", RUN+="/usr/sbin/hplj1018"
#Own udev rule for HP Laserjet 1020
KERNEL=="lp*", SUBSYSTEMS=="usb", SYSFS{idVendor}=="03f0", SYSFS{product}=="HP LaserJet 1020", SYMLINK+="hplj1020", RUN+="/usr/sbin/hplj1020"
KERNEL=="lp*", RUN+="/etc/init.d/ccpd restart"

[Till Kamppeter (till-kamppeter)]

fool, then this is an upstream bug in the Canon driver package. The Canon driver package must contain a file to be installed in /etc/udev/rules.d/ which contains the line

KERNEL=="lp*", RUN+="/etc/init.d/ccpd restart"

or perhaps better

KERNEL=="lp*", SUBSYSTEMS=="usb", SYSFS{idVendor}=="XXXX", RUN+="/etc/init.d/ccpd restart"

with XXXX replaced by Canon's USB vendor ID in hex.

The file /etc/udev/rules.d/85-hpjl10xx.rules is part of the foo2zjs package, a driver for some HP LaserJets and many other cheap laser printers. It would produce a maintenance nightmare if one adds a feature to a package of a completely independent other driver to get a certain printer driver to work.

[fool (write-me)]

It seems that no file was added by the canon LBP2900 driver. My whole directory is this:

xxx@xxx:~$ ls -l /etc/udev/rules.d/
insgesamt 240
-rw-r--r-- 1 root root 132 2007-10-05 17:49 00-init.rules
lrwxrwxrwx 1 root root 22 2008-03-15 07:47 025_logitechmouse.rules -> ../logitechmouse.rules
-rw-r--r-- 1 root root 272 2007-10-05 17:49 05-options.rules
-rw-r--r-- 1 root root 3076 2007-10-05 17:49 20-names.rules
-rw-r--r-- 1 root root 119 2007-10-05 17:49 30-cdrom_id.rules
-rw-r--r-- 1 root root 3258 2007-10-05 17:49 40-permissions.rules
-rw-r--r-- 1 root root 30 2007-09-19 02:01 45-fuse.rules
-rw-r--r-- 1 root root 420 2008-04-27 14:29 45-hplip.rules
-rw-r--r-- 1 root root 60410 2007-10-16 01:26 45-libgphoto2.rules
-rw-r--r-- 1 root root 50851 2007-10-05 17:26 45-libsane.rules
-rw-r--r-- 1 root root 5716 2007-09-16 04:05 50-xserver-xorg-input-wacom.rules
-rw-r--r-- 1 root root 980 2008-02-05 06:34 55-hpmud.rules
lrwxrwxrwx 1 root root 19 2008-03-14 23:38 60-libpisock.rules -> ../libpisock9.rules
-rw-r--r-- 1 root root 649 2007-10-05 17:49 60-symlinks.rules
-rw-r--r-- 1 root root 1365 2007-10-05 17:49 65-persistent-input.rules
-rw-r--r-- 1 root root 4261 2007-10-05 17:49 65-persistent-storage.rules
-rw-r--r-- 1 root root 1065 2008-03-28 11:08 70-persistent-cd.rules
-rw-r--r-- 1 root root 490 2008-03-15 05:48 70-persistent-net.rules
-rw-r--r-- 1 root root 186 2007-10-05 17:49 75-cd-aliases-generator.rules
-rw-r--r-- 1 root root 869 2007-10-05 17:49 75-persistent-net-generator.rules
-rw-r--r-- 1 root root 564 2007-10-05 17:49 80-programs.rules
-rw-r--r-- 1 root root 171 2007-09-04 04:52 85-alsa.rules
-rw-r--r-- 1 root root 1443 2007-05-18 17:48 85-brltty.rules
-rw-r--r-- 1 root root 81 2007-06-14 10:58 85-hdparm.rules
-rw-r--r-- 1 root root 771 2008-04-27 18:20 85-hplj10xx.rules
-rw-r--r-- 1 root root 126 2007-10-03 06:48 85-hwclock.rules
-rw-r--r-- 1 root root 708 2007-09-20 02:25 85-ifupdown.rules
-rw-r--r-- 1 root root 950 2007-03-07 22:45 85-pcmcia.rules
-rw-r--r-- 1 root root 3040 2007-10-05 17:49 90-modprobe.rules
-rw-r--r-- 1 root root 90 2007-10-08 20:48 95-hal.rules
-rw-r--r-- 1 root root 77 2007-10-05 17:49 99-udevmonitor.rules
lrwxrwxrwx 1 root root 15 2008-03-14 23:38 libmtp.rules -> ../libmtp.rules
-rw-r--r-- 1 root root 1224 2007-10-05 17:49 README
xxx@xxx:~$