Bug#843060: libgcr-base-3-1: Gcr python bindings via gobject introspection can easily crash python

[Daniel Kahn Gillmor]

Package: libgcr-base-3-1
Version: 3.20.0-3
Severity: normal

Consider the following python script:

    import gi
    gi.require_version('Gcr', '3')
    from gi.repository import Gcr
    p = Gcr.SystemPrompt()
    p.init()
    p.close()
    p.init()


It will crash python at the last line with the following error:

(process:24799): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed
**
Gcr:ERROR:gcr/gcr-system-prompt.c:956:perform_init_async: assertion failed: (self->pv->prompt_path != NULL)
Aborted

At worst, it should throw an exception or resolve the problem in some
other pythonic way.  It should not crash the entire python process.

        --dkg


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libgcr-base-3-1 depends on:
ii  libc6            2.24-5
ii  libgck-1-0       3.20.0-3
ii  libgcr-3-common  3.20.0-3
ii  libgcrypt20      1.7.3-2
ii  libglib2.0-0     2.50.1-1
ii  libp11-kit0      0.23.2-5

libgcr-base-3-1 recommends no packages.

libgcr-base-3-1 suggests no packages.

-- no debconf information