When clicking on the 'chat' tabicon in the tabtoolbar the chat tab doesn't open anymore. The error message is: Timestamp: 25-4-2012 17:30:32 Error: Error: No such tab mode: chat Source File: resource:///modules/errUtils.js Line: 124 Also the chat account manager (via Tools/Chat Status/Show Accounts) no longer opens: Timestamp: 25-4-2012 17:32:13 Error: TypeError: chatHandler is undefined Source File: chrome://messenger/content/messenger.xul Line: 1 This is happening since a number of builds, about 2 weeks ago. Tested with all extensions and themes disabled, it still gives these errors.
There's probably an error displayed way earlier (at the time the first Thunderbird window appears) from the file chat-messenger-overlay.js. It would be very helpful if you could find that error message and paste it.
Could this be the one? Timestamp: 26-4-2012 9:43:58 Error: TypeError: footer is null Source File: resource:///modules/LightweightThemeConsumer.jsm Line: 92
This one doesn't seem related to chat, it's in the code of Personas (or whatever that light weight theme feature is called these days).
(In reply to Alfred Kayser from comment #0) > When clicking on the 'chat' tabicon in the tabtoolbar the chat tab doesn't > open anymore. The error message is: > Timestamp: 25-4-2012 17:30:32 > Error: Error: No such tab mode: chat > Source File: resource:///modules/errUtils.js > Line: 124 I just experienced this, and the real cause was bug 754780 (and I had in my error console the errors mentioned at bug 754780 comment 0). If you are seeing that bug too, deleting global-messages-db.sqlite from your profile folder and restarting should make the issue disappear. > Also the chat account manager (via Tools/Chat Status/Show Accounts) no > longer opens: > Timestamp: 25-4-2012 17:32:13 > Error: TypeError: chatHandler is undefined > Source File: chrome://messenger/content/messenger.xul > Line: 1 I've never seen this error, so the problem you are/were seeing is likely slightly different from what I saw today.
I have done differnet tests on IM system on different Versions 24.3, 25beta to 28beta and 29a2 (earlybird) but never saw an error like the described. has someone seen this in the last year? of not, can we mark this as "WORKSFORME"
Seems like this was fixed in a different bug. Closing this as WFM. Please reopen / file a new bug if you're still seeing this issue.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.