Endless loop with password prompt(s) in thunderbird produced by EDS Contacts Integration

> Clicking "Cancel" on these dialogs should make the addon stop asking for authentication.

You're absolutely right. I can certainly make it not bother you after you click cancel - though when should we reprompt? I presume that at some point you'll have your Exchange address books ready to go, and you'll want to reauthenticate. Is it alright if it asks again the next time Thunderbird starts up?

-Mike

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Is it alright if it asks again the next time Thunderbird starts
> up?

This sounds reasonable.

Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOiJ80fAK/hT/mPgARAtpxAJ0cAmkQCeTjQ9gqV1arqrNWATsA1ACfYEnw
hFa1aypQ+bKNveD8TwlsLZo=
=qpMw
-----END PGP SIGNATURE-----

Committed in release 0.3.7a.

http://bazaar.launchpad.net/~mconley/thunderbird-eds-extension/0.3/revision/93

I've uploaded the fix for this to oneiric-proposed now

Hello Daniel, or anyone else affected,

Accepted thunderbird into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I have installed the update, and do not get into an endless loop anymore when activating the addon:
it asks me for the password twice (different address books?!), I click OK and it goes away.

While that's better than before, it still appears to not be able to connect (I see 0 addresses), so it should probably re-open the password prompt while it cannot connect (but stop asking for it when clicking Cancel).

After restarting Thunderbird (and also disabling/enabling the extension) it still does not ask for the password.

I should have tested it with a wrong password first.

How would I reset the password prompt to ask me again?

Given that, the update is better than before, so it can go to oneiric-updates, although I cannot say, if it would cause any regression with a working setup.

This bug was fixed in the package thunderbird - 8.0+build1-0ubuntu0.11.10.1

---------------
thunderbird (8.0+build1-0ubuntu0.11.10.1) oneiric-security; urgency=low

  * New upstream stable release v8.0 (THUNDERBIRD_8_0_BUILD1)

  * Update messagingmenu-extension to 0.8.3
    - This version backs out the change made in 7.0.1+build1+nobinonly-0ubuntu2
      that didn't fix LP#850229
  * Don't disable our bundled addons on upgrade
    - update debian/vendor.js
  * Move custom scripts to debian/build
    - move debian/get-xpi-id.py to debian/build/get-xpi-id.py
    - move debian/refresh-supported-locales.pl to
       debian/build/refresh-supported-locales.pl
    - move debian/extract-file.py to debian/build/extract-file.py
    - move debian/testsuite.mk to debian/build
    - update debian/rules
  * Shrink the default mozconfig right down so that we use mostly upstream
    defaults, rather than overriding them with our own options. It is still
    possible to override them though. We also drop the pkg-config checks in
    debian/rules which allowed a fallback build configuration when dependencies
    aren't satisfied. Really, the build should just fail here rather than
    continuing in some undesirable fallback mode
    - update debian/thunderbird-dev.links.in
    - update debian/mozconfig.in
    - update debian/control.in
    - update debian/rules
  * Refresh build-depends, as this hasn't been done for a while:
    - Drop patchutils, libxft-dev, libxinerama-dev, libgnome2-dev, sharutils
      and bzip2. These don't appear to be needed
    - Drop liborbit2-dev - only appears to be required if there is no libidl
    - Add libglib2.0-dev, libext-dev, libfontconfig1-dev and libpango1.0-dev,
      as the configure script checks for these directly
    - Add minimum versions to libgconf2-dev, libgnomevfs2-dev, yasm and
      libgnomeui-dev
    - Specify minimum versions for libnspr4-dev, libcairo2-dev, libsqlite3-dev
      and libnss3-dev when using system versions of those libs
  * Introduce a branch config file (debian/config/branch.mk) which holds
    settings which shouldn't be merged between branches (eg, whether
    the crash reporter should be enabled)
    - add debian/config/branch.mk
    - update debian/rules
  * Move debian/locales.* to debian/config
    - move debian/locales.shipped => debian/config/locales.shipped
    - move debian/locales.unavail => debian/config/locales.unavail
    - update debian/rules
    - update debian/build/refresh-supported-locales.pl
  * Move debian/mozconfig.in to debian/config
  * Touch debian/control.in during clean to force a refresh of debian/control,
    so we can check if it is out-of-date and fail if it is
    - update debian/rules
  * Refresh patches:
    - update debian/patches/ctypes-callback-reentry-fix.patch
    - update debian/patches/theme-refresh-compose-toolbar-icons.patch
    - update debian/patches/theme-refresh-message-header-buttons.patch
  * Drop the mozilla-devscripts dependency. We were only using this for creating
    tarballs anyway. Instead, implement our own get-orig-source target, which
    also fixes some problems we were having
    - update debian/control.in
    - remove debian/moz-r...