In OpenSUSE 13.2 x64, I normally configure F9 to run the normal update check. Under Software Updater Settings I set the keyboard shortcut to F9 for the updater. When I then press F9, the menu is triggered. I tried switching to another key shortcut, F10, and the same thing happened.
Which menu is triggered?
And what Desktop Environment are you using? It sounds like KDE, and I suppose you mean the sofware updater in the system tray, right?
I just tried that, and it seems to work fine here.
After setting the shortcut ‘F9’, now when I press ‘F9’ the software updater pops up.
Sorry it took a while to respond. I tried it again and the menu is triggered. I am using KDE and using the x64 bit version of OpenSUSE 13.2, I should point out that my system is rather old (~5 years). Could there be hardware issues causing this problem?
If I am not mistaken, I think wolfi asked:
What a fool I am sometimes! I forgot to include that it is the Start Menu that is triggered.
Well, and what happens if you do not assign F9 or F10 to the software updater?
Is the Start Menu triggered then as well?
Can you use the other F-Keys?
If your keyboard has a Fn key, try to press that first or in combination with F9 or F10.
What does the “Shortcuts” configuration window say when you assign F9 or F10, does it recognize the keys correctly?
Does changing the keyboard layout make any difference?
And run “xev” in a terminal window, press F9 and/or F10 and post the output, please.
Ok, same thing happens when I change keyboard layout from the default generic 104 key to a specific Lenovo family of keyboards. The output from xev (when the F9 key is assigned to the updater and pressed) is as follows (the F10 key when no longer assigned to the updater does nothing, as I would expect. The last part is me closing the start menu with the mouse so that I can copy and paste the xev text.
Outer window is 0x2e00001, inner window is 0x2e00002
PropertyNotify event, serial 8, synthetic NO, window 0x2e00001,
atom 0x27 (WM_NAME), time 22759634, state PropertyNewValue
PropertyNotify event, serial 9, synthetic NO, window 0x2e00001,
atom 0x22 (WM_COMMAND), time 22759634, state PropertyNewValue
PropertyNotify event, serial 10, synthetic NO, window 0x2e00001,
atom 0x28 (WM_NORMAL_HINTS), time 22759634, state PropertyNewValue
CreateNotify event, serial 11, synthetic NO, window 0x2e00001,
parent 0x2e00001, window 0x2e00002, (10,10), width 50, height 50
border_width 4, override NO
PropertyNotify event, serial 12, synthetic NO, window 0x2e00001,
atom 0x21d (_KDE_NET_WM_USER_CREATION_TIME), time 22759634, state PropertyNewValue
PropertyNotify event, serial 14, synthetic NO, window 0x2e00001,
atom 0x13c (WM_PROTOCOLS), time 22759634, state PropertyNewValue
MapNotify event, serial 15, synthetic NO, window 0x2e00001,
event 0x2e00001, window 0x2e00002, override NO
ConfigureNotify event, serial 22, synthetic NO, window 0x2e00001,
event 0x2e00001, window 0x2e00001, (0,0), width 178, height 178,
border_width 0, above 0x2c00012, override NO
ReparentNotify event, serial 22, synthetic NO, window 0x2e00001,
event 0x2e00001, window 0x2e00001, parent 0x1eb6568,
(0,0), override NO
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x165 (_NET_WM_STATE), time 22759636, state PropertyNewValue
MapNotify event, serial 22, synthetic NO, window 0x2e00001,
event 0x2e00001, window 0x2e00001, override NO
VisibilityNotify event, serial 22, synthetic NO, window 0x2e00001,
state VisibilityPartiallyObscured
Expose event, serial 22, synthetic NO, window 0x2e00001,
(0,0), width 1, height 1, count 0
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x143 (WM_STATE), time 22759636, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x215 (_KDE_NET_WM_ACTIVITIES), time 22759636, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x165 (_NET_WM_STATE), time 22759637, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x1f8 (_NET_WM_DESKTOP), time 22759637, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x200 (_NET_FRAME_EXTENTS), time 22759639, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x181 (_KDE_NET_WM_FRAME_STRUT), time 22759639, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x1fe (_NET_WM_ALLOWED_ACTIONS), time 22759639, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x165 (_NET_WM_STATE), time 22759639, state PropertyNewValue
FocusIn event, serial 22, synthetic NO, window 0x2e00001,
mode NotifyNormal, detail NotifyNonlinear
KeymapNotify event, serial 22, synthetic NO, window 0x0,
keys: 0 0 0 0 16 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
VisibilityNotify event, serial 22, synthetic NO, window 0x2e00001,
state VisibilityUnobscured
Expose event, serial 22, synthetic NO, window 0x2e00001,
(1,0), width 177, height 1, count 4
Expose event, serial 22, synthetic NO, window 0x2e00001,
(0,1), width 178, height 9, count 3
Expose event, serial 22, synthetic NO, window 0x2e00001,
(0,10), width 10, height 58, count 2
Expose event, serial 22, synthetic NO, window 0x2e00001,
(68,10), width 110, height 58, count 1
Expose event, serial 22, synthetic NO, window 0x2e00001,
(0,68), width 178, height 110, count 0
ConfigureNotify event, serial 22, synthetic YES, window 0x2e00001,
event 0x2e00001, window 0x2e00001, (853,23), width 178, height 178,
border_width 0, above 0x0, override NO
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x215 (_KDE_NET_WM_ACTIVITIES), time 22759639, state PropertyNewValue
PropertyNotify event, serial 22, synthetic NO, window 0x2e00001,
atom 0x165 (_NET_WM_STATE), time 22759639, state PropertyNewValue
KeyRelease event, serial 36, synthetic NO, window 0x2e00001,
root 0x7e, subw 0x0, time 22759690, (-789,549), root:(64,572),
state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
" XLookupString gives 1 bytes: (0d) "
XFilterEvent returns: False
PropertyNotify event, serial 39, synthetic NO, window 0x2e00001,
atom 0x1fb (_NET_WM_ICON_GEOMETRY), time 22759928, state PropertyNewValue
PropertyNotify event, serial 40, synthetic NO, window 0x2e00001,
atom 0x1fb (_NET_WM_ICON_GEOMETRY), time 22759930, state PropertyNewValue
FocusOut event, serial 40, synthetic NO, window 0x2e00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 40, synthetic NO, window 0x2e00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 21 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
FocusOut event, serial 40, synthetic NO, window 0x2e00001,
mode NotifyNormal, detail NotifyNonlinear
FocusIn event, serial 40, synthetic NO, window 0x2e00001,
mode NotifyNormal, detail NotifyNonlinear
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
FocusOut event, serial 40, synthetic NO, window 0x2e00001,
mode NotifyNormal, detail NotifyNonlinear
And what if you choose a different keyboard layout in YaST->Hardware->System Keyboard Layout and try as a new user?
The output from xev (when the F9 key is assigned to the updater and pressed) is as follows (the F10 key when no longer assigned to the updater does nothing, as I would expect. The last part is me closing the start menu with the mouse so that I can copy and paste the xev text.
…
KeyRelease event, serial 36, synthetic NO, window 0x2e00001,
root 0x7e, subw 0x0, time 22759690, (-789,549), root:(64,572),
state 0x0, keycode 36 (keysym 0xff0d, Return), same_screen YES,
" XLookupString gives 1 bytes: (0d) "
XFilterEvent returns: False
…
This is the only relevant thing I see in there.
Did you press/release the return key?
Does the same appear when you press F10 (without having it assigned to anything)?
As I said, I cannot reproduce that here, everything’s working as expected.
And I have no idea what could cause something like this at the moment…
I have no clue what could be causing this to happen either. Having said that, if it works fine on your system, there must be something intrinsically problematic with my system. I know certain Linux distributions have trouble running off of this particular version of the system BIOS. It’s old and will eventually get replaced. Thanks for your help.