|Summary:||Screen blinks 3 times after user login everytime in my Feora 27, then became stable.|
|Product:||[Fedora] Fedora||Reporter:||Muhammad usama tahir <tom.hanks2196>|
|Component:||kernel||Assignee:||Kernel Maintainer List <kernel-maint>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||27||CC:||airlied, ajax, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved, tom.hanks2196|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2018-03-23 16:45:24 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Muhammad usama tahir 2017-11-24 12:56:51 UTC
Description of problem:Blinking of Screen after user login everytime. Version-Release number of selected component (if applicable): 4.13.13 kernel ver. How reproducible:one every time I login my user account. Steps to Reproduce: 1.I updated my Fedora 26 to 27 2.Then update using terminal using dnf update command. 3.After that my kernel upate from 4.13.9 to 4.13.13 and after that I am facing the issue of screen blinking.
Comment 1 Laura Abbott 2018-02-20 19:59:16 UTC
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Comment 2 Laura Abbott 2018-03-23 16:45:24 UTC
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you did actually update, we apologize for the inconvenience (there are a lot of bugs). If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.