Closed
Bug 747874
Opened 12 years ago
Closed 10 years ago
My error console has started showing an error in imIncomingServer.js
Categories
(Thunderbird :: Instant Messaging, defect)
Thunderbird
Instant Messaging
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: unicorn.consulting, Unassigned)
References
Details
Timestamp: 23/04/2012 7:40:26 PM Error: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: resource:///components/imIncomingServer.js :: <TOP_LEVEL> :: line 175" data: no] Source File: resource:///components/imIncomingServer.js Line: 175 The line in question is get username() this._prefBranch.getCharPref("userName"), Filing in Im as the comments in the Set that follows the get indicate it is an IM function. set username(aUsername) { if (!aUsername) { // nsMsgAccountManager::GetIncomingServer expects the pref to // be named userName but some early test versions with IM had // the pref named username. return; } this._prefBranch.setCharPref("userName", aUsername); },
Comment 1•12 years ago
|
||
Duplicate of bug 747741, but as this has slightly more info I'll dupe it forward.
Updated•12 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Comment 4•12 years ago
|
||
From bug 758152: "I would expect this error to only exist on profiles with IM accounts created before the fix for bug 736434 landed, does this match what you observed?" So recreating my account fixed it at least for me. Is this acceptable as a workaround or is that bug expected to be fixed?
Comment 5•12 years ago
|
||
(In reply to Wolfgang Rosenauer [:wolfiR] from comment #4) > From bug 758152: > "I would expect this error to only exist on profiles with IM accounts > created before the fix for bug 736434 landed, does this match what you > observed?" > > So recreating my account fixed it at least for me. Thanks for the confirmation. > Is this acceptable as a workaround or is that bug expected to be fixed? I'm not sure (I don't really know how many people are affected by this issue), and there were more pressing chat related issues to fix, so I must admit I may not have given this bug all the attention it deserved.
So is it enough to manually rename the pref in pref.js from .username to .userName? So this only affects users that tried the experimental versions of IM before it got officially exposed in TB15?
Comment 7•12 years ago
|
||
(In reply to :aceman from comment #6) > So is it enough to manually rename the pref in pref.js from .username to > .userName? It should, yes. > So this only affects users that tried the experimental versions of IM before > it got officially exposed in TB15? It affects users who created IM accounts on Daily between the 2012-03-12 and the 2012-03-23 builds, and people who created IM accounts on Earlybird between the 2012-03-13 and the 2012-04-02 builds.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•