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
koreader crashes on Kindle DXG #1868
Comments
|
Is that when opening a book directly or the File Manager? Opening a CRe-handled book currently most likely crashes in fun and interesting ways in my builds, for reasons beyond my comprehension (and that I couldn't manage to debug). |
|
Looks like it crashed in readerui, so it's trying to open a book. @elektronaut0815 , did you get the release directly from our release page on github? Our official kindle release only works on touch based kindle devices right now. For k3/dxg/k4/k2, you will need to compile your own version with kindle-legacy as the target. If you don't know how to setup cross compile environment, you can take https://github.com/koreader/virdevenv/tree/master/vm/ubuntu a try. Feel free to ping us if you got stuck at any step ;) |
|
Correct, it crashed directly after trying to open a book. |
|
Oh, I see. NiLuJe's build should work then. I thought you downloaded it from github instead. Does the crash happen to any book? |
|
Yes, any book. |
|
For curiosity's sake, does it happen with books handled by another engine than CRe (pdf or djvu for instance)? |
|
Those books were all Epub's, I just tried a PDF now, which is displayed without crash. |
|
@NiLuJe , I tested your build on my kpw1, it crashes on epubs and only works for pdf. |
|
Yeah, that's why I was asking, that might just be a side-effect of the CRe
|
|
Okay, the just-released snapshots should now have a properly working CRe... (Stupid ABI mismatch, I had some crap in my env...) TL;DR: Can you reproduce with my current >= -309 snapshots? |
|
Still not working with current snapshot. |
|
Okay, so there's a definite issue somewhere in the codebase, and not only a silly mistake on my part, thanks :). |
|
@elektronaut0815 are you still getting the same error? Fun fact, I tried a new kindle-legacy build with the latest master, EPUB is working fine for me, but now it says no engine found for PDFs... I will probably take a closer look at weekend to see what's actually happening. |
|
Okay on PDF & ePub on a K4 over here. |
|
Okay also on a K3. |
|
... And okay also on a K2. :? |
|
Even checked on a clean install to make sure, and, yep, works fine on my end... :? |
|
After updated https://github.com/koreader/koxtoolchain to use @NiLuJe 's ct-ng kindle branch, everything is working again on my K3 now. @elektronaut0815 can you give @NiLuJe 's latest build a try? PS: @NiLuJe, the kernel version you specified in the sample file does not exist in ct-ng. Did you do anything special to make ct-ng fetch your version? I ended up using 2_6_32 for kindle-legacy TC. |
|
That kernel version is in my kindle, branch, make sure you don't have an After updated https://github.com/koreader/koxtoolchain to use @NiLuJe PS: @NiLuJe https://github.com/NiLuJe, the kernel version you specified — |
|
... On the tip of the branch, that is, whereas your script is checking out
|
|
haha, I am an idiot. Thanks for catching that, I forgot to change the commit hash ;) |
|
@NiLuJe btw, which version of binutils should we use for kindle-legacy? linaro-2.24.0-2014.11-2? |
|
The latest when using gold, but with bfd we don't really care. That said,
|
|
@houqp: Any particular reason for sticking w/ GCC 4.8? (If the idea is to avoid GCC 5, which is not such a crazy idea, GCC 4.9 is also a solid choice ;)). Same question for glibc 2.11 in the Kobo TC? |
|
I haven't finished up the kindle tc clean up yet. GCC 5 for some reason does not work for me. I need to dig further into it. The rest should be in sync with your sample setting. As for Kobo TC, I haven't started rebuilding it based on your sample yet ;) |
|
This should definitely be fixed by now (updated TCs, proper targets, and the only GCC >4 issue we actually had fixed) :). |
Issue
KOReader won't start, it immediately crashes.
Steps to reproduce
Simply start KOReader from KUAL.
The text was updated successfully, but these errors were encountered: