View Single Post
Old 02-06-2016, 12:06 PM   #4
Phssthpok
Age improves with wine.
Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.Phssthpok knows how to set a laser printer to stun.
 
Posts: 583
Karma: 95229
Join Date: Nov 2014
Device: Kindle Oasis, Kobo Libra II
Quote:
Originally Posted by kovidgoyal View Post
What file is open on the device?
It is indeed the metadata file (metadata.calibre) that's it's hanging on to.

There is a difference this time: instead of the one process I described, there are 3 processes: a calibre-parallel.exe (no command-line parameters) with 2 subprocesses, one of which is another calibre-parallel.exe with no command-line parameters, and the other one with these parameters:
Code:
--pipe-worker "from calibre.gui2.tweak_book.completion.worker import run_main, main; run_main(main)"
As I write, the Kindle was ejected from within Calibre just over 40 minutes ago, Calibre is no longer showing the device tools on the toolbar, the metadata file hasn't been written to since, but all three processes still have an open handle to the metadata file, are all idle, and I can't eject the device.

Last edited by Phssthpok; 02-06-2016 at 12:30 PM.
Phssthpok is offline   Reply With Quote