Bug 13964 – Line In selection with checkbox on home menu immediately after firmware update

Bug 13964 - Line In selection with checkbox on home menu immediately after firmware update

Summary:

Line In selection with checkbox on home menu immediately after firmware update

Status:	CLOSED FIXED

Product:	SB Radio
Classification:	Unclassified
Component:	Menus
Version:	Include FW version in comment
Platform:	PC Windows XP

Importance:	P1 normal (vote)
Target Milestone:	7.4.0
Assigned To:	Wadzinski Tom

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-10 22:14 UTC by Mickey Gee
Modified:	2010-05-27 14:45 UTC (History)
CC List:	3 users (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 Mickey Gee 2009-09-10 22:14:42 UTC

When manually updating Baby firmware from SC (using 7484 and 7506), I see the Line In menu item with associated checkbox on the home menu. It appears immediately after the firmware update and stay there for awhile. The checkbox seems to work and it appear to work normally.

I think it appears between My Apps and Favorites, but I'm not quite sure.

Once I reboot Baby, the Line In option disappears from the home menu.

Comment 1 Wadzinski Tom 2009-09-11 08:36:42 UTC

Works for me. There were several line in checks in in the last couple of days, 
and I suspect you caught a mid-stream change.

Comment 2 James Richardson 2009-10-05 14:35:49 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Comment 3 Chris Owens 2010-05-27 14:45:59 UTC

These bugs have all been marked resolved and belong to a component which is being removed.  Therefore they have been moved to the most applicable of the new components.