Hi folks,
Had this issue for about as long as I can remember since starting to use OSMC but always had it on the back burner in favour of getting other issues sorted out.
I’m getting increasingly frequent issues with corrupt or missing icons and fonts, seemingly caused by browsing my music library.
I found this previous report https://discourse.osmc.tv/t/garbled-fonts-in-menu/81858 but since the attached screengrabs have expired I can’t say if it is 100% the same issue.
My experience is that Icons on the left side menu can disappear being replaced by a solid block of colour. This also affects the letter at top of screen when browsing libraries using the slider. The main menu listing of album names and artists and possibly other areas which I will work on getting pics of myself.
I can’t see anything in the logs I have but will try and get some debug logs up after trying to test this today as I work on a theory that this issue does not occur with fonts set to Arial.
As for a fix I have so far only found that a reboot, or reload of the skin or font will resolve this. I’m using Estuary with a custom colour set if this helps.
What device are you using?
Can you reproduce it with the OSMC skin?
Hi Sam,
I’ve experienced this across all my devices at some stage or another (again typically when browsing the music library) so Pi4, Vero 4K+ and V.
I don’t use the OSMC skin but next time I’m playing music I’ll switch to it and see.
One thing I just remembered, I delete the vendor_logo.png for a cleaner interface, could this possibly have a knock on effect?
Honestly, if you deleted the vendor logo, then you aren’t using Estuary as shipped. That has all the graphics in a texture pack, and you can’t delete just one without really understanding texture packs… The only way you could delete just one is if you download Estuary from the Github repo manually and then activated it. That’s going to make it very hard to troubleshoot as you are, in essence, using a custom skin.
I have replaced vendor_logo.png at /usr/share/kodi/media and will monitor things, if that proves to be the culprit then hands up, sorry for wasting your time.
Rebooted my Vero V after replacing the .png, skin set to Estuary, was playing music for a while, then left it on music browser, came back to it some time later and pressed ‘back’ to go to main menu. Got corrupt fonts with music selected on main menu.
2024-03-27 15:40:35.857 T:2956 info <general>: CActiveAESink::OpenSink - initialize sink
2024-03-27 15:40:35.857 T:2956 info <general>: CAESinkALSA::Initialize - Requested layout FL, FR, FC, BL, BR
2024-03-27 15:40:35.857 T:2956 info <general>: CAESinkALSA::Initialize - set digital codec 0
2024-03-27 15:40:35.857 T:2956 info <general>: CAESinkALSA::Initialize - Attempting to open device "default"
2024-03-27 15:40:35.864 T:2956 info <general>: CAESinkALSA::Initialize - Opened device "default"
2024-03-27 15:40:35.864 T:2956 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2024-03-27 15:40:35.864 T:2956 info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2024-03-27 15:40:35.898 T:2956 info <general>: CAESinkALSA::Initialize - speaker layout 10
2024-03-27 15:40:58.230 T:2956 info <general>: CActiveAESink::OpenSink - initialize sink
2024-03-27 15:40:58.230 T:2956 info <general>: CAESinkALSA::Initialize - Requested layout FL, FR, FC, BL, BR
2024-03-27 15:40:58.230 T:2956 info <general>: CAESinkALSA::Initialize - set digital codec 0
2024-03-27 15:40:58.230 T:2956 info <general>: CAESinkALSA::Initialize - Attempting to open device "default"
2024-03-27 15:40:58.236 T:2956 info <general>: CAESinkALSA::Initialize - Opened device "default"
2024-03-27 15:40:58.236 T:2956 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2024-03-27 15:40:58.236 T:2956 info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2024-03-27 15:40:58.268 T:2956 info <general>: CAESinkALSA::Initialize - speaker layout 10
2024-03-27 15:41:56.098 T:2901 info <general>: NFS is idle. Closing the remaining connections.
Nothing that relates from this time in the logs that I could see.
Any thoughts?
Had this issue again tonight, switched to OSMC skin and tried to repeat what I had been doing and didn’t experience any issues.
What can I do to help diagnose this, being that it is quite sporadic? Debug mode and then try to reproduce?
If so is there any component specific logging that would assist?
Had this issue again over the weekend which caused the main menu items to be replaced by the blocky ‘font’. I’m working on the possibility that it could be caused by Shadertoy as this is a common link between all my devices as I always have the full screen graphic equaliser preset active.
This is the main menu after encountering issue in prev. post. Will continue using music browser with no visualisation, no issues as yet. Anyone have any thoughts on Shadertoy being the cause?
On Pi this could look like GPU memory is exhausted.
The pic in my prev. post is of my Vero V. But have experienced on 4K+ / Pi 3 / Pi 4.
Then I am guessing some texture or asset is corrupted.
Does this happen when you don’t modify the skin?
I’ve tried two approaches, replaced vendor_logo.png with blank .png of same name and removed vendor_logo.png completely. Have experienced this issue in both scenarios.
But does it happen when you don’t make these modifications?
Yes, just replicated it this morning by skipping between albums / tracks. However that again was with fullscreen Shadertoy enabled. I have now disabled it again and am continuing to try and reproduce the issue.
It does seem to be related to Shadertoy, Sam.
Played music for about an hour with no visualisation and couldn’t reproduce. Turned Shadertoy back on and within 2 track changes, the main menu buttons disappeared, then changed to blocky font.
All settings for it are default, show fanart background disabled, Animate background disabled.
Now trying other presets than my usual 2D LED Spectrum.
Encountered this issue on my Vero V today again, should I pass to Shadertoy devs, I presume at Issues · xbmc/visualization.shadertoy · GitHub
Which shadertoy plugin are you using?
I was using ‘Sound sinus wave’ and changed it because of quite some mali issue according to @sam_nazarko: OSMC Vero V Review - #274 by Theetjuh
No idea if it works well again, I could test it this afternoon.
Still an issue … blocky as hell after a few minutes.
