openjdk team mailing list archive

[yh1000 <1226962@xxxxxxxxxxxxxxxxxx>]

​To all,​
The PPA + the  "restart unity-settings-daemon" did the trick for me.
(Hebrew)
Perfect.

Thanks

Yechiam



On Thu, May 22, 2014 at 11:04 PM, William Hua <1226962@xxxxxxxxxxxxxxxxxx>wrote:

> Hi Artur, I just tried PhpStorm with the PPA installed and it seems to
> work for me (tested ru and gr). What keyboard shortcuts are you trying?
> Also, can you try to "restart unity-settings-daemon" after installing
> the PPA to see if that helps?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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 Released
> Status in “gnome-settings-daemon” package in Ubuntu:
>   Triaged
> Status in “gnome-terminal” package in Ubuntu:
>   Triaged
> Status in “indicator-keyboard” package in Ubuntu:
>   Triaged
> Status in “openjdk-7” package in Ubuntu:
>   Triaged
> Status in “unity” package in Ubuntu:
>   Triaged
> Status in “unity-settings-daemon” package in Ubuntu:
>   Triaged
> Status in “gnome-settings-daemon” package in Fedora:
>   Unknown
> Status in “gnome-shell” 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.
>
>
>   Dear Ubuntu users and developers!
>   Please include the following information to your comment about non-latin
> shortcuts problems:
>   1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME,
> Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or
> clean installed
>   2. What keyboard layout do you have
>   3. What shortcut for keyboard layout switching do you use
>   4. On which session you have problems - that is one from Unity, GNOME
> Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback
> (Compiz)
>   5. With which program and its version and origin (Ubuntu repositories,
> PPA, non-deb binary package from some website) you have problems.
>
>   By providing this information you can make bug-fixing much simpler and
>   may be faster.
>
>   ----------
>   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
>

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-7 in Ubuntu.
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 Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” 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.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  ----------
  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