Description of problem: The password field does not appear till 5 +/- seconds have elapsed. Version-Release number of selected component: $ rpm -qa | grep greeter slick-greeter-1.5.4-2.fc35.x86_64 slick-greeter-mate-1.5.4-2.fc35.noarch # rpm -qa | grep lightdm lightdm-gobject-1.30.0-15.fc35.x86_64 lightdm-1.30.0-15.fc35.x86_64 lightdm-settings-1.5.5-2.fc35.noarch How reproducible: Every time I login from at boot or reboot. Additional info: Mate-Desktop ver 1.26 This bug description has similar characteristics "2022956" Edit: Revised conditions and added lightdm components
It works fine here under cinnamon on my slow media PC $ inxi -SCG System: Host: mpd Kernel: 5.15.4-201.fc35.x86_64 x86_64 bits: 64 Desktop: Cinnamon 5.2.1 Distro: Fedora release 35 (Thirty Five) CPU: Info: Quad Core model: Intel Celeron J4105 bits: 64 type: MCP cache: L2: 16 MiB Speed: 851 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 1641 2: 1496 3: 1126 4: 1271 Graphics: Device-1: Intel GeminiLake [UHD Graphics 600] driver: i915 v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: intel resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 600 (GLK 2) v: 4.6 Mesa 21.2.5 [+0.00s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for background to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for background-color to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for logo to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for other-monitors-logo to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for theme-name to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for icon-theme-name to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for font-name to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for play-ready-sound to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for xft-hintstyle to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for xft-rgba to default [+0.01s] DEBUG: settings.vala:161: Overriding dconf setting for enable-hidpi with on [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for only-on-monitor to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for clock-format to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for draw-user-backgrounds to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for stretch-background-across-monitors to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for draw-grid to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-hostname to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-power to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-a11y to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-clock to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-keyboard to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-quit to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for xft-antialias to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for activate-numlock to default [+0.01s] DEBUG: settings.vala:206: Resetting dconf setting for xft-dpi to default [+0.01s] DEBUG: settings.vala:224: Resetting dconf setting for hidden-users to default [+0.01s] DEBUG: settings.vala:224: Resetting dconf setting for group-filter to default [+0.01s] DEBUG: slick-greeter.vala:632: HiDPI support: on [+0.01s] DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created [+0.29s] DEBUG: unsetenv() is not thread-safe and should not be used after threads are created [+0.32s] DEBUG: slick-greeter.vala:651: Starting slick-greeter 1.5.4 UID=985 LANG=en_GB.UTF-8 [+0.32s] DEBUG: slick-greeter.vala:654: Setting cursor [+0.32s] DEBUG: slick-greeter.vala:668: Loading command line options [+0.32s] DEBUG: slick-greeter.vala:695: Setting GTK+ settings [+0.35s] DEBUG: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ [+0.44s] DEBUG: slick-greeter.vala:718: Creating Slick Greeter [+0.44s] DEBUG: slick-greeter.vala:55: Creating background surface [+0.44s] DEBUG: Connecting to display manager... [+0.44s] DEBUG: Wrote 26 bytes to daemon [+0.44s] DEBUG: Read 8 bytes from daemon [+0.44s] DEBUG: Read 160 bytes from daemon [+0.44s] DEBUG: Connected api=1 version=1.30.0 hide-users=false has-guest-account=false default-session=default show-manual-login=false show-remote-login=true [+0.65s] DEBUG: Loading users from org.freedesktop.Accounts [+0.65s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.67s] DEBUG: user-list.vala:1036: Adding/updating user leigh (Leigh Scott) [+0.67s] DEBUG: Loading sessions from org.freedesktop.DisplayManager [+0.67s] DEBUG: main-window.vala:229: Monitor 0 is 1920x1080 pixels at 0,0 [+0.67s] DEBUG: main-window.vala:245: MainWindow is 0x0 pixels [+0.67s] DEBUG: slick-greeter.vala:721: Showing greeter [+0.67s] DEBUG: slick-greeter.vala:303: Showing main window [+0.75s] DEBUG: background.vala:66: Making background #202020 at 1920x1080 [+0.75s] DEBUG: background.vala:77: Render of background #202020 complete [+0.76s] DEBUG: Loaded session /usr/share/xsessions/cinnamon.desktop (Cinnamon, This session logs you into Cinnamon) [+0.76s] DEBUG: Loaded session /usr/share/xsessions/cinnamon2d.desktop (Cinnamon (Software Rendering), This session logs you into Cinnamon (using software rendering)) [+0.76s] DEBUG: Starting authentication for user leigh... [+0.76s] DEBUG: Wrote 21 bytes to daemon [+0.76s] DEBUG: slick-greeter.vala:731: Starting main loop [+0.77s] DEBUG: background.vala:605: Regenerating backgrounds [+0.77s] DEBUG: background.vala:66: Making background #202020 at 1920x1080 [+0.77s] DEBUG: background.vala:77: Render of background #202020 complete [+0.77s] DEBUG: background.vala:66: Making background /usr/share/backgrounds/tiles/default_blue.jpg at 1920x1080 [+0.77s] DEBUG: background.vala:605: Regenerating backgrounds [+0.77s] DEBUG: background.vala:66: Making background #202020 at 1920x1080 [+0.77s] DEBUG: background.vala:77: Render of background #202020 complete [+0.77s] DEBUG: background.vala:66: Making background /usr/share/backgrounds/tiles/default_blue.jpg at 1920x1080 [+0.82s] DEBUG: slick-greeter.vala:291: starting system-ready sound [+0.83s] DEBUG: background.vala:119: Render of background /usr/share/backgrounds/tiles/default_blue.jpg complete [+0.90s] DEBUG: background.vala:119: Render of background /usr/share/backgrounds/tiles/default_blue.jpg complete [+0.96s] DEBUG: Read 8 bytes from daemon [+0.96s] DEBUG: Read 35 bytes from daemon [+0.96s] DEBUG: Prompt user with 1 message(s) [+8.97s] DEBUG: Providing response to display manager [+8.97s] DEBUG: Wrote 28 bytes to daemon [+9.08s] DEBUG: Read 8 bytes from daemon [+9.08s] DEBUG: Read 17 bytes from daemon [+9.08s] DEBUG: Authentication complete for user leigh with return code 0 [+9.08s] DEBUG: main-window.vala:204: Killing orca and onboard [+9.08s] DEBUG: Starting session cinnamon [+9.08s] DEBUG: Wrote 20 bytes to daemon [+9.08s] DEBUG: Read 8 bytes from daemon [+9.08s] DEBUG: Read 4 bytes from daemon [+9.08s] DEBUG: slick-greeter.vala:726: Got a SIGTERM [+9.08s] DEBUG: slick-greeter.vala:734: Cleaning up [+9.08s] DEBUG: slick-greeter.vala:747: Exiting
You need to reassign the issue to the Mate maintainer (fedora) to investigate or I could close it as 'Works for me'.
"You need to reassign the issue" Who is "you", me the OP or bugzilla hierarchy? inxi: System: Host: t4s Kernel: 5.15.5-200.fc35.x86_64 x86_64 bits: 64 Desktop: MATE 1.26.0 Distro: Fedora release 35 (Thirty Five) CPU: Info: Dual Core model: Intel Core i7-6600U bits: 64 type: MT MCP cache: L2: 512 KiB Speed: 800 MHz min/max: 400/3400 MHz Core speeds (MHz): 1: 779 2: 800 3: 785 4: 800 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel Device-2: Chicony Integrated Camera type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 2048x1152~60Hz OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.2.5 Greeter log: [+0.00s] DEBUG: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ [+0.01s] DEBUG: settings.vala:161: Overriding dconf setting for background with /usr/share/backgrounds/cosmos/helix-nebula.jpg [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for background-color to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for logo to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for other-monitors-logo to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for theme-name to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for icon-theme-name to default [+0.01s] DEBUG: settings.vala:161: Overriding dconf setting for font-name with Noto Sans 14 [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for play-ready-sound to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for xft-hintstyle to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for xft-rgba to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for enable-hidpi to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for only-on-monitor to default [+0.01s] DEBUG: settings.vala:170: Resetting dconf setting for clock-format to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for draw-user-backgrounds to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for stretch-background-across-monitors to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for draw-grid to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-hostname to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-power to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-a11y to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-clock to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-keyboard to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for show-quit to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for xft-antialias to default [+0.01s] DEBUG: settings.vala:188: Resetting dconf setting for activate-numlock to default [+0.01s] DEBUG: settings.vala:197: Overriding dconf setting for xft-dpi with 144 [+0.01s] CRITICAL: g_settings_set_value: key 'xft-dpi' in 'x.dm.slick-greeter' expects type 'd', but a GVariant of type 'i' was given [+0.01s] DEBUG: settings.vala:224: Resetting dconf setting for hidden-users to default [+0.01s] DEBUG: settings.vala:224: Resetting dconf setting for group-filter to default [+0.01s] DEBUG: slick-greeter.vala:632: HiDPI support: auto /usr/bin/slick-greeter-check-hidpi:17: DeprecationWarning: Gdk.Screen.get_primary_monitor is deprecated primary = screen.get_primary_monitor() /usr/bin/slick-greeter-check-hidpi:19: DeprecationWarning: Gdk.Screen.get_monitor_geometry is deprecated rect = screen.get_monitor_geometry(primary) /usr/bin/slick-greeter-check-hidpi:20: DeprecationWarning: Gdk.Screen.get_monitor_width_mm is deprecated width_mm = screen.get_monitor_width_mm(primary)
I can't reproduce the issue with 2 systems using nvidia graphic and lightdm with slick-greeter to login into MATE 1.26 desktop, here the password field is still there immediately. I am still wondering why this should be a MATE desktop problem because non of a MATE application is still active at this point during boot process. Also, author of mentioned issue is using cinnamon. https://bugzilla.redhat.com/show_bug.cgi?id=2022956 Both greeter slick-greeter or lightdm-gtk has the same problem. In result i don't think this is related to MATE or cinnamon desktop. Maybe lightdm has an issue to read accounts database?
Lightdm Log excerpt: [+1.09s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1.09s] DEBUG: Session pid=944: Started with service 'lightdm-greeter', username 'lightdm' [+1.11s] DEBUG: Session pid=944: Authentication complete with return value 0: Success [+1.11s] DEBUG: Seat seat0: Session authenticated, running command [+1.11s] DEBUG: Session pid=944: Running command /usr/sbin/slick-greeter [+1.11s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+1.11s] DEBUG: Session pid=944: Logging to /var/log/lightdm/seat0-greeter.log [+1.46s] DEBUG: Activating VT 1 [+1.46s] DEBUG: Activating login1 session c1 [+1.46s] DEBUG: Seat seat0 changes active session to c1 [+1.46s] DEBUG: Session c1 is already active [+2.02s] DEBUG: Greeter connected version=1.30.0 api=1 resettable=false [+2.47s] DEBUG: Greeter start authentication for jbk [+2.47s] DEBUG: Session pid=1013: Started with service 'lightdm', username 'jbk' [+8.57s] DEBUG: Session pid=1013: Got 1 message(s) from PAM [+8.57s] DEBUG: Prompt greeter with 1 message(s) [+19.07s] DEBUG: Continue authentication [+19.09s] DEBUG: Session pid=1013: Authentication complete with return value 0: Success [+19.09s] DEBUG: Authenticate result for user jbk: Success ###END#### Secure Log excerpt: Dec 3 08:24:06 t4s sshd[835]: Server listening on :: port 22. Dec 3 08:24:07 t4s lightdm[954]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=990) by (uid=0) Dec 3 08:24:07 t4s systemd[963]: pam_unix(systemd-user:session): session opened for user lightdm(uid=990) by (uid=0) Dec 3 08:24:08 t4s polkitd[712]: <no filename>:3: action=[Action id='org.freedesktop.login1.suspend'] Dec 3 08:24:08 t4s polkitd[712]: <no filename>:4: subject=[Subject pid=975 user='lightdm' groups=lightdm seat='seat0' session='c1' local=true active=true] Dec 3 08:24:08 t4s polkitd[712]: <no filename>:3: action=[Action id='org.freedesktop.login1.hibernate'] Dec 3 08:24:08 t4s polkitd[712]: <no filename>:4: subject=[Subject pid=975 user='lightdm' groups=lightdm seat='seat0' session='c1' local=true active=true] Dec 3 08:24:09 t4s polkitd[712]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny'] Dec 3 08:24:09 t4s polkitd[712]: <no filename>:4: subject=[Subject pid=975 user='lightdm' groups=lightdm seat='seat0' session='c1' local=true active=true] Dec 3 08:24:21 t4s lightdm[1025]: gkr-pam: unable to locate daemon control file Dec 3 08:24:21 t4s lightdm[1025]: gkr-pam: stashed password to try later in open session Dec 3 08:24:21 t4s lightdm[954]: pam_unix(lightdm-greeter:session): session closed for user lightdm Dec 3 08:24:22 t4s systemd[1089]: pam_unix(systemd-user:session): session opened for user jbk(uid=1001) by (uid=0) Dec 3 08:24:22 t4s lightdm[1025]: pam_unix(lightdm:session): session opened for user jbk(uid=1001) by (uid=0) Dec 3 08:24:22 t4s lightdm[1025]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring Dec 3 08:24:25 t4s polkitd[712]: Registered Authentication Agent for unix-session:2 (system bus name :1.59 [/usr/libexec/polkit-mate-authentication-agent-1], object path /org/mate/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) ####END########
Adding historical context. I upgraded from F34 to F35 on 11/04/2021. Since then there have been no updates to the Mate-Desktop, Lightdm or Slick-greeter between then and today 12/06/2021. My symptoms did not start until after 11/20/2021 +/- a few days. I check and install updates once or twice a week. So it seems to me it is a component that reports to the greeter that has changed.
After googling for login delays I came across a comment that removing the finger print reader software "fprintd" fixed that one persons issues. So I removed "fprintd" and two dependent packages then rebooted. My password prompt is now nolonger delayed. I've rebooted a couple times now without delay. There must be a flaw in the "Case statement" on which authentication method to present in the interface between the pam database and lightdm.
Sure, it could be fprintd/libfprint hanging for a bit at startup. Can you please provide logs from such a hang for the fprintd unit? Ideally with debugging enabled, see at the bottom of https://gitlab.freedesktop.org/libfprint/fprintd/-/blob/master/README
Also, do you have TLP installed?
Created attachment 1845292 [details] Output from journalctl -b -u fprintd.service
Summary of steps taken to fulfill request for information in comments 8 & 9. I reinstalled fprintd using dnf with the history <spec> option because fprintd-pam was not included as a dependency. ############################################################ # dnf install fprintd Fedora 35 - x86_64 - Updates 45 kB/s | 8.1 kB 00:00 Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: fprintd x86_64 1.94.1-1.fc35 updates 164 k Installing dependencies: libfprint x86_64 1.94.2-1.fc35 updates 310 k Transaction Summary ############################################################ Note does not bring back one dependency removed in prior transaction #190. ############################################################ $ sudo dnf history undo 190 Last metadata expiration check: 0:08:49 ago on Wed 08 Dec 2021 08:05:08 AM EST. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: fprintd x86_64 1.94.1-1.fc35 updates 164 k Installing dependencies: fprintd-pam x86_64 1.94.1-1.fc35 updates 24 k libfprint x86_64 1.94.2-1.fc35 updates 310 k Transaction Summary ############################################################ Added debugging to fprintd.service To enable debug output run `systemctl edit fprintd.service` then enter: ``` [Service] Environment=G_MESSAGES_DEBUG=all ``` Save the result and restart fprintd using `systemctl restart fprintd.service`. # journalctl -b -u fprintd.service >tmp/fpserv.out cp tmp/fpserv.out tmp/fprintdserv.out Attaching fprintdserv.out to bug 2028872. $ rpm -qa | grep -i tlp results in empty output. ######## End of Commentary ######################################
As a followup I removed just the package "fprintd-pam" since it is not installed automatically with the command "dnf install fprintd" to see what happened on reboot. After reboot the password prompt was presented without delay. Running "journalctl -b -u fprintd.service" provided no output. So in response to comments #2 & #4 above was fprintd-pam installed and/or fprintd and dependent package?
OK, can you also provide full system logs for the time between these two messages? Dec 08 10:17:24 t4s fprintd[1028]: Launching FprintObject Dec 08 10:17:30 t4s fprintd[1028]: Preparing devices for resume It is a bit odd. If the `Preparing devices for resume` message was not delayed, I would just say that USB enumeration is hanging (in that case, kernel logs might be helpful). As-is, I am a bit confused about it and it would be nice to just get the full system logs to see if that tells us more.
Created attachment 1845298 [details] Journal output per request in comment #13 I didn't see anything relevant in the time range requested. I'm thinking those USB devices listed are common identifiers for known fingerprint readers and because my system doesn't have one they are coming up empty.
As I suspected, bluetooth kernel bug. *** This bug has been marked as a duplicate of bug 2019857 ***