CTRL + ALT + F1 not working on Gnome 3.28.2 with GTX1060

C3n21 · 07-27-2018, 04:11 AM

Quote:

Originally Posted by ferrari

Some more information might help here:

1) Debian version?

2) Systemd? If this is the case, examine logind.conf and report back

Code:

cat /etc/systemd/logind.conf

Reference:
https://manpages.debian.org/jessie/s...conf.5.en.html

When I get off work I'll tell you

Mill J · 07-27-2018, 06:44 AM

Does your keyboard have an "fn" key? Try Ctrl + Alt + fn + f4.

C3n21 · 07-27-2018, 07:25 AM

Quote:

Originally Posted by Mill J

Does your keyboard have an "fn" key? Try Ctrl + Alt + fn + f4.

Yes it has but it's used to turn on the LEDs, reduce the polling rate etc... (It's a CMStorm Quickfire pro).
However when I'm at home I'll try it out, thanks for the suggestion.

C3n21 · 08-10-2018, 02:11 PM

Quote:

Originally Posted by ferrari

Some more information might help here:

1) Debian version?

2) Systemd? If this is the case, examine logind.conf and report back

Code:

cat /etc/systemd/logind.conf

Reference:
https://manpages.debian.org/jessie/s...conf.5.en.html

Sorry if I hadn't replied sooner but I've been a little busy.

However here you are:

1)

Code:

uname -a
Linux C3n21 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux

Code:

cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

2)

Code:

cat /etc/systemd/logind.conf
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See logind.conf(5) for details.

[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
#UserTasksMax=33%

It seems regular, isn't it?

I've been investigating about this fact with a couple of friends and they suggested me that it could be a shortcut issue.
However I've tried using Gnome Shortcut to add CTRL + ALT + F1 to execute the command

Code:

 sudo chvt 1

to boot into the CLI, but it obviously requires super user password, so it doesn't work.
In addition, when I try to add the "CTRL + ALT + F1" shortcut it doesn't accept those 3 keys simultaneously, I could only type in "CTRL + F1" or "ALT + F1" and even so it doesn't work.

C3n21 · 08-15-2018, 09:01 AM

ferrari · 08-15-2018, 02:32 PM

It's the X-server that's responsible for trapping the key combination for changing VT, so I can only think that the keyboard codes differ from what is expected with somehow

What keyboard hardware do you have?

Code:

xinput

Look for the keyboard device and get the info eg for device 11 do

Code:

xinput list-props 11

You can use evtest to examine the input data for a given device...

Code:

evtest

For example, when I press CTRL+ALT+F3, I get

Code:

Event: time 1534361241.002042, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1534361241.002042, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1534361241.002042, -------------- SYN_REPORT ------------
Event: time 1534361241.133983, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1534361241.133983, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1534361241.133983, -------------- SYN_REPORT ------------
Event: time 1534361241.208006, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3d
Event: time 1534361241.208006, type 1 (EV_KEY), code 61 (KEY_F3), value 1

Not sure that I can really help further with this though. A bug report might be needed.

ferrari · 08-15-2018, 02:40 PM

I also wanted to share this Ubuntu thread I turned up while searching online. It happens to describe similar behaviour when the vesa video driver was in use, so you might want to check that your graphics is working as expected perhaps. You can examine the Xorg log, or if inxi is installed, run

Code:

inxi -Gxx

C3n21 · 08-16-2018, 01:57 AM

Quote:

Originally Posted by ferrari

It's the X-server that's responsible for trapping the key combination for changing VT, so I can only think that the keyboard codes differ from what is expected with somehow

What keyboard hardware do you have?

Code:

xinput

Look for the keyboard device and get the info eg for device 11 do

Code:

xinput list-props 11

You can use evtest to examine the input data for a given device...

Code:

evtest

For example, when I press CTRL+ALT+F3, I get

Code:

Event: time 1534361241.002042, type 4 (EV_MSC), code 4 (MSC_SCAN), value 1d
Event: time 1534361241.002042, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1534361241.002042, -------------- SYN_REPORT ------------
Event: time 1534361241.133983, type 4 (EV_MSC), code 4 (MSC_SCAN), value 38
Event: time 1534361241.133983, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1534361241.133983, -------------- SYN_REPORT ------------
Event: time 1534361241.208006, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3d
Event: time 1534361241.208006, type 1 (EV_KEY), code 61 (KEY_F3), value 1

Not sure that I can really help further with this though. A bug report might be needed.

This is what I get running

Code:

evtest

Code:

Event: time 1534402115.654538, -------------- SYN_REPORT ------------
Event: time 1534402119.440532, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
Event: time 1534402119.440532, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1534402119.440532, -------------- SYN_REPORT ------------
Event: time 1534402119.490600, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2
Event: time 1534402119.490600, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
Event: time 1534402119.490600, -------------- SYN_REPORT ------------
Event: time 1534402119.750075, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
Event: time 1534402119.750075, -------------- SYN_REPORT ------------
Event: time 1534402119.753575, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
Event: time 1534402119.753575, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0
Event: time 1534402119.753575, -------------- SYN_REPORT ------------
Event: time 1534402119.764557, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e2
Event: time 1534402119.764557, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
Event: time 1534402119.764557, -------------- SYN_REPORT ------------
^[OR^[OREvent: time 1534402158.258993, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e1

I've noticed that it doesn't recognize F1 and F2 keys when the program runs, because it doesn't print anything, whereas pressing F3-F7 seems to return me the ASCII value of those keys eg. ^[OS for F4.

Code:

xiput

Code:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ USB Gaming Mouse                        	id=9	[slave  pointer  (2)]
⎜   ↳ USB Gaming Mouse                        	id=11	[slave  pointer  (2)]
⎜   ↳ CM Storm Quickfire Pro Ultimate N key   	id=13	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ USB Gaming Mouse                        	id=10	[slave  keyboard (3)]
    ↳ CM Storm Quickfire Pro Ultimate N key   	id=12	[slave  keyboard (3)]
    ↳ UVC Camera (046d:0825)                  	id=14	[slave  keyboard (3)]
    ↳ USB Gaming Mouse                        	id=15	[slave  keyboard (3)]
    ↳ CM Storm Quickfire Pro Ultimate N key   	id=16	[slave  keyboard (3)]

Code:

sudo xinput list-props 12
Device 'CM Storm Quickfire Pro Ultimate N key':
	Device Enabled (152):	1
	Coordinate Transformation Matrix (154):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Send Events Modes Available (273):	1, 0
	libinput Send Events Mode Enabled (274):	0, 0
	libinput Send Events Mode Enabled Default (275):	0, 0
	Device Node (276):	"/dev/input/event2"
	Device Product ID (277):	9494, 22

Code:

sudo xinput list-props 16
Device 'CM Storm Quickfire Pro Ultimate N key':
	Device Enabled (152):	1
	Coordinate Transformation Matrix (154):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (293):	0
	libinput Natural Scrolling Enabled Default (294):	0
	libinput Send Events Modes Available (273):	1, 0
	libinput Send Events Mode Enabled (274):	0, 0
	libinput Send Events Mode Enabled Default (275):	0, 0
	Device Node (276):	"/dev/input/event3"
	Device Product ID (277):	9494, 22

C3n21 · 08-16-2018, 02:11 AM

Quote:

Originally Posted by ferrari

I also wanted to share this Ubuntu thread I turned up while searching online. It happens to describe similar behaviour when the vesa video driver was in use, so you might want to check that your graphics is working as expected perhaps. You can examine the Xorg log, or if inxi is installed, run

Code:

inxi -Gxx

Code:

inxi -G
Graphics:
  Card-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 390.48 
  Display: x11 server: X.Org 1.19.2 driver: nvidia 
  resolution: 1280x1024~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 390.48

This is what I get.

C3n21 · 08-16-2018, 02:15 AM

Quote:

Originally Posted by ferrari

I also wanted to share this Ubuntu thread I turned up while searching online. It happens to describe similar behaviour when the vesa video driver was in use, so you might want to check that your graphics is working as expected perhaps. You can examine the Xorg log, or if inxi is installed, run

Code:

inxi -Gxx

I've also checked all the Xorg logs but it seems it doesn't use Vesa Driver (I've seeked with CTRL + F).

ferrari · 08-16-2018, 03:31 AM

That graphics output confirms the nvidia driver is in use, so we can discard that idea.

Quote:

I've noticed that it doesn't recognize F1 and F2 keys when the program runs, because it doesn't print anything, whereas pressing F3-F7 seems to return me the ASCII value of those keys eg. ^[OS for F4.

Unfortunately, the output snippet you shared didn't show the F4 key code explicitly, but I assume it reports something like

Code:

Event: time 1534407914.709106, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3e
Event: time 1534407914.709106, type 1 (EV_KEY), code 62 (KEY_F4), value 1

Your xinput data shows us that you're using a 'CM Storm Quickfire Pro Ultimate N key' keyboard. I'm not familiar with this hardware, but from a quick online search I did turn up a couple of threads reporting function key behaviour that might also be relevant to you perhaps...

https://community.coolermaster.com/t...oying-fn-lock/
http://www.tomshardware.com/answers/...s-working.html

Is there a chance that function lock is on here?

C3n21 · 08-16-2018, 06:05 AM

Quote:

Originally Posted by ferrari

Unfortunately, the output snippet you shared didn't show the F4 key code explicitly, but I assume it reports something like

Code:

Event: time 1534407914.709106, type 4 (EV_MSC), code 4 (MSC_SCAN), value 3e
Event: time 1534407914.709106, type 1 (EV_KEY), code 62 (KEY_F4), value 1

No, evtest doesn't output me anything like that when I press F* keys but when it prints out ^[OS when I press F3, ^[OR for F4 etc.

Code:

Event: time 1534417415.631179, -------------- SYN_REPORT ------------
^[OR^[OS^[[15~^[[17~^[[18~^[[19~^[[20~^[[24~

that's what I get pressing F3-F9 and F12 (one by one), other F* keys are binded to a shortcut in the terminal so they don't print out anything.

ferrari · 08-16-2018, 01:42 PM

Quote:

No, evtest doesn't output me anything like that when I press F* keys but when it prints out ^[OS when I press F3, ^[OR for F4 etc.

Ok, well that explains why these keys don't work as expected then.

C3n21 · 12-27-2018, 10:03 AM

After a long time I did a reinstallation of Debian and Arch Linux and now all works really fine, so I guess it was an issue with graphics driver or something.
Thank you really much for helping me!