Hide Forgot
Description of problem: It says ... It seems you are running upgrade from XWindows. You should switch to VT, because of bug in systemd-udev. It may lead to unpredictable things. See https://www.happyassassin.net/2016/10/04/x-crash-during-fedora-update-when-system-has-hybrid-graphics-and-systemd-udev-is-in-update/ but in fact I'm not. It's a remote ssh session, in screen. At least you can easily skip the warning. Version-Release number of selected component (if applicable): fedora-upgrade-25.2-1.fc24.noarch How reproducible: Only on 1 out of 3 systems I am upgrading. Steps to Reproduce: 1. Just run fedora-upgrade
The test is: if [ "$DISPLAY" != "" ]; then so it is not super smart test. And yes it may give false positive in case you are running screen or tmux from GUI. I think it is better to give false positive rather than have false negative. Do you know of better test?
If you want "running X locally" then something like: if [[ "$DISPLAY" =~ ^: ]]; then ... Note that is a bash-ism.
But that returns 0 in both cases - when running in and without screen under display manager. It will just return false when running over remote ssh. So it is little bit better, but still not ideal.
(In reply to Miroslav Suchý from comment #3) > But that returns 0 in both cases - when running in and without screen under > display manager. Well OK but the error message says nothing about it being safe to run in screen under X, it says you should switch to a VT. If it's safe to be running in screen or tmux under X, then: if [[ "$DISPLAY" =~ ^: ]] && [ -z "$STY" ] && [ -z "$TMUX" ]; then ...
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.