Remove the automatic generation of the *_gen_* private functions jsc-types bindings

Bug #1111732 reported by Alexandre Abreu on 2013-01-31
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WebApps: unity-firefox-extension
Undecided
Unassigned
unity-firefox-extension (Ubuntu)
Undecided
Unassigned
Quantal
Medium
Unassigned

Bug Description

[Impact]

At the moment, the jsc-types bindings (needed so that the extension can directly access the C API functions exported by libunity-webapps) are being generated automatically every time one builds the extension by direct parsing of the gir files generated from libunity-webapps.

Part of those exported bindings are some internal functions part of libunity-webapps that are being wrongly exported as symbols along with public parts of the API. This has been fixed in libunity-webapps trunk, where those symbols are not being exported. But now the issue is that we have a chicken and egg problem:

- we cannot release a new libunity-webapps version since the already released unity-firefox-extension will look for those missing bindings and break if they are not found,

- we cannot guarantee that releasing both libunity-webapps and unity-firefox-extension the user will install both at the same time, and it is not recommended (to keep packages individually "revertible") to add dependencies between updates,

Therefore, this update to unity-firefox-extension does not actually change very much that would be user visible; but it is a necessary prerequisite to a larger libunity-webapps SRU that we will be submitting after this one is approved. If this does not get approved, then the libunity-webapps SRU that we need to do will not function at all.

The idea is to make sure that we can release a new libunity-webapps version (that does not export anymore the private symbols) that won't break the ufe extension. We statically generate the bindings, instead of dynamically then, to have control over what the extension tries to bind with.

The list of bindings is the same as before, just without the private symbols (not used by the extension anyway).

[Test Case]

Verify that the extension works as expected under Firefox:

- opening a integrated website e.g. bbc.co.uk/news or twitter.com
- accepting the integration,
- making sure that an integration happens: launcher icon is there along with some notifications and/or messaging menu integration (in the case of twitter),

[Regression Potential]

None really since we only remove some function bindings that are anyway not exposed/used by the extension. The worst case would be that no integration happens anymore at all.

Related branches

CVE References

Changed in unity-firefox-extension (Ubuntu):
status: New → Fix Released
Changed in unity-firefox-extension (Ubuntu Quantal):
importance: Undecided → Medium
description: updated

Hello Alexandre, or anyone else affected,

Accepted unity-firefox-extension into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/unity-firefox-extension/2.4.4-0ubuntu0.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 add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and 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 unity-firefox-extension (Ubuntu Quantal):
status: New → Fix Committed
tags: added: verification-needed
Víctor R. Ruiz (vrruiz) wrote :

Tested using up-to-date Quantal, Firefox 19.0+build1-0ubuntu0.12.10.1 and xul-ext-unity 2.4.4-0ubuntu0.1

Test case:
1. Open http://launchpad.net/
2. Accept integration

Expected result:
- Launcher icon must be displayed.

Actual result: Works ok.

Test case:
1. Open http://ubuntuone.com/5rYjHq5Y1jJvlCt0xW6M5L
2. Accept integration.

Expected results:
- Launcher icon must be displayed.
- Launcher action "Sports" must be added.
- Notification must be shown.
- Sound menu entry must be displayed.
- Messaging menu entry must be displayed.

Actual results: Everything works ok.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-firefox-extension - 2.4.4-0ubuntu0.1

---------------
unity-firefox-extension (2.4.4-0ubuntu0.1) quantal-proposed; urgency=low

  * -debian/patches/CVE-2012-0958.patch
      - removed, merged upstream
  * -debian/patches/CVE-2012-0960
      - removed, merged upstream
  * New upstream release.
    - Crash when navigating to another page immediately
      after initializing unity integration (LP: #1076350).
    - Remove unity-webapps.js file generation for now. (LP: #1111732)
    - Add stress test.
    - Update to FF18.
    - Fix warnings.
 -- Robert Bruce Park <email address hidden> Wed, 30 Jan 2013 13:12:30 -0800

Changed in unity-firefox-extension (Ubuntu Quantal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers