670502 - Opening account manager (account settings) from compose window fails

Status: RESOLVED FIXED

Description

[AlexIhrig]

Opening the account manager from compose window -> Tools menu fails without an error in error console.

Tested with Thunderbird 5.0 and todays 8.0-comm-central build in safe-mode.

Comment 1

[Ludovic Hirlimann [:Usul]]

WFM on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:7.0a2) Gecko/20110713 Thunderbird/7.0a2.

Alex can you find the regression window ?

Comment 2

[AlexIhrig]

Hmm,

maybe only a problem with my 'old' profile. Testing with a new, clean profile WFM. Testing with my 'old' profile in safe-mode doesn't work.

Comment 3

[Ludovic Hirlimann [:Usul]]

Alex - does deleteing localstore.rdf in your old profile helps ?

Comment 5

[Wayne Mery (:wsmwk, NI for questions)]

regression range http://hg.mozilla.org/comm-central/pushloghtml?startdate=2011-03-07+03%3A00&enddate=2011-03-08+06%3A00
works 20110307
fails 20110308
puts the mark on Bug 549045

reproduces in safe mode with 2011-09-19 build

Comment 6

[Mark Banner (:standard8)]

Based on the comments here and the duplicate thread, we're going to need to get some idea of a test profile that exhibits the problem (e.g. I can't reproduce)

Comment 7

[Wayne Mery (:wsmwk, NI for questions)]

I've just used a pretty clean test profile in safe mode and one imap account.
1. open TB
2. open compose
3. tools | account settings

results: no account settings, nothing in error console
at startup: error console has
 Warning: Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead.
Source File: chrome://messenger/content/messenger.xul
Line: 0

I'll try to send you a profile

Comment 8

[:aceman]

I can see this too, on TB8, linux, on a used profile. On TB11, relativelly clean profile it work fine.

Comment 9

[Jim Porter (:squib)]

Taking this, since I inadvertently fixed it as part of another bug.

Comment 10

[Thomas D. (currently busy elsewhere; needinfo?me)]

(In reply to Jim Porter (:squib) from comment #9)
> Taking this, since I inadvertently fixed it as part of another bug.

If I read Bug 526998 Comment 13 correctly, the other bug is bug 526998, which is ready to land.

Comment 11

[Jim Porter (:squib)]

Fixed by bug 526998.