09-08-2023, 02:36 PM
@romain
You gave no details of your setup so we're pretty much in the dark here. Physical details (like what kind of display are you using), software settings (like moodeutl -s output), all grist for our mill when we're trying to diagnose problems remotely.
In my case, I just brought up a fresh moOde 8.3.5 player (64-bit) on an RPi3B+ which has an official Raspberry Pi 7" Screen installed. The local display was set "on"; the mouse cursor was set "off"; the popup keyboard (aka on-screen keyboard or OSK) was set "on". Result: local display works fine.
Then I did an in-place software update to 8.3.6.
When the dust had settled, I saw the same thing @Nutul saw. My local display came back up but with the mouse cursor "on" despite the System Config options saying it was still "off". A simple on-off cycle in the options fixed that.
In my case the popup keyboard was restored but perhaps I didn't trigger something @Nutul did.
Result: Local display on my updated 8.3.6 player is working fine.
Regards,
Kent
You gave no details of your setup so we're pretty much in the dark here. Physical details (like what kind of display are you using), software settings (like moodeutl -s output), all grist for our mill when we're trying to diagnose problems remotely.
In my case, I just brought up a fresh moOde 8.3.5 player (64-bit) on an RPi3B+ which has an official Raspberry Pi 7" Screen installed. The local display was set "on"; the mouse cursor was set "off"; the popup keyboard (aka on-screen keyboard or OSK) was set "on". Result: local display works fine.
Then I did an in-place software update to 8.3.6.
When the dust had settled, I saw the same thing @Nutul saw. My local display came back up but with the mouse cursor "on" despite the System Config options saying it was still "off". A simple on-off cycle in the options fixed that.
In my case the popup keyboard was restored but perhaps I didn't trigger something @Nutul did.
Result: Local display on my updated 8.3.6 player is working fine.
Regards,
Kent
