Login twice gnome

igtr · October 23, 2025, 2:16pm

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

OpenMandriva Lx version:
OpenMandriva Lx release 25.06 (ROME) Rolling for x86_64

Desktop environment (KDE, LXQT…):
Gnome

Description of the issue (screenshots if relevant):
From few months ago to now, I’m required to login into the user twice to actually login into the user when using GDM and Gnome (This doesn’t happens when logging through ssh or tty).

This happens to all users in the machine, and I have to put the correct password twice in a row to login.

I tried really hard to find a solution myself, but I could not find.

Relevant informations (hardware involved, software version, logs or output…):

cat /etc/os-release

NAME="OpenMandriva Lx"
VERSION="25.06 (ROME) Rolling"
ID="openmandriva"
VERSION_ID="25.06"
PRETTY_NAME="OpenMandriva Lx 25.06 (ROME) Rolling"
BUILD_ID="20250605.11"
VERSION_CODENAME="rome"
ANSI_COLOR="1;43"
LOGO="openmandriva"
CPE_NAME="cpe:/o:openmandriva:openmandriva_lx:25.06"
HOME_URL="http://openmandriva.org/"
BUG_REPORT_URL="https://github.com/OpenMandrivaAssociation/distribution/issues/"
SUPPORT_URL="https://forum.openmandriva.org"
PRIVACY_POLICY_URL="https://www.openmandriva.org/tos"

cat /etc/product.id.OpenMandriva

vendor=OpenMandriva,distribution=OpenMandriva Lx,type=Basic,version=25.06,branch=Rock,release=1,arch=x86_64,product=OpenMandriva Lx

dnf info gdm

Name         : gdm
Version      : 48.0
Release      : 1
Architecture : x86_64
Size         : 5.0 M
Source       : gdm-48.0-1.src.rpm
Repository   : @System
From repo    : rolling-x86_64
Summary      : The GNOME Display Manager
URL          : https://www.gnome.org/projects/gdm/
License      : GPLv2+
Description  : Gdm (the GNOME Display Manager) is a highly configurable
             : reimplementation of xdm, the X Display Manager. Gdm allows you to log
             : into your system with the X Window System running and supports running
             : several different X sessions on your local machine at the same time.

gnome-shell --version

GNOME Shell 48.2

cat /etc/gdm/custom.conf

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
Enable=true

cat /etc/pam.d/gdm-password

#%PAM-1.0
auth         required      pam_env.so
auth         sufficient    pam_succeed_if.so quiet_fail user ingroup nopasswdlogin
auth         substack      system-auth
auth         optional      pam_gnome_keyring.so
auth         include       postlogin

account      required      pam_nologin.so
account      include       system-auth
password     optional      pam_gnome_keyring.so use_authtok
password     include       system-auth

session      required      pam_loginuid.so
session      optional      pam_keyinit.so force revoke
session      required      pam_namespace.so
session      optional      pam_gnome_keyring.so auto_start
session      include       system-auth
session      include       postlogin

sudo journalctl -xeu gdm

out 23 15:40:50 gdm[1226]: Gdm: GdmSessionWorkerJob: : SessionWorkerJob on pid 4163
out 23 15:40:50 gdm-password][4163]: Gdm: Enabling debugging
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: connecting to address: unix:path=/run/gdm/dbus/dbus-612c824m
out 23 15:40:50 gdm[1226]: Gdm: GdmDBusServer: new connection 0x7f7a3c0070c0
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Handling new connection from worker
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Authenticating new connection
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: worker connection is 0x7f7a3c0070c0
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Emitting conversation-started signal
out 23 15:40:50 gdm[1226]: Gdm: GdmManager: session conversation started for service gdm-password on session
out 23 15:40:50 gdm[1226]: Gdm: GdmManager: ignoring session conversation since its not automatic login conversation
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: setting session to type 'wayland'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Set up service gdm-password for username work on session (0x559b20c91ef0)
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: selecting user 'work' for session '(null)' (0x559b20c91ef0)
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Beginning initialization
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: Conversation started
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: trying to track new user with username work
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: finding user 'work' state 1
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: waiting for user manager to load before finding user 'work'
out 23 15:40:50 gdm-password][4163]: accountsservice: Finding a graphical session for user 0
out 23 15:40:50 gdm-password][4163]: accountsservice: Failed to identify the current session
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: seat unloaded, so trying to set loaded property
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: user manager now loaded, proceeding with fetch user request for user 'work'
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: finding user 'work' state 2
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: Looking for user 'work' in accounts service
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: already loaded, so not setting loaded property
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: Found object path of user 'work': /org/freedesktop/Accounts/User1001
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: finding user 'work' state 3
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: user 'work' fetched
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: user work is now loaded
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: user work was not yet known, adding it
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: tracking user 'work'
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: not yet loaded, so not emitting user-added signal
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: no pending users, trying to set loaded property
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: already loaded, so not setting loaded property
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionSettings: saved session is gnome (type )
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: Saved session is gnome
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionSettings: saved language is
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: queuing setup for user: work (null)
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: finished handling request for user 'work'
out 23 15:40:50 gdm-password][4163]: accountsservice: ActUserManager: unrefing manager owned by fetch user request
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to SETUP_COMPLETE
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: initializing PAM; service=gdm-password username=work seat=seat0
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: getting session command for file 'gnome.desktop'
out 23 15:40:50 gdm[1226]: Gdm: GdmSession: checking if file 'gnome.desktop' is wayland session: yes
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_SEAT=seat0'
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: state SETUP_COMPLETE
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to AUTHENTICATED
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: authenticating user work
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: 1 new messages received from PAM
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: username is 'work'
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: old-username='work' new-username='work'
out 23 15:40:50 gdm-password][4163]: Gdm: GdmSessionWorker: received pam message of type 1 with payload 'Contraseña: '
out 23 15:40:53 gdm-password][4163]: Gdm: GdmSessionWorker: trying to get updated username
out 23 15:40:53 gdm-password][4163]: Gdm: GdmSessionWorker: PAM conversation returning 0: Éxito
out 23 15:40:54 gdm-password][4163]: gkr-pam: unable to locate daemon control file
out 23 15:40:54 gdm-password][4163]: gkr-pam: stashed password to try later in open session
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: state AUTHENTICATED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: trying to get updated username
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: username is 'work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: old-username='work' new-username='work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to AUTHORIZED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: determining if authenticated user (password required:0) is authorized to session
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: state AUTHORIZED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to ACCREDITED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'LOGNAME=work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'USER=work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'USERNAME=work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'HOME=/home/work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'PWD=/home/work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'SHELL=/usr/bin/zsh'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/usr/games'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: state ACCREDITED
out 23 15:40:54 gdm[1226]: Gdm: GdmSession: type wayland, program? no, seat seat0
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: session display mode set to new-vt
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=wayland'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to ACCOUNT_DETAILS_SAVED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: saving account details for user work
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: attempting to change state to SESSION_OPENED
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: Set PAM environment variable: 'XDG_VTNR=2'
out 23 15:40:54 gdm-password][4163]: gkr-pam: unable to locate daemon control file
out 23 15:40:54 gdm-password][4163]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
out 23 15:40:54 gdm-password][4163]: pam_unix(gdm-password:session): session opened for user work(uid=1001) by (uid=0)
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: 1 new messages received from PAM
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: username is 'work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: old-username='work' new-username='work'
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: received pam message of type 4 with payload 'Último inicio de sesión: qui out 23 15:40:45 CEST 2025 en >
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: PAM conversation returning 0: Éxito
out 23 15:40:54 gdm-password][4163]: Gdm: GdmSessionWorker: state SESSION_OPENED
out 23 15:40:54 gdm[1226]: Gdm: GdmSession: Emitting 'session-opened' signal
out 23 15:40:57 gdm[1226]: Gdm: GdmManager: Will start session when ready
out 23 15:40:57 gdm[1226]: Gdm: GdmManager: start or jump to session
out 23 15:40:57 gdm[1226]: Gdm: GdmSession: Ignoring session (null) as requested
out 23 15:40:57 gdm[1226]: Gdm: GdmManager: no matching sessions found
out 23 15:40:57 gdm[1226]: Gdm: GdmManager: migrated: 0
out 23 15:40:57 gdm[1226]: Gdm: GdmSession: type wayland, program? no, seat seat0

Thanks for any help

zeroability · October 24, 2025, 1:06am

I was able to.

sigvirt · October 24, 2025, 8:34am

to find a solution? The linked gdm issue is 2 years old and still open.

@igtr I don’t have any suggestion of value but have you tried xsession instead of wayland? I don’t use Gnome much (not on OM anyway) but on my Debian Trixie and Fedora Silverblue42 installs (both at Gnome 48) I don’t have the issue you mentioned.

zeroability · October 24, 2025, 10:03am

Contacting GNOME is probably the solution. It’s likely a GDM bug. Since it isn’t wide spread, it’s likely related to your specific hardware.

As suggested, try X11 and even our default DE Plasma to see if you can reproduce it. GNOME is a community spin and you will be testing if you use it.

igtr · October 24, 2025, 10:22am

I don’t have any suggestion of value but have you tried xsession instead of wayland? I don’t use Gnome much (not on OM anyway) but on my Debian Trixie and Fedora Silverblue42 installs (both at Gnome 48) I don’t have the issue you mentioned.

I tried with Xserssion and it works. But using X I lose waypipe and other things that I use a lot.

Contacting GNOME is probably the solution. It’s likely a GDM bug. Since it isn’t wide spread, it’s likely related to your specific hardware.

I don’t think so, because it was working before. Was after a update that this issue started.

As suggested, try X11 and even our default DE Plasma to see if you can reproduce it. GNOME is a community spin and you will be testing if you use it.

What is the KDE greeter package name? so I can test with it.

sigvirt · October 24, 2025, 2:15pm

There are two packages sddm and plasma6-sddm (I guess the former is plasma 5 version). I installed OM from plasma6-x11 iso, so have plasma6-sddm package installed. You could try the same.

Btw, I installed Gnome (using task-gnome-minimal) to test. I am not facing any issue as you have reported (so far atleast). When I type password at GDM login prompt and hit enter, it shows a message about my last login but then logs me in without issue.

The details of commands you posted are similar for me except for journalctl.

journalctl -xeu gdm

Oct 24 17:37:05 rome-vm systemd[1]: Starting gdm.service - GNOME Display Manager…
░░ Subject: A start job for unit gdm.service has begun execution
░░ Defined-By: systemd
░░ Support: ``https://openmandriva.org
░░
░░ A start job for unit gdm.service has begun execution.
░░
░░ The job identifier is 309.
Oct 24 17:37:06 rome-vm systemd[1]: Started gdm.service - GNOME Display Manager.
░░ Subject: A start job for unit gdm.service has finished successfully
░░ Defined-By: systemd
░░ Support: ``https://openmandriva.org
░░
░░ A start job for unit gdm.service has finished successfully.
░░
░░ The job identifier is 309.
Oct 24 17:37:06 rome-vm gdm-launch-environment][831]: PAM unable to dlopen(/usr/lib64/security/pam_console.so): /usr/lib64/security/pam_console.so: cannot open shared >
Oct 24 17:37:06 rome-vm gdm-launch-environment][831]: PAM adding faulty module: /usr/lib64/security/pam_console.so
Oct 24 17:37:20 rome-vm gdm-password][1537]: gkr-pam: unable to locate daemon control file
Oct 24 17:37:20 rome-vm gdm-password][1537]: gkr-pam: stashed password to try later in open session
Oct 24 17:37:20 rome-vm gdm-password][1537]: gkr-pam: unable to locate daemon control file
Oct 24 17:37:20 rome-vm gdm-password][1537]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Oct 24 17:37:20 rome-vm gdm-password][1537]: pam_unix(gdm-password:session): session opened for user sv(uid=1010) by (uid=0)
Oct 24 17:37:23 rome-vm gnome-keyring-daemon[1547]: another secret service is running
Oct 24 17:37:27 rome-vm gdm[722]: Gdm: Child process -882 was already dead.

If I face similar issue, I’ll update.

P.S.: I absolutely liked the way you presented your command outputs, considering it was your first post. You probably are similarly organized even in your personal life! Welcome to OM btw!

igtr · October 24, 2025, 3:21pm

Probably because I have debug enabled in gdm. Can you enable it in your gdm? So we can compare the logs better.

/etc/gdm/custom.conf

[debug]
# Uncomment the line below to turn on debugging
Enable=true

I installed the plasma6-sddm, and I’m still having the same issue

sudo journalctl -xeu sddm

out 24 17:00:57 systemd[1]: Started sddm.service - Simple Desktop Display Manager.
░░ Subject: A start job for unit sddm.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://openmandriva.org
░░ 
░░ A start job for unit sddm.service has finished successfully.
░░ 
░░ The job identifier is 10500.
out 24 17:00:57 sddm[28145]: Initializing...
out 24 17:00:57 sddm[28145]: Starting...
out 24 17:00:57 sddm[28145]: Logind interface found
out 24 17:00:57 sddm[28145]: Adding new display...
out 24 17:00:57 sddm[28145]: Loaded empty theme configuration
out 24 17:00:57 sddm[28145]: Using VT 1
out 24 17:00:57 sddm[28145]: Display server started.
out 24 17:00:57 sddm[28145]: Socket server starting...
out 24 17:00:57 sddm[28145]: Socket server started.
out 24 17:00:57 sddm[28145]: The configured theme "breeze" doesn't exist, using the embedded theme instead
out 24 17:00:57 sddm[28145]: Loaded empty theme configuration
out 24 17:00:57 sddm[28145]: Greeter starting...
out 24 17:00:57 sddm-helper[28147]: [PAM] Starting...
out 24 17:00:57 sddm-helper[28147]: [PAM] Authenticating...
out 24 17:00:57 sddm-helper[28147]: [PAM] returning.
out 24 17:00:57 sddm-helper[28147]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=989) by (uid=0)
out 24 17:00:57 sddm-helper[28147]: Starting X11 session: "/usr/bin/X -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--qTtnpN"
out 24 17:00:57 sddm[28145]: Greeter session started successfully
out 24 17:00:58 sddm[28145]: Message received from greeter: Connect
out 24 17:01:06 sddm[28145]: Message received from greeter: Login
out 24 17:01:06 sddm[28145]: Reading from "/usr/share/wayland-sessions/gnome-wayland.desktop"
out 24 17:01:06 sddm[28145]: Session "/usr/share/wayland-sessions/gnome-wayland.desktop" selected, command: "/usr/bin/gnome-session" for VT 2
out 24 17:02:06 sddm-helper[28882]: [PAM] Starting...
out 24 17:02:06 sddm-helper[28882]: [PAM] Authenticating...
out 24 17:02:06 sddm-helper[28882]: [PAM] Preparing to converse...
out 24 17:02:06 sddm-helper[28882]: [PAM] Conversation with 1 messages
out 24 17:02:06 sddm-helper[28882]: gkr-pam: unable to locate daemon control file
out 24 17:02:06 sddm-helper[28882]: [PAM] returning.
out 24 17:02:06 sddm-helper[28882]: gkr-pam: stashed password to try later in open session
out 24 17:02:06 sddm[28145]: Authentication for user  "work"  successful
out 24 17:02:06 sddm-helper[28882]: gkr-pam: unable to locate daemon control file
out 24 17:02:06 sddm-helper[28882]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
out 24 17:02:06 sddm-helper[28882]: pam_unix(sddm:session): session opened for user work(uid=1001) by (uid=0)
out 24 17:02:06 sddm-helper[28882]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/bin/gnome-session"
out 24 17:02:06 sddm[28145]: Session started true
out 24 17:02:06 sddm[28145]: Auth: sddm-helper exited successfully
out 24 17:02:06 sddm[28145]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
out 24 17:02:07 sddm-helper[28882]: [PAM] Closing session
out 24 17:02:07 sddm-helper[28882]: pam_unix(sddm:session): session closed for user work
out 24 17:02:07 sddm-helper[28882]: [PAM] Ended.
out 24 17:02:07 sddm[28145]: Auth: sddm-helper exited successfully
out 24 17:02:07 sddm[28145]: Socket server stopping...
out 24 17:02:07 sddm[28145]: Socket server stopped.
out 24 17:02:07 sddm[28145]: Removing display SDDM::Display(0x558f0ccd1450) ...
out 24 17:02:07 sddm[28145]: Adding new display...
out 24 17:02:07 sddm[28145]: Loaded empty theme configuration
out 24 17:02:07 sddm[28145]: Using VT 1
out 24 17:02:07 sddm[28145]: Display server started.
out 24 17:02:07 sddm[28145]: Socket server starting...
out 24 17:02:07 sddm[28145]: Socket server started.
out 24 17:02:07 sddm[28145]: The configured theme "breeze" doesn't exist, using the embedded theme instead
out 24 17:02:07 sddm[28145]: Loaded empty theme configuration
out 24 17:02:07 sddm[28145]: Greeter starting...
out 24 17:02:07 sddm-helper[29050]: [PAM] Starting...
out 24 17:02:07 sddm-helper[29050]: [PAM] Authenticating...
out 24 17:02:07 sddm-helper[29050]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=989) by (uid=0)
out 24 17:02:07 sddm-helper[29050]: [PAM] returning.
out 24 17:02:07 sddm-helper[29050]: Starting X11 session: "/usr/bin/X -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--uXGlbZ"
out 24 17:02:07 sddm[28145]: Greeter session started successfully
out 24 17:02:07 sddm[28145]: Message received from greeter: Connect
out 24 17:02:14 sddm[28145]: Message received from greeter: Login
out 24 17:02:14 sddm[28145]: Reading from "/usr/share/wayland-sessions/gnome-wayland.desktop"
out 24 17:02:14 sddm[28145]: Session "/usr/share/wayland-sessions/gnome-wayland.desktop" selected, command: "/usr/bin/gnome-session" for VT 7
out 24 17:02:14 sddm-helper[29096]: [PAM] Starting...
out 24 17:02:14 sddm-helper[29096]: [PAM] Authenticating...
out 24 17:02:14 sddm-helper[29096]: [PAM] Preparing to converse...
out 24 17:02:14 sddm-helper[29096]: [PAM] Conversation with 1 messages
out 24 17:02:14 sddm-helper[29096]: gkr-pam: unable to locate daemon control file
out 24 17:02:14 sddm-helper[29096]: [PAM] returning.
out 24 17:02:14 sddm-helper[29096]: gkr-pam: stashed password to try later in open session
out 24 17:02:14 sddm[28145]: Authentication for user  "work"  successful
out 24 17:02:14 sddm-helper[29096]: gkr-pam: unable to locate daemon control file
out 24 17:02:14 sddm-helper[29096]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
out 24 17:02:14 sddm-helper[29096]: pam_unix(sddm:session): session opened for user work(uid=1001) by (uid=0)
out 24 17:02:14 sddm-helper[29096]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/bin/gnome-session"
out 24 17:02:14 sddm[28145]: Session started true
out 24 17:02:14 sddm[28145]: Auth: sddm-helper exited successfully
out 24 17:02:14 sddm[28145]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
out 24 17:02:23 sddm[28145]: Auth: sddm-helper exited successfully
out 24 17:02:23 sddm[28145]: Socket server stopping...
out 24 17:02:23 sddm[28145]: Socket server stopped.
out 24 17:02:23 sddm[28145]: Removing display SDDM::Display(0x558f0ccc7e70) ...
out 24 17:02:23 sddm[28145]: Adding new display...
out 24 17:02:23 sddm[28145]: Loaded empty theme configuration
out 24 17:02:23 sddm[28145]: Using VT 1
out 24 17:02:23 sddm[28145]: Display server started.
out 24 17:02:23 sddm[28145]: Socket server starting...
out 24 17:02:23 sddm[28145]: Socket server started.
out 24 17:02:23 sddm[28145]: The configured theme "breeze" doesn't exist, using the embedded theme instead
out 24 17:02:23 sddm[28145]: Loaded empty theme configuration
out 24 17:02:23 sddm[28145]: Greeter starting...
out 24 17:02:23 sddm-helper[29948]: [PAM] Starting...
out 24 17:02:23 sddm-helper[29948]: [PAM] Authenticating...
out 24 17:02:23 sddm-helper[29948]: [PAM] returning.
out 24 17:02:23 sddm-helper[29948]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=989) by (uid=0)
out 24 17:02:23 sddm-helper[29948]: Starting X11 session: "/usr/bin/X -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--eOPSSa"
out 24 17:02:23 sddm[28145]: Greeter session started successfully
out 24 17:02:23 sddm[28145]: Message received from greeter: Connect
out 24 17:02:34 sddm[28145]: Message received from greeter: Login
out 24 17:02:34 sddm[28145]: Reading from "/usr/share/wayland-sessions/gnome-wayland.desktop"
out 24 17:02:34 sddm[28145]: Session "/usr/share/wayland-sessions/gnome-wayland.desktop" selected, command: "/usr/bin/gnome-session" for VT 7
out 24 17:02:40 sddm[28145]: Session started true
out 24 17:02:45 sddm[28145]: Greeter stopping...
out 24 17:02:45 sddm[28145]: Auth: sddm-helper exited with 255
out 24 17:02:45 sddm[28145]: Greeter stopped. SDDM::Auth::HelperExitStatus(255)
out 24 17:02:46 sddm[28145]: Auth: sddm-helper exited successfully
out 24 17:02:46 sddm[28145]: Socket server stopping...
out 24 17:02:46 sddm[28145]: Socket server stopped.
out 24 17:02:46 sddm[28145]: Removing display SDDM::Display(0x558f0ccc7e70) ...
out 24 17:02:46 sddm[28145]: Adding new display...
out 24 17:02:46 sddm[28145]: Loaded empty theme configuration
out 24 17:02:46 sddm[28145]: Using VT 1
out 24 17:02:46 sddm[28145]: Display server started.
out 24 17:02:46 sddm[28145]: Socket server starting...
out 24 17:02:46 sddm[28145]: Socket server started.
out 24 17:02:46 sddm[28145]: The configured theme "breeze" doesn't exist, using the embedded theme instead
out 24 17:02:46 sddm[28145]: Loaded empty theme configuration
out 24 17:02:46 sddm[28145]: Greeter starting...
out 24 17:02:46 sddm-helper[31077]: [PAM] Starting...
out 24 17:02:46 sddm-helper[31077]: [PAM] Authenticating...
out 24 17:02:46 sddm-helper[31077]: [PAM] returning.
out 24 17:02:46 sddm-helper[31077]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=989) by (uid=0)
out 24 17:02:46 sddm-helper[31077]: Starting X11 session: "/usr/bin/X -background none -seat seat0 -noreset -keeptty -novtswitch -verbose 3" "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--gvJHmn"
out 24 17:02:46 sddm[28145]: Greeter session started successfully
out 24 17:02:47 sddm[28145]: Message received from greeter: Connect
out 24 17:03:20 sddm[28145]: Signal received: SIGTERM
out 24 17:03:20 systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
░░ Subject: A stop job for unit sddm.service has begun execution
░░ Defined-By: systemd
░░ Support: https://openmandriva.org
░░ 
░░ A stop job for unit sddm.service has begun execution.
░░ 
░░ The job identifier is 15643.
out 24 17:03:20 sddm[28145]: Greeter stopping...
out 24 17:03:20 sddm[28145]: Auth: sddm-helper exited with 255
out 24 17:03:20 sddm[28145]: Greeter stopped. SDDM::Auth::HelperExitStatus(255)
out 24 17:03:20 sddm[28145]: Socket server stopping...
out 24 17:03:20 sddm[28145]: Socket server stopped.
out 24 17:03:20 systemd[1]: sddm.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://openmandriva.org
░░ 
░░ The unit sddm.service has successfully entered the 'dead' state.
out 24 17:03:20 systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.
░░ Subject: A stop job for unit sddm.service has finished
░░ Defined-By: systemd
░░ Support: https://openmandriva.org
░░ 
░░ A stop job for unit sddm.service has finished.
░░ 
░░ The job identifier is 15643 and the job result is done.

Well, the greeter doesn’t seem to be the issue. What logs do you recommends me to take a look?

P.S.: I absolutely liked the way you presented your command outputs, considering it was your first post. You probably are similarly organized even in your personal life! Welcome to OM btw!

Thanks

sigvirt · October 24, 2025, 5:55pm

Here is the log requested.

gdm-log.txt (36.5 KB)

Before enabling GDM, I had tried to login several times to Gnome (wayland) from SDDM and had no issues. Still have no issue using GDM.

No idea, sorry. Hopefully my gdm log will give you some clue.

You did mention that same thing happens for all users but is it possible to create a dummy user and try?

zeroability · October 25, 2025, 12:25pm

We don’t support Wayland for production workflows. You will always be a tester if you use it.

See the above reply, and the part where I said you will also be a tester if you use GNOME also applies here.