I am not able to log in as a graphical user on one of my workstations. The login screen works normally, except that: * The "Session" box is empty * The "Layout" box reads "??zz" (?? is blue) When I type my password and hit return, nothing happens. I can run a terminal session (CTRL+ALT F2) OK, but $startx fails.
This started to happen on Fedora 38. I (foolishly) upgraded to Fedora 39, which only made things worse: I can no longer log in to the machine remotely via ssh. Currently running Fedora 39 with all upgrades installed.
Any ideas on what's going on or how to investigate?
Dear Jonathan Ryshpan
f39 is one of the smoothly updated versions, and some parts related to the actual GUI may be broken or parts necessary for the GUI may have been removed.
Therefore, it seems that the problem will be solved by additionally installing the parts related to the GUI that you want to actually configure and proceeding with the installation part of a different GUI type.
# dnf group list
I am installing and using lightdm(F39 Server with KDE) because it operates more smoothly.
If there are too many parts that are difficult to modify after upgrading, I recommend installing f39 through the normal installation process.
Have a fun!
written by simmon
On 15 Nov 2023, at 09:03, Jonathan Ryshpan jonrysh@pacbell.net wrote:
I can no longer log in to the machine remotely via ssh
Over time the security of ssh is improved as cryptography research recommends. If are using an old version of ssh to connect that may be the problem. If you have a weak ssh key that may the be the problem.
What does ssh -v tell you is going wrong?
Barry
On Wed, 2023-11-15 at 10:17 +0000, Barry wrote:
On 15 Nov 2023, at 09:03, Jonathan Ryshpan jonrysh@pacbell.net wrote: I can no longer log in to the machine remotely via ssh
Over time the security of ssh is improved as cryptography research recommends. If are using an old version of ssh to connect that may be the problem. If you have a weak ssh key that may the be the problem.
This got better after a while for no apparent reason. I suspect that the dns server for my local net did not recognize the upgraded machine for a while, but then started to when something timed out. Ssh is working, and also the machine (a server) is now visible. Thanks for your help.
On 15 Nov 2023, at 10:27, Jonathan Ryshpan jonrysh@pacbell.net wrote:
I suspect that the dns server for my local net did not recognize the upgraded machine for a while, but then started to when something timed out. Ssh is working, and also the machine (a server) is now visible.
I sometimes have to flush the DNS cache on machines to fix this type of issue. macOS is particularly bad for this, but Windows and Fedora get stale as well.
You can use the dig command to get DNS info directly from your DNS servers to find out what your DNS servers know about and compare to the output of host command.
Barry
Am 15.11.23 um 11:27 schrieb Jonathan Ryshpan:
This got better after a while for no apparent reason. I suspect that the dns server for my local net did not recognize the upgraded machine for a while, but then started to when something timed out. Ssh is working, and also the machine (a server) is now visible. Thanks for your help.
Did you check your bootlogs (journalctl -r -b ...)?
In my logs I found a lot issues with f39 after upgrading from 38 to 39, many of them indicating massive problems related to polkit, systemd and SELinux (polkit seems to be the origin of most of the problem - IMHO it's foobared).
That said, I can not recommend f39 to anybody. In its present shape fc39 provided the worst upgrade experience to me for many years. It really doesn't need much and I'll downgrade to f38 from backups.
Ralf
On Wed, 2023-11-15 at 14:01 +0100, Ralf Corsépius wrote:
Am 15.11.23 um 11:27 schrieb Jonathan Ryshpan:
This got better after a while for no apparent reason. I suspect that the dns server for my local net did not recognize the upgraded machine for a while, but then started to when something timed out. Ssh is working, and also the machine (a server) is now visible. Thanks for your help.
Did you check your bootlogs (journalctl -r -b ...)?
In my logs I found a lot issues with f39 after upgrading from 38 to 39, many of them indicating massive problems related to polkit, systemd and SELinux (polkit seems to be the origin of most of the problem - IMHO it's foobared).
That said, I can not recommend f39 to anybody. In its present shape fc39 provided the worst upgrade experience to me for many years. It really doesn't need much and I'll downgrade to f38 from backups.
My experience is entirely different. For me it's been the smoothest upgrade I've seen in years.
poc
Am 15.11.23 um 15:48 schrieb Patrick O'Callaghan:
My experience is entirely different. For me it's been the smoothest upgrade I've seen in years.
Just one example of many I am experiencing, I dared to bz'ed so far: https://bugzilla.redhat.com/show_bug.cgi?id=2248838
Ralf
-
Barry -
Barry Scott
-
Jonathan Ryshpan -
Patrick O'Callaghan -
Ralf Corsépius -
simmon simmon