Bug 2167386

More info: This is not specific to a certain user account, one even try to login user1 - fails, and then user2 works. Once a login was sucessful one can log out and in without further problems.

The issue seems similar to https://forum.xfce.org/viewtopic.php?id=3176, even though the solution in there doesn't work from me as /tmp/.ICE-unix is empty after a reboot already.

Lightdm with Cinnamon session works as expected here on multiple PC's.

Could be an XFCE issue.

Ok, using "startxfce4" directly works.

From lightdm.log:

[+1.42s] DEBUG: Activating login1 session c1
[+1.42s] DEBUG: Seat seat0 changes active session to c1
[+1.42s] DEBUG: Session c1 is already active
[+1.67s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+2.20s] DEBUG: Greeter start authentication for YYY
[+2.20s] DEBUG: Session pid=1314: Started with service 'lightdm', username 'YYY'
[+2.34s] DEBUG: Session pid=1314: Got 1 message(s) from PAM
[+2.34s] DEBUG: Prompt greeter with 1 message(s)
[+10.81s] DEBUG: Seat seat0 changes active session to 
[+15.35s] DEBUG: Seat seat0 changes active session to 2
[+57.78s] DEBUG: Seat seat0 changes active session to c1
[+57.78s] DEBUG: Session c1 is already active
[+60.62s] DEBUG: Continue authentication
[+60.74s] DEBUG: Session pid=1314: Authentication complete with return value 0: Success
[+60.74s] DEBUG: Authenticate result for user YYY: Success
[+60.74s] DEBUG: User YYY authorized
[+60.75s] DEBUG: Greeter sets language en_US.utf8
[+61.33s] DEBUG: Greeter closed communication channel
[+61.33s] DEBUG: Session pid=1255: Exited with return value 1
[+61.33s] DEBUG: Seat seat0: Session stopped
[+61.33s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+61.33s] DEBUG: Seat seat0: Stopping
[+61.33s] DEBUG: Seat seat0: Stopping display server
[+61.33s] DEBUG: Sending signal 15 to process 1201
[+61.33s] DEBUG: Seat seat0: Stopping session
[+61.33s] DEBUG: Session pid=1314: Exited with return value 0
[+61.33s] DEBUG: Seat seat0: Session stopped
[+61.35s] DEBUG: Seat seat0 changes active session to 
[+61.58s] DEBUG: Process 1201 exited with return value 0
[+61.58s] DEBUG: XServer 0: X server stopped
[+61.58s] DEBUG: Releasing VT 1
[+61.58s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+61.58s] DEBUG: Seat seat0: Display server stopped
[+61.58s] DEBUG: Seat seat0: Stopped
[+61.58s] DEBUG: Required seat has stopped
[+61.58s] DEBUG: Stopping display manager
[+61.58s] DEBUG: Display manager stopped
[+61.58s] DEBUG: Stopping daemon
[+61.58s] DEBUG: Exiting with return value 1

and seat0-greeter.log has a "No protocol specified" in there.

I installed another F37 with XFCE in a VM from the netinst media and the issue shows up there as well.

This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

https://github.com/canonical/lightdm/issues/291#issuecomment-1834402939 has the solution to the issue:

"Start lightdm after systemd-hostnamed.service by adding an appropriate line to /lib/systemd/system/lightdm.service."

Is this reproducible with fedora 38/39?
F37 is EOL.

Can you please open a pull request at upstream first? I don't see one in linked report at github.

(In reply to Wolfgang Ulbrich from comment #9)
> Is this reproducible with fedora 38/39?
> F37 is EOL.

Yup, still persists on F39. I updated the affected version two weeks ago.

(In reply to Wolfgang Ulbrich from comment #10)
> Can you please open a pull request at upstream first? I don't see one in
> linked report at github.

The lightdm.service files are distribution specific, but Github canonical/lightdm/pull/336 has the fix for Debian.

*** Bug 2252315 has been marked as a duplicate of this bug. ***

Upstream merged the fix for debian.

FEDORA-2024-cd3ff85232 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd3ff85232

FEDORA-EPEL-2024-b4ab66d80e has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b4ab66d80e

FEDORA-2024-96ac9f7948 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-96ac9f7948

FEDORA-EPEL-2024-1134025600 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-1134025600

FEDORA-EPEL-2024-1134025600 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-1134025600

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-EPEL-2024-b4ab66d80e has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b4ab66d80e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-cd3ff85232 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-cd3ff85232`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd3ff85232

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-96ac9f7948 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-96ac9f7948`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-96ac9f7948

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-cd3ff85232 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-EPEL-2024-1134025600 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-EPEL-2024-b4ab66d80e has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2024-96ac9f7948 (lightdm-1.32.0-7.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.