This doesn't seem to affect use of the printer, but it spams syslog something fierce: Nov 6 08:00:23 ftgme2 kernel: usblp0: removed Nov 6 08:00:23 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1817 Nov 6 08:00:28 ftgme2 kernel: usblp0: removed Nov 6 08:00:28 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1817 Nov 6 08:00:33 ftgme2 kernel: usblp0: removed Nov 6 08:00:33 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1817 Nov 6 08:00:39 ftgme2 kernel: usblp0: removed Nov 6 08:00:39 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1817 Nov 6 08:00:44 ftgme2 kernel: usblp0: removed Nov 6 08:00:44 ftgme2 kernel: usblp 1-1:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1817 Apparently, something is deciding to disconnect the printer if it is idle for 5 seconds, at which point it is immediately "seen" again and reconnected.
This is no longer happening with current cauldron.
Status: NEW => RESOLVEDResolution: (none) => FIXED