Description of problem: Connecting with rdesktop to a Windows 7 box that has GoToMeeting running inside it with a remote participant's screen shared (or starting up GoToMeeting from within the rdesktop session) causes gnome-shell window management to hang. I cannot close the rdesktop window, and I sporadically cannot click on other widgets such as the clock/calendar, logout menu, or Activities. I am unable to enter overview mode with the keyboard Super key, and neither am I able to use Alt-Tab, Ctrl-Alt-Arrow keys to switch to a different application or desktop. The only thing I can do is go to another text VC with Ctrl-Alt-F3, log in, and killall rdesktop. Returning to the desktop then restores control. It seems like a focus grabbing problem, but I'm not sure, because sometimes I CAN click e.g. the clock/calendar widget, but still can't do any of the other actions. Typing Super-M sometimes allows me to be able to access the clock/calendar, but doesn't seem to unstick anything else. If I right-click the rdesktop icon in the top bar, a Quit menu appears, but clicking on it does nothing and does not even dismiss the menu. Then the menu gets stuck there. Version-Release number of selected component (if applicable): gnome-settings-daemon-3.16.3-1.fc22.x86_64 gnome-shell-3.16.4-1.fc22.x86_64 kernel-4.4.3-201.fc22.x86_64 mutter-3.16.4-1.fc22.x86_64 rdesktop-1.8.3-1.fc22.x86_64 xorg-x11-drv-ati-7.5.0-3.fc22.x86_64 How reproducible: Every week for the last 2 or 3 weeks when I have a GoToMeeting :-) Steps to Reproduce: 1. rdesktop windows7.box 2. Start GoToMeeting 3. Maybe maximize GoToMeeting once a participant has shared their screen Actual results: As describe above Expected results: No hang Additional info: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550]
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.