I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
poc
On Sat, 2023-04-01 at 18:10 +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Looking at a picture of the keyboard, it has keys in those positions. Does the keyboard produce anything else when they're pressed?
Looking in my Mate keyboard prefs, in the layout prefs, options button, there's a miscellaneous compatiblity option that mentions emulating those keys for Mac keyboards. I dunno how and where it does it, does it put them anywhere useful for you?
I purposely avoid keyboards with non-standard layouts for this kind of reason. Somebody doesn't know what some keys are for, decides they're not useful, and makes the keyboard terrible for actual computer users.
Let's remove the cursor arrow keys, something I use all the time, and make you have to use some weird keyboard combination to type them, instead. You can just hop back and forth between keyboard and mouse to put the cursor where you want it (also inconvenient, and not the only purpose for using the cursor keys). People who design these things should be horsewhipped, then strapped down in front of a linotype machine.
On Sun, 2023-04-02 at 03:03 +0930, Tim via users wrote:
On Sat, 2023-04-01 at 18:10 +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Looking at a picture of the keyboard, it has keys in those positions. Does the keyboard produce anything else when they're pressed?
xev shows events for most things. I'm not that concerned as I was mainly asking a rhetorical question about the configurability or otherwise of the SysRq key.
It turns out however that you can get the effect of SysRq by sending magic commands to /proc/sysrq-trigger:
https://ngelinux.com/what-is-proc-sysrq-trigger-in-linux-and-how-to-use-sysr...
Of course that's only possible if you have access to at least a basic shell, so probably not that useful if your DE has frozen.
poc
On 4/1/23 10:10, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Hi Patrick,
I've seen several things say the "Camera" key is the ScreenShot/PrintScreen key.
Alone is the whole screen, with CMD|alt gets the focused window.
On my generic <xev> says it is keycode 107, keysym 0xff61, "Print"
On Sat, 2023-04-01 at 12:37 -0700, Mike Wright wrote:
On 4/1/23 10:10, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Hi Patrick,
I've seen several things say the "Camera" key is the ScreenShot/PrintScreen key.
Alone is the whole screen, with CMD|alt gets the focused window.
On my generic <xev> says it is keycode 107, keysym 0xff61, "Print"
On mine (using KDE/Plasma) the "camera" key rather weirdly gets me a browser tab with a search for Ksnapshot. This happens even when I'm not focussed on the browser.
With CMD|Alt, nothing happens (the CMD|Alt on its own gives up/down events).
The "calculator" key fires up Kcalc :-)
poc
On Sat, 2023-04-01 at 21:11 -0400, Jonathan Billings wrote:
On Apr 1, 2023, at 13:11, Patrick O'Callaghan pocallaghan@gmail.com wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html#i-hit-sysrq-bu...
I hit SysRq, but nothing seems to happen, what’s wrong? There are some keyboards that produce a different keycode for SysRq than the pre-defined value of 99 (see KEY_SYSRQ in include/uapi/linux/input-event-codes.h), or which don’t have a SysRq key at all. In these cases, run showkey -s to find an appropriate scancode sequence, and use setkeycodes <sequence> 99to map this sequence to the usual SysRq code (e.g., setkeycodes e05b 99). It’s probably best to put this command in a boot script. Oh, and by the way, you exit showkey by not typing anything for ten seconds.
Thanks, that's useful.
[BTW, you forgot to include a text-only alternative in your reply - see the list guidelines.]
poc
On Sat, Apr 01, 2023 at 06:10:50PM +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Here's a very old kernel sources page that explains the sysrq routine, and I think it was one of the pages version that helped me a lot:
https://mirrors.edge.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Do...
Here, it seems, is the latest one: https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
HTH Wolfgang
On Sun, Apr 02, 2023 at 05:03:33PM +0200, Wolfgang Pfeiffer wrote:
On Sat, Apr 01, 2023 at 06:10:50PM +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
[ ... ]
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
Via Google:
" Where is print screen key on logitech mx keys?
On the Logitech MX Keys (PC layout), you can use the camera icon above the number pad to take a screen shot of all windows at once. If you press the "ALT" or "CMD|alt" + "camera icon" it will only capture the active window. "
Not being sure if it helps ..
Wolfgang
On Sun, 2023-04-02 at 17:20 +0200, Wolfgang Pfeiffer wrote:
On Sun, Apr 02, 2023 at 05:03:33PM +0200, Wolfgang Pfeiffer wrote:
On Sat, Apr 01, 2023 at 06:10:50PM +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
[ ... ]
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
Via Google:
" Where is print screen key on logitech mx keys?
On the Logitech MX Keys (PC layout), you can use the camera icon above the number pad to take a screen shot of all windows at once. If you press the "ALT" or "CMD|alt" + "camera icon" it will only capture the active window. "
Not being sure if it helps ..
As I said earlier, that doesn't help. It also doesn't actually work like that, at least on KDE/Plasma. Maybe on Gnome it does.
poc
On Sun, 2 Apr 2023 17:03:33 +0200 Wolfgang Pfeiffer roto@gmx.net wrote:
On Sat, Apr 01, 2023 at 06:10:50PM +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Here's a very old kernel sources page that explains the sysrq routine, and I think it was one of the pages version that helped me a lot:
https://mirrors.edge.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Do...
Here, it seems, is the latest one: https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
Thanks for posting these. I used a mnemonic to remember what to press, 'busier' in reverse, 'reisub'. But, after reading the documentation, I think I only need to press 'sub'. Unless there is a runaway process.
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
When I use xev, and press Print Screen, I get the following output, FocusOut event, serial 48, synthetic NO, window 0x7200001, mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 48, synthetic NO, window 0x7200001, mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 48, 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 which doesn't seem to provide the keycode.
When I press the Print Screen key in showkey -s, I get the following output. 0xe0 0x2a 0xe0 0x37 0xe0 0xaa 0xe0 0xb7 None of those resolves to 99, hex 0x63. When I run without the -s, using the default. I then get 99 as the output. Option -k is the default, keycodes. So, I think using showkey without an option in a console is the correct method.
On Sun, 2023-04-02 at 10:14 -0700, stan via users wrote:
On Sun, 2 Apr 2023 17:03:33 +0200 Wolfgang Pfeiffer roto@gmx.net wrote:
On Sat, Apr 01, 2023 at 06:10:50PM +0100, Patrick O'Callaghan wrote:
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
Here's a very old kernel sources page that explains the sysrq routine, and I think it was one of the pages version that helped me a lot:
https://mirrors.edge.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/Do...
Here, it seems, is the latest one: https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
Thanks for posting these. I used a mnemonic to remember what to press, 'busier' in reverse, 'reisub'. But, after reading the documentation, I think I only need to press 'sub'. Unless there is a runaway process.
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
When I use xev, and press Print Screen, I get the following output, FocusOut event, serial 48, synthetic NO, window 0x7200001, mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 48, synthetic NO, window 0x7200001, mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 48, 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 which doesn't seem to provide the keycode.
When I press the Print Screen key in showkey -s, I get the following output. 0xe0 0x2a 0xe0 0x37 0xe0 0xaa 0xe0 0xb7 None of those resolves to 99, hex 0x63. When I run without the -s, using the default. I then get 99 as the output. Option -k is the default, keycodes. So, I think using showkey without an option in a console is the correct method.
That also gives me 99 twice (for press/release) when I hit the "camera" key (plus the strange browser tab of a search for Ksnapshot).
poc
On Sun, Apr 02, 2023 at 10:14:51AM -0700, stan via users wrote:
On Sun, 2 Apr 2023 17:03:33 +0200 Wolfgang Pfeiffer roto@gmx.net wrote:
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>. I use xev for finding it.
When I use xev, and press Print Screen, I get the following output, FocusOut event, serial 48, synthetic NO, window 0x7200001, mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 48, synthetic NO, window 0x7200001, mode NotifyUngrab, detail NotifyAncestor
Pressing the <Print> key alone yields this in the xev log messages:
KeyRelease event, serial 35, synthetic NO, window 0x2200001, root 0x428, subw 0x2200002, time 3388184737, (48,51), root:(919,491), state 0x0, keycode 110 (keysym 0xff50, Home), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
I have to press <Fn>+<Print> to see the <Print> message in xev:
KeyRelease event, serial 38, synthetic NO, window 0x2200001, root 0x428, subw 0x0, time 3390028490, (76,93), root:(947,533), state 0x0, keycode 107 (keysym 0xff61, Print), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
------------ So to see the help screen for sysrq on a tty I type
1: <Alt> key (keep holding) 2: <Fn>+<Print> (Keep and release) 3: h 4: release all ------------
So I don't think the standard key for step 2, which is pressing <Print> or <Sysrq> only, on x86, is written in stone - it probably took me some time to find the <Fn> key was needed for step 2 here, too... :)
And yes: Im on x86
Wolfgang
On Sun, 2 Apr 2023 20:19:00 +0200 Wolfgang Pfeiffer roto@gmx.net wrote:
Pressing the <Print> key alone yields this in the xev log messages:
KeyRelease event, serial 35, synthetic NO, window 0x2200001, root 0x428, subw 0x2200002, time 3388184737, (48,51), root:(919,491), state 0x0, keycode 110 (keysym 0xff50, Home), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
I have to press <Fn>+<Print> to see the <Print> message in xev:
KeyRelease event, serial 38, synthetic NO, window 0x2200001, root 0x428, subw 0x0, time 3390028490, (76,93), root:(947,533), state 0x0, keycode 107 (keysym 0xff61, Print), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
I tried this in xev, and with any of the modifier keys and their combinations, the data for the modifier(s) shows, but print screen doesn't even register as being pressed. Maybe it has to do with the keyboard? A mystery, but not urgent enough for me to spend more time on, since I have a solution.
On Mon, Apr 03, 2023 at 07:41:32AM -0700, stan via users wrote:
On Sun, 2 Apr 2023 20:19:00 +0200 Wolfgang Pfeiffer roto@gmx.net wrote:
I have to press <Fn>+<Print> to see the <Print> message in xev:
KeyRelease event, serial 38, synthetic NO, window 0x2200001, root 0x428, subw 0x0, time 3390028490, (76,93), root:(947,533), state 0x0, keycode 107 (keysym 0xff61, Print), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
I tried this in xev, and with any of the modifier keys and their combinations, the data for the modifier(s) shows, but print screen doesn't even register as being pressed. Maybe it has to do with the keyboard? A mystery, but not urgent enough for me to spend more time on, since I have a solution.
I'd guess yes - it might have to do with the keyboard hardware whether something works, or not ..
Maybe check the "User's guide", "Quick Start Guide" or whatever it is called, that might have been shipped with the computer - mine was a brochure, just 6 pages long, and it informs the user e.g. about the "functions keys" at the top row of the keyboard, and that they should be pressed together with the "Fn" key to activate, or change, sound, wifi or whatever ...
Here's a picture of a keyboard that seems to be very similar to the one I'm using. Please note the top row keys, and the bottom row <Fn> key:
https://videogamesuncovered.com/wp-content/uploads/2017/04/Alienware-17-R4-k...
Wolfgang
On Mon, 2023-04-03 at 19:59 +0200, Wolfgang Pfeiffer wrote:
Here's a picture of a keyboard that seems to be very similar to the one I'm using. Please note the top row keys, and the bottom row <Fn> key:
https://videogamesuncovered.com/wp-content/uploads/2017/04/Alienware-17-R4-k...
Macro keys down the left?
I really wish more keyboards had some extra user keys down the left. For one thing it'd balance the layout of the keyboards with QWERTY off- centre because the cursor and numpad (which I do want). And have some way for you to type something directly that otherwise has peculiar key combinations. While function keys could do that, they're usually already predefined, and not always easy to redefine.
On 4/3/2023 9:14 PM, Tim via users wrote:
I really wish more keyboards had some extra user keys down the left. For one thing it'd balance the layout of the keyboards with QWERTY off- centre because the cursor and numpad (which I do want). And have some way for you to type something directly that otherwise has peculiar key combinations. While function keys could do that, they're usually already predefined, and not always easy to redefine.
Yeah, that and having easy access to keyboard macros is super nice. Sucks that they're really hard to find nowadays. :(
Slade
On Sun, Apr 02, 2023 at 05:03:33PM +0200, Wolfgang Pfeiffer wrote:
Looks like you first need to identify your print/sysrq key - it might be a combo of (on my keyboard) <Fn>-<Print> or <Alt>-<Print>.
that last line should have said: "be a combo of (on my keyboard) <Fn>-<Print> or something else - I found the <Fn>-<Print> keys only by tests, IIRC ..
Sorry, Wolfgang
Question: In search it appears that that is a keyboard for MAC computers. Perhaps that is why it doesn't have a key with those labels. Might be a key on mac keyboard that sends same key codes.
On 1 Apr 2023 at 18:10, Patrick O'Callaghan wrote:
Subject: Where is the magic SysReq key? From: Patrick O'Callaghan pocallaghan@gmail.com To: users@lists.fedoraproject.org Date sent: Sat, 01 Apr 2023 18:10:50 +0100 Send reply to: Community support for Fedora users users@lists.fedoraproject.org
I have a Logitech MX series wireless keyboard, and no keys are labelled as SysRq or PrtScr. Is there a way to configure a different sequence for the magic SysRq function? The man pages are not helpful.
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+
On Mon, 2023-04-03 at 01:10 +1000, Michael D. Setzer II wrote:
Question: In search it appears that that is a keyboard for MAC computers. Perhaps that is why it doesn't have a key with those labels. Might be a key on mac keyboard that sends same key codes.
I think it's meant to be cross-platform, though it does have some MAC- style keycaps, but AFAIK Logitech doesn't pay any attention to Linux. They have a Windows-only key configuration binary downloadable.
I like the kb for other features. It's very smooth with good action, and has programmable hotkeys to connect to up to three Bluetooth receivers, so I can easily switch it between the desktop, laptop and tablet.
poc
-
Jonathan Billings -
Michael D. Setzer II -
Mike Wright -
Patrick O'Callaghan -
Slade Watkins -
stan -
Tim -
Wolfgang Pfeiffer