dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #10061
[Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
14:04. Unity hotkeys (cmd+a/f/m/c/v) still doesn't work in non-latin
layout.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1226962
Title:
Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Status in LibreOffice Productivity Suite:
Confirmed
Status in IBus:
New
Status in Indicator keyboard:
Fix Released
Status in Inkscape: A Vector Drawing Tool:
New
Status in Mutter:
Fix Released
Status in The OpenOffice.org Suite:
New
Status in Unity:
Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
In Progress
Status in “indicator-keyboard” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Status in “unity-settings-daemon” package in Ubuntu:
Fix Released
Status in “gnome-settings-daemon” package in Fedora:
Unknown
Bug description:
New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout.
Hotkeys with F1-12, numbers and other non-character buttons works perfectly.
Window manager hotkeys not affected by this bug. All hotkeys in system
parameters->keyboard->hotkeys->windows works perfect with any keyboard
layout.
Workaround for some system hotkeys and two layouts (english and non-
latin): rebind all hotkeys in your local layout. For example instead
of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
english layout. If you use english and two different non-latin
layouts this workaround helps only with one of them.
----------
For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322.
----------
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions