View Single Post
Old 03-22-2018, 04:53 PM   #476
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 ItalianUruguayan View Post
I see, thanks a lot I'll see if I can do something to make it work, but probably I will not be able to achieve that (since my programming knowledge is close to zero) but you never know.

The new versions of KoboLauncher work well on newer firmwares, though. This starts to give this problem when you go below 3.16.0.
In run_nickel.sh there is
Code:
if [ -f /usr/local/Kobo/sickel ];
then
    /usr/local/Kobo/sickel -platform kobo:noscreen $@
fi
sickel was introduced later than 3.15.0. If you downgraded to 3.15.0 without doing a factory reset, /usr/local/Kobo/sickel is still at your device, and will therefore be executed (which very likely causes a problem). So you can try to delete the file sickel or to modify the code to the effect that sickel is only called if the firmware is higher than 3.15.0.

Last edited by tshering; 03-22-2018 at 04:57 PM.
tshering is offline   Reply With Quote