Make reboot_on_exit=false work?

[baskerville]

I've tried reboot_on_exit=false on my Glo HD (with firmware 4.3.8945) and it seems to produce a crash while Nickel is relaunching but I'm not sure on how to debug.

[NiLuJe]

A description of what leads you to think it's a crash would be nice ;).

(i.e., what exactly happens, when, what's on screen or not; that kind of thing ;)).

Also, which version/build of KOReader are you running?

---

That said, I haven't had time to check how everything behaves on FW 4.x in general, so, here be dragons ;).

[baskerville]

Thanks, well after quitting KOReader, I can see Nickel's progress bar starting to fill, but the home screen is never reached: the progress bar stays frozen at 3 filled bars out of 5.

I'm using KOReader version v2015.11-896-g4316284.

I witnessed the same behavior when I tried with the latest 3.x firmware.

[NiLuJe]

I vaguely recall fixing at least one apparent cause of this (IIRC, making sure WIFi was disabled before restarting Nickel), but apparently that wasn't enough ;).

I'll hopefully have more free time available in a few weeks to try and dig into that again, but, as you said, debugging those issues is kind of annoyingly hard...

[pazos]

Yes, It happens to me too. I mentioned elsewhere, but seems related to https://github.com/koreader/koreader/blob/master/platform/kobo/koreader.sh#L48:L57.

@NiLuJe I think siphon nickel full environment should be safe on fmon side, but produces the same crash in fmon returning to nickel.

@baskerville: you can try deleting those lines https://github.com/koreader/koreader/blob/master/platform/kobo/koreader.sh#L49:L53

nickel environment should be handled by nickel.sh in https://github.com/koreader/koreader/blob/master/platform/kobo/nickel.sh#L10:L27 and https://github.com/koreader/koreader/blob/master/platform/kobo/nickel.sh#L62:L70

[baskerville]

@pazos I tried: I tought nickel was caught into an infinite loop because the black squares kept being filled and emptied, but after about 15 seconds the home screen finally appeared but it was displayed in a tiny region of the screen and there was a critical error dialog box with only one button: sign off!

[NiLuJe]

Yep, that (the broken fb output) sounds familiar, and is one of the reasons I switched to a full siphon... Somehow, something's missing somewhere, or something causes nickel to initialize differently, and doing shit on both ends initially appeared to do the trick on my end... @pazos: To be clear, are you confirming that, right now, the exact same crash happens when exiting KOReader when launched from fmon instead of kfmon?

[baskerville]

I found something that sounds related https://www.mobileread.com/forums/showpost.php?p=3403689&postcount=266.

[NiLuJe]

We do kill wi-fi when starting nickel, because I noticed that well before FW 4.x

…

On Apr 9, 2017 10:48 AM, "Bastien Dejean" ***@***.***> wrote: I found something that sounds related https://www.mobileread.com/ forums/showpost.php?p=3403689&postcount=266. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG1Zq7gNgcgNb-AHhPMpoTI6_DDa1shks5ruJtDgaJpZM4MdwBp> .

[pazos]

@baskerville: sorry to hear that!

@NiLuJe: yes, siphoning the whole environment makes imposible to return to nickel (It gets stuck on the third square, like baskerville).

I'm not sure what causes this but fmon works really nice loading the minimum environment. Returning from koreader to nickel is less than 3 seconds in my KA1

[baskerville]

@pazos Can you provide a link to the fmon archive?

[pazos]

here is the updated one I proposed for the new instructions. I'm waiting for the fix to this bug and upload kfmon instructions in koreader wiki too.

Look at the lastest comment in
koreader/koreader#2575. It clashes with kfmon, so you'll need to remove kfmon first

[pazos]

@NiLuJe: I do understand why you launch kfmon via udev hook, but I think I'm going to try to start it from inittab and see what's happen. As you pointed out maybe the environment is different and could cause issues.

kfmon is a good improvement over fmon, with documentation, readable sources and a lot of checks. The missing feature is returning without reboot, which I've been doing since 2012 with fmon.

@baskerville:
The only bug that I can find in nickel without rebooting is:

on returning to nickel: the first sync fails (udhcpcd ins't able to get a lease). Nickel itself seems to handle it in less than a minute. So the next sync will work.

steps to reproduce:
-- enable wifi in nickel
-- run koreader
-- sleep the device
-- back from sleep
-- connnect to wifi again
-- return to nickel

[baskerville]

@pazos Thanks, fmon works great (as long as nickel isn't killed while syncing). I wrote a C version of fmon and I improved the shell scripts (wrapping the call inside the loop in on-animator.sh is unnecessary).

[pazos]

cool!!!!

Please create install instructions and we're done :)

I think is better to move further fmon development to your repo and leave this issue open here.

[NiLuJe]

Okay, term & finals are nearly done, I'll be able to take a good look at this Real Soon now! :).