Opening Attachment does not work if Thunderbird is executed as Remote App on Microsoft Remotedesktopserver
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: gm, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0
Steps to reproduce:
Thunderbird is started from another Remote-App on Microsoft Remote Desktop Server (Windows Server 2016). All was working fine till update to 68.4.1.
Opening an Attachment (as an example an xlsx-File from Excel) now cannot start directly the assigned application anymore (for example LibreOffice Calc).
Actual results:
Opening an xlsx-Attachment first starts dialog, what to do with it, suggests opening wirh LibreOffice Calc (as expected so far), but when I confirm the start another Dialog starts "Dieser Link muss mit einer Anwendung gestartet werden" (This link has to be opened with an application) and shows sent to file as only option first, alternatively I can open a search dialog from a button.
The search I does not offer applications but I can navigate through file system to scalc.exe and start with it.
Then there is an option to save this setting for all file-links, but I didn't check it.
I fear this setting then saved for all attachments no matter what type this actually would be.
The users working on the system reported, that nothing happened after confirming the "Start with"-dialog, i suspect they checked save on the second start dialog with the option "file" to get rid of this dialog.
Expected results:
After select "Open with: LibreOffice Calc" the Attachment should open in LibreOfficeCalc as did before
(I tested with portable Version 60.9.1 and it did again, so seems not to be a problem with Microsoft Updates, but with Thunderbird).
Hint: if Thunderbird is executed in a regular Remote Desktop Session, the problem does not occur even in version 68.4.1, only in context of a remote app.
|
||
Comment 1•5 years ago
|
||
I think this is a duplicate of bug 1602726.
|
||
Comment 3•4 years ago
|
||
Reporter, do you see this issue when using version 78?
Resolved per whiteboard
Hello, sorry for delay.
currently version 78.9.1 is used, since 68.4.2 the problem is not reported again.
Thank you very much
Description
•