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

Bug#371740: marked as done (cupsys: no connection to usb after upgrade)



Your message dated Sun, 1 Jun 2008 23:09:06 +0200
with message-id <20080601210906.GB6509@piware.de>
and subject line Cleaning up old bug reports
has caused the Debian Bug report #371740,
regarding cupsys: no connection to usb after upgrade
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.)


-- 
371740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=371740
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
package: cupsys
version: 1.2.1-2
severity: normal

Since upgrading to the latest version I cannot print anymore. The messages are rather unhelpful. The web interface tells me:

"Unable to open USB device "usb:/dev/usb/lp0": Success"

Success? wtf? and /dev/usb/lp0 exists like it did with cupsys 1.1

error_log tells me

E [07/Jun/2006:20:18:51 +0200] Resume-Printer: Unauthorized
E [07/Jun/2006:20:18:51 +0200] PID 31130 (/usr/lib/cups/backend/usb) stopped with status 1!
E [07/Jun/2006:20:18:51 +0200] [Job 868] Unable to open USB device "usb:/dev/usb/lp0": Success

For that "Resume-Printer: Unauthorized": the web interface tells me "Printer .. has been started".

Thomas
-- 


"Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail


--- End Message ---
--- Begin Message ---
Dear bug submitter,

This bug was reported against a very old version of cups (older than
in the current stable Debian version "Etch"). About a year ago,
Martin-Eric Racine asked for feedback whether the bug still applied to
the current Debian Etch version, but we did not get any feedback. In
order to not keep around old, hardware-specific, and inactive bugs
around forever, I close this bug now.

Please report back if you still experience the problem with the
current version in Etch; if you can test Lenny/unstable, that would be
highly appreciated, of course. I will reopen this bug then.

Thank you for your report!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply to: