After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 410215 - problems with introspection
problems with introspection
Status: RESOLVED OBSOLETE
Product: tracker
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jamie McCracken
Jamie McCracken
Depends on:
Blocks:
 
 
Reported: 2007-02-20 23:55 UTC by Michael Biebl
Modified: 2008-10-13 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Biebl 2007-02-20 23:55:44 UTC
The original bug report is filed at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411778

Summary:

Tracker causes dbus-python to segfault (or more precisely my
dbus-inspector application; but I shouldn't be able to do this with pure
python code). I'll clone the bug report to python-dbus, too. But it
should probably be fixed on both sides:

---
Introspect error: Connection was disconnected before a reply was
received
Introspection failed for org.freedesktop.Tracker (:1.956),
/org/freedesktop/DBus/Local
process 4277: 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]    4277 segmentation fault  ./dbus-inspector
---

It seems that trackerd disconnects when I'm trying to do introspection,
which apparently requires me to reinitialise dbus on the client side.
(other introspection errors on e.g. NetworkManager or Hal are handled
gracefully.)
Comment 1 Ivan Frade 2008-10-13 11:11:14 UTC
we have rewritten almost all the dbus code, and now dbus introspection is working nicely.

So i close the bug as obsolete.