Comment 8 for bug 1806269

Steps to reproduce on my system:
- Run 'nm-connection-editor'
- Select any network (in my case, a home WLAN for which the computer
  doesn't have the password yet; but *all other* networks are also affected)
- Click the 'Edit' button

Expected behavior: Not sure how, but it should open the configuration
dialog eventually.

Actual behavior: Segfault in src/libnma/nma-cert-chooser-button.c:95

Relevant part of gdb's output:

    #0 0xb76b121e in modules_initialized (object=0x0, res=0x8104d8e0,
    user_data=0x81058178) at src/libnma/nma-cert-chooser-button.c:95
            self = 0x81058178 [NMACertChooserButton]
            error = 0x0
            modules = 0x0
            iter = {stamp = -2134551640, user_data = 0x80c553c8,
                    user_data2 = 0x1, user_data3 = 0x80f8af20}

And line 95 is:

    93 if (!modules) {
    94 /* The Front Fell Off. */
    95 g_critical ("Error getting registered modules: %s",
                                error->message);
    96 g_error_free (error);
    97 }

It tries to access the 'message' field of 'error', which is null.
So there is a soft-error (no modules found), which is then handled badly at
some point ('error' ends up being null-but-accessed).

'error' probably should be written by
'gck_modules_initialize_registered_finish',
and I have no idea why it doesn't.

Not sure if the problem is with gck or with libnma's usage of it.

Assuming it's libnma's fault, is this the right place to report bugs?
Can someone look into it and maybe even fix it?

Cheers,
Ben
PS: Already report downstream in the Debian BTS as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865013#41