View Single Post
Old 06-14-2015, 12:23 PM   #342
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by Markismus View Post
Question:
Should I just reinstall everything or is there an easy fix?
I do not know!

Quote:
Originally Posted by Markismus View Post
Problem situation:
All of a sudden koreader won't start from KSM7.
Does "All of a sudden" mean that no changes have been made to KSM and you were trying to run the same koreader version that worked up to that point?


Quote:
Originally Posted by Markismus View Post
No crash-logs whatsover in koreader.
Was an empty crash.log file written at all (see the timestamp)? If yes, we know for sure that the line
Code:
./reader.lua "${args}" 2> crash.log
has been executed. But then, why did koreader not run? If no crash log file was written we can assume that reader.lua has not been called, or that for some reason crash.log has not been written to disk.

Quote:
Originally Posted by Markismus View Post
So I looked around and saw that an Nickel update was present. I did a partial update, but still koreader doesn't start.
The presence of a nickel update file should only have an effect if you call Koreader in a koreader-nickel/nickel-koreader loop. Otherwise it should not have any consequences.

Quote:
Originally Posted by Markismus View Post
I installed patch 4 for KSM7. No joy.
You tried running the same koreader version as before. Right?
Quote:
Originally Posted by Markismus View Post
When I press koreader the screen rotates upside-down. When I tap it again, it rotates back.
Which menu are you talking about now? Was it the main menu, and you pressed "start koreader"? Or was it in the "select koreader version" menu and you pressed "koreader.sh"? From your next statements I see that starting from "select koreader version" results in a rotation? Is it the same when starting from the main menu?

Quote:
Originally Posted by Markismus View Post
I installed the newest release of koreader next to the non-starting one. When I select a koreader version, the screen rotates. I tap and it rotates back.
If I understood it correctly up to this point, you cannot start any of the present koreader versions successfully? (I just suppose that you tried starting the main version from the main menu too.)

Frankly, I do not know why koreader does not start on your device. I installed today the most recent nightly build. I have now three versions on this device and all of them run without issues.

As for the rotation issue, I do not have a model with this problem and therefore cannot do any testing myself. I definitely got the rotation script wrong at some points in the latest update (and possibly also in previous updates). It might be that I restore the rotation incorrectly in the script that starts koreader, and that all H2O users with the current KSM version encouter this problem but only you reported it. Or maybe they are all running an older version of koreader that reboots the device after exiting koreader.
If however the script restores the rotation generally correctly, your experience might indicate that in your case the script is not running up to that point, and exits without restoring the rotation. Considering that on your device both koreader versions refuse to run, might indicate that the script is even not running up to the point of calling koreader. Maybe you could to some testing in order to see which parts of the scripts get actually executed.
tshering is offline   Reply With Quote