Bug 22365 - Assertion when Gypsy can't be found
Summary: Assertion when Gypsy can't be found
Status: RESOLVED WORKSFORME
Alias: None
Product: dbus
Classification: Unclassified
Component: GLib (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Geoclue Bugs
QA Contact: Geoclue Bugs
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2009-06-19 05:30 UTC by Bastien Nocera
Modified: 2010-09-28 09:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Bastien Nocera 2009-06-19 05:30:47 UTC
$ /usr/libexec/geoclue-gypsy
Gypsy provider using 00:0D:B5:70:54:75
Error - The name org.freedesktop.Gypsy was not provided by any .service files?

** (process:32028): CRITICAL **: dbus_g_error_get_name: assertion `error->code == DBUS_GERROR_REMOTE_EXCEPTION' failed
process 32028: arguments to dbus_message_new_error() were incorrect, assertion "error_name != NULL" failed in file dbus-message.c line 1206.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Comment 1 Bastien Nocera 2009-06-19 12:55:18 UTC
This is a bug in dbus-glib.

The first function called on the proxy after creation through dbus_g_proxy_new_for_name() can fail on something that's not a remote error.
Comment 2 Bastien Nocera 2009-06-19 12:55:50 UTC
This is with dbus-glib-0.80-2.fc11.x86_64
Comment 3 Simon McVittie 2009-07-20 06:03:28 UTC
I think this is Bug #16776, could you try with 0.82 or cherry-pick my patch "teach dbus_g_method_return_error about DBUS_GERROR"? If my patch fixes this symptom, feel free to close it as a duplicate.
Comment 4 Simon McVittie 2010-07-12 08:38:44 UTC
Could someone try this with dbus-glib 0.82, please?
Comment 5 Simon McVittie 2010-09-28 09:24:02 UTC
In the absence of any feedback, I'm going to assume this is a duplicate of Bug #16776.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.