@dhdurgee:
The fix I referred to was the fact that the "restart framework" button in KUAL didn't actually restart the ScreenSavers hack too. That's what's been fixed
.
And yes, on FW 5.x, that's the only way to make the framework happy when it gets its panties in a bunch about a screensaver.
As for the actual root cause, since it pretty much should never happen, and the hack takes great pains to avoid upsetting the framework if ever something goes wrong for some strange reason, beats me.
Just to double-check, because I just realized you're on a K3 and not something running FW 5.x: what was actually shown as a screensaver when you deemed it broken? A white screen or an outdated cover? An outdated cover is the expected behavior, but a white screen certainly isn't, and, IIRC, the framework is much more forgiving on legacy devices, and will pick up a working image on the next cycle (if the underlying image is actually switched to a working one, that is ^^).
That it would keep showing a white screen would point to a real bug. Which is definitely not out of the question, since cover mode on legacy devices is pretty much a house of cards waiting to be blown out ^^.
(Yup, it's been the day of "Oh god, the FW 2.x/3.x/4.x branch of the code is terrible" ^^).