Closed
Bug 360525
Opened 19 years ago
Closed 19 years ago
S/Mime LDAP cert fetching no longer works on trunk
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
MailNews Core
Security: S/MIME
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: KaiE, Assigned: KaiE)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
1.38 KB,
patch
|
mscott
:
review+
|
Details | Diff | Splinter Review |
When nsIEventQueueService was taken away (on trunk), nobody noticed that that our Mail Cert LDAP fetching relies on it.
It no longer works, when attempting to use it I get this error:
TypeError: Components.classes['@mozilla.org/event-queue-service;1'] has no properties exception creating ldap connection
The fix is to make use of the new thread manager, patch in hand.
| Assignee | ||
Updated•19 years ago
|
Keywords: regression
Priority: -- → P1
| Assignee | ||
Comment 1•19 years ago
|
||
Attachment #245428 -
Flags: review?(mscott)
| Assignee | ||
Updated•19 years ago
|
Version: 1.8 Branch → Trunk
Comment 2•19 years ago
|
||
Comment on attachment 245428 [details] [diff] [review]
Patch v1
Kai, thanks a lot for tracking this down!
Attachment #245428 -
Flags: review?(mscott) → review+
| Assignee | ||
Comment 3•19 years ago
|
||
fixed on trunk
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 4•19 years ago
|
||
It looks like it introduced a regression - I cannot sign any emails starting today.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061207 Thunderbird/3.0a1 ID:2006120703
| Assignee | ||
Comment 5•18 years ago
|
||
(In reply to comment #4)
> It looks like it introduced a regression - I cannot sign any emails starting
> today.
>
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061207
> Thunderbird/3.0a1 ID:2006120703
I can not confirm this issue.
Signing works fine for me using the latest nightly Thunderbird trunk build.
If you still see this problem, please file a new separate bug report.
Thanks.
Comment 6•18 years ago
|
||
It fixed by itself in the next build.
You need to log in
before you can comment on or make changes to this bug.
Description
•