View Single Post
Old 12-02-2014, 09:44 PM   #5
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,378
Karma: 27230406
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
IIRC when you eject a USB device from within calibre, it remains in ejected_devices until the USB scan no longer detects the device, at which point it is removed from ejected_devices.

A connection attempt to an ejected device will only happen if the system at some point reports that device as no longer present and then later reports it as present again. I dont think anything can be done about that, since it indicates something buggy in the system in question.

Doesn't the wireless driver listen for connections in a separate thread? In which case why would re-ordering the scan list make any difference?
kovidgoyal is online now   Reply With Quote