Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#32588 - [cups] most usb epson printers does not work anymore

Attached to Project: Arch Linux
Opened by Nicola (drakkan) - Sunday, 11 November 2012, 00:40 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 25 November 2012, 18:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



after systemd update most epson usb printer does not work anymore,

lpinfo -v show only cups-pdf as local printer

DEBUG: list_devices
DEBUG: libusb_get_device_list=11
DEBUG2: Printer found with device ID: MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX;MDL:Epson Stylus SX130;CLS:PRINTER;DES:EPSON Epson Stylus SX130;CID:EpsonStd3;FID:FXN,DPN,WFN,ETN,AFN,DAN;
Device URI: usb://EPSON/Stylus%20SX130?serial=NBLK223312%20%20%20%20%20%20%20%20&interface=1
direct usb://EPSON/Stylus%20SX130?serial=NBLK223312%20%20%20%20%20%20%20%20&interface=1 "Epson Stylus SX130" "Epson Stylus SX130" "MFG:EPSON;CMD:ESCPL2,BDC,D4,D4PX;MDL:Epson Stylus SX130;CLS:PRINTER;DES:EPSON Epson Stylus SX130;CID:EpsonStd3;FID:FXN,DPN,WFN,ETN,AFN,DAN;
" ""

blacklist or not blacklist usblp make no difference and this is not a permission issue (tryed udev rule too)

even adding the uri manually does not make the printer work, see also:
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 25 November 2012, 18:00 GMT
Reason for closing:  None
Comment by Nicola (drakkan) - Sunday, 25 November 2012, 01:10 GMT
tested again today and now works:

lpinfo -v
network socket
network ipps
network https
file cups-pdf:/
network lpd
network http
network ipp
network smb
direct usb://EPSON/Stylus%20SX130?serial=NBLK223312%20%20%20%20%20%20%20%20&interface=1

probably the latest updates (kernel?) solved the problem