Created attachment 1006667 [details] journalctl --since=-"24 hours" I installed the F22 alpha yesterday morning (March 25) and immediately did a “dnf install”. The system ticked along fine for about 24 hours. I noticed the odd flicker on the screen when I logged back in after hibernating and the position of the cursor was quite specific when clicking firefox tabs. Other than that. All good. Since then I have had to forcibly power down 4 times when the screen alternates between flickering and a black screen. I can not get any reaction from the keyboard. The first time this happened the computer was hibernating and I attempted to enter my password. The last time the computer was hibernating and did not react when I entered my password. The other 2 times I have been simply alt-tabbing between workspaces. I am using cinnamon. I have 4 workspaces open. - firefox - 2 terminals plus (on 2 occasions a QEMU session) - thunderbird + an “X” windows session using ssh to access another computer - libreoffice I attach information about my kernel plus lspci. Also a journalctl. The last reboot was 14:14, I am not sure why there is a huge time difference. Sorry but I am not sure of the component. I was looking for UI/graphics/GUI but could not find a suitable match [tim@lizard ~]$ uname -r 4.0.0-0.rc4.git0.1.fc22.x86_64 [tim@lizard ~]$ rpm -qa kernel\* | sort kernel-4.0.0-0.rc1.git0.1.fc22.x86_64 kernel-4.0.0-0.rc4.git0.1.fc22.x86_64 kernel-core-4.0.0-0.rc1.git0.1.fc22.x86_64 kernel-core-4.0.0-0.rc4.git0.1.fc22.x86_64 kernel-headers-4.0.0-0.rc4.git0.1.fc22.x86_64 kernel-modules-4.0.0-0.rc1.git0.1.fc22.x86_64 kernel-modules-4.0.0-0.rc4.git0.1.fc22.x86_64 [tim@lizard ~]$ [tim@lizard ~]$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 4 port SATA IDE Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 00:1f.5 IDE interface: Intel Corporation 6 Series/C200 Series Chipset Family 2 port SATA IDE Controller (rev 05) 02:00.0 Ethernet controller: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet (rev c0) 03:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 30) [tim@lizard ~]$ 2. 3. Actual results: Expected results: Additional info:
after reporting this I figured I had never had a clean reboot with this kernel so I tried that. A reboot rather than a shutdown. I am not sure what happened but the PC did not reboot. And I got no response from the power key. The reboot key did work though. I booted into the original kernel [tim@lizard ~]$ uname -r 4.0.0-0.rc1.git0.1.fc22.x86_64 And reboot worked just fine. So, I'll stick with this kernel for the time being.
Another snippet to throw into the mix...I use a VM with the following command: qemu-system-x86_64 -hda Templates/alf.img -boot c -m 2048 -enable-kvm -vga qxl the "-vga qxl" was suggested in response to another bug report (1195026) where the mouse cursor was not visible. I just tried to bring up the VM and noticed the cursor was wobbling a bit. Could it be the VM is using up too much graphics? I'll point out that the VM has not always been active when this problem occurs.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
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.
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.