Not that I have a white window on-screen. (The Move starts at 0,0 which could be a clue that Windows has not yet initialized a Window for the task? Unless maybe there's a 0x0 window at screen 0,0?)Ī white box without a frame is not yet a window. The usual MOVE, etc., fix for "off-screen" situations, do not bring a window into view. It is not running "off-screen" - there is no window frame showing when I Alt-Tab into it. Edits and a name-timestamp-change for version fork. could there have been something in that ODT file that hosed something in the non-volatile data somewhere? It was merely edits to the earlier version. an application window initialization hang?Īll these symptoms appeared when I restarted Calibre after that "wink-out."īut. I don't recall seeing that Console Windows Host" in there before. Along with the usual "calibre worker process" and the "The main calibre program". And looking at the details under the "The main calibre program (3)" in Task Manager there is a "Console Windows Host" task running under Calibre. I can see Calibre "running" in the Task Manager Apps pane, but there is no window on screen. Today's earlier one is there, but the later one isn't. The metadata for ODT file I dropped did not make it into the Library DB. Did it earlier today, last night, weeks, without a hitch.īut this time Calibre said "Bye Felicia" and hasn't spoken since. The specific action was dragging an ODT file (Libre Office Text) onto Calibre for an EPUB conversion. I was working in other unrelated programs when Calibre "winked out". I do not allow Windows to update without me so this wasn't some backdoor sneak from MS. And seems "permanent."Ĭalibre was updated from file calibre-64bit-6.29.0.msi on
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |