My gut feeling is that the following is the cause:
févr. 17 11:09:07 dresden gnome-shell[4485]: Failed to interact with fprintd
service: Error: GSettings key enable-authd-authentication not found in schema
com.ubuntu.login-screen
Stack trace:
_checkKey@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:779:23
createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:729:30
_getDetectedDefaultService@resource:///org/gnome/shell/gdm/util.js:905:34
_initFingerprintManager@resource:///org/gnome/shell/gdm/util.js:526:23
_updateEnabledServices@resource:///org/gnome/shell/gdm/util.js:858:18
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:183:14
_createUserVerifier@resource:///org/gnome/shell/gdm/authPrompt.js:147:16
_init@resource:///org/gnome/shell/gdm/authPrompt.js:89:35
AuthPrompt@resource:///org/gnome/shell/gdm/authPrompt.js:66:4
_init@resource:///org/gnome/shell/gdm/loginDialog.js:535:28
LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4
_ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:470:28
showDialog@resource:///org/gnome/shell/ui/screenShield.js:402:14
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:316:26
_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:762:18
_loadBackground/signalId</id<@resource:///org/gnome/shell/ui/layout.js:691:26
@resource:///org/gnome/shell/ui/init.js:21:20
I can't find trace of this error in earlier logs of the system, and it *does*
talk of auth prompts...
However, I was unable to find any mention of "enable-authd-authentication" in
the sources of either gdm3, gcr or fprintd.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gcr in Ubuntu.
https://bugs.launchpad.net/bugs/2098654
Title:
/usr/libexec/gcr-
prompter:11:gtk_im_multicontext_set_slave:im_module_setting_changed:g_closure_invoke:signal_emit_unlocked_R:signal_emit_valist_unlocked
Status in gcr package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gcr. This problem was most recently seen with package version 3.41.2-1build3,
the problem page at
https://errors.ubuntu.com/problem/f88a0764d64cfefc84addd1205ea7824f0aec75c
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/2098654/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp