Red Hat Bugzilla – Bug 194240
frame on new display causes loss of function
Last modified: 2008-05-06 11:59:17 EDT
After opening a frame on a new display in order to collaborate on a file which
was being edited, I no longer had control of my own frame. Keyboard entry is
ignored, I can get at the GTK menus although they seem to do nothing useful.
Clicking the 'close' button in the window manager doesn't even work.
Not even scrolling up and down in the file works -- although thankfully resizing
the window does work, so at least I can _see_ the text he's added to my file :)
When I click on a GTK menu and my opponent uses cursor keys, both he and I get
confused as his cursor key movement moves around the menus on my screen which he
Multi-player emacs used to be _much_ more useful than this.
(In reply to comment #0)
> After opening a frame on a new display in order to collaborate on a file which
> was being edited, I no longer had control of my own frame. Keyboard entry is
> ignored, I can get at the GTK menus although they seem to do nothing useful.
> Clicking the 'close' button in the window manager doesn't even work.
Were you both running FC5?
I'll try to reproduce as soon as I get my FC5 laptop back from IBM warranty
Yeah. The machine on which emacs was running was FC5/i386; the remote X server
(In reply to comment #2)
> Yeah. The machine on which emacs was running was FC5/i386; the remote X server
> was FC6/x86_64.
Have you tried it with the remote display on RHEL4 or FC5?
Sorry, that was a typo. The remote display was FC5.
(In reply to comment #4)
> Sorry, that was a typo. The remote display was FC5.
With an FC5 emacs (21.4-15) and a RHEL-4 display, everything works fine. I'll
try swapping roles.
RHEL-4 emacs on FC-5 display also works. Now I need to scrounge up another FC-5
box try FC-5 emacs on FC-5 display.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.