Closed Bug 758527 Opened 12 years ago Closed 10 years ago

Creating a new irc account doesn't bring it online

Categories

(Thunderbird :: Instant Messaging, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Usul, Unassigned)

References

Details

STR
New profile
Add an IRC account
I'm told I'm available but I can't join chatrooms and I'm told I'm not connected
I see 
Timestamp: 5/25/2012 12:25:57 AM
Error: [Exception... "'TypeError: this._proxyCancel is null' when calling method: [prplIAccount::disconnect]"  nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)"  location: "JS frame :: resource:///components/imAccounts.js :: <TOP_LEVEL> :: line 635"  data: no]
Source File: resource:///components/imAccounts.js
Line: 635

In the error console
(In reply to Ludovic Hirlimann [:Usul] from comment #0)
> STR
> New profile
> Add an IRC account
> I'm told I'm available but I can't join chatrooms and I'm told I'm not
> connected

So, I don't know why your account isn't connected (was there an error message displayed in the "Show Accounts" dialog?), but:

> 'TypeError: this._proxyCancel is null'

I debugged this error yesterday.
The check-in I'll port to comm-central: https://hg.instantbird.org/instantbird/rev/a6b5bedeef6d
The Instantbird bug: https://bugzilla.instantbird.org/show_bug.cgi?id=1464
This is a work-around for a necko bug, which I also filed: bug 758219

> Error: [Exception [...] when calling method: [prplIAccount::disconnect]
> Source File: resource:///components/imAccounts.js
> Line: 635

Calling disconnect immediately after creating an account is another issue that I debugged yesterday:
Check-in I'll port: https://hg.instantbird.org/instantbird/rev/53db88041a77
Instantbird bug: https://bugzilla.instantbird.org/show_bug.cgi?id=1465

To hit this, I assume you have used non-default settings for your IRC account.
If you used SSL, you can possibly have hit https://bugzilla.instantbird.org/show_bug.cgi?id=1455 (I'll also port this work-around to comm-central very soon; the real cause is bug 711786, another necko bug).
If you used freenode over SSL, you likely hit https://bugzilla.instantbird.org/show_bug.cgi?id=1292 for which I don't have any good solution at this point.
Of course I've enabled SSL :-) And I was trying mozilla.org's servers.

Can we set some dependencies I'll re-test when you have landed all your possible solutions.
(In reply to Florian Quèze from comment #1)

> > 'TypeError: this._proxyCancel is null'
> 
> I debugged this error yesterday.
> The check-in I'll port to comm-central:
> https://hg.instantbird.org/instantbird/rev/a6b5bedeef6d
> The Instantbird bug: https://bugzilla.instantbird.org/show_bug.cgi?id=1464
> This is a work-around for a necko bug, which I also filed: bug 758219

http://hg.mozilla.org/comm-central/rev/8170fae457fd

> > Error: [Exception [...] when calling method: [prplIAccount::disconnect]
> > Source File: resource:///components/imAccounts.js
> > Line: 635
> 
> Calling disconnect immediately after creating an account is another issue
> that I debugged yesterday:
> Check-in I'll port: https://hg.instantbird.org/instantbird/rev/53db88041a77
> Instantbird bug: https://bugzilla.instantbird.org/show_bug.cgi?id=1465

http://hg.mozilla.org/comm-central/rev/654ab8135717

> If you used SSL, you can possibly have hit
> https://bugzilla.instantbird.org/show_bug.cgi?id=1455 (I'll also port this
> work-around to comm-central very soon; the real cause is bug 711786, another
> necko bug).

http://hg.mozilla.org/comm-central/rev/017bc6894e0c
Depends on: 753807
(In reply to Ludovic Hirlimann [:Usul] (away until August 5th) from comment #2)

> Can we set some dependencies I'll re-test when you have landed all your
> possible solutions.

I think all the "possible solutions" have landed, so please re-test and resolve if it's appropriate :).
Is this still an issue or has this been fixed?
As far as we know this should work fine. Please reopen this if it doesn't.
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.