[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791766: marked as done (/usr/lib/cups/backend-available/usb: USB backend eats 100% CPU)



Your message dated Tue, 15 Sep 2015 20:13:29 +0200
with message-id <1543393.XESbtRjxQb@odyx.org>
and subject line Re: Bug#791766: /usr/lib/cups/backend-available/usb: USB backend eats 100% CPU
has caused the Debian Bug report #791766,
regarding /usr/lib/cups/backend-available/usb: USB backend eats 100% CPU
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
791766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791766
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups
Version: 2.0.3-6
Severity: important
File: /usr/lib/cups/backend-available/usb

Hi there,

sometimes it happens that I print a file to a USB-attached printer
and instead of printing, the usb process eats up 100% cpu. Nothing
else happens, apart from some GNOME window popping up and asking if my
printer is actually connected. In fact, it is.

This is what strace says the offending process does all the time:

ioctl(15, USBDEVFS_CLAIMINTERFACE, 0x7fffad353bfc) = -1 EBUSY (Device
or resource busy)

This repeasts endlessly.

Please tell me how I can provide further information.

Cheers,

Fabian


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cups depends on:
ii  cups-client            2.0.3-6
ii  cups-common            2.0.3-6
ii  cups-core-drivers      2.0.3-6
ii  cups-daemon            2.0.3-6
ii  cups-filters           1.0.69-1
ii  cups-ppdc              1.7.5-12
ii  cups-server-common     2.0.3-6
ii  debconf [debconf-2.0]  1.5.56
ii  ghostscript            9.06~dfsg-2
ii  libavahi-client3       0.6.31-5
ii  libavahi-common3       0.6.31-5
ii  libc-bin               2.19-18
ii  libc6                  2.19-18
ii  libcups2               2.0.3-6
ii  libcupscgi1            2.0.3-6
ii  libcupsimage2          2.0.3-6
ii  libcupsmime1           2.0.3-6
ii  libcupsppdc1           2.0.3-6
ii  libgcc1                1:5.1.1-12
ii  libstdc++6             5.1.1-12
ii  libusb-1.0-0           2:1.0.19-1
ii  lsb-base               4.1+Debian13+nmu1
ii  poppler-utils          0.26.5-2
ii  procps                 2:3.3.10-2

Versions of packages cups recommends:
ii  avahi-daemon                     0.6.31-5
ii  colord                           1.2.1-1+b2
ii  cups-filters [ghostscript-cups]  1.0.69-1
ii  printer-driver-gutenprint        5.2.10-3

Versions of packages cups suggests:
pn  cups-bsd                                   <none>
pn  cups-pdf                                   <none>
ii  foomatic-db-compressed-ppds [foomatic-db]  20150411-1
ii  hplip                                      3.14.6-1+b2
ii  printer-driver-hpcups                      3.14.6-1+b2
ii  smbclient                                  2:4.1.17+dfsg-4
ii  udev                                       221-1

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd

--- End Message ---
--- Begin Message ---
Version: 2.1.0-3

Le lundi, 14 septembre 2015, 13.49:33 Till Kamppeter a écrit :
> This is fixed now in cups 2.1.0-3.
> 
> It is the following upstream bug report:
> 
> https://www.cups.org/str.php?L4707
> 
> The fix I have backported to said cups release.

Hereby closing the bug, I have also marked the patch as fixing this bug 
in git.

Cheers, 
OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply to: