[gdm/benzea/fix-conversation-error-reporting] session: Initialize DBus error domain before resolving errors




commit f3c52a66016852388d4a98018345cd1e45e06bb6
Author: Benjamin Berg <bberg redhat com>
Date:   Wed Mar 10 11:43:00 2021 +0100

    session: Initialize DBus error domain before resolving errors
    
    We would not initialize the DBus error domain before we retrieved the
    first error, but only did so to compare the error after receiving them.
    This means that the first error we received will not be resolved
    correctly, while all subsequent ones are resolved.
    
    Fix this by calling GDM_SESSION_WORKER_ERROR from gdm_session_class_init.

 daemon/gdm-session.c | 3 +++
 1 file changed, 3 insertions(+)
---
diff --git a/daemon/gdm-session.c b/daemon/gdm-session.c
index a6f00b66d..455c39b66 100644
--- a/daemon/gdm-session.c
+++ b/daemon/gdm-session.c
@@ -3998,6 +3998,9 @@ gdm_session_class_init (GdmSessionClass *session_class)
                                                                FALSE,
                                                                G_PARAM_READWRITE | G_PARAM_CONSTRUCT | 
G_PARAM_STATIC_STRINGS));
 #endif
+
+        /* Ensure we can resolve errors */
+        g_type_ensure (GDM_SESSION_WORKER_ERROR);
 }
 
 GdmSession *


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]