Quote:
Originally Posted by PeterT
GeoffR; when I do the same on my Glo, no problem at all!
|
Okay, I found that a stack log was created at some point, just not at the time of the initial problem, and I am able to reproduce it consistently on an unpatched device with these steps:
Initial state: No patches, no undocumented FeatureSettings active, wi-fi off, database size 63.7MB, 799 books, 18 sideloaded fonts.
1. Power off and on again (to start with a clean slate)
2. Open a
KePub book (I used
this one, bought and synced from Kobo)
3. Select Kobo Tsukushi Mincho, Kobo UD Kakugo, OpenDyslexic, Malabar, Amasis
4. Tap home to close the KePub book
5. Open a DRM-free
ePub book (I used Timescape by Gregory Benford, 401 pages, no embedded fonts)
6. Select Kobo Tsukushi Mincho font
7 Swipe to turn a page (at this point the book closed and was marked finished)
8. Open the ePub book again (It displays a blank page)
9. Open Aa menu, select Amasis
10. Tap home to close the ePub book
The stack log was produced after step 8 or 9 I think (it is not there after step 7, at least.) Who can I sent it to?
Edit: To explain, I don't think opening the KePub is related to the problem, it is just an easy reproducable way of allocating some resources to simulate the state the device would be in after a bit of ordinary use.
Edit2: The stack log is not produced if I remove my sideloaded fonts, but the problem remains unchanged. I've sent the info to a Kobo representative.