Description of problem: After a graphical login (gdm?) X hangs with panel constantly redrawing the last screen row and the menu panel never appearing. The only way out is pressing the laptop power button but then the system complains about Panel not responding. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: Just boot the laptop into Linux 4.8.y/4.9.y kernel. Actual results: X hangs. Expected results: X should work. Additional info: If I boot using 3.11 rescue kernel, the panel hang doesn't happen (but that kernel doesn't support my Wi-Fi adapter).
I don't see that with a updated f24 VM, i am using a Mate developer version regular. But i am using lightdm desktop-manager which is the default for Mate desktop. Maybe a problem with using gdm from gnome?
(In reply to Wolfgang Ulbrich from comment #1) > I don't see that with a updated f24 VM, i am using a Mate developer version > regular. I suspect the nVidia driver (nouveau?) has to do with this hang. My laptop has nVidao Quadro K1100M (and I had issues with the driver before). > But i am using lightdm desktop-manager which is the default for Mate desktop. > Maybe a problem with using gdm from gnome? Then I probably use lightdm as well if that's the default.
(In reply to Sergei Shtylyov from comment #0) > Additional info: > If I boot using 3.11 rescue kernel, the panel hang doesn't happen (but that > kernel doesn't support my Wi-Fi adapter). Actually even with 3.11 kernel X hangs as well -- presumably when I boot after powering up my DSL router... Also, my audio doesn't work. :-(
(In reply to Sergei Shtylyov from comment #0) > Steps to Reproduce: > Just boot the laptop into Linux 4.8.y/4.9.y kernel. Note that 4.8.y drivers are from FC23 and X worked correctly with this kernel there. 4.9.y kernel is from FC24...
(In reply to Sergei Shtylyov from comment #4) > (In reply to Sergei Shtylyov from comment #0) > > > Steps to Reproduce: > > Just boot the laptop into Linux 4.8.y/4.9.y kernel. > > Note that 4.8.y drivers Kernels, not drivers, of course. :-)
Created attachment 1247824 [details] dmesg (Linux 4.6.9-100)
Created attachment 1247847 [details] Xorg.0.log
Booting with 'nouveau.modeset=0' fixes everything (although Intel driver controls the display)...
Someone told me nouveau driver is buggy nowadays, i prefer to run origin nvidia driver. re-asign it o driver package.
(In reply to Sergei Shtylyov from comment #8) > Booting with 'nouveau.modeset=0' fixes everything (although Intel driver > controls the display)... Well, it's more complex than that. I'm not sure yet what the conditions are (cold boot?) but the hang still happens even without nouveau...
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.