KPV: a PDF reader for Kindle, based on muPDF, GPLv3

[knc1]

Then that is probably a report BY reader.lua could not find something it needed.
Although that is a bit strange, Lua usually have very good error messages (and a stack back-trace).

Read the reader.lua file (it is human readable, only compiled at runtime) and check for things listed in a 'require' statement not being present.
You will have to check against the search paths used by the Lua that is being executed (Lua has its own search paths compiled in).

[knc1]

Originally Posted by emcintosh

In kpdf.sh (which happens to be located in /mnt/us/kindlepdfviewer/):
Line 08: cd /mnt/us/kindlepdfviewer/
Line 25: ./reader.lua "$1" 2> crash.log

Alternative line 25 I had tried: /mnt/us/kindlepdfviewer/reader.lua "$1" 2> crash.log
- - - - -

And the first line of reader.lua:

#!./koreader-base

Ref: https://github.com/koreader/kindlepd...ter/reader.lua

And the first line of koreader-base:

#!./luajit

Ref: https://github.com/koreader/koreader.../koreader-base

Which ends with:

if not arg[1] then
	error("you must give the name of the main lua executable as the first argument")
end
local file = arg[1]
table.remove(arg, 1)

ARGV=arg

dofile(file)

Note that the error test only tests for the presence of an argument, not if it makes any sense in the context that the script is called.

So, what are you passing as arg[1]?
Does it include a full path to the file?

[ellamasarms]

Originally Posted by emcintosh

I had a similar problem to Fralik - jailbroken Kindle Keyboard on firmware 3.4.2, launching KindlePDFViever gives 'Success!' message then returns me to native menu. I looked in the crash.log file and found that reader.lua wasn't being found, even though it was clearly present in the same directory as the launching script.

Changing the line in kpdf.sh to give the path explicitly (mnt/us/…) didn't work. I could get the script to find (and fail to execute, obviously) other files, but reader.lua remained invisible.

I tried the latest stable (2013.1) build, latest nightly (93, 7/7/13) and the previous stable (2012.11) but none worked. I noticed that the last two nightlies were labelled 'deprecated' and therefore tried the one before them (85, 14/5/13). This worked.

I put this post here in case anyone else has 'reader.lua not found' problems - Google turns up three copies of a question about this (after someone used the devs' fix to issue 814 on Github), but no solutions.

honestly, i'm so grateful for this! i finally got launchpad installed and kpv running!!!

[Philip Man]

Link to last snapshot of KPV is missing.
https://github.com/koreader/kindlepd.../wiki/Download
Is there another source to the binary files?

[Frenzie]

Originally Posted by Philip Man

Link to last snapshot of KPV is missing.
https://github.com/koreader/kindlepd.../wiki/Download
Is there another source to the binary files?

This reply is probably a bit late, but Archive.org preserved it in case you have an old device that won't run KOReader: http://web.archive.org/web/201601171...er-v2013.1.zip

[MarjaE]

Since Librerator is no longer supported, are there any plans to make KindlePdfViewer easier to open?

Shift-P-D assumes two-handed coordination.

[Frenzie]

It's no more supported than Librerator, but it looks like you should be able to change it in the launchpad/kpdf.ini file.

[Actions]
# start kindlepdfviewer with filebrowser in /mnt/us/documents
P D = !/mnt/us/kindlepdfviewer/kpdf.sh /mnt/us/documents
# start kindlepdfviewer with last document
P P = !/mnt/us/kindlepdfviewer/kpdf.sh
# start kindlepdfviewer without framework in /mnt/us/documents
P K = !/mnt/us/kindlepdfviewer/kpdf.sh --framework_stop /mnt/us/documents
# start kindlepdfviewer without framework on last read document
P L = !/mnt/us/kindlepdfviewer/kpdf.sh --framework_stop
# restart amazon framework - when it got irritated
P R = !/etc/init.d/framework restart