Bug#411785: python-dbus: Causes segfaults

Package: python-dbus
Version: 0.80.2-1
Severity: normal

Python-dbus can be caused to segfault:
---
import dbus
sb = dbus.SystemBus()
sb.get_is_connected()
[1] 492 segmentation fault python
---

I was trying to find a way to force a reconnect, to avoid the error in
#411778 (I'll clone that bug to python-dbus):
---
Introspect error: Connection was disconnected before a reply was
received
Introspection failed for org.freedesktop.Tracker (:1.956),
/org/freedesktop/DBus/Local
process 3545: arguments to dbus_pending_call_set_notify() were
incorrect, assertion "pending != NULL" failed in file
dbus-pending-call.c line 598.
This is normally a bug in some application using the D-Bus library.
[1] 3545 segmentation fault ./dbus-inspector
---

It seems that the abrupt disconnection by tracker brings dbus-python
into an inconsistent state.

-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-

Versions of packages python-dbus depends on:
ii libc6 2.3.6.ds1-12 GNU C Library: Shared libraries
ii libdbus-1-3 1.0.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.72-4 simple interprocess messaging syst
ii libglib2.0-0 2.12.9-2 The GLib library of C routines
ii python 2.4.4-2 An interactive high-level object-o
ii python-support 0.5.6 automated rebuilding support for p

Versions of packages python-dbus recommends:
ii python-gobject 2.12.3-1 Python bindings for the GObject li

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org