GNOME Bugzilla – Bug 685434
Freeze because of exception on unlock when there is an authentication error
Last modified: 2012-10-03 20:08:32 UTC
When an authentication error occurs (in this case a dbus access issue), gnome-shell freeze. This is because of an uncaught exception occuring, caused by a typo (spotted by Olav). Agent unregistration failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "UnregisterAgent" with signature "o" on interface "org.bluez.Adapter" doesn't exist 'g-io-error-quark' JS ERROR: !!! Failed to open reauthentication channel JS ERROR: !!! message = '"GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Aucune session disponible pour la réauthentification de blino"' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/gdm/util.js"' JS ERROR: !!! lineNumber = '154' JS ERROR: !!! stack = '"0 anonymous("result" = [object _private_Gio_SimpleAsyncResult], "client" = [object _private_Gdm_Client])@/usr/share/gnome-shell/js/gdm/util.js:154 1 wrapper([object _private_Gdm_Client], [object _private_Gio_SimpleAsyncResult])@/usr/share/gjs-1.0/lang.js:204 "' JS ERROR: !!! Exception was: TypeError: this._hold.relase is not a function JS ERROR: !!! message = '"this._hold.relase is not a function"' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/gdm/util.js"' JS ERROR: !!! lineNumber = '146' JS ERROR: !!! stack = '"("Failed to open reauthentication channel",[object _private_Gio_DBusError])@/usr/share/gnome-shell/js/gdm/util.js:146 wrapper("Failed to open reauthentication channel",[object _private_Gio_DBusError])@/usr/share/gjs-1.0/lang.js:204 ([object _private_Gdm_Client],[object _private_Gio_SimpleAsyncResult])@/usr/share/gnome-shell/js/gdm/util.js:165 wrapper([object _private_Gdm_Client],[object _private_Gio_SimpleAsyncResult])@/usr/share/gjs-1.0/lang.js:204 "'
Created attachment 225708 [details] [review] ShellUserVerifier: fix typo in function name, caught on auth error This patch fixes the typo.
Review of attachment 225708 [details] [review]: I thought I had fixed that before merging, but yes, that's it.
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.