Hide Forgot
Created attachment 1201864 [details] journalctl log showing multiple shutdown messages Description of problem: This is a relatively new installation, less than 1 week old, of Fedora 24 Cinnamon Desktop which is not shutting down unless the ESC key is pressed very shortly after the screen goes blank. Then I see the shutdown messages and the machine does shutdown. If I do not press the ESC key immediately the machine does not shutdown. - If I press the ESC key after the time window, then multiple pressing of the ESC is of no effect. I have been using Fedora from F13 and my previous version was F22, which I was very happy. I am trying to get my head around all the changes in F24 since F22. More details: 1. Starting with a populated desktop with applications and the the shutdown process is activated. 2. All the applications are killed 3. The screen does black 4. There is no change for some time. 5. If I wait more than say 15 sec, now matter what I press nothing changes - I have to then use the power button to power down the machine. I see errors in some applications. Lotus Notes does not save any of the changes from the last session. 6. If I press ESC within 5 sec of the screen going black, I see the shutdown messages, as I would expect, and the machine shuts down successfully I have left the machine to wait it out for 15 min and no shutdown. - The first sign of problems was that I was not seeing any of the shutdown messages just a blank screen. I had the idea from a posting on a fedora forum:- http://forums.fedoraforum.org/showthread.php?p=1770963&posted=1#post1770963 I have tested the shutdown from:- a. Gnome Desktop - with the ESC b. From the Login Screen - without the ESC keypress Version-Release number of selected component (if applicable): kernel: 4.7.3-200.fc24.x86_64 cinnamon-desktop-3.0.2-1.fc24.x86_64 cinnamon-3.0.7-1.fc24.x86_64 cinnamon-screensaver-3.0.1-1.fc24.x86_64 cinnamon-menus-3.0.2-1.fc24.x86_64 cinnamon-settings-daemon-3.0.1-1.fc24.x86_64 cinnamon-control-center-filesystem-3.0.1-1.fc24.x86_64 cinnamon-translations-3.0.3-1.fc24.noarch -- I am not sure if Cinnamon is the worst starting point or just coincidence How reproducible: Every time I select Shutdown and do not press ESC. - this is the same when selecting from the GUI or from the command line # shutdown -h -t now Steps to Reproduce: 1. Select shutdown by any method - GUI or from command line 2. Wait for the screen to go black and wait for 15 sec 3. Press any key or even Cntl-Alt-Del, there is no change 4. I have waited up to 10 min and there are no shutdown messages == 5. If the ESC key is pressed just as the screen goes black, then shutdown messages are listed 6. The machine shuts down. Actual results: When no shutdown messages are displayed, then no further actions take place Expected results: 1. Invoke shutdown 2. Screen goes dark 3. Shutdown messages are displayed 4. machine shutsdown or reboot as requested. Additional info: I have a log for the successful shutdown. I have filtered out all the gdm-x error messages - about 10 per second.
I have been experiencing this issue for about 3 days now. Since I have been able to shutdown the machine correctly, in my last attempt to shutdown I have seen the Fedora spash-screen for the first time in a few days. I pressed ESC and the machine shutdown correctly. I am requesting that this bug be put on hold for the time being as the machine is behaving as per default correct operation. If I detect additional errors I will collect additional information.
I thought that my logoff issues were behind me but this does not seem to be the case this morning. I was doing some additional testing with a mail application whose fonts were corrupted when deployed under Cinnamon and I tried to perform the re-installation under Gnome and to retest under Cinnamon. I was able to logout from Cinnamon and the to login to Gnome. After testing I got the same results - an application issue, I attempted to logout from Gnome and to log back in under Cinnamon. When I attempted to logout of Gnome the screen went black and stayed unresponsive until I powered down. I noted the time when I decided to power-down and to take a break from this problem. I have now captured the events from the journal for that period and I see that there was a kernel abort which killed the X-Server and then I was not able to see any further events - I am not sure if the machine would have ever shutdown after that event. It may be that the failure to shutdown may be associated to Kernel Abort with the X-Server being killed and then the shutdown being severely hampered. I am uploading the partial journal log for this time period.
Created attachment 1202001 [details] journalctl log for the time period for shutdown request to power off.
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.