Bug 1308369

Summary: Flickering on monitor screen after switching it off
Product: [Fedora] Fedora Reporter: pasqual milvaques <pasqual.milvaques>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: pasqual.milvaques, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 18:44:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description pasqual milvaques 2016-02-14 21:35:38 UTC
Description of problem:
In a laptop equipped with an amd carrizo cpu and an additional monitor (or tv) connected to the hdmi output, the additional screen is configured as an extension screen (not in clone mode) using xrandr or mate-display-properties or gnome control center, if then the laptop screen is switched off with xrandr (or mate-display…) the screen becomes blank but start flickering at a rate of around 1 flicker per second. The sound output is also affected when this happens, starts to experience retards and what seems buffering problems

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-7.6.0-0.4.20150729git5510cd6.fc23.x86_64
kernel-4.3.5-300.fc23.x86_64
mesa-dri-drivers-11.1.0-2.20151218.fc23.x86_64
xorg-x11-server-Xorg-1.18.0-2.fc23.x86_64
xorg-x11-server-utils-7.7-17.fc23.x86_64

How reproducible: always 

Steps to Reproduce:
1. Connect to the laptop and additional monitor through hdmi
2. Using some tool of the os (xrandr or mate-display-properties or gnome control center), extend the monitor to the additional screen
3. Switch off the laptop screen with the OS tool

Actual results:
Laptop screen flickering
Sound output not working correctly

Expected results:
Laptop screen completely blank
Sound keeps working

Additional info:
Problem reproduced in a HP Pavilion - 15-ab102ns laptop
Machine is equipped with an amd a10-8700p (carrizo) cpu with integrated gpu and audio

Comment 1 Fedora End Of Life 2016-11-24 15:34:22 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 2 Fedora End Of Life 2016-12-20 18:44:10 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.