Description of problem: Was installing a network printer via the KDE printer applet Version-Release number of selected component: cups-1.5.4-16.fc18 Additional info: backtrace_rating: 4 cmdline: usb crash_function: __opendirat executable: /usr/lib/cups/backend/usb kernel: 3.6.7-5.fc18.i686 remote_result: NOTFOUND uid: 4 Truncated backtrace: Thread no. 1 (7 frames) #0 __opendirat at ../sysdeps/unix/opendir.c:86 #1 __opendir at ../sysdeps/unix/opendir.c:155 #2 usbfs_get_device_list at os/linux_usbfs.c:1092 #3 op_get_device_list at os/linux_usbfs.c:1284 #4 libusb_get_device_list at core.c:606 #5 find_device at usb-libusb.c:873 #6 list_devices at usb-libusb.c:226
Created attachment 654769 [details] File: backtrace
Created attachment 654770 [details] File: cgroup
Created attachment 654771 [details] File: core_backtrace
Created attachment 654772 [details] File: dso_list
Created attachment 654773 [details] File: environ
Created attachment 654774 [details] File: limits
Created attachment 654775 [details] File: maps
Created attachment 654776 [details] File: open_fds
Created attachment 654777 [details] File: proc_pid_status
Created attachment 654778 [details] File: var_log_messages
The problem occurred in libusb_get_device_list() after updating libgusb to 0.1.4-1.fc18.i686 libusb-1 API says that: "If your application is guaranteed to only ever include a single libusb user (i.e. you), you do not have to worry about contexts: pass NULL in every function call where a context is required. The default context will be used." CUPS uses a default context when initializing libusb, i.e. libusb_init(NULL); numdevs = libusb_get_device_list(NULL, &list); not sure whether the problem is in libgusb, libusb-1 or cups (using default context), reassigning to libgusb for now.
So it's actually libusbx that gets used here, not libgusb. I think what must have happened here is that libusb_init() failed because it could find a path to usbfs. mkruger: what does this command say?: ls /dev/bus/usb /proc/bus/usb /dev/usbdev*
[root@localhost mike]# ls /dev/bus/usb /proc/bus/usb /dev/usbdev* ls: cannot access /dev/bus/usb: No such file or directory ls: cannot access /proc/bus/usb: No such file or directory ls: cannot access /dev/usbdev*: No such file or directory I probably should mention this is a virtual machine (vmware esxi 5.1)
When I encountered this problem, I also encountered bug 882066. Perhaps there is some relation.
There is. Closing that as a duplicate of this (seeing as this one has more information about the root cause).
*** Bug 882066 has been marked as a duplicate of this bug. ***
Could you please run this command?: udevadm info --export-db > devices.txt and attach devices.txt?
Created attachment 661240 [details] udev dump
OK. You don't have a USB controller at all. Perhaps libusbx should code better with that situation. Changing component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.