Bugtracker - Pocketbook Pro - 2.0.5

[preempalver]

I have the same problem, and the epub you published gave me the same error with PB adobeviewer. and Coolreader3. with fbreader, fbreader180 no problems.
I used wikipaedia function to make a couple of books, downloaded as .odt files, saved as html with openoffice then imported and transformed in epub with calibre. same error.
moreover, I don't see anymore the book covers of recently converted epub files.

Edit:

It turned out that there are problems transferring via bluetooth from my linux to Pocketbook, at least it seems.

[J.C.]

Originally Posted by troll05

Works fine with mine too, did you ever change the location of the file and open it with "last read ebooks" or via another shortcut? Or change name of the title weather in Calibre or just so, because these Metafile Updates only work from device to PC, not the other way round, so if you do a major change to the file you have to delete it and then add again, otherwise you will get exactly the mentioned message

This doesn't happen with just one book, it happens with all of my epubs so far, opening a book with the hot-list widget after it failed to open just fails again.

I do not use Calibre to sync files, I didn't update these files on the device, I prepared the files and copied the files to the device manually.

Just to be clear, any updating of files I did was done in preparation before copying the files to the device for the first time.


Edit:
Gave it some thinking and trial and error and it seems the path name is somehow in error.

While my books were in sdcard\Books\#New the sample book was in sdcard\Books\#Misc ,
which could or could not be important, but my books are also more likely to contain brackets and apostrophes.

Now that I've renamed #New to 1_New AdobeViewer seems to handle my files, so:
either a combination of a path with #New or just # and Brackets and/or Apostrophes caused the system to send the wrong path to AdobeViewer.
Or more likely since the other readers don't object its AdobeViewer at fault.

So the conclusion seems to be some AdobeViewer bug or supposed protection feature is at fault, not much better/different then the windows chm reader refusing to open files when the path contained # but perhaps a bit more complex.