Bug 1142002 - Gnome Shell 3.12.2 Ressume from blank screen/Dimming fails on Monitor 1
Summary: Gnome Shell 3.12.2 Ressume from blank screen/Dimming fails on Monitor 1
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-16 01:34 UTC by Jay Elem
Modified: 2015-06-29 22:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:33:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Vid Info Xorg Info (12.62 KB, text/plain)
2014-09-16 01:37 UTC, Jay Elem
no flags Details

Description Jay Elem 2014-09-16 01:34:27 UTC
Title: Gnome Shell 3.12.2 Ressume from blank screen/Dimming fails on Monitor 1

Class: System Error

Date: Mon Sep 15 21:04:50 ADT 2014
Reported By: Jay Elem
Email: fiver22

Product: GNOME Shell            Version: 3.12.2
Platform: Fedora                Version: 3.16.2-200.fc20.x86_64


Is it reproducible: Yes, consistently.

Description
===========
Screen Dimming remains at lowest setting as it should after no use on 2 monitors: when resuming with keystroke
or mouse movement only Monitor 2 Dimming 'wakes' to full brightness.
The primary, Monitor 1 Dimming stays at lowest brightness.


Steps to Produce/Reproduce
--------------------------
Let screens blank after no use. Wake up screens with mouse movement or keyboard activity.
Monitor 1 remains Dimming minimum while monitor 2's brightness resumes as expected.


Expected Results
----------------
Both Monitors 'wake' and Dimming brightness returns to normal level on activity


Actual Results
--------------
Monitor 1 stays 'blank' (Dimming brightness at lowest level)
Monitor 2 'wakes' as expected.


Workarounds
-----------
1. launch 'gnome settings' on monitor 2. use search to bring up 'Power' settings.
2. Move Screen brightness slider (it is set at active or maximum)
Screen Dimming brightness on Monitor 1 returns to expected brightness.

Comment 1 Jay Elem 2014-09-16 01:37:42 UTC
Created attachment 937775 [details]
Vid Info Xorg Info

Comment 2 Fedora End Of Life 2015-05-29 12:53:25 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 22:33:32 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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