Re: Can't log in to graphical workstation

2023-11-15 Thread Joe Zeff

On 11/15/2023 02:15 PM, Michael D. Setzer II via users wrote:

Wonder if changing to lightdm would work? Have used lightdm in
past with some machines, and it seems to be a simplier desktop
manager, but still works with gnome and xfce?


I don't know about Gnome, but it's the default with Xfce.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Michael D. Setzer II via users
Interesting
plasma-workspace-x11
https://packages.fedoraproject.org/pkgs/plasma-workspace/plasma-
workspace-x11/index.html

Nov 15 10:46:36 OaklandWeather.localdomain sddm[1125]: Invalid 
session ""
Seems to be issue??
Wonder if changing to lightdm would work? Have used lightdm in 
past with some machines, and it seems to be a simplier desktop 
manager, but still works with gnome and xfce?

dnf whatprovides */plasma-workspace*
shows a lot of packages. 



On 15 Nov 2023 at 12:03, Jonathan Ryshpan wrote:

Subject:    Re: Can't log in to graphical workstation
From:   Jonathan Ryshpan 
To: mi...@guam.net
Date sent:  Wed, 15 Nov 2023 12:03:51 -0800
Organization:   Berkeley Linux Team
Copies to:  Fedora List 
Send reply to:  jonr...@pacbell.net, Community support for Fedora users 


> 
> On Wed, 2023-11-15 at 22:26 +1000, Michael D. Setzer II wrote:
> Now I understand, it is the local graphic login that is not working?
> 1. Did you install the server install on tis machine or the workstation 
> one?
> Think the server installation doesn't install the gui by default. 
> Did that once to see what it did, and without the gui it was not usefull. 
> 2. In you login to a terminal window. run systemctl status gdm and see 
> what it reports.
> 
> Since I run kde, the display manager is actually sddm, and systemctl gives 
> very interesting info. Some research shows that a package is missing, namely 
> plasma-workspace-x11. Installing it cures things. The problem actually arose 
> in Fedora 38 (I have no idea how.); I upgraded to Fedora 39 to see if this 
> would cure the problem, but since plasma-workspace-x11 was missing from 
> 38, it stayed missing in 39.
> 
> $ systemctl status sddm.service 
> ● sddm.service - Simple Desktop Display Manager 
> Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; preset: 
> enabled) 
> Drop-In: /usr/lib/systemd/system/service.d 
> └─10-timeout-abort.conf 
> Active: active (running) since Wed 2023-11-15 03:09:44 PST; 8h ago 
> Docs: man:sddm(1) 
> man:sddm.conf(5) 
> Main PID: 1125 (sddm) 
> Tasks: 2 (limit: 9302) 
> Memory: 20.1M 
> CPU: 71ms 
> CGroup: /system.slice/sddm.service 
> └─1125 /usr/bin/sddm 
> 
> Nov 15 03:09:44 OaklandWeather.localdomain systemd[1]: Started sddm.service - 
> Simple 
> Desktop Display Manager. 
> Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Unable to find 
> autologin session 
> entry "plasma" 
> Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Autologin failed! 
> Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: The configured theme 
> "01-breeze-fedora" doesn't exist, using the embedded theme instead 
> Nov 15 03:09:45 OaklandWeather.localdomain sddm-helper[1164]: 
> pam_unix(sddm-greeter:session): session opened for user sddm(uid=988) by 
> (uid=0) 
> Nov 15 10:46:36 OaklandWeather.localdomain sddm[1125]: Invalid session ""
> 
> -- 
> Many Thanks - Jonathan Ryshpan 
> 
>  Trust everyone -- But cut the cards.
> 
> 


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 22:26 +1000, Michael D. Setzer II wrote:
> Now I understand, it is the local graphic login that is not working?
> 1. Did you install the server install on tis machine or the
> workstation one?
> Think the server installation doesn't install the gui by default. 
> Did that once to see what it did, and without the gui it was not
> usefull.
> 2. In you login to a terminal window. run systemctl status gdm and see
> what it reports.

Since I run kde, the display manager is actually sddm, and systemctl
gives very interesting info. Some research shows that a package is
missing, namely plasma-workspace-x11. Installing it cures things. The
problem actually arose in Fedora 38 (I have no idea how.); I upgraded to
Fedora 39 to see if this would cure the problem, but since plasma-
workspace-x11 was missing from 38, it stayed missing in 39.

$ systemctl status sddm.service  
● sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled;
preset: enabled)
   Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Wed 2023-11-15 03:09:44 PST; 8h ago
  Docs: man:sddm(1)
man:sddm.conf(5)
  Main PID: 1125 (sddm)
 Tasks: 2 (limit: 9302)
Memory: 20.1M
   CPU: 71ms
CGroup: /system.slice/sddm.service
└─1125 /usr/bin/sddm


Nov 15 03:09:44 OaklandWeather.localdomain systemd[1]: Started
sddm.service - Simple Desktop Display Manager.
Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Unable to find
autologin session entry "plasma"

Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: Autologin failed!

Nov 15 03:09:45 OaklandWeather.localdomain sddm[1125]: The configured
theme "01-breeze-fedora" doesn't exist, using the embedded theme instead

Nov 15 03:09:45 OaklandWeather.localdomain sddm-helper[1164]:
pam_unix(sddm-greeter:session): session opened for user sddm(uid=988) by
(uid=0)
Nov 15 10:46:36 OaklandWeather.localdomain sddm[1125]: Invalid session
""

-- 
Many Thanks - Jonathan Ryshpan 

 Trust everyone -- But cut the cards.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Ralf Corsépius



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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Patrick O'Callaghan
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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Ralf Corsépius

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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Barry Scott


> On 15 Nov 2023, at 10:27, Jonathan Ryshpan  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

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 10:17 +, Barry wrote:
> > On 15 Nov 2023, at 09:03, Jonathan Ryshpan 
> > 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.

-- 
Sincerely Jonathan Ryshpan 

 Procrastinators do it later.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Jonathan Ryshpan
On Wed, 2023-11-15 at 20:15 +1000, Michael D. Setzer II wrote:
> Note sure what graphic login you are referring to?
> I have used tigervnc up to Fedora 38, but found that there are 
> issues with 39, so have switch to TurboVNC.
The "graphic login" is the plain ordinary login screen that appears when
the computer starts up.


-- 
Sincerely Jonathan Ryshpan 

 Those who have put out the eyes of the people
 reproach them for their blindness. -- Milton
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread Barry


> On 15 Nov 2023, at 09:03, Jonathan Ryshpan  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


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Can't log in to graphical workstation

2023-11-15 Thread simmon simmon
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
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue