Bug 1788 – Problem changing brightness with remote

Bug 1788 - Problem changing brightness with remote

Summary:

Problem changing brightness with remote

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	IR
Version:	6.1.0
Platform:	Other SuSE Linux

Importance:	P2 minor (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-07-09 06:55 UTC by Felix Mueller
Modified:	2008-09-15 14:37 UTC (History)
CC List:	0 users

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 Felix Mueller 2005-07-09 06:55:17 UTC

If 'Adjust Brighness Manually' is set on the webinterface, I can change
brightness with the remote just fine. However if 'Adjust Brightness
Automatically' is set I am unable to change the brightness. Upon pressing the
brightness button on the remote the display lights up one level and then drops
back to the current level. 
Also changing brightness with the remote seem only to affect the idle brightness
settings on the web interface.
This only happens on a SB2. SLIMP3 and SBG are not affected. Workaround: use
Webinterface to set brighness level.

Comment 1 Blackketter Dean 2005-07-09 08:26:19 UTC

I don't see this, Felix.  Note that there's been some new behavior, namely that the BRIGHTNESS button 
permanently changes the brightness level at the current brightness "mode".  So, if the player is idle, i.e. 
the screensaver has kicked in, the button sets the idle brightness, etc.   

Does this explain what you are seeing?

Comment 2 Felix Mueller 2005-07-09 17:00:52 UTC

Deleting .slimserver.pref resolved the issue. Sorry for the noise. Bug can be
closed.

Comment 3 KDF 2005-07-09 17:03:26 UTC

no, felix.  thanks!

Comment 4 Chris Owens 2006-06-16 14:42:01 UTC

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.