Bug 10527 - SqueezeBox should not change display brightness level for "Can't Connect" message.
: SqueezeBox should not change display brightness level for "Can't Connect" mes...
Status: RESOLVED DUPLICATE of bug 10393
Product: SB 2/3
Classification: Unclassified
Component: Hardware
: unspecified
: All All
: -- enhancement with 1 vote (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-02 22:37 UTC by Gordon Harris
Modified: 2009-01-03 13:19 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Harris 2009-01-02 22:37:15 UTC
With more and more folks using some sort of power scheme on their servers to go into suspend or hibernation on idle, the resulting bright "Can't connect to SqueezeCenter" message is probably causing momentary panic in millions upon millions of SqueezeBox owners who suddenly see this message flashed in their bedrooms late at night, probably causing high blood pressure and, in some cases, perhaps premature death. See this thread for one user's account of their near death experience: http://forums.slimdevices.com/showthread.php?t=31652

See this thread for a slightly less inflammatory discussion: http://forums.slimdevices.com/showthread.php?t=57552, and especially peterw's sensible idea that the SqueezeBox ought to display its "Can't connect to SqueezeCenter" message in the brightness that was in use just before the connection was lost...the idea being that power control schemes could set the brightness of the player to off before shutting down the server so as to prevent this false alarm.
Comment 1 Philip Meyer 2009-01-03 00:26:30 UTC
I totally agree - displaying the message at full brightness is really bad for people that use SqueezeBoxes in the bedroom.

Displaying the message at the same brightness that the display was previously using would be a reasonable solution.
Comment 2 KDF 2009-01-03 00:37:12 UTC
see incarnations driven by the same initial thread in bug 4670, bug 4673 and bug 4673.
Comment 3 KDF 2009-01-03 13:19:57 UTC
basically, this is a dupe of 10393, marking as such since there is more activity and a target there.

*** This bug has been marked as a duplicate of bug 10393 ***