Unity.ActivationResponse does not work properly for python scopes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Undecided
|
Unassigned | ||
libunity |
Fix Released
|
Low
|
Unassigned | ||
gobject-introspection (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
libunity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
vala (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Test Case]
1) Run `python -c "from gi.repository import Unity; print Unity.Activatio
2) The command shouldn't cause a segmentation fault
[Regression Potential]
Besides gir not working, nothing else comes to mind.
====Original Report====
When attempting to use a custom activation of a lens result in a scope written in python, Unity.Activatio
TypeError: can't convert return value to desired type
../pathtolens/
../pathtolens/
../pathtolens/
Similar errors are generated when using other "Unity.Handletype"s (although using NOT_HANDLED only produces the TypeError part, not any of the warnings.)
This issue is also described at http://
Related branches
Changed in libunity: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
importance: | Medium → Low |
Changed in libunity: | |
status: | Confirmed → Fix Committed |
description: | updated |
Changed in libunity (Ubuntu): | |
status: | New → Fix Committed |
no longer affects: | unity (Ubuntu) |
Changed in gobject-introspection (Ubuntu Precise): | |
status: | New → Invalid |
no longer affects: | gobject-introspection (Ubuntu Precise) |
Changed in unity: | |
status: | Incomplete → Fix Released |
Changed in libunity (Ubuntu): | |
status: | Fix Committed → Invalid |
Changed in libunity (Ubuntu Precise): | |
status: | New → Triaged |
no longer affects: | vala (Ubuntu Precise) |
Changed in vala (Ubuntu): | |
status: | New → Triaged |
Changed in libunity (Ubuntu Precise): | |
status: | Triaged → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in libunity: | |
status: | Fix Committed → Fix Released |
no longer affects: | libunity (Ubuntu Quantal) |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
Changed in unity (Ubuntu Precise): | |
status: | New → Fix Released |
Looks like a proper and confirmed bug, but is GObject Introspection to blame for this one?