Bug 14181 – cannot turn off / power off Baby or Fab4 if chosen screensaver no longer present

Bug 14181 - cannot turn off / power off Baby or Fab4 if chosen screensaver no longer present

Summary:

cannot turn off / power off Baby or Fab4 if chosen screensaver no longer present

Status:	CLOSED FIXED

Product:	SqueezePlay
Classification:	Unclassified
Component:	UI
Version:	unspecified
Platform:	All All

Importance:	P3 normal (vote)
Target Milestone:	7.5.0
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-21 21:17 UTC by Peter Watkins
Modified:	2010-04-08 17:26 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Peter Watkins 2009-09-21 21:17:40 UTC

Baby at r7671, Fab4 at r7670.

I cannot turn the players off. Not with an IR remote sending power_toggle, nor power_off discrete code, nor with Baby's front panel button, nor with Fab4's onscreen button on Fab4's home screen.

The cause? I installed Erland's Daylight clock and set it as the When Off saver. When I installed the firmware upgrade, I lost that applet, and ended up with no When Off screensaver. Once I choose a screensaver from the stock firmware, all's well (bug 14151 is still present, but otherwise all's well after specifying a screensaver that's installed on the device).

Comment 1 Chris Owens 2009-10-21 09:49:23 UTC

moving current p2 bugs to p3 to make room for moving p1.5 bugs to p2

Comment 2 Pat Ransil 2009-10-23 05:11:08 UTC

Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.

Comment 3 Pat Ransil 2009-10-23 05:17:15 UTC

Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.

Comment 4 Ben Klaas 2010-02-19 08:29:32 UTC

Peter, I think this was resolved at r8208 (Dec 9) which adds a default fallback screensaver when the configured applet is not available.

Reopen if you see otherwise...

Comment 5 Chris Owens 2010-04-08 17:26:24 UTC

This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!