USB backend not accessing device

[Andreas Kostyrka]

Hi!

I've got a Samsung CLP-510, but it's not connected all the time, so I
have no idea which broke the printing.

Debian cupsys 1.2.4-1

I've managed to trace the USB backend via strace (by creating a wrapper
script), and noticed the follwoing strange behaviour:

uname({sys="Linux", node="andi-lap", ...}) = 0
brk(0)                                  = 0x804c000
brk(0x806d000)                          = 0x806d000
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
write(2, "STATE: +connecting-to-device\n", 29) = 29
write(2, "INFO: Printer not connected; wil"..., 57) = 57
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL}, 8) = 0

That begs the question, how can the usb backend know that the printer is
not connected without checking it in any way, ...

TIA,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb.log
Type: text/x-log
Size: 961 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20070502/e9f829d6/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usb2.log
Type: text/x-log
Size: 7974 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20070502/e9f829d6/attachment-0001.bin>