RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 591774 - screen remains dim when coming back from idle
Summary: screen remains dim when coming back from idle
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-power-manager
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 04:59 UTC by Devin Reade
Modified: 2023-09-14 01:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:26:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
dmesg output (63.16 KB, text/plain)
2010-05-13 04:59 UTC, Devin Reade 		no flags Details
View All

Description Devin Reade 2010-05-13 04:59:14 UTC 
Created attachment 413630 [details]
dmesg output

Description of problem:

RHEL6.0 beta install on a Lenovo Thinkpad T500 (discrete graphics mode).

If the text console is showing (via ctrl-alt-F2) and the machine is left idle for a while, the screen blanker kicks in.  However, when a key is kit thus causing the login prompt to become visible again, the display is set to its dimmest setting.  Using the thinkpad keys to increase the display brightness has no effect while in text mode. Using alt-F1 to go back to graphics mode, the graphics screen is at its dimmest setting as well.  Once in graphics mode, the thinkpad keys can be used to increase the brightness again.

In gnome-power-manager for AC power (where this occurs), the box "Dim display when idle" is NOT checked and "set display brightness to" is 100%.  (For battery power, "dim display when idle" is checked.)

If the system is in graphics mode when it goes idle and the display is blanked out, then it is at the proper brightness when a key is pressed.

Let me know what other diags are desired. (dmesg attached)

Version-Release number of selected component (if applicable):
gnome-power-manager-2.28.2-2.el6.x86_64

How reproducible:


Steps to Reproduce:
1. Ctrl-alt-F2 to get to text login prompt
2. Let the system go idle.  The screen will blank
3. Touch a key.  The screen will unblank but will be very dim
  
Actual results: on return from idle, the display is set to its dimmest setting


Expected results: on return from idle, the display should be at the original brightness
Comment 2 RHEL Program Management 2010-05-13 06:37:37 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Taunus 2010-06-04 11:41:39 UTC 
Also when you try to adjust brightness back to normal in login screen it does not work. It works after logging in. T400 with discrete graphics, ati mobility radeon hd 3470.
Comment 4 RHEL Program Management 2010-07-15 14:23:29 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 5 Taunus 2010-08-24 12:41:44 UTC 
Testing
Comment 6 Taunus 2010-08-26 12:32:36 UTC 
Yeah it is still an issue with beta2refresh
Comment 7 RHEL Program Management 2011-04-04 01:51:04 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 8 Richard Hughes 2014-05-20 08:45:40 UTC 
The brightness is not supposed to be changed when sitting on a different VT. Can you do something like this and post the logs please:

(in vt7, i.e. X)

killall gnome-power-manager
gnome-power-manager --verbose

Then switch to vt1, wait for the bug, then post the complete logs. Thanks.
Comment 9 gingerling 2016-06-16 10:37:46 UTC 
think I have this, my brightness keeps going down to zero and staying there
Comment 10 Jan Kurik 2017-12-06 12:26:02 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Comment 11 Red Hat Bugzilla 2023-09-14 01:21:10 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.