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 782451 - Some keyboard accelerators of the form "<alt>*" don't work
Some keyboard accelerators of the form "<alt>*" don't work
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-05-10 15:27 UTC by Casey Jao
Modified: 2018-05-22 17:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Casey Jao 2017-05-10 15:27:24 UTC
There is a weird problem with Evince's keybindings that seems to result from an underlying problem in GTK3. 

As set in ev-application.c, the key combinations "<alt>P" and "<alt>N" are assigned to the "win.go-back-history" and "win.go-forward-history" actions, respectively. It turns out that only "<alt>N" works. Swapping "<alt>P" and "<alt>N" in the program code lets me trigger "win.go-back-history" with <alt>N but breaks the shortcut for "win.go-forward-history". Having launched evince with --gtk-debug=keybindings, it appears that "<alt>P" is intercepted before reaching the main program as I see several "found exact match, keyval=112" messages. 

There seem to be general issues with key combinations of the form "<alt>*" which are not limited to Evince. If I switch some accelerators in gedit to "<alt>P" or "<alt>F" (for example, changing the find shortcut from <Control>F to <alt>F), they no longer work despite the fact that gtk_application_get_actions_for_accel reveals no conflicts. However "<alt>N" works fine.

The "<alt>P" and "<alt>N" shortcuts work fine in Evince 3.18 on Ubuntu 16.04. I first noticed the problems in Evince 3.22 and Evince 3.24 installed via flatpak. 

Any ideas for what might be happening?
Comment 1 Casey Jao 2017-07-22 02:51:11 UTC
Update: this GTK bug (https://bugzilla.gnome.org/show_bug.cgi?id=785236) appears to be the underlying cause.
Comment 2 GNOME Infrastructure Team 2018-05-22 17:08:46 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/779.