View Single Post
Old 04-12-2018, 07:13 AM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,457
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by jehrler View Post
attached is the debug file
That debug log shows two connects. The first connect worked without pause.

The second, around 9 minutes after the first, had a 2.5 minute pause at the point just after the device was detected (CC connected and exchanged network traffic) and before calibre asks CC if it has appropriate memory. When the pause happens calibre is informing its GUI and any interested plugins that a device has connected. CC is waiting for calibre at that point and cannot be involved in the pause.

This sequence demonstrates that the problem is in the Mini. It argues that something on the Mini is preventing the calibre GUI (or something connected to the GUI such as some kind of tray notifier) from running. I have no idea what that "something" might be, nor do I have any idea whether there is some setting that affects it.

FWIW: it seems that this "pause" is at a different place than the one indicated by the CC debug log. If that is indeed the case then whatever is happening on the Mini doesn't consistently happen at the same time.
chaley is offline   Reply With Quote