Unity.Activation interface is incompatible with PyGI

Bug #781650 reported by Johannes H. Jensen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
Undecided
Unassigned
libunity
Fix Released
Undecided
Unassigned
unity-2d
Fix Released
Undecided
Unassigned
libunity (Ubuntu)
Fix Released
Undecided
Unassigned
unity (Ubuntu)
Fix Released
Undecided
Unassigned

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);

Changed in libunity:
status: New → Confirmed
Changed in libunity (Ubuntu):
status: New → Confirmed
Changed in unity-2d:
status: New → Invalid
Changed in unity:
status: New → Invalid
Changed in unity:
status: Invalid → Confirmed
Changed in unity-2d:
status: Invalid → Confirmed
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

This was fixed in the 4.0 series of libunity

Changed in libunity:
status: Confirmed → Fix Released
Changed in unity:
status: Confirmed → Fix Released
Changed in unity-2d:
status: Confirmed → Fix Released
Changed in libunity (Ubuntu):
status: Confirmed → Fix Released
Changed in unity (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.