KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[goldencore]

@hawhill
Yes, I start Koreader via KUAL and I also have the freezing issue with different epubs. As soon as I open the font size dialog everything comes to a stop. (Same thing just happened while choosing the "Borders" setting.)

Regarding the dictionaries: This is working now! Somehow the dict directory was empty. Maybe I just imagined putting files there! :-) Who knows....

[hawhill]

OK, so there's probably some kind of deadlock. Will investigate soon.

[donMaranzano]

I have installed the reader but sharing function is not working. What I'm doing wrong?

[hawhill]

Errm - what sharing function exactly? Can you go a bit into detail what function you are trying to use and what actually happens?

[donMaranzano]

Originally Posted by hawhill

Errm - what sharing function exactly? Can you go a bit into detail what function you are trying to use and what actually happens?

I'm selecting a text from the book, it gives me four options: Highlight, Translate, Add Note and Share are disabled.

[hawhill]

Yes, Note adding and sharing are not yet implemented. There is, however, the evernote plugin. It's not yet coupled with the "share" button, though.

[tchzhy]

I found there is a bug. After I had opened a pdf file and then wanted to change the columns, my kindle was found to be freezed and then it rebooted.

I am using PW2, FW:5.4.3.2, koreader version: v2014.04-1289-gddae003.

[knc1]

Originally Posted by tchzhy

I found there is a bug. After I had opened a pdf file and then wanted to change the columns, my kindle was found to be freezed and then it rebooted.

I am using PW2, FW:5.4.3.2, koreader version: v2014.04-1289-gddae003.

Most likely not a bug, but instead you reached the memory limit of the Kindle.
What size is your pdf file?

If you have the technical background, you could check this by enabling a swap file and see if the problem goes away.

[tchzhy]

Originally Posted by knc1

Most likely not a bug, but instead you reached the memory limit of the Kindle.
What size is your pdf file?

If you have the technical background, you could check this by enabling a swap file and see if the problem goes away.

It is about 23.1M.
I tried to open a 1.23M pdf file and got the same result. Kindle freezed and rebooted.

[knc1]

Originally Posted by tchzhy

It is about 23.1M.
I tried to open a 1.23M pdf file and got the same result. Kindle freezed and rebooted.

I agree, those sizes should not be too big to handle.

Although the description of what is happening is that of memory exhaustion (but for another (bug?) reason).

Checking the system log files ( ;dm in the Kindle's search bar ) might give some information, but will probably only tell that the application was terminated for over-limit memory use.

I have to turn this question over to Hawhill.

[hawhill]

The size of the PDF won't really matter. It's more complicated with PDF, some objects will claim memory, some won't. As a rule of thumb, bitmaps and, most of all, transparency/filter masks will be costly. That said, I don't think the issue at hand has to do with that.

The column icons will only influence the reflow - do you have reflow activated?

That said, we do nothing that would make the Kindle reboot (I think). Freeze up - yes, we can do that :-) It shouldn't happen of course, but well. But freezing and rebooting are mutually exclusive. I take it it "froze" only for a short while?

If no crash.log file is left behind, we probably need a publicly available PDF to try to reproduce the crash. It seems to look good for me and the PDFs I tried, but then I just plowed boldly through the code base and there was one change to the library we use to do PDF reflow. So I would not absolutely exclude it. However, we need to reproduce the problem. Before going any further - did you try to reinstall over the existing files? It's not unheard of that files get corrupted during copying to the Kindle, so making sure (again) that the right ones are on the device is always a good idea.

[jation]

In last (20141201) version whenever I try to change font size KPW2 freeze and after 30 seconds restart.
In previous versions I have some random freezes (when try to change margins, line spacing, font... ) and I must to manually restart kindle.
All this happening with epub files.

[tchzhy]

Originally Posted by hawhill

The size of the PDF won't really matter. It's more complicated with PDF, some objects will claim memory, some won't. As a rule of thumb, bitmaps and, most of all, transparency/filter masks will be costly. That said, I don't think the issue at hand has to do with that.

The column icons will only influence the reflow - do you have reflow activated?

That said, we do nothing that would make the Kindle reboot (I think). Freeze up - yes, we can do that :-) It shouldn't happen of course, but well. But freezing and rebooting are mutually exclusive. I take it it "froze" only for a short while?

If no crash.log file is left behind, we probably need a publicly available PDF to try to reproduce the crash. It seems to look good for me and the PDFs I tried, but then I just plowed boldly through the code base and there was one change to the library we use to do PDF reflow. So I would not absolutely exclude it. However, we need to reproduce the problem. Before going any further - did you try to reinstall over the existing files? It's not unheard of that files get corrupted during copying to the Kindle, so making sure (again) that the right ones are on the device is always a good idea.

With and without the reflow activated, after I had tried to change the columns, kindle freezed and rebbooted.

The following is what I found in the crash.log under koreader directory:

warning: not building glyph bbox table for font 'ABCDEE+溘冼_GB2312' with 7580 glyphs

[johnnyb]

Hi there, I've started using koreader on the Paperwhite 2 (5.4.5.1) and I must say that I'm blown away by the ease of use, speed and stability for PDFs especially. No other ereader does provide this level of quality, absolutely great!
However, once I read a couple of things, I tried to export my highlights to Evernote (such a great idea!) but after entering my credentials (and I verfied they were correct on my phone by logging out and in again) I get the following message:
"An error occurred while logging in: plugins/evernote.koplugin/EvernoteOAuth.lua:339: OAuth verifier not found"
I understand that this has something to do with the fact that somehow I get no response from Evernote to allow koreader to be logged in, but I have found no way to remedy this. What I've tried so far: search the web for solutions using various parts of the error message, no results. Checking if there's something pending on Evernote's side that I need to allow first, nothing (I dont have 2 step authentication active). Both updating and reinstalling koreader, same problem with every version I've tried.
Anyone any idea what I'm missing? Help is greatly appreciated!

[chrox]

Originally Posted by johnnyb

Hi there, I've started using koreader on the Paperwhite 2 (5.4.5.1) and I must say that I'm blown away by the ease of use, speed and stability for PDFs especially. No other ereader does provide this level of quality, absolutely great!
However, once I read a couple of things, I tried to export my highlights to Evernote (such a great idea!) but after entering my credentials (and I verfied they were correct on my phone by logging out and in again) I get the following message:
"An error occurred while logging in: plugins/evernote.koplugin/EvernoteOAuth.lua:339: OAuth verifier not found"
I understand that this has something to do with the fact that somehow I get no response from Evernote to allow koreader to be logged in, but I have found no way to remedy this. What I've tried so far: search the web for solutions using various parts of the error message, no results. Checking if there's something pending on Evernote's side that I need to allow first, nothing (I dont have 2 step authentication active). Both updating and reinstalling koreader, same problem with every version I've tried.
Anyone any idea what I'm missing? Help is greatly appreciated!

It was a bug in koreader but it's already fixed in the latest nightly build.