Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: alt+f2 or ctrl+alt+f* keys not working

  1. #1

    Default alt+f2 or ctrl+alt+f* keys not working

    Hi all

    I've got the latest everything on OpenSuse, been away so haven't used it since i updated it

    On today and I noticed straightaway that alt+f2 isn't working, when i try to alt+f10 i notice that nothing attached to these f keys are working

    Has anyone seen this as well?

  2. #2

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Works fine here: Alt+F2 opens krunner, Ctrl+Alt+F2 switches to VT2.

    I suppose you mean switching between the VTs with Ctrl+Alt+Fn doesn't work.
    When did you do the last update?
    I have seen this before under certain circumstances, but the plymouth update released last Monday should fix that.

    Or do your F-Keys not work at all?

  3. #3

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    last update was on starting up today

    reckon the F keys mightn't work at all, just tried refreshing with F5 and nothing

  4. #4

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Try running "xev" in a terminal window, do you get any output when you press a function key?

    Maybe a hardware issue?
    Or some keyboards have a "Fn" key which you have to press to activate the function keys...

  5. #5

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    I get output but a bit dodgy, pressing 'e' then 'f1' in the snippet below, is the lookupstring relevant?

    Code:
    KeyRelease event, serial 42, synthetic NO, window 0x4200001,    root 0x291, subw 0x0, time 3504193, (595,866), root:(600,892),
        state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
        XLookupString gives 1 bytes: (65) "e"
        XFilterEvent returns: False
    
    
    KeyPress event, serial 42, synthetic NO, window 0x4200001,
        root 0x291, subw 0x0, time 3506233, (592,866), root:(597,892),
        state 0x10, keycode 146 (keysym 0xff6a, Help), same_screen YES,
        XLookupString gives 0 bytes: 
        XmbLookupString gives 0 bytes: 
        XFilterEvent returns: False
    edit: yeah it's always worked with this keyboard though unless an update killed it, it's some microsoft keyboard with the kinda multimedia keys no one ever uses but the basic stuff has always been fine

  6. #6

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Quote Originally Posted by TheBloodyNine View Post
    I get output but a bit dodgy, pressing 'e' then 'f1' in the snippet below, is the lookupstring relevant?

    Code:
    KeyRelease event, serial 42, synthetic NO, window 0x4200001,    root 0x291, subw 0x0, time 3504193, (595,866), root:(600,892),
        state 0x10, keycode 26 (keysym 0x65, e), same_screen YES,
        XLookupString gives 1 bytes: (65) "e"
        XFilterEvent returns: False
    
    
    KeyPress event, serial 42, synthetic NO, window 0x4200001,
        root 0x291, subw 0x0, time 3506233, (592,866), root:(597,892),
        state 0x10, keycode 146 (keysym 0xff6a, Help), same_screen YES,
        XLookupString gives 0 bytes: 
        XmbLookupString gives 0 bytes: 
        XFilterEvent returns: False
    edit: yeah it's always worked with this keyboard though unless an update killed it, it's some microsoft keyboard with the kinda multimedia keys no one ever uses but the basic stuff has always been fine
    So it's recognized as "Help" key instead of F10.
    Especially with Microsoft keyboards I have seen the Fn key which you have to press to switch the F-Keys to their F-function.
    Look for a key labelled "Fn" and press it, your F-keys should then be recognized as F1-F12 (maybe a LED on the keyboard will switch on or off then like for Caps-Lock).

  7. #7

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Sorry, the key is called "F-Lock".
    See also: F-Lock - Wikipedia, the free encyclopedia

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Did I miss something. On what openSUSE version and what desktop environment are the posts i n this discussion based?
    Henk van Velden

  9. #9

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Quote Originally Posted by hcvv View Post
    Did I miss something. On what openSUSE version and what desktop environment are the posts i n this discussion based?
    Well, if it is indeed because of the F-Lock key (and I really think so because his F1 key is recognized as Help), it doesn't matter and would be the same in any operating system and DE (even on the BIOS screen)

    But at least he did say:
    Quote Originally Posted by TheBloodyNine View Post
    I've got the latest everything on OpenSuse
    Although that's not very concrete...

  10. #10
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: alt+f2 or ctrl+alt+f* keys not working

    Quote Originally Posted by wolfi323 View Post
    But at least he did say:

    Although that's not very concrete...
    got the latest everything on OpenSuse
    It indeed isn't concrete. Some people could argue that this means 13.1 MS3 at this moment in time.
    In any case this is a very bewildering remark for somebody reading this, say, next year.

    I always wonder why people take the trouble to type such useless expressions where the simple truth: 12.2 is much shorter, clearer and ready for the future.

    And even when the problem is independet from a desktop, the OP did not post he did this outside a desktop. And when he did it inside, he should have told us, All pieces of information that are obvious to provide help in a quick and correct bug resolving process.
    Henk van Velden

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •