Hi:
Firstly, in dbus-glib the call g_dbus_proxy_get_cached_property does not block IO, so the answer value got is came from local cache instead of Rtk side through dbus message. In general, this call could be used in "g-properties-changed" signal callback to update local cache.
If you want to query some properties registered on Rtk service using g-dbus, the send_method_call(XXX_NAME,XXX_PATH,DBUS_INTERFACE_PROPERTIES, "Get", ...) could be used to get the real value.
The "operation not permitted" error returned may be caused due to the permission problem inside the rtkit. You could check the rtkit version and update its package, then try it again.
With blessings.
On Sat, 22 Feb 2014 21:08:57 +0100, Emmanuel Pacaud<emmanuel@xxxxxxxxx>wrote:
>Description: Text Data
>Hi, > >I'm trying to do an implementation of rtkit make_realtime, using the >g_dbus API. > >But I'm blocking on some issues I don't know how to solve. > >I have attached a sample program. When I try to run it, I get: > >./dbus > >** (process:16064): WARNING **: [::make_realtime] Failed to get >MaxRealtimePriority > >** (process:16064): WARNING **: [::make_realtime] Failed to set realtime >scheduling using rtkit >(GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not >permitted) > >Why MaxRealtimePriority property is not returned ? > >Why the dbus call returns 'Operation not permitted' (even as root) ? > > >Any ideas ? > > Thanks, > > Emmanuel.>Attachment: dbus.c
>Description: Text Data
_______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-list
