Upon restart after update, Thunderbird doesn't open previously opened attachments in tabs. error "the address wasn't understood"
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: bug-str, Unassigned)
References
Details
(Whiteboard: [closeme 2023-12-15])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0
Steps to reproduce:
Observed on multiple versions for many months (and several years).
The latest version: 102.9.0 (64 bit) on Windows 10.
Have an attachment(s) (PDF file(s)) from e-mail message(s).
When the update asks to restart Thunderbird, confirm.
(That prompt to restart promises to restore all the opened messages.)
Upon restart, the tabs are open, but they are empty: no [PDF] attachments within those tabs.
Actual results:
Previously opened (PDF) attachments are not opened.
I suspect the reason is that the temporary files for the attachments are deleted upon Thunderbird restart.
Expected results:
The attachments should be opened (maybe cached for that before the restart?).
Comment 1•2 years ago
|
||
Thanks Igor, that's odd although not terrible ;-)
We won't fix that for 102. Fixing this for 115 will probably depend on bug 1824593.
Just in case, here are the relevant records from the Error Console (v.102.12.0):
Warning: Invalid absolute docBaseUrl: "imap://imap.gmail.com:993/fetch%3EUID%3E/INBOX%3E****?part=1.2&filename=CAO-22%20General%20Field%20Trip%20Guidelines%20SY23.pdf&type=application/pdf". pdf.worker.js:1121:13
Warning: Indexing all PDF objects pdf.worker.js:1121:13
Invalid or corrupted PDF file.
PDF.js v2.15.305 (build: 2a386eff9)
Message: Invalid PDF structure. viewer.js:1197:15
Uncaught (in promise)
Object { message: "Invalid PDF structure.", name: "InvalidPDFException", stack: "BaseExceptionClosure@resource://pdf.js/build/pdf.js:538:29\n__webpack_modules__<@resource://pdf.js/build/pdf.js:541:2\n__w_pdfjs_require__@resource://pdf.js/build/pdf.js:16061:41\n@resource://pdf.js/build/pdf.js:16306:32\n@resource://pdf.js/build/pdf.js:16331:3\n@resource://pdf.js/build/pdf.js:16334:12\nwebpackUniversalModuleDefinition@resource://pdf.js/build/pdf.js:31:50\n@resource://pdf.js/build/pdf.js:32:3\n" }
**** is an obfuscation
Comment 3•1 year ago
|
||
Igor do you still experience this in version 115?
I just tested this while updating to 115.5.1 (64-bit) on Win-10 (and then once again - with this newest version).
The PDF from the attachment cannot be opened, but the error is different:
The address wasn’t understood
One of the following (imap) is not a registered protocol or is not allowed in this context.
You might need to install other software to open this address.
Here is what I see in the Error console:
16:55:23.791 services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource. Utils.sys.mjs:322
16:55:29.339
Assert failed: Calendar manager initialised calendars before loadCalendarComponent ran on the first 3pane window. This should not happen.
calUtils.jsm:130:15
16:55:31.244 Found 0 public keys and 0 secret keys (0 protected, 0 unprotected) RNPLib.jsm:551:15
16:55:32.039 Security Error: Content at about:neterror?e=unknownProtocolFound&u=imap%3A//%40imap.**.***%3A993/fetch%253EUID%253E/INBOX%253E71741%3Fpart%3D1.2%26filename%3DPSO%25208_30%2520Concert%2520Memo%2520December%25209th.docx.pdf%26type%3Dapplication/pdf&c=UTF-8&d=One%20of%20the%20following%20%28imap%29%20is%20not%20a%20registered%20protocol%20or%20is%20not%20allowed%20in%20this%20context. may not load or link to chrome://global/skin/icons/info.svg.
****** is an obfuscation for the user and domain names.
While only the last line is pertaining to the attachment (as far as I can tel), I am showing all entries in the Error console.
Error message upon the restart of Thunderbird with an attached PDF file opened in a tab. Overlaid is the pop-up with the Thunderbird version.
Updated•11 months ago
|
Comment 7•10 months ago
|
||
Do you mean bug 1846054? Because that's the bug for that error message, and it should fix this bug.
Comment 8•10 months ago
|
||
(In reply to Geoff Lankow (:darktrojan) from comment #7)
Do you mean bug 1846054? Because that's the bug for that error message, and it should fix this bug.
Sort of :)
Description
•