Dim Screensaver Won't Un-Dim

I’ve been using just the Dim screensaver for years. Right now I’m running Kodi on OSMC on both a Vero and an RPi. I use the Back Row skin for both.

Recently I’ve noticed that the first time I use Kodi each day the screen stays dimmed even after I press a remote key. I can navigate the GUI just fine and even start playing a video, but the screen stays dim until I reboot. I have yet to try just restarting Kodi to see if that fixes it. On the Vero I’m using both the iOS Kodi remote and CEC. On the Pi i’m using the iOS remote and an add-on MCE remote.

Is there anything specific I should look for in the log?

What follows is the log beginning with the first keypress that should have stopped the screensaver.

11:16:01 T:1918108704   DEBUG: CAnnouncementManager - Announcement: OnScreensaverDeactivated from xbmc
11:16:01 T:1918108704   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverDeactivated
11:16:01 T:1613640736   DEBUG: service.libraryautoupdate-0.9.8 : screen saver off
11:16:08 T:1918108704   DEBUG: PushCecKeypress - received key  b duration 0
11:16:08 T:1956118528   DEBUG: OnKey: 11 (0x0b) pressed, action is Select
11:16:08 T:1956118528   DEBUG: CGUIMediaWindow::GetDirectory (videodb://tvshows/titles/833/)
11:16:08 T:1956118528   DEBUG:   ParentPath = [videodb://tvshows/titles/]
11:16:08 T:1135244320  NOTICE: Thread JobWorker start, auto delete: true
11:16:08 T:1135244320   DEBUG: RunQuery took 51 ms for 1 items query: SELECT * FROM season_view  WHERE season_view.idShow = 833
11:16:08 T:1135244320   DEBUG: RunQuery took 5 ms for 0 items query: select * from movie_view join movielinktvshow on movielinktvshow.idMovie=movie_view.idMovie WHERE movielinktvshow.idShow = 833
11:16:08 T:1956118528    INFO: MYSQL server has gone. Will try 4 more attempt(s) to reconnect.
11:16:08 T:1918108704   DEBUG: PushCecKeypress - received key  b duration 125
11:16:08 T:1956118528   DEBUG: CGUIMediaWindow::GetDirectory (videodb://tvshows/titles/833/-2/?tvshowid=833)
11:16:08 T:1956118528   DEBUG:   ParentPath = [videodb://tvshows/titles/]
11:16:08 T:1135244320   DEBUG: RunQuery took 9 ms for 8 items query: select * from episode_view  WHERE episode_view.idShow = 833
11:16:08 T:1135244320   DEBUG: RunQuery took 3 ms for 0 items query: select * from movie_view join movielinktvshow on movielinktvshow.idMovie=movie_view.idMovie WHERE movielinktvshow.idShow = 833
11:16:08 T:1956118528   DEBUG: WindowVideoNav::GetDirectory
11:16:08 T:1009767456  NOTICE: Thread BackgroundLoader start, auto delete: false
11:16:08 T:1956118528   DEBUG: SECTION:LoadDLL(special://xbmcbin/system/ImageLib-arm.so)
11:16:08 T:1956118528   DEBUG: Loading: /usr/lib/kodi/system/ImageLib-arm.so
11:16:08 T:1009767456   DEBUG: Thread BackgroundLoader 1009767456 terminating
11:16:08 T:1009767456  NOTICE: Thread JobWorker start, auto delete: true
11:16:08 T:1604989984  NOTICE: Previous line repeats 2 times.
11:16:08 T:1604989984   DEBUG: SECTION:LoadDLL(libnfs.so.4)
11:16:08 T:1604989984   DEBUG: Loading: libnfs.so.4
11:16:09 T:1604989984   DEBUG: NFS: Context for 192.168.0.75/Volumes/Media not open - get a new context.
11:16:09 T:1604989984   DEBUG: NFS: Connected to server 192.168.0.75 and export /Volumes/Media
11:16:09 T:1604989984   DEBUG: NFS: chunks: r/w 65536/65536
11:16:11 T:1918108704   DEBUG: PushCecKeypress - received key a6 duration 0
11:16:11 T:1956118528   DEBUG: OnKey: 166 (0xa6) pressed, action is Up
11:16:11 T:1918108704   DEBUG: PushCecKeypress - received key a6 duration 231
11:16:12 T:1918108704   DEBUG: PushCecKeypress - received key a7 duration 0
11:16:12 T:1956118528   DEBUG: OnKey: 167 (0xa7) pressed, action is Down
11:16:12 T:1918108704   DEBUG: PushCecKeypress - received key a7 duration 235
11:16:14 T:1918108704   DEBUG: PushCecKeypress - received key a8 duration 0
11:16:14 T:1956118528   DEBUG: OnKey: 168 (0xa8) pressed, action is Right
11:16:14 T:1918108704   DEBUG: PushCecKeypress - received key a8 duration 230
11:16:15 T:1918108704   DEBUG: PushCecKeypress - received key a9 duration 0
11:16:15 T:1956118528   DEBUG: OnKey: 169 (0xa9) pressed, action is Left
11:16:15 T:1918108704   DEBUG: PushCecKeypress - received key a9 duration 232

Soon after that the log contains over 1400 entries identical to the following

11:19:02 T:1956118528    INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x60604e0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'

And, yes, all 1400+ have the same time stamp: 11:19:02

Entire log from the first keypress is here:

kodi.log

1 Like

I’ve got this sometimes as well, but it happend in previous builds as well though

1 Like

Ah, thank-you.

Finally a problem where I’m not the only one.

I have seen this but very rarely, as far back as Gotham on Raspbmc.

Usually when I choose to reboot it un-dims just as its shutting down…

Seems like a long standing bug.

Yup here as well, but mostly I do a service restart

Interesting. I’d never seen it before the last few days.

I’m switching screen savers to see if that fixes it.

Dim always undims if it kicks in when I’ve paused a video.

In fact, it seems to only refuse to undim the first time I use Kodi each day.

I have also experienced this problem, intermittently, with various versions (OSMC & RaspBMC) and usually, simply starting playback of a video file and stopping will un-dim the screen in most cases. Sometimes a full reboot has been necessary. Your mileage may vary.

I tried that once or twice, but that displayed just a dimmed movie…

Some here. Just a dimmed movie.

Now that I have changed screen savers, the problem has gone away.

I’m using some cartoon cat which the family finds amusing.

Same problem here for the last few days.
I found that switching skins momentarily woke the screen up.
Playing a video stream didn’t wake it up.
Hope this gets sorted out.
I leave my RPi2 on all the time so hopefully this has fixed it - I’ll report back if it doesn’t.

1 Like

Once it is dimmed, does waiting for screensaver to dim again and then waking it up fix it?

So, you’re saying that when the screensaver doesn’t undim, we should wait for the length of time it would take to dim again and then try to undim? (What awful language….)

If we assume the dim screensaver does a dim on start and an undim on stop and for some reason occasionally the undim fails to happen, you might expect another dim/undim cycle to have a good chance of fixing it.

If it never fixes it then it probably suggests the bug is something else.

It doesn’t. At least not for me. I’m still using Dim on my Vero.

I just had the dim again, waiting for it to dim and undim again, didn’t work…

So, I’ve had to do this a couple more times since.
I’m going to try switching skins more permanently to see if I still have the same problem.
This is unfortunate because the OSMC skin has acceptance from my wife (SAF).
I’ll report back on my findings…

:boom: update :boom: - so I changed skins but ultimately had the same problem.
Wondered whether it was something to do with the CEC control & checked by using the Kodi remote (http) app instead - same result. So I guess the problem is not skin or CEC related.
Must be something within Kodi/OSMC itself.

Yep, here to. I can reproduce it by calling ReloadSkin(). After that dim won’t work as it should.

1 Like

Ah very interesting. Thanks for the heads up on reload skin.

Cc @sam_nazarko

Nice find, I’ll do some tests

Sam

I’ve got a fix for this:

I’ve added to backports.

1 Like