Bug 1294978

lsusb -v output:

Bus 003 Device 003: ID 04f9:0054 Brother Industries, Ltd 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x04f9 Brother Industries, Ltd
  idProduct          0x0054 
  bcdDevice            1.00
  iManufacturer           1 Brother
  iProduct                2 HL-1110 series
  iSerial                 3 K3N506794
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         7 Printer
      bInterfaceSubClass      1 Printer
      bInterfaceProtocol      2 Bidirectional
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

While the udev-configure-printer tries to configure 003-002, the lsusb claims the printer is 003-003 device. But I guess that's because you run the lsusb later (perhaps after reboot or so ?). Can you confirm that ?

(In reply to Andreas Spengler from comment #0)
> Dec 31 12:59:30 server udev-configure-printer[1105]: add usb-003-002

(In reply to Andreas Spengler from comment #1)
> Bus 003 Device 003: ID 04f9:0054 Brother Industries, Ltd

Yes, Jiri, that's true. Sorry, should have mentioned it...

Ok, could you try it once more with 
# udevadm monitor
in another terminal.
Once it fails, run the
# lsusb
and
# strace /usr/lib/udev/udev-configure-printer add usb-003-002 > strace.txt 2>&1
where the numbers in usb-003-002 has to be replaced with correct bus and device numbers of the printer (per lsusb).

Attach all the outputs (you might want to compress them first).

Thanks

to me:
Seem it failed in get_ieee1284_id_from_child ()
because udev couldn't enumerate (with filter) devices.

[root@server ~]# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[45843.060616] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2 (usb)
KERNEL[45843.063652] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0 (usb)
UDEV  [45843.097694] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2 (usb)
KERNEL[45843.149212] add      /module/usblp (module)
UDEV  [45843.151218] add      /module/usblp (module)
KERNEL[45843.153218] add      /class/usbmisc (class)
KERNEL[45843.153720] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/usbmisc/lp0 (usbmisc)
KERNEL[45843.153826] add      /bus/usb/drivers/usblp (drivers)
UDEV  [45843.153959] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0 (usb)
UDEV  [45843.154485] add      /class/usbmisc (class)
UDEV  [45843.156734] add      /bus/usb/drivers/usblp (drivers)
UDEV  [45843.159283] add      /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/usbmisc/lp0 (usbmisc)

Created attachment 1113271 [details]
gzipped strace output

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.