Description of problem: When holding F11 key for a brief moment entire desktop freezes. gnome-terminal, in what it seems to be stuck in some kind of loop. If gnome-terminal is not killed immediately from a VT entire computer becomes unresponsive when swapping starts to occur with gnome-shell process overfilling RAM. This issue seems to not affect Wayland, only X. Version-Release number of selected component (if applicable): gnome-terminal-3.22.0-1.fc25.x86_64 gnome-shell-3.22.1-2.fc25.x86_64 How reproducible: Hold F11 key on gnome-terminal. Actual results: Animations seems to lag and to not keep up with window switching. Nevertheless, although depressing F11 key is fairly quick, gnome-terminal seems to be stuck in a loop. gnome-shell freeze occurs and if waiting long enough entire computer becomes unresponsive. Expected results: To be able to keep up with window mode switching or at least recover from it. Additional info: I propose this bug as a F25 Final blocker due to: > Default application functionality > All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.
Proposed as a Blocker for 25-final by Fedora user srakitnican using the blocker tracking app because: This bug affects system stability in what is my opinion fairly widely used application option. I propose this bug due to: > Default application functionality > All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.
Discussed during the 2016-10-31 blocker review meeting: [1] The decision to classify this bug as a RejectedBlocker was made as the impact of this bug is not ruled to be "basic functionality" and therefore does not meet any criteria. We may be willing to grant a Freeze Exception status if the fix is non-invasive, but will need more details on said fix before voting. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-10-31/f25-blocker-review.2016-10-31-16.01.txt
This bug is triggered with an unusual operation and is unlikely to affect a large number of users. If new investigation shows other methods of triggering, we may reconsider it. This bug has not been approved to the "Prioritized bugs list".
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Still an issue in a fully updated Fedora 27 release.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.