touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #04035
[Bug 781650] Re: Unity.Activation interface is incompatible with PyGI
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/781650
Title:
Unity.Activation interface is incompatible with PyGI
Status in LibUnity:
Fix Released
Status in Unity:
Fix Released
Status in Unity 2D:
Fix Released
Status in “libunity” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Bug description:
Following the discussion on ayatana-dev: https://lists.launchpad.net
/ayatana-dev/msg00148.html
The Unity.Activation interface is incompatible with PyGI because of
the use of callbacks:
UnityActivationStatus activate (const gchar* uri, GAsyncReadyCallback
_callback_, gpointer _user_data_);
Resulting in warnings and corrupt arguments when passed to python:
** (process:23642): WARNING **: You are trying to use an API which
returns a callback.Callback returns can not be supported. Returning
None instead.
The underlying problem seems to be that the interface is defined as
async in the Vala code. As suggested by Mikkel in the mailing list,
the method should be converted into a normal synchronous one, i.e.:
UnityActivationStatus activate (const gchar *uri);
To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/781650/+subscriptions