Closed Bug 1778048 Opened 1 month ago Closed 25 days ago

After upgrading to 102, signing with S/MIME sometimes fails [and problems with NNTP and Reply-all]

Categories

(MailNews Core :: Security: S/MIME, defect, P2)

Thunderbird 102

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1745033

People

(Reporter: reinfried.o.peter, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

4.78 KB, text/plain
Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0

Steps to reproduce:

Upgrade to TB 102 on macOS

Actual results:

Sometimes signing with S/MIME does not work, after restart it works for the same email for some time then stops working again.

Error loading NNTP articles from server.

If I choose "answer to all" CCs are not included

Expected results:

All my emails should be signed with S/MIME

New NNTP articles should be displayed/fetched

CC should be included if I choose "answer to all"

Blocks: tb102found
See Also: → 1777683

(In reply to Pepe from comment #0)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Firefox/102.0

Hey Pepe, thanks.
Unfortunately, we will be unable to act on your report as it covers multiple issues, and lacks proper steps to reproduce (STR), numbered instructions to us what exactly we need to do in TB to see your problem. It's a big app ;-)
Would you mind doing the following?

  • add proper STR for the s/Mime issue on this bug, then we'll morph it.
  • file NNTP issue as a separate bug with steps with details about the error - anything in error console (Cmd+Shift+J)?

Reply-all issue is tracked in bug 1777683.

Upgrade to TB 102 on macOS

Which version did you upgrade from, and how old is your profile?

Severity: -- → S2
Component: Untriaged → Security: S/MIME
Priority: -- → P2
Product: Thunderbird → MailNews Core
Summary: After upgrading to 102 there are problems with S/MIME, NNTP and Replies → After upgrading to 102 there are problems with S/MIME [and NNTP and Reply-all]
Summary: After upgrading to 102 there are problems with S/MIME [and NNTP and Reply-all] → After upgrading to 102, signing with S/MIME sometimes fails [and problems with NNTP and Reply-all]

The version I was upgrading from was 91.x and my profile is quite old, because I'm using TB for many, many years.

STR:

S/MIME:
I start TB, try to reply to an email or open a new email and when I try to send it, there come up 2 windows:
"Nachricht wird erstellt" that doesn't close or finish. If I close it, I can see a second window: "Senden der Nachricht fehlgeschlagen.
Kann Nachricht nicht signieren. Bitte überprüfen Sie, ob die Zertifikate, die für dieses Konto in den Konten-Einstellungen angegeben sind, für E-Mail gültig und vertrauenswürdig sind."
I close the window and restart TB and try to send the same email again and it works and I can send some emails and then after some time the 2 windows show up again.

Reply to all:
In the message window the CC-Line is empty

NNTP:
If I try to open a newsgroup nothing happens. If I open the window to subscribe new groups or to update the list, I see "Fehler beim Abruf der Nachrichten vom Server"

Attached file error console
Error Console: (NNTP)
TypeError: server.wrappedJSObject is undefined

Pepe, the regression in 102 with inability to send S/MIME is confirmed, we're working on a fix, please see bug 1777336 comment 43 for instructions how to work around it, until we're releasing a fixed update.

(In reply to Pepe from comment #3)

Error Console: (NNTP)
TypeError: server.wrappedJSObject is undefined

Looks the same as bug 1745033 to me. Glad to see I'm not the only one with that problem.

See Also: → 1745033

Duping. This seems a mix of bug 1745033 and 1777336.

Status: UNCONFIRMED → RESOLVED
Closed: 25 days ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1745033
You need to log in before you can comment on or make changes to this bug.