View Single Post
Old 04-08-2022, 08:49 PM   #173
MGlitch
Wizard
MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.
 
Posts: 2,857
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
This seems to have either broken, or just does not work with the Kobo Sage.

Running
Kobo firmware 4.31.19086
NickelMenu 0.5.4
NickelDBus 0.2.0 (I installed this over what KU installed just in case neither made a difference)
KU 0.5.3Beta1

What happens:

KU's NM item is there, running it the first time did install nickel dbus (since installed over but at least this far it appeared to be doing what it was supposed to). After the NDbus install, subsequent runs of KU produce the following results: Starting KoboUNCaged, running precautionary library rescan, kobo uncaged Finished.

This happens with wifi on OR off, it never prompts me to turn it on.

The same setup works as expected on a Kobo Forma running 4.31.19086 so it does not appear to be the firmware.

Steps taken to fix the issue:

1) Installed ndbus manually just incase it was a weird case of an old version
2) re-downloaded NM and KoboUncaged to ensure I was on the specified versions
3) turned wifi on just in case connecting was the issue
4) since my Sage is patched and I can't recall what patches might conflict nor what patches i had on my Forma, I reinstalled the 4.31 firmware to wipe all patches out

None of the above has had any affect on the process that happens upon running KU.

ETA 1- Apparently the Libra 2 is *also* affected by this issue.

Unfortunately I'm not sure if it's 4.31.19086 on these devices or just these devices. I'll try installing 4.30 on one and see if that fixes it. Though I have my doubts.

ETA 2- Tried 4.30 on the Libra 2 to the same result.

ETA 3- So feeling like a dunce, I checked the log which pretty much confirms it's a Sage/Libra 2 issue:

Code:
Apr 08 21:25:44 [Kobo-UNCaGED] Enabled loopback interface
Apr 08 21:25:44 [Kobo-UNCaGED] Starting Kobo UNCaGED
[Kobo-UNCaGED] 2022/04/08 21:25:44 Started Kobo-UNCaGED
[Kobo-UNCaGED] 2022/04/08 21:25:44 Creating KU object
[Kobo-UNCaGED] 2022/04/08 21:25:44 Getting Kobo Info
[Kobo-UNCaGED] 2022/04/08 21:25:44 New: failed to get kobo info: New: unknown device
[Kobo-UNCaGED] 2022/04/08 21:25:44 New: failed to get kobo info: New: unknown device
Apr 08 21:25:44 [Kobo-UNCaGED] Running precautionary library rescan
Apr 08 21:25:47 [Kobo-UNCaGED] Disabled loopback interface

Last edited by MGlitch; 04-08-2022 at 09:28 PM.
MGlitch is offline   Reply With Quote