Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#26408 - [xkeyboard-config] gnome-terminal is broken with 2.4.1-1
Attached to Project:
Arch Linux
Opened by Vasily Khoruzhick (anarsoul) - Wednesday, 12 October 2011, 08:42 GMT
Last edited by Jan de Groot (JGC) - Friday, 09 November 2012, 14:36 GMT
Opened by Vasily Khoruzhick (anarsoul) - Wednesday, 12 October 2011, 08:42 GMT
Last edited by Jan de Groot (JGC) - Friday, 09 November 2012, 14:36 GMT
|
DetailsDescription:
Makes gnome-terminal behave strangely, on F10 it opens context menu (one which appears on right mouse click), but F10 shortcut is disabled in gnome-terminal (and anyway, it opens another menu when F10 shortcut is enabled) Additional info: * package version(s) 2.4.1-1 * config and/or log files etc. Steps to reproduce: Launch gnome-terminal, disable F10 shortcut, press F10. |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 09 November 2012, 14:36 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in GNOME 3.6 and latest xkeyboard-config.
Friday, 09 November 2012, 14:36 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in GNOME 3.6 and latest xkeyboard-config.
This looks like fix:
http://cgit.freedesktop.org/xkeyboard-config/commit/?id=1d1338afa6aa555c5f6c83d07fceec43a4d87f0d
@Vasily please try it too.
FS#26414for Shift+Fn.Newest git version of xkeyboard-config has same issue.
I tested different older revisions and F10 seems to first break after this commit http://cgit.freedesktop.org/xkeyboard-config/commit/?id=062b5bfcc59f9f6e4e11ba394bbe459af2a07b7e
It's probably not the best solution, but as far as I can tell it's the only one around :p
Looks like fix was commited into xkeyboard-config.