Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
GIMP
GIMP
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,753
    • Issues 2,753
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 35
    • Merge Requests 35
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GIMPGIMP
  • Issues
  • #1603

Closed
Open
Opened Jun 09, 2018 by ShiroYuki_Mot@ShiroYuki_Mot

GIMP 2.10.2 Windows x86 Only, Keyboards Key Binding Error

GIMP version: GIMP 2.10 2

Operating System: MS Windows 10 version 1803 x86 Only!

Package: Official Installer from gimp.org (gimp-2.10.2-setup.exe) + change DLLs (#1516 (closed))

Description of the bug

I do not know whether it is environment dependent or locale dependent,
On Windows x86 only, keyboard binding is out of order.
In the Japanese environment, if you type the ascii character, the correct one will not call back.
I think that it is probably a trouble with GLib. I am not familiar with this, so I do not know the details ...

Currently, I am taking measures by starting Japanese IME and entering characters.
Originally, this is unnecessary for ascii input, but I can type letters correctly.
It is impossible for keyboard shortcut by this solution, so now, I open the history or I use menu items.

PS; Not only me, Another Japanese user reported me that a same situation is occurring (on my blog's comments).
He(/She?) is taking measures by adding the US keyboard driver.
Yes. Of course, it is not necessary to add such a driver, usually.

Is the bug reproducible? Always

Additional information

Screen shot
Gitlab_KeyBinding_WinOnlyX86

Edited Jun 09, 2018 by ShiroYuki_Mot
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gimp#1603