KOreader "No reader engine" on PW1

LittleBiG · 12-23-2020, 05:53 AM

The development builds after 2020.12 doesn't work for PW1. It restructures the cache, reload all cover thumbnails, then I get an error message "No reader engine for this file or invalid file" whichever book I want to open. The only solution is downgrade to the latest stable, however, no cover is shown after that.

NiLuJe · 12-23-2020, 06:54 AM

Try with a nightly, there was a memory alignment issue in the zstd version used in the release, that was hotfixed a few hours later. It *would* unfortunately be fatal on a Kindle, given how the alignment trap is setup there

.

(I checked on a K3 a few days ago, and everything behaved as it was supposed to there).

LittleBiG · 12-23-2020, 08:39 AM

The problem first appeared with nightly 24, and it is the same even now with 30. I have a modern interface with no reader engine it seems.

NiLuJe · 12-23-2020, 09:29 AM

PW1 is flat, so, more on that later, but 2020.12-27 worked out just fine on a K3, and -30 just fine on a PW2.

LittleBiG · 12-23-2020, 10:27 AM

Quote:

Originally Posted by NiLuJe

PW1 is flat, so, more on that later, but 2020.12-27 worked out just fine on a K3, and -30 just fine on a PW2.

Thanks, I am looking forward to it. In the meantime I deleted my KOreader instance then copied the latest nightly to my reader. It was all the same :-(

NiLuJe · 12-23-2020, 10:29 AM

Well, I did find a fun Kindle special bug in the process, but everything's also fine on my end on a PW1 on 5.6.1.1 with -30.

I would have said try a clean install, but apparently you did, so, check the crash.log instead (in koreader/crash.log).

LittleBiG · 12-23-2020, 10:36 AM

12/23/20-16:32:30 INFO opening file /mnt/us/koreader/crash.log
[!] doShowReader coroutine crashed:
frontend/apps/reader/readerui.lua:226: attempt to call method 'isStub' (a nil value)
stack traceback:
frontend/ui/widget/widget.lua:48: in function 'new'
frontend/apps/reader/readerui.lua:578: in function 'doShowReader'
frontend/apps/reader/readerui.lua:536: in function <frontend/apps/reader/readerui.lua:535>12/23/20-16:32:30 INFO FM loaded plugin SSH at plugins/SSH.koplugin

NiLuJe · 12-23-2020, 10:44 AM

I'm going to need the full context, not just an excerpt.

LittleBiG · 12-23-2020, 10:53 AM

I hope it is ok for you renamed to txt and attached.

NiLuJe · 12-23-2020, 11:00 AM

Which FW version is your PW1 running on?

NiLuJe · 12-23-2020, 11:03 AM

And this vaguely looks like an incomplete/badly updated install, so I'd try a *really* clean install, from scratch

.

LittleBiG · 12-23-2020, 01:00 PM

Quote:

Originally Posted by NiLuJe

And this vaguely looks like an incomplete/badly updated install, so I'd try a *really* clean install, from scratch

.

Thank you, I have just finished and KOreader works like a charm now.

LittleBiG · 12-23-2020, 01:55 PM

Came back. Something changed in KOreader so when I run a book by kpvbooklet, I get this error message. And this was the very problem before too.

NiLuJe · 12-23-2020, 02:45 PM

Ah, now that makes more sense

.

I'll try to suss out why that is, exactly.

yparitcher · 12-23-2020, 05:45 PM

https://github.com/koreader/koreader/pull/7041

12-23-2020, 05:53 AM	#1
LittleBiG Zealot Posts: 122 Karma: 10 Join Date: Nov 2014 Device: Kindle Oasis 3, K4NT, Kobo Mini	KOreader "No reader engine" on PW1 The development builds after 2020.12 doesn't work for PW1. It restructures the cache, reload all cover thumbnails, then I get an error message "No reader engine for this file or invalid file" whichever book I want to open. The only solution is downgrade to the latest stable, however, no cover is shown after that.

12-23-2020, 06:54 AM	#2
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Try with a nightly, there was a memory alignment issue in the zstd version used in the release, that was hotfixed a few hours later. It would unfortunately be fatal on a Kindle, given how the alignment trap is setup there . (I checked on a K3 a few days ago, and everything behaved as it was supposed to there). Last edited by NiLuJe; 12-23-2020 at 06:57 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Closed] Calibre 4 Ebook Reader -- Don't Show "Next," "Previous" Triangles	nkormanik	Calibre	49	01-18-2020 02:22 PM
Is there an alternative "pdf reader" like koreader for non jb kindle	Uphantom89	Kindle Developer's Corner	4	06-16-2019 01:29 AM
Can't open ebooks: "No reader engine for this file" (Onyx i86)	medwatt	KOReader	5	03-17-2016 10:43 AM
Kindle PW1 - attempt to "cure" a demo unit	aesop	Kindle Developer's Corner	5	06-26-2015 03:48 PM
"Koreader" and "Coolreader" Prefixes	Ken Maltby	Feedback	3	05-21-2015 06:39 PM

12-23-2020, 08:39 AM	#3
LittleBiG Zealot Posts: 122 Karma: 10 Join Date: Nov 2014 Device: Kindle Oasis 3, K4NT, Kobo Mini	The problem first appeared with nightly 24, and it is the same even now with 30. I have a modern interface with no reader engine it seems.

12-23-2020, 09:29 AM	#4
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	PW1 is flat, so, more on that later, but 2020.12-27 worked out just fine on a K3, and -30 just fine on a PW2.

12-23-2020, 10:29 AM	#6
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Well, I did find a fun Kindle special bug in the process, but everything's also fine on my end on a PW1 on 5.6.1.1 with -30. I would have said try a clean install, but apparently you did, so, check the crash.log instead (in koreader/crash.log).

12-23-2020, 10:36 AM	#7
LittleBiG Zealot Posts: 122 Karma: 10 Join Date: Nov 2014 Device: Kindle Oasis 3, K4NT, Kobo Mini	12/23/20-16:32:30 INFO opening file /mnt/us/koreader/crash.log [!] doShowReader coroutine crashed: frontend/apps/reader/readerui.lua:226: attempt to call method 'isStub' (a nil value) stack traceback: frontend/ui/widget/widget.lua:48: in function 'new' frontend/apps/reader/readerui.lua:578: in function 'doShowReader' frontend/apps/reader/readerui.lua:536: in function <frontend/apps/reader/readerui.lua:535>12/23/20-16:32:30 INFO FM loaded plugin SSH at plugins/SSH.koplugin

12-23-2020, 10:44 AM	#8
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	I'm going to need the full context, not just an excerpt.

12-23-2020, 11:00 AM	#10
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Which FW version is your PW1 running on?

12-23-2020, 11:03 AM	#11
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	And this vaguely looks like an incomplete/badly updated install, so I'd try a really clean install, from scratch .

12-23-2020, 01:55 PM	#13
LittleBiG Zealot Posts: 122 Karma: 10 Join Date: Nov 2014 Device: Kindle Oasis 3, K4NT, Kobo Mini	Came back. Something changed in KOreader so when I run a book by kpvbooklet, I get this error message. And this was the very problem before too.

12-23-2020, 02:45 PM	#14
NiLuJe BLAM! Posts: 13,477 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Ah, now that makes more sense . I'll try to suss out why that is, exactly.

12-23-2020, 05:45 PM	#15
yparitcher Connoisseur Posts: 52 Karma: 616590 Join Date: Feb 2019 Device: K4 KT4 PW4 PW5	https://github.com/koreader/koreader/pull/7041

Advert

Advert