Bugzilla – Bug 809
Changing Font Size from Slimserver doesn't have effect
Last modified: 2008-12-18 11:54:14 UTC
I have noticed that this problem lies with the 5.4.1 nightly builds, when I roll back to the 5.4 stable release it goes away. The problem is if I try and set the standy font to Huge and the active font to Large, the active font also changes to HUGE. There doesn't seem to be anyway to get the SB to stay with a setting of Standby HUGE and active LARGE. Not sure if it matters but I also have the Brightness when ON set to 4 and the brightness when off or idles set to 2. I have tried changing this from both the remote and slimserver with the same symptom. As rolling back the version of slimserver fixes the problem the bug is obviously with the slimserver vs. the SB. I noticed that this problem started happening a few weeks ago when I started loading the 5.4.1 nightly builds.
Which date is your morst recent for the nightly build? I've tried this out just now. The player is in standby mode, with the active font set to Large. i change the standby font from medium to Huge and click change. the response at the top says standby font 3, the player changes to huge. then I play a file, the player powers on and changes to large font just as it should.
how are you controlling this through the player settings? Are you changing the radio button, or the pulldown menus? What are the four fonts listed, top to bottom for both font types in player settings, display?
Right now I have reverted back to the stable build but the last I tried the nightly was about a week ago. I have tried changing the font two ways with the same unexpected effect: 1) From the web menu on Slimserver as you outline above and 2) From the remote control Both seem to place both standby and active fonts to the same. I can try and recreate this by upgrading again. Are there any debugs that you would like be to capture if I am able to recreate this?
ah ok. There was a fix put in, coincidentally, a week ago to fix a number of funky font issues in 5.4.1. I expect you should find that it will work for you now.
Keith, Have you been able to confirm that the latest builds are working for you?
ok, well, all signs would indicate that this was fixed just after the point where testing was stopped. this can be reopened if there is any forthcoming negative results.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.