Forma Odd font abnormality on Forma post-upgrade 4.32

[Skydog]

I'm well aware of the major font re-write in the current update, however...

My Forma and Sage now display a strange font problem that I have not seen reported. Instead of the normal serif, all system fonts, i.e., home page, my books list, settings, sub-menus, everything, all display in a large sans-serif font, about 30% larger than normal. I noticed the anomaly when I first connected via USB post-upgrade and the "Connected and charging" font was larger and displayed in sans-serif.

I reinstalled the update and the result is the same, with or without patches installed. The only solution is to restart the Sage & Forma after every USB eject and the system font then returns to normal.

Has anyone else seen this? This has never occurred with the Libra2/H20, or Elipsa.

[davidfor]

I haven't noticed anything different on any of my devices. The two things I can think of would be a patch that isn't working the same as before, or the "Large Print Mode" in the Beta Features has been turned on.

There were changes a while ago. But, if you have been keeping up with the firmware updates, that would not be anything new.

[Skydog]

Originally Posted by davidfor

I haven't noticed anything different on any of my devices. The two things I can think of would be a patch that isn't working the same as before, or the "Large Print Mode" in the Beta Features has been turned on.

There were changes a while ago. But, if you have been keeping up with the firmware updates, that would not be anything new.

As mentioned, this happened without any patches installed, fresh after the update. Large Print Mode has never been activated either. Very strange.

Edit: I lied. I was able to replicate this on my Sage as well.

[PeterT]

Any additional fonts installed?

Sent from my Pixel 4a using Tapatalk

[Skydog]

Originally Posted by PeterT

Any additional fonts installed?

Sent from my Pixel 4a using Tapatalk

Yes:

Amazon Ember
Bookerly
Charis6eink
Literata Book
Sitka Text

Edit: Same problem on the Sage too.

[rtiangha]

A couple of us reported this in the 4.32 thread (if you open a book in this state, it''ll throw a message about adding Georgia as a supplemental font). A hypothesis was that there were too many sideloaded fonts but you don't have a lot. I still think it's a lack of ram problem preventing a service or executable from restarting after USB disconnect (to which I would suggest to the devs locking in that service into memory like NickelMenu does).

So, let's try something else: do you have a lot of books and/or a large KoboReader.sqlite database file (mine is 600 mb+ and I get the issue)? A large database would also eat up ram. Just shooting from the hip here.

[Skydog]

Originally Posted by rtiangha

A couple of us reported this in the 4.32 thread (if you open a book in this state, it''ll throw a message about adding Georgia as a supplemental font). A hypothesis was that there were too many sideloaded fonts but you don't have a lot. I still think it's a lack of ram problem preventing a service or executable from restarting after USB disconnect (to which I would suggest to the devs locking in that service into memory like NickelMenu does).

So, let's try something else: do you have a lot of books and/or a large KoboReader.sqlite database file (mine is 600 mb+ and I get the issue)? A large database would also eat up ram. Just shooting from the hip here.

Thank you for your reply. I thought I had digested the entire thread but I missed this issue. I have not experienced any messaging regarding adding Georgia, only the change to a large system sans-serif as soon as I connect via USB (first noticed with "Connected and charging" text). Neither the Libras nor the Elipsa display the problem.

Below are figures for number of books (all sideloaded) and corresponding size of KoboReader.sqlite files:

Sage: 400 books, 36mb

Forma: 700 books, 57mb

[rtiangha]

Hmm, then that may not be it either. So here's a total shot in the dark: If you remove Sitka, does the issue continue? It has a weird em value and maybe that''s triggering things. That's the only other thing I can think of that we have in common.

[Skydog]

Originally Posted by rtiangha

Hmm, then that may not be it either. So here's a total shot in the dark: If you remove Sitka, does the issue continue? It has a weird em value and maybe that''s triggering things. That's the only other thing I can think of that we have in common.

I had already deleted Sitka and the problem persists with only Amazon Ember, Bookerly, Charis6eink and Literata Book installed. I haven't yet but I am considering removing all added fonts and adding a few back one at a time. This is a real head-scratcher, particularly since this does not occur with the Libras or Elipsa. There's nothing worse than having everything running smoothly and customized only to have Kobo break something. Although not a fatal bug, it's d------ed irritating having to power off/on after every disconnect, particularly since the Sage cover has no cutout for the power button.

[JSWolf]

Originally Posted by Skydog

I had already deleted Sitka and the problem persists with only Amazon Ember, Bookerly, Charis6eink and Literata Book installed. I haven't yet but I am considering removing all added fonts and adding a few back one at a time. This is a real head-scratcher, particularly since this does not occur with the Libras or Elipsa. There's nothing worse than having everything running smoothly and customized only to have Kobo break something. Although not a fatal bug, it's d------ed irritating having to power off/on after every disconnect, particularly since the Sage cover has no cutout for the power button.

What happens if you remove all side loaded fonts? If it doesn't happen, try adding one font at a time and then testing until you see the problem.

I'm not sure if you should reboot between font changes.

[Skydog]

Originally Posted by JSWolf

What happens if you remove all side loaded fonts? If it doesn't happen, try adding one font at a time and then testing until you see the problem.

I'm not sure if you should reboot between font changes.

Did that already with no change. This is only occurring on the Sage and Forma, not Libras (both) or Elipsa. One thing not yet tried is a complete removal of added fonts prior to reinstalling the update (without patches). The only other option for troubleshooting is a factory reset which I do not care to do.

[Krios]

Try deleting fonts.sqlite database file, i think it's in .kobo folder.

[Skydog]

Originally Posted by Krios

Try deleting fonts.sqlite database file, i think it's in .kobo folder.

Ah... I had not thought of that. I'll incorporate it in my troubleshooting when I can carve out some time later today.

Thank you!

[JSWolf]

Originally Posted by Skydog

Ah... I had not thought of that. I'll incorporate it in my troubleshooting when I can carve out some time later today.

Thank you!

Also check "Kobo eReader.conf" to see if there is anything there that might cause this problem.

[Skydog]

UPDATE: Solved!

Thanks to all for the suggestions, a special hats off to Krios who provided the missing piece of the puzzle. Following is what fixed the problem for me:

• Delete both the fonts folder (user fonts) and the fonts.sqlite file located in .kobo folder
• Eject and restart device (Power off & power on)
• Connect device - the normal system serif font should appear (as evidenced by "Connected and charging")
• Create a new fonts folder and add one font, eject and verify
• I added one font at a time and disconnected, just to confirm there were no additional anomalies