Keyboard shortcuts for selecting tools no longer functions

[Michael Healy]

I am using Linux Mint Maya. Normally I can type "S" for select or "M" for move and these shortcuts no longer work and I must use the mouse with the tool box. I tried reinstalling and to no avail. Restarted my linux desktop, nope! Just wanted to report this....

[Cameron White (cameronwhite91)]

There have been a few bug fixes recently for how keyboard shortcuts are handled. Could you try out a daily build and see if that fixes the issue - ppa:pinta-maintainers/pinta-daily ?

[Michael Healy (mehaul)]

On 12/26/2012 08:44 PM, Cameron White wrote:
> There have been a few bug fixes recently for how keyboard shortcuts are
> handled. Could you try out a daily build and see if that fixes the issue
> - ppa:pinta-maintainers/pinta-daily ?
>
Thank you I will try this and post the results.
michael

[Michael Healy (mehaul)]

On 12/27/2012 12:25 AM, mehaul wrote:
> On 12/26/2012 08:44 PM, Cameron White wrote:
>> There have been a few bug fixes recently for how keyboard shortcuts are
>> handled. Could you try out a daily build and see if that fixes the issue
>> - ppa:pinta-maintainers/pinta-daily ?
>>
> Thank you I will try this and post the results.
> michael
I tried updating the repository yet to no avail. I will just use the
mouse and tool box instead of the shortcuts for now. Pinta is still a
fine app and in a week or so I will try and solve the shortcut issue.
(As time to play permits) Thank you for your attention to this matter.
Happy New Year to you!

[Michael Healy (mehaul)]

On 12/27/2012 01:16 PM, mehaul wrote:
> On 12/27/2012 12:25 AM, mehaul wrote:
>> On 12/26/2012 08:44 PM, Cameron White wrote:
>>> There have been a few bug fixes recently for how keyboard shortcuts are
>>> handled. Could you try out a daily build and see if that fixes the
>>> issue
>>> - ppa:pinta-maintainers/pinta-daily ?
>>>
>> Thank you I will try this and post the results.
>> michael
> I tried updating the repository yet to no avail. I will just use the
> mouse and tool box instead of the shortcuts for now. Pinta is still a
> fine app and in a week or so I will try and solve the shortcut issue.
> (As time to play permits) Thank you for your attention to this matter.
> Happy New Year to you!
Dear Cameron White,
I played with this Pinta bug a little more and have to share with you my
results. I am almost embarrassed but I have to share just in case
someone else reports the same bug in the future. *I had the NUM LOCK
button on*. When I turned it off the keyboard shortcuts for Pinta work
perfectly.. Had to share and thank you for your software and attention
to the problems that all folks including dummies like me share with you.
Peace and Happy New Year!

michael

[grofaty (grofaty)]

Michael, turning on "Num Lock" key should not effect the shortcut keys, because shortcuts are not numbers. Are probably not using standard keyboard with personal computer, are you? Are you using some laptop with some special key to turn on Num Lock on standard alphabet keys? If yes, then we can mark this bug as Invalid.

[Michael Healy (mehaul)]

On 12/30/2012 01:17 AM, grofaty wrote:
> Michael, turning on "Num Lock" key should not effect the shortcut keys,
> because shortcuts are not numbers. Are probably not using standard
> keyboard with personal computer, are you? Are you using some laptop with
> some special key to turn on Num Lock on standard alphabet keys? If yes,
> then we can mark this bug as Invalid.
>
I am using a Toshiba Satellite 17" wide with regular keyboard. The NUM
lock affects general navigation behaviour when certain keys are pressed
such as paragraph dn, paragraph up ect. The only keys affected are the
number keys and not the letters. The letters S for selecting areas of a
picture in Pinta and M for moving are rendered useless when the Num lock
is on.

Hope this helps! Thank you again! Michael

[Cameron White (cameronwhite91)]

Could you run the 'xmodmap' command in a terminal and paste the output? I suspect that the code we use to filter out Num Lock, Caps Lock, and similar keys may not be working correctly for your system (see bug #633104)

[Michael Healy (mehaul)]

On 12/30/2012 02:46 PM, Cameron White wrote:
> Could you run the 'xmodmap' command in a terminal and paste the output?
> I suspect that the code we use to filter out Num Lock, Caps Lock, and
> similar keys may not be working correctly for your system (see bug
> #633104)
>
Here's what I got:

xmodmap
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):

shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)

Hope this helps!

michael

[grofaty (grofaty)]

On my laptop I have found out that having similar problem with "Num Lock" turned on. Actually I never use "Num Lock" on my laptop, so I haven't spoted this problem before. On my laptop if Num Lock is turned on then letter M is not working for example, but letter S works fine, this is somehow logical, because Num Lock on my laptop only influenches letters in first keyboard row from U to right, in middle row from J to right, in last third row from M to right.

I executed the xmodmap command:
===============
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):

shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
===============

I see Michael and I have the same output for Num_lock.

[Kosta Korenkov (7r0ggy)]

Just installed Pinta on Ubuntu 14.04 x64. Tools shortcuts are not working and this has nothing to do with NumLock. Any thoughts?

[pleabargain (dennisgdaniels)]

same: none of the shortcut keys are working

Title,Version,Path
AtkSharp,3.24.24.34,/snap/pinta/16/lib/pinta/AtkSharp.dll
CairoSharp,3.24.24.34,/snap/pinta/16/lib/pinta/CairoSharp.dll
Clipper,6.4.2.0,/snap/pinta/16/lib/pinta/Clipper.dll
GdkSharp,3.24.24.34,/snap/pinta/16/lib/pinta/GdkSharp.dll
GioSharp,3.24.24.34,/snap/pinta/16/lib/pinta/GioSharp.dll
GLibSharp,3.24.24.34,/snap/pinta/16/lib/pinta/GLibSharp.dll
GtkSharp,3.24.24.34,/snap/pinta/16/lib/pinta/GtkSharp.dll
netstandard,2.1.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/netstandard.dll
NGettext,0.6.1.0,/snap/pinta/16/lib/pinta/NGettext.dll
PangoSharp,3.24.24.34,/snap/pinta/16/lib/pinta/PangoSharp.dll
Pinta,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.dll
Pinta.Core,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Core.dll
Pinta.Docking,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Docking.dll
Pinta.Effects,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Effects.dll
Pinta.Gui.Widgets,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Gui.Widgets.dll
Pinta.Resources,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Resources.dll
Pinta.Tools,2.0.0.0,/snap/pinta/16/lib/pinta/Pinta.Tools.dll
System.Collections,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Collections.dll
System.Collections.Concurrent,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Collections.Concurrent.dll
System.Collections.Specialized,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Collections.Specialized.dll
System.ComponentModel,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.ComponentModel.dll
System.Console,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Console.dll
System.Diagnostics.DiagnosticSource,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Diagnostics.DiagnosticSource.dll
System.Diagnostics.Tracing,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Diagnostics.Tracing.dll
System.Linq,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Linq.dll
System.Memory,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Memory.dll
System.Net.Http,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Net.Http.dll
System.Net.Primitives,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Net.Primitives.dll
System.Net.Security,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Net.Security.dll
System.ObjectModel,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.ObjectModel.dll
System.Private.CoreLib,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Private.CoreLib.dll
System.Private.Uri,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Private.Uri.dll
System.Private.Xml,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Private.Xml.dll
System.Private.Xml.Linq,6.0.0.0,/snap/pinta/16/usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.1/System.Private.X...

[Cameron White (cameronwhite91)]

hmm, could you try running the 'xmodmap' command in the terminal (similar to the above comment), and also check if the Num Lock setting is related to the issue?

I'm wondering if this bug got reintroduced in Pinta 2.0 from https://github.com/PintaProject/Pinta/commit/478813d38db349a43417b9a155a0eea3fb0c3419 which started including the mod2 mask for macOS

[Cameron White (cameronwhite91)]

I've committed a fix for that since the mod2 key should only be involved on macOS
https://github.com/PintaProject/Pinta/releases/tag/dev-preview-builds has an updated build if you'd like to test it out (the ubuntu build there just requires having GTK libraries etc installed on the system, but is standalone otherwise)

[Cameron White (cameronwhite91)]

Tested on Ubuntu 18.04 with Pinta 2.0 and the issue could be reproduced with Num Lock enabled (and xmodmap indicates that mod2 was set to Num_Lock). The commit mentioned in comment #12 fixed it in my testing.