Unable to authenticate with smartcard: gnome-shell throws on unhandled promise rejection

Bug #2065432 reported by Kyle Metscher
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Upstream report: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7526

Opening as part of response to support ticket.

After boot, GDM does not prompt for smartcard authentication correctly. It is possible to strike Esc and get GDM to prompt for a username and a smartcard PIN from the initial locked-out state, but this does not start a new desktop session and instead hangs. Striking Esc allows for the login to be attempted again, but with the same results.

Syslog entries include unhandled promise rejections from the onSessionOpened event in loginDialog, and perhaps more importantly also from the user verification stack that is used to create the initial authentication options prompt (stack traces of the syslog entries attached).

Affects GDM 46.0-2ubuntu1 in Noble.

To reproduce, configure smartcard auth for a network user on a new Noble install and try to sign in.

Revision history for this message
Kyle Metscher (kmetscher) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdm3 (Ubuntu):
status: New → Confirmed
affects: gdm3 (Ubuntu) → gnome-shell (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.