This bug was fixed in the package firefox - 36.0+build2-0ubuntu0.14.10.4

---------------
firefox (36.0+build2-0ubuntu0.14.10.4) utopic-security; urgency=medium

  * New upstream stable release (FIREFOX_36_0_BUILD2)
    - see USN-2505-1

  * Refresh patches
    - update debian/patches/unity-menubar.patch
    - update debian/patches/ubuntu-ua-string-changes.patch
    - update debian/patches/dont-include-hyphenation-patterns.patch
    - update debian/patches/dont-override-general-useragent-locale.patch
  * Don't clone the nightly profile from the default profile at startup
    - update debian/firefox.sh.in
  * Don't use --with-app-basename to create the co-installable nightly build
    as it's not useful anymore, and changing the application name to
    "Firefox-Trunk" has always been problematic for code / addons that check
    the appname. Continue to use --with-app-name as before (which just changes
    the install name and the remoting name), and add a patch to introduce
    --with-app-profile, which allows us to change the profile location
    - update debian/build/rules.mk
    - update debian/build/config.mk
    - update debian/config/mozconfig.in
    - update debian/rules
    - add debian/patches/support-coinstallable-trunk-build.patch
    - add debian/patches/set-prgname-to-remoting-name.patch
    - update debian/patches/series
  * Install the gmp-clearkey directory
  * Add Google OAuth ID so contact import for Hello works (LP: #1401402)
  * Add Uzbek language pack
  * Add patch from Bugzilla to implement non-Skia fallback for unaccelerated
    rendering of 3D transforms to fix a build failure on platforms where Skia
    is not supported
    - add debian/patches/add-non-skia-fallback.patch
    - update debian/patches/series
  * Backport patch to fix a build failure in IonMonkey on platforms without
    a codegen
    - add debian/patches/fix-ion-ftbfs.patch
    - update debian/patches/series
  * Backport patch to fix a build failure in some unified builds
    - add debian/patches/fix-unified-ftbfs.patch
    - update debian/patches/series
 -- Chris Coulson <chris.coul...@canonical.com>   Mon, 23 Feb 2015 13:59:59 
+0000

** Changed in: firefox (Ubuntu)
       Status: Fix Committed => Fix Released

** Changed in: firefox (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1401402

Title:
  Ubuntu build of Firefox lacks Google OAuth ID, prevents contact import
  in Hello

Status in The Mozilla Firefox Browser:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Starting from verstion 34.0, Firefox, including Ubuntu build thereof, 
supports WebRTC based voice/video communication feature named "Hello":
  
https://support.mozilla.org/en-US/kb/firefox-hello-make-receive-calls-without-account

  This feature works in Ubuntu build, except importing contacts from Google 
account:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1106854
  Attempt to import contacts results in this Google error page:
  ====
  401. That’s an error.

  Error: invalid_client

  The OAuth client was not found.
  Request Details

      scope=https://www.google.com/m8/feeds
      response_type=code
      redirect_uri=urn:ietf:wg:oauth:2.0:oob:auto
      client_id=no-google-oauth-api-clientid
  ====

  Apparently, for the import feature to work, the build needs to include Google 
OAuth Client ID. The process is discussed here:
  https://wiki.mozilla.org/Loop/OAuth_Setup

  Apparently, Ubuntu's build of Firefox does not include this Client ID.
  Please consider adding it. Hopefully then "Hello" will be fully functional, 
including contacts import.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1401402/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to