Ubuntu
cups package

[regression] usblp module blacklisted since karmic

Bug #436495 reported by Bernd Schubert
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: cups

I have a Kyocera FS1000+ printer, which only has a parallel interface. However, since my mainboard does't provide a parallel interface, I use a usb2parallel adapter. Problem is now in karmic that cups blacklists usblp in /etc/modprobe.d/blacklist-cups.conf. So without notification, old printer configurations will be broken. Users will be very happy to see their printing broke after the update to karmic and they won't have an idea what happened. I don't know if printer detection works with native usb printers, but it doesn't work at all with my usb2parallel adapter. If I try to detect a printer:

[ 9105.581105] usb[14650]: segfault at 7fffbf14d000 ip 00007f2a9262eac4 sp 00007fffbf149818 error 4 in libc-2.10.1.so[7f2a925ac000+166000]

Eventually after I figured out that /dev/usb/lp0 was missing, I loaded usblp, but even with that my printer is not detected anymore. So anyone who deleted the old configuration in the mean time to let it re-detect, will have a problem now. Something like "parallel:/dev/usb/lp0" is not obvious to people not configuring printers each and every day.

Related branches

lp:debian/squeeze/cups
Revision history for this message
Steven Harms (sharms) wrote :

Blacklisting usblp by default is going to break a lot of users with usb -> parallel adapters, I can confirm this

Changed in cups (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cups - 1.4.1-4

---------------
cups (1.4.1-4) unstable; urgency=low

  [ Till Kamppeter ]
  * debian/patches/usb-backend-both-usblp-and-libusb.dpatch: Make the USB
    backend supporting both printer access via libusb and via the usblp kernel
    module. Make it also printing via libusb if the URI for the queue was
    generated via usblp and vice versa. This should solve most USB printing
    problems which occured on the transition to CUPS 1.4.x (LP: #420015,
    LP: #436495; Closes: #546558, #545288, #545453).

  [ Martin Pitt ]
  * debian/rules: Make the USB backend run as root again, udev rules do not
    cover all printers. (LP: #420015)
  * Drop debian/blacklist-cups.conf, and remove it on upgrade. With Till's fix
    from above this is not necessary any more.

cups (1.4.1-3) unstable; urgency=low

  * Add disable-pie-mipsen.dpatch: Disable PIE on mipsen, its binutils
    segfaults with it. (Closes: #548246)

 -- Martin Pitt <email address hidden> Wed, 30 Sep 2009 15:17:53 +0200

Changed in cups (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
andoreasu (andoreasu) wrote :

this problem still persists for me

Changed in cups (Ubuntu):
status: Fix Released → In Progress
status: In Progress → Confirmed
Rolf Leggewie (r0lf)
summary: - [regression] printing broken in karmic
+ [regression] usblp module blacklisted since karmic
Revision history for this message
Aymeric Mansoux (aymeric) wrote :

Thanks for the "parallel:/dev/usb/lp0" hint Bernd. I can now use my printer again even though it is not detected.

Revision history for this message
johnfrith (johnfrith1) wrote :

After upgrading to Lucid, I had to re-install my parallel printer, but got it working. Today, after doing an OS upgrade, it's stopped working completely - re-install doesn't work. Am using "parallel:/dev/usb/lp0". It's a good printer, I don't want to have to throw it away. Any idea if this is being looked at?

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

The blacklisting we have removed as it caused many problems, so thia bug is fixed. The segmentation fault of the "usb" CUPS backend is another problem treated in bug #564917. Therefore I will turn this bug back to "Fix Released". Please continue discussion of the segmentation fault in the other bug.

Changed in cups (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.