Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Screen locks after login using smartcard pin
Version-Release number of selected component (if applicable):
gnome-shell-3.22.3-9.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. "Require smartcard for Login" and "Lock screen on smartcard removal"
are enabled using authconfig UI
2. Reboot
3. Login using smartcard pin
Actual results:
Login is successful but screen locks soon after login
Expected results:
Additional info:
May 11 13:26:18 dhcp129-112 kernel: in libgtk-3.so.0.2200.10[7f0a6dbf9000+6f4000]
May 11 13:26:18 dhcp129-112 abrt-hook-ccpp: Process 1808 (gnome-session-failed) of user 42 killed by SIGSEGV - dumping core
May 11 13:26:18 dhcp129-112 kernel: fuse init (API version 7.22)
May 11 13:26:18 dhcp129-112 systemd: Mounting FUSE Control File System...
May 11 13:26:19 dhcp129-112 systemd: Mounted FUSE Control File System.
May 11 13:26:19 dhcp129-112 abrt-server: Duplicate: core backtrace
May 11 13:26:19 dhcp129-112 abrt-server: DUP_OF_DIR: /var/spool/abrt/ccpp-2017-05-09-13:52:06-3476
May 11 13:26:19 dhcp129-112 abrt-server: Deleting problem directory ccpp-2017-05-11-13:26:18-1808 (dup of ccpp-2017-05-09-13:52:06-3476)
May 11 13:26:19 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 11 13:26:19 dhcp129-112 dbus[802]: [system] Activating service name='org.freedesktop.problems' (using servicehelper)
May 11 13:26:19 dhcp129-112 dbus-daemon: dbus[802]: [system] Successfully activated service 'org.freedesktop.problems'
May 11 13:26:19 dhcp129-112 dbus[802]: [system] Successfully activated service 'org.freedesktop.problems'
May 11 13:26:19 dhcp129-112 gnome-session: generating cookie with syscall
May 11 13:26:19 dhcp129-112 gnome-session: generating cookie with syscall
May 11 13:26:19 dhcp129-112 gnome-session: generating cookie with syscall
May 11 13:26:19 dhcp129-112 gnome-session: generating cookie with syscall
May 11 13:26:19 dhcp129-112 abrt-server: Email address of sender was not specified. Would you like to do so now? If not, 'user@localhost' is to be used [y/N]
May 11 13:26:19 dhcp129-112 abrt-server: Email address of receiver was not specified. Would you like to do so now? If not, 'root@localhost' is to be used [y/N]
May 11 13:26:19 dhcp129-112 abrt-server: Sending an email...
May 11 13:26:19 dhcp129-112 abrt-server: Sending a notification email to: root@localhost
May 11 13:26:19 dhcp129-112 gnome-keyring-daemon[2043]: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 gnome-keyring-daemon[2042]: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 journal: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 gnome-keyring-daemon[2044]: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 journal: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 journal: couldn't access control socket: /run/user/1002/keyring/control: No such file or directory
May 11 13:26:19 dhcp129-112 abrt-server: Email was sent to: root@localhost
May 11 13:26:19 dhcp129-112 gnome-keyring-ssh.desktop: SSH_AUTH_SOCK=/run/user/1002/keyring/ssh
May 11 13:26:20 dhcp129-112 rtkit-daemon[797]: Successfully made thread 2063 of process 2063 (/usr/bin/pulseaudio) owned by '1002' high priority at nice level -11.
May 11 13:26:20 dhcp129-112 rtkit-daemon[797]: Successfully made thread 2066 of process 2063 (/usr/bin/pulseaudio) owned by '1002' RT at priority 5.
May 11 13:26:21 dhcp129-112 rtkit-daemon[797]: Successfully made thread 2069 of process 2063 (/usr/bin/pulseaudio) owned by '1002' RT at priority 5.
May 11 13:26:21 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
May 11 13:26:21 dhcp129-112 dbus[802]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
May 11 13:26:21 dhcp129-112 journal: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
May 11 13:26:21 dhcp129-112 journal: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
May 11 13:26:21 dhcp129-112 journal: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
May 11 13:26:21 dhcp129-112 journal: JS WARNING: [resource:///org/gnome/shell/gdm/loginDialog.js 1030]: anonymous function does not always return a value
May 11 13:26:22 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
May 11 13:26:22 dhcp129-112 dbus[802]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
May 11 13:26:22 dhcp129-112 systemd: Starting Location Lookup Service...
May 11 13:26:22 dhcp129-112 dbus-daemon: dbus[802]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
May 11 13:26:22 dhcp129-112 dbus[802]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
May 11 13:26:22 dhcp129-112 systemd: Started Location Lookup Service.
May 11 13:26:23 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 11 13:26:23 dhcp129-112 dbus[802]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May 11 13:26:23 dhcp129-112 systemd: Starting Disk Manager...
May 11 13:26:23 dhcp129-112 udisksd[2106]: udisks daemon version 2.1.2 starting
May 11 13:26:24 dhcp129-112 dbus-daemon: dbus[802]: [system] Successfully activated service 'org.freedesktop.UDisks2'
May 11 13:26:24 dhcp129-112 dbus[802]: [system] Successfully activated service 'org.freedesktop.UDisks2'
May 11 13:26:24 dhcp129-112 udisksd[2106]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May 11 13:26:24 dhcp129-112 systemd: Started Disk Manager.
May 11 13:26:25 dhcp129-112 systemd: Starting Stop Read-Ahead Data Collection...
May 11 13:26:25 dhcp129-112 systemd: Started Stop Read-Ahead Data Collection.
May 11 13:26:28 dhcp129-112 spice-vdagent[2206]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
May 11 13:26:28 dhcp129-112 gnome-session: gnome-session-binary[1811]: WARNING: App 'spice-vdagent.desktop' exited with code 1
May 11 13:26:28 dhcp129-112 gnome-session-binary[1811]: WARNING: App 'spice-vdagent.desktop' exited with code 1
May 11 13:26:28 dhcp129-112 journal: JS WARNING: [/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js 367]: octal literals and octal escape sequences are deprecated
May 11 13:26:28 dhcp129-112 journal: JS WARNING: [/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js 367]: octal literals and octal escape sequences are deprecated
May 11 13:26:28 dhcp129-112 journal: JS WARNING: [/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js 367]: octal literals and octal escape sequences are deprecated
May 11 13:26:29 dhcp129-112 journal: Failed to load background 'file:///usr/share/backgrounds/gnome/adwaita-lock.jpg': Error opening file /usr/share/backgrounds/gnome/adwaita-lock.jpg: No such file or directory
May 11 13:26:29 dhcp129-112 journal: Unable to connect to ibus: Could not connect: Connection refused
May 11 13:26:29 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
May 11 13:26:29 dhcp129-112 dbus[802]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service'
May 11 13:26:29 dhcp129-112 journal: JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files#012_proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83
May 11 13:26:29 dhcp129-112 systemd: Starting Location Lookup Service...
May 11 13:26:29 dhcp129-112 dbus[802]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
May 11 13:26:29 dhcp129-112 dbus-daemon: dbus[802]: [system] Successfully activated service 'org.freedesktop.GeoClue2'
May 11 13:26:29 dhcp129-112 systemd: Started Location Lookup Service.
May 11 13:26:30 dhcp129-112 gnome-shell: GNOME Shell started at Thu May 11 2017 13:26:28 GMT-0400 (EDT)
May 11 13:26:30 dhcp129-112 imsettings-start.desktop: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._imsettings_2derror_2dquark.Code5: Current desktop isn't targeted by IMSettings.
May 11 13:26:30 dhcp129-112 journal: No devices in use, exit
May 11 13:26:31 dhcp129-112 vmware-user.desktop: vmware-user: could not open /proc/fs/vmblock/dev
May 11 13:26:32 dhcp129-112 gnome-session-binary: Entering running state
May 11 13:26:32 dhcp129-112 libcanberra-login-sound.desktop: Failed to play sound: File or data not found
May 11 13:26:35 dhcp129-112 journal: STACK_OP_ADD: window 0x2000001 already in stack
May 11 13:26:35 dhcp129-112 journal: STACK_OP_ADD: window 0x2000001 already in stack
May 11 13:26:36 dhcp129-112 dbus-daemon: dbus[802]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
May 11 13:26:36 dhcp129-112 dbus[802]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
May 11 13:26:36 dhcp129-112 systemd: Starting Fingerprint Authentication Daemon...
May 11 13:26:36 dhcp129-112 dbus-daemon: dbus[802]: [system] Successfully activated service 'net.reactivated.Fprint'
May 11 13:26:36 dhcp129-112 dbus[802]: [system] Successfully activated service 'net.reactivated.Fprint'
May 11 13:26:36 dhcp129-112 systemd: Started Fingerprint Authentication Daemon.
May 11 13:26:36 dhcp129-112 fprintd: Launching FprintObject
May 11 13:26:36 dhcp129-112 journal: D-Bus service launched with name: net.reactivated.Fprint
May 11 13:26:36 dhcp129-112 journal: entering main loop
May 11 13:26:38 dhcp129-112 systemd-logind: Removed session c1.
May 11 13:26:38 dhcp129-112 systemd: Removed slice User Slice of gdm.
May 11 13:26:38 dhcp129-112 systemd: Stopping User Slice of gdm.
May 11 13:26:39 dhcp129-112 journal: g_slice_set_config: assertion 'sys_page_size == 0' failed
May 11 13:26:42 dhcp129-112 gnome-software-service.desktop: 17:26:42:0762 flatpak Unable to create FlatpakInstallation for: Permission denied
May 11 13:26:43 dhcp129-112 gnome-software-service.desktop: 17:26:43:0682 Gs failed to call gs_plugin_add_updates_historical on packagekit-offline: No updates available
May 11 13:26:46 dhcp129-112 dbus-daemon: dbus[802]: [system] Failed to activate service 'org.bluez': timed out
May 11 13:26:46 dhcp129-112 dbus[802]: [system] Failed to activate service 'org.bluez': timed out
May 11 13:26:46 dhcp129-112 pulseaudio[2063]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 11 13:26:51 dhcp129-112 tracker-store.desktop: (uint32 1,)
May 11 13:27:01 dhcp129-112 org.gnome.Shell.desktop: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00015 (gnome-init)
May 11 13:27:04 dhcp129-112 chronyd[810]: Selected source 10.5.26.10
Comment 3Ray Strode [halfline]
2017-05-12 14:00:08 UTC
(In reply to Ray Strode [halfline] from comment #3)
> is this opensc or coolkey ?
Both environments have the same issue
Comment 5Ray Strode [halfline]
2017-06-14 18:45:19 UTC
JS ERROR: could not get remote objects for service org.gnome.SettingsDaemon.Smartcard path /org/gnome/SettingsDaemon/Smartcard: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Smartcard was not provided by any .service files#012_proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:83
I wonder if we're racing with settings-daemon starting up.
Comment 6Ray Strode [halfline]
2017-06-14 21:09:46 UTC
I have a patch that I believe should address this. devack+
Created attachment 1288201[details]
/var/log/messages
Things look very inconsistent with smartcard login tests. I am not sure if it is gnome-shell or any other component causing this. Attaching /var/log/messages
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2098