MobileRead Forums - View Single Post

Section8 · 07-27-2013, 01:23 PM

I recently had this little surprise upon importing a book and restarting calibre. The steps were:

1. I clicked on a newly downloaded .epub in my file manager, which I have configured to launch calibre and import the .epub into my "originals" library. The specific command is: "calibre --with-library=/home/john/Calibre/Originals"

2. A few minutes later, with calibre still running, I installed a plugin (Find duplicates). After installation, a dialog appears prompting me to restart calibre - I clicked the restart button.

3. Upon restarting, calibre then imports the .epub from step 1 a second time.

I'm guessing this happened because calibre restarted with the identical, full command line it was originally started with (to import that .epub). I certainly don't expect this to be a high-priority bug (if it is considered a bug at all). As someone who's developed software, this has the feel of one of those "bugs" that, if fixed, the fix will end up cause worse bugs that the one it fixed.

07-27-2013, 01:23 PM	#1
Section8 Addict Posts: 265 Karma: 2121470 Join Date: Oct 2011 Location: Arlington, TX Device: Kindle PW4, Moon+ Reader on a cheap Android tablet	Calibre restart surprise I recently had this little surprise upon importing a book and restarting calibre. The steps were: 1. I clicked on a newly downloaded .epub in my file manager, which I have configured to launch calibre and import the .epub into my "originals" library. The specific command is: "calibre --with-library=/home/john/Calibre/Originals" 2. A few minutes later, with calibre still running, I installed a plugin (Find duplicates). After installation, a dialog appears prompting me to restart calibre - I clicked the restart button. 3. Upon restarting, calibre then imports the .epub from step 1 a second time. I'm guessing this happened because calibre restarted with the identical, full command line it was originally started with (to import that .epub). I certainly don't expect this to be a high-priority bug (if it is considered a bug at all). As someone who's developed software, this has the feel of one of those "bugs" that, if fixed, the fix will end up cause worse bugs that the one it fixed.