How to enable Authselect

Ask Fedora
21

reboot from Fedora42:

amunir@middlewareadmin ~]$ uname -r
6.19.11-100.fc42.x86_64

but still can not loginto desk top:

[amunir@middlewareadmin ~]$ sudo journalctl -g gnome -p err
– Boot 7671ca983bc54368b9c6d5b0e33ce961 –
– Boot 6031c886d50f4612a4803bb0c92093ec –
– Boot 2f2e1a68110245dda85fa63c0fe72ba1 –
– Boot 4ba45869045349baa2c78df87e35ec89 –
– Boot cb5bd00019ba4222bf1b2d5e52fbf061 –
– Boot 65d0b514b60c49b98d23a23c3a7fb1e7 –
– Boot 88a27135764f4287a5ab5517316f311a –
– Boot 172c831d751240d78b621e128ef03921 –
– Boot 7add464d3db048fea8dc61eb417999f0 –
– Boot 63a282a325da4123a04e98cb8343e3fb –
– Boot 17aee646d14b4b90b609b6411d6147a6 –
– Boot 5736a601be2e4b4f9d31804fb90a1aab –
– Boot a7b5e21807794f1fa682d609dfa1b916 –
– Boot f9bf55eb5047497591ff9523eed2b49a –
– Boot 700228751a9645f384185027a26ad56d –
– Boot 5646039d3bce4a11bc57d5c10e11176a –
– Boot a060a3a706714a1c9e83cde0d108e40c –
– Boot a28ba2f0fab941b4bd5ff66e1bb30471 –
– Boot 1569123869d945538a797f9a9da0daf7 –
– Boot 6393c18cb7e84899aa3e825d59ccbbfd –
– Boot b7c8d06ff31c4e3393f2ba5437da8943 –
– Boot f5a4fca311494abdaa9a5e85cbbdebdb –
– Boot a129e3facb17409b983d0961dd6a2f90 –
– Boot 79a9b79adda544bfa66f01f8e01b33dd –
– Boot 4553ea6e6ec14c099eed8778c42e0a20 –
– Boot f6aee60cca23491da768207beb22c8b3 –
– Boot 560b95db58c34f68a4bc616ebabf8be3 –
– Boot a2d34805a17c43f3bf3c7bd0e3115838 –
– Boot 2e64ca47882e4a658aada0fdd5f45ef9 –
– Boot bbf4e1078b7e44ec9a04eb533332d2b7 –
– Boot af9b2a21a1474390b86144ba13a27cd1 –
– Boot f83b7deb4da54413b5e48989ff0eec43 –
– Boot d144a26a03384474ba61ac4d5eadad50 –
– Boot a33860ed93df4b9b99c63a92affd5ecc –
– Boot 1f098e0646a8469384ffacd681323f72 –
– No entries –

22

[amunir@middlewareadmin ~]$ sudo journalctl --since=today -g gnome -p err
– Boot f83b7deb4da54413b5e48989ff0eec43 –
– Boot d144a26a03384474ba61ac4d5eadad50 –
– Boot a33860ed93df4b9b99c63a92affd5ecc –
– Boot 1f098e0646a8469384ffacd681323f72 –
– No entries –

23

OK. How about if you try signing in, and then immediately run the following command to show all the messages that are related to your sign in attempt?

sudo journalctl --no-hostname --since=-1min
24

[amunir@middlewareadmin ~]$ sudo journalctl --no-hostname --since=-1min
Apr 17 10:54:41 gnome-shell[1489]: GdmGreeterProxy: connection is closed
Apr 17 10:54:41 gdm[1319]: Gdm: gdm_settings_get_value: assertion ‘settings->backends != NULL’ failed
Apr 17 10:54:41 gdm-password][3214]: Gdm: gdm_settings_get_value: assertion ‘settings->backends != NULL’ failed
Apr 17 10:54:45 gnome-shell[1489]: Gio.IOErrorEnum: Timeout was reached

                               Stack trace:
                                 _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:454:45
                                 @resource:///org/gnome/shell/ui/init.js:21:20
                                 ### Promise created here: ###
                                 _setEngine@resource:///org/gnome/shell/misc/ibusManager.js:284:30
                                 setCompletionEnabled@resource:///org/gnome/shell/misc/ibusManager.js:367:24
                                 setOskCompletion@resource:///org/gnome/shell/ui/keyboard.js:2134:48
                                 open@resource:///org/gnome/shell/ui/keyboard.js:1732:34
                                 _onKeyFocusChanged/this._showIdleId<@resource:///org/gnome/shell/ui/keyboard.js:1403:22
                                 @resource:///org/gnome/shell/ui/init.js:21:20

Apr 17 10:54:49 gdm-password][3214]: gkr-pam: unable to locate daemon control file
Apr 17 10:54:49 audit[3214]: AUDIT1100 pid=3214 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_loca>
Apr 17 10:54:49 gdm-password][3214]: gkr-pam: stashed password to try later in open session
Apr 17 10:54:49 audit[3214]: AUDIT1101 pid=3214 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser ac>
Apr 17 10:54:49 audit[3214]: AUDIT1103 pid=3214 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_g>
Apr 17 10:54:49 audit[3214]: AUDIT2300 pid=3214 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=pam_selinux default-context=unconfined_u:unconfined_r:unconfined>
Apr 17 10:54:49 systemd-logind[962]: New session ‘6’ of user ‘amunir’ with class ‘user’ and type ‘x11’.
Apr 17 10:54:49 systemd[1]: Started session-6.scope - Session 6 of User amunir.
Apr 17 10:54:49 gdm-password][3214]: pam_unix(gdm-password:session): session opened for user amunir(uid=1000) by amunir(uid=0)
Apr 17 10:54:49 gdm-password][3214]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Apr 17 10:54:49 audit[3214]: AUDIT1105 pid=3214 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,p>
Apr 17 10:54:49 audit[3214]: AUDIT1112 pid=3214 uid=0 auid=1000 ses=6 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe=“/usr/libexec/gdm-session-worker” hostname=? addr=? te>
Apr 17 10:54:54 audit[3602]: AUDIT1101 pid=3602 uid=1000 auid=1000 ses=4 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser>

25

OK, that stack trace will probably give us something to go on. I’ll see what I can find.

26

Does the user you are trying to sign in as have a ~/.config/systemd/user/default.target file in their home directory? If so, does it contain the following?

[Unit]
AllowIsolate=yes

It looks like someone has report that that can cause problems.[1]

If removing that doesn’t help, can you try creating another user account and signing in with the new account?

  1. ↩︎

27

If creating a new user works around the problem, then it is probably a GNOME extension. You should be able to run gsettings set org.gnome.shell disable-user-extensions true from the command line to disable all the GNOME extensions. I think that command should work when you are signed in with the non-working user via SSH.

28

I do not have this file ~/.config/systemd/user/default.target

but i have following:

/home/amunir/.config/dconf/user

29

Does it work if you create a separate user? You should be able to use sudo useradd <username> to create a new user. You will also need to run sudo passwd <username> to set the user’s password.

30

Yes that worked. create a new account and login with to Fedora43 on my desk top. Thanks

31

It’s probably one of the GNOME extensions that you’ve installed in your other account. I think you should be able to use sudo -u <broken-username> gsettings set org.gnome.shell disable-user-extensions true to disable all the GNOME extensions in that other account.

Edit: I’ve been told that sudo -u ... won’t work and you should try run0 -u ... instead.

Also, beware that you will want to use your old account to run sudo usermod -a -G wheel <new-account> (via SSH) before you delete your old account. The new account will not be able to use sudo until it is added to the wheel group.

32

I will keep my old account for all my work except login to desktop where I use my new account.