Menus do not work when connected via Remote Desktop
Categories
(Core :: Widget: Win32, defect, P3)
Tracking
()
People
(Reporter: fright-rusts4u, Unassigned)
Details
(Whiteboard: widget-next)
Updated•8 years ago
|
Updated•8 years ago
|
Comment 2•7 years ago
|
||
| Reporter | ||
Comment 5•7 years ago
|
||
Comment 7•7 years ago
|
||
Comment 8•7 years ago
|
||
Comment 10•7 years ago
|
||
Comment 11•7 years ago
|
||
Comment 12•7 years ago
|
||
Comment 13•7 years ago
|
||
Comment 14•7 years ago
|
||
Comment 15•7 years ago
|
||
Comment 16•7 years ago
|
||
Comment 17•7 years ago
|
||
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
Comment 20•6 years ago
|
||
Comment 21•6 years ago
|
||
Same here on Thunderbird 60.4.0 (32-bit) and Windows 7:
Thunderbird is either completly unresponsive or at least the main menus and context menu is not opening.
This happens if you access an already started Thunderbird over remote desktop.
Workaround:
- Kill Thunderbird process via task manager.
- Start Thunderbird again over remote desktop.
Comment 22•6 years ago
|
||
Thunderbird is also doing the same for my 40+ users on Server 2008 R2 (x64)... so now both Firefox and Thunderbird are having the issue. Thunderbird 60.3.1 (32-bit) and Firefox 61.0 (64-bit). Both have been upgraded several times since my first comment, 9 months ago. We use a variety of RDP clients... Linux, Wyse and Windows 7 & 10... does not seem to favor any one client.
This is now becoming MUCH more problematic as anytime this happens, one or more of the actual Firefox exe process begins to eat up RAM and CPU. When you have 40 users logged in simultaneously, it really plays hell on the system speed. I've killed single firefox.exe processes that reached over 4G in size (users typically have 6+ processes now since Firefox went to their "multiprocess" design).
9 months ago this was a Firefox only issue. Upgraded have apparently migrated the issue to Thunderbird. Normally this would be placed on the Thunderbird side but it looks like the exact same issue... same cause, same result, same workaround... probably a shared code base... best guess.
Comment 23•6 years ago
|
||
This problem was fixed in Thunderbird 65.0b1
Comment 24•6 years ago
|
||
Dear Alexander,
great that the bug has beeen fixed in Thunderbird.
Do you know when it will be fixed in Firefox?
Best regards,
James
Comment 25•6 years ago
|
||
James, I don't remember exactly. It was fixed in semtember-october 2018. Maybe in Firefox 62. But you can check it easy.
Comment 26•6 years ago
|
||
Dear Alexander,
thank you for the hint.
I did check the behaviour with Firefox 64 (64 Bit), the Bug seems to be fixed.
However the ESR-Release (60.4.0 64 Bit) seems still to be affected by this Bug.
Do you know if it will be fixed in ESR as well?
Best regards,
James
Comment 27•6 years ago
|
||
Hi all,
It seems this bug is still not fixed, and it got worse in the past weeks, not only on resolution change on the remote clients, but several times a day without even disconnecting the remote desktop apps.
Platform is win2008r2 both thunderbird and firefox-esr is affected, therefore it's in the core.
I've tried it with several different remote desktop clients also.
Please, if anyone have any idea how to debug it, I would be very grateful!
Thanks!
Updated•6 years ago
|
Comment 28•6 years ago
|
||
That problem was fixed in Thunderbird 60.6.0 !
Comment 29•6 years ago
|
||
Aaron, what system and version are you remoting into? And does it reproduce using version 68 or newer??
Comment 30•6 years ago
|
||
speedster, Server 2008 is very near EOL, and it seems like you have bigger issues than what this bug covers. Have you asked for help in support?
Comment 31•5 years ago
|
||
I stopped experiencing this problem, probably due to Firefox/Windows updates.
To provide a data point: Windows 10 -> Windows 10, Firefox 68.x ESR does not experience this problem.
Comment 32•5 years ago
|
||
Thanks for the updates
=> WFM
Description
•