Unity.Activation interface is incompatible with PyGI
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:/
The Unity.Activation interface is incompatible with PyGI because of the use of callbacks:
UnityActivation
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.:
UnityActivation
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 |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
This was fixed in the 4.0 series of libunity