Bug 18060 - Clock screensavers misbehave if Player is booted before the server
: Clock screensavers misbehave if Player is booted before the server
Status: UNCONFIRMED
Product: SB Touch
Classification: Unclassified
Component: Screensavers
: unspecified
: PC Linux (other)
: -- minor with 2 votes (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-24 14:57 UTC by Mikael Nyberg
Modified: 2013-11-24 14:59 UTC (History)
1 user (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael Nyberg 2013-11-24 14:57:54 UTC
How to reproduce

Configure the screesaver as follows .

Transparent Clock for the stopped saver .
Black clock for the off saver .

Put the player in off state .

Pull the plug on the player .

Stop the server.

Power up the player again .

It resumed to the home menu no clock no stopped screensaver or off screensaver .

It sends WOL signal to the server so my server is booting up .

When the server is up and running and connected still no screensaver not stopped or off screensaver , no screensaver . I did wait long enough so it should have kicked in.

I navigate to the now playing screen it says stopped on the current playlist ,still no screensaver .

Start and stop the playlist ,still no stopped screensaver . Note I mean stop not pause ! there is a difference hold the pause button longer .

Now i push off on the player and get the off screensaver ! yeah .

Now start the playlist again and then stops it and now i get the stopped screensaver ??

After discussion in the forum we agree that this is due to that if the server was absent during boot Touch may not update it's clock for a very long time thus show no clock based screen savers .

The behaviour was assumed to be this :

"When the server comes back up the Touch does not necessarily connect to it until you do some form of trying to play music, THEN it connects, gets the current time and now it can display the clock. "

This is not ideal ,but it does not work that way either I could play music start an stop the track have it show the cover and now playing screen . The clock did not start to work until I did a off/on cycle in the UI (soft off and on or start to use it again )
So merely playing music did not trigger it to fetch current time . So I probably have to wait for the scheduled time sync

I does connect without playing music , I can go to the now playing screen and it shows the track list the cover and the state stopped or pause . So it's fully aware of where it is in the playlist and it's state .
Usually it's probably the action of chosing "my music" or if you go to the now playing screen .

Just pressing "off" and keep it like that also apparently triggers an immediate time sync then the clock shows up directly in off screen saver .
This behaviour smells like a workaround to me :) someone was aware of this and many users do use the clock in off mode , not that many will use it in stop mode they may use now playing for example .

But this workaround is offset by that other behaviour/bug if you power cycle an "off" Touch it resumes in "stopped" mode when you power it on again .
https://bugs-archive.lyrion.org/show_bug.cgi?id=17297

All said and done this can be better even if it's not exactly critical.

Sugested solution . Touch should try to sync it's clock directly on contact with a server just as it does when booted up against a properly running server , the diference here is the Touch was running before server it should not matter which is the case the result should be the same .

Also try to make this work without the user actively having to Touch a button or anything .