New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't open books from library when files are associated on some Pocketbooks #11760
Comments
For me it doesn't seem to depend on the format, happens with both epub and pdf. I don't get any message in the UI, but there does in fact seem to be a
If I remember correctly, the first book opened fine, but the second didn't. For more context, I don't think I have the OpenDyslexic font in question installed on the other reader (which doesn't have this issue), but on this reader I had the font installed since before I downloaded KOreader and I never experienced anything similar to this when opening books directly from KOreader's file browser. |
I do seem to have access to OpenDyslexic on the other reader, but I don't see it in the location mentioned above. Is is possible that KOreader comes with OpenDyslexic, and the error stems from the name clash, or something like that? Doesn't explain why it works some of the time, though. |
A slightly misleading name. There's always a little bit of info written there (device, version, etc.) but it's where you should look in case there's a crash. In this case I'm not seeing any issues. The font thing is just a warning/diagnostic message. |
You're right, I removed the font files and no longer see the "error", but the behaviour prevails. Any other ideas? I'm thinking whether I could write into the crash.log myself to trace whether the |
This stuff indicates the launch:
|
Yes, but me opening the first file, which is in the log after this line, was without issues. I'm not even sure me trying to open the second file is in the log, because the mention in the log might be from when I opened the KOreader manually. |
It seems I can completely avoid the behaviour in question by always killing currently running KOreader instance beforehand. That does kind of sound like a new instance begins the start up, notices the one that is already running, passes on the arguments and quits, but does not switch the old instance to the foreground? Also when I trigger this behaviour, then kill the instance and open a different book, first the new book loads completely, and after that the book with which the behaviour was triggered starts loading, but I don't think that is very relevant. |
If I were to guess at the moment, my money would be on API for switching tasks changing somewhere between Touch Basic's 4.4 firmware and Aqua 2's 5.20 firmware, and KOreader's code being updated for or written for the newer API. I don't have any other hypothesis that would explain why the exact same configuration works on the newer reader but not on the older one. If that were the case, I think the line in question would be line 18: koreader/platform/pocketbook/koreader.app Lines 16 to 19 in e51b71f
|
It seems to me the Pocketbook Basic Touch does not have the |
No, it seems like |
Issue
I'm not sure why, but when I set up file associations (Device -> Associate file extensions -> epub, epub3, pdf) so that KOreader would open automatically when starting the reader, I can no longer reliably open books from the system library application or from the "recent books" on home screen. Sometimes it works, but most of the time nothing happens (the given book starts opening only when I manually start KOreader). I should also note that opening books on reader startup works flawlessly, and I have no such issues whatsoever on my other Pocketbook reader (Aqua 2).
If you have any ideas what might help with diagnostics, I'd be most happy to try it out.
The text was updated successfully, but these errors were encountered: