Closed
Bug 1912244
Opened 2 years ago
Closed 2 years ago
Segmentation fault when verifying identity in an encrypted chat (OTR)
Categories
(Thunderbird :: Instant Messaging, defect)
Tracking
(thunderbird_esr128 affected)
RESOLVED
DUPLICATE
of bug 1895737
| Tracking | Status | |
|---|---|---|
| thunderbird_esr128 | --- | affected |
People
(Reporter: rautyrauty, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0
Steps to reproduce:
- Log in to an existing account
- Go to the Chat (Ctrl+5) -> Start -> Select the protocol for the IRC account -> Next -> You do not need to enter the password -> Next -> Enter an alias -> Next -> Done
- Add Contact -> Enter the username (for example, of a second machine) -> Start a conversation -> Go to the encryption status and select Start an encrypted conversation
- Enter a question and answer in the identity confirmation window
- On the second machine, in the confirmation request notification that appears, click Confirm and enter the previously specified response
Actual results:
On the first machine thunderbird crashes with a segmentation fault.
Expected results:
A message about the successful confirmation of the identity of the second contact appeared on the first machine. The encryption status has changed to Confidential.
The bug is not reproducible on 115.9.0
| Reporter | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Blocks: tb128found
Comment 2•2 years ago
|
||
Maybe the same as bug 1895737?
Comment 3•2 years ago
|
||
Sounds likely.
Keywords: regression
Summary: Segmentation fault when verifying identity in an encrypted chat → Segmentation fault when verifying identity in an encrypted chat (OTR)
| Reporter | ||
Comment 4•2 years ago
|
||
Yes, probably the same. If 1895737 bug gets fixed, but this doesn't, I'll reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1895737
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•