Hello Mark, or anyone else affected, Accepted libunity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libunity/5.12.0-0ubuntu1.1 in a few hours and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libunity (Ubuntu Precise) Status: Fix Released => In Progress ** Changed in: libunity (Ubuntu Precise) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/893688 Title: Unity.ActivationResponse does not work properly for python scopes Status in LibUnity: Fix Committed Status in Unity: Fix Released Status in “gobject-introspection” package in Ubuntu: Fix Released Status in “libunity” package in Ubuntu: Fix Released Status in “vala” package in Ubuntu: Fix Released Status in “libunity” source package in Precise: Fix Committed Bug description: [Test Case] 1) Run `python -c "from gi.repository import Unity; print Unity.ActivationResponse.new(Unity.HandledType.SHOW_DASH, '')"` 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.ActivationResponse does not work as advertised at https://wiki.ubuntu.com/Unity/Lenses#Handling_Activation, which suggests that the line Unity.ActivationResponse.new(Unity.HandledType.SHOW_DASH) should pass a response to keep the dash open. Instead, an error in generated suggesting that a second argument needs to be passed to the function. On adding a second argument, the error further suggests that it needs to be a string. On using a string, the following error is generated: TypeError: can't convert return value to desired type ../pathtolens/lens.py:100: Warning: g_object_get_qdata: assertion G_IS_OBJECT (object)' failed GObject.MainLoop().run() ../pathtolens/lens.py:100: Warning: g_object_set_qdata_full: assertionG_IS_OBJECT (object)' failed GObject.MainLoop().run() ../pathtolens/lens.py:100: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed GObject.MainLoop().run() 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://askubuntu.com/questions/78826 /cant-get-activate-uri-signal-working-when-making-a-lens To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/893688/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
