After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 493361 - When Vim component has focus, main window does not receive keyboard events
When Vim component has focus, main window does not receive keyboard events
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2007-11-04 13:37 UTC by Ali Afshar
Modified: 2020-11-06 20:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ali Afshar 2007-11-04 13:37:57 UTC
Please describe the problem:
Using PIDA, which embeds Vim in a GTK Socket, when the Vim component has focus, keyboard shortcuts do not reach the main window. For example, ctrl-shift-t which opens a new terminal when vim component is focussed in every other window manager, does nothing in Metacity.



Steps to reproduce:



Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Havoc Pennington 2007-11-05 04:59:18 UTC
I'd encourage you to also debug this in the app; while it could be a metacity bug, I'm having a hard time imagining what the bug would be. It does not mean much that the bug happens with some window managers and not others. That could just mean the app has a race condition or otherwise relies on something about the WM that is not guaranteed by the specs, and metacity happens to trigger the app bug for some reason.

If nothing else, documenting exactly what happens in the app - which app windows have focus, which focus events arrive, and which keystrokes go to which windows - and how this is different under a non-metacity WM - would help a lot in tracking down any metacity issue.

The very simple thing to check first of course is that there's no metacity or gnome global keybinding set up for ctrl+shift+t - check that you can send that key sequence to "xev" - I'm sure this is obvious enough that it's not the problem, though.


Comment 2 Elijah Newren 2008-07-05 18:39:16 UTC
If I understand correctly, it looks like others discovered that this bug was not metacity specific, duplicating with both fvwm and fluxbox.  See http://groups.google.com/group/pida/browse_thread/thread/f2951a1dc7ac7bf8.

Ali: Am I reading that thread right?  Okay to mark this bug as notgnome?
Comment 3 Ali Afshar 2008-07-05 20:29:43 UTC
Elijah: Yes, you are correct, however it does work with the following window managers:

* xfce4/xfwm4
* kde/kwin

So I would hesitate to suggest that "even though the bug is also present in fluxbox, does not mean that it is not a bug in gnome". I suspect that Gnome/Metacity wants to be in the league of xfce4 and kde, rather than the league of fvwm and fluxbox.

Thanks for giving the bug your attention!
Comment 4 André Klapper 2020-11-06 20:06:35 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.