Left ctrl+alt+up arrow issue

Have a rather custom setup, believe this to be a BIOS bug.
When the Fn and Ctrl keys are swapped in BIOS, Left CTRL+ALT+UP arrow doesn't do anything unless or until you release either CTRL or ALT. At that point it sends a single keypress event with no repeat. To send another, you have to release and re-press all three keys down again and release ctrl or alt again. Rather annoying on Linux with multiple workspaces and switching them with ctrl+alt+up/down
Right CTRL+ALT+UP works fine. Any combination works fine such as left CTRL and right ALT and up, or switch them. It's just when you use left ctrl and left alt and up that it doesn't send anything.
Left ctrl+alt+down/left/right all work fine - it's only the up key that doesn't send keypress events. Also works fine with an external keyboard.
I run Linux on my twist, and debugging with xev or even just cat'ing the keyboard input device shows no keystroke sent upon hitting the up arrow while holding down left ctrl and left alt. So this isn't a software issue by any means.

You are not alone, bad news is that it's not a Twist issue, affects several models and some quite old too...
Here is another thread: http://forums.lenovo.com/t5/Linux-Discussion/BIOS-Bug-Enabling-Fn-Ctrl-swap-breaks-Ctrl-Alt-Up/td-p/...

Similar Messages

Brand new 15" MacBook Pro Retina - unplugged from Thunderbolt Display and Keyboards today find keyboard alpha-numerics not working; except the function keys, delete key, tab key, command/ctrl/shift/alt/fn and arrow keys; and 7/8/9/u/o/j/l nudge cursor

Brand new 15" MacBook Pro Retina - unplugged from Thunderbolt Display and Keyboards today find keyboard alpha-numerics not working; except the function keys, delete key, tab key, command/ctrl/shift/alt/fn and arrow keys; and 7/8/9/u/o/j/l produce cursor nudges.

It's a new machine - and the Thunderbolt Display is meant to work with it. You need to just make an appointment at your local Apple Store and have them fix whatever is wrong.
If you like, you could always try a SMC reset and a PRAM/NVRAM reset to see if either of those will get your keyboard back in working order...
Clinton

Photoshop CC for PC - ctrl-alt-arrow key Does Nothing

I installed Photoshop CC on a new PC, and the ctrl-alt-arrow keystroke does nothing. It used to shrink the marquee around pixels and move the selection by 1 pixel. Now it does nothing. Using shift-ctrl-alt-arrow shrinks the marquee around pixels and moves the selection by 10 pixels, which is what it's supposed to do. Any help is appreciated.

I'm re-reading your posts, and I'm guessing you started having this problem when you installed on the new PC.
What I'm thinking is that unchecking the hotkeys is not enough, the hotkey utility may be still be "trapping" the ctrl-alt-arrow keystroke.
I decided to check this for myself. First I open the task manager in Windows 7. and saw a process called "igfxHK.exe" I ended that process and started Photoshop and then tried ctrl-alt-arrow and to my surprise, that does work. igfxHK = Intel Graphics HotKey.
Now the next trick is to block it from loading in the first place. I guess you could try to move or rename it. I don't want to ask you to adjust entries in the Registry yet. I have to go in a few minutes.
From this article: Ctrl+Alt+Arrow key no longer working — Photoshop for Windows — ClearPS.com
"The good news is that (as far as I can tell) hkcmd doesn't appear to be necessary as my graphics drivers are still functioning fine after I've removed it (I went into regedit, searched for hkcmd and deleted all entries). From searching online I see that hkcmd is known to conflict with other apps, so it seems that it's likely the cause rather than PhotoShop. Why PhotoShop and hkcmd suddenly started to cause conflicts after months of proper functioning, I don't know." hkcmd is like igfxHK.
Gene

Ctrl-Alt-Backspace issue with Fluxbox and SLiM

Hi folks :)
I'm pretty new to Arch, had a few attempts at installing it in the past but wasn't quite ready and so decided to expand my Linux knowledge a little more, first. Well, I've done that and now I'm having another go, and things are going quite well. However, I have one minor problem. In ~/.xinitrc, I have the line 'exec startfluxbox' to start Fluxbox and do everything that is contained within the ever-so-handy 'startfluxbox' file. That works perfectly. However, if I restart X by pressing the Ctrl-Alt-Backspace combination, I'm sent to the command line rather than SLiM. However, if I replace 'exec startfluxbox' with 'exec fluxbox' it works fine and brings me straight back to the SLiM login window. Of course, I then can't make use of the 'startfluxbox' file.
Could anybody shed some light on why this might be happening? I know it's more than likely going to be something simple that I've missed, but any help would be appreciated. :)
Thanks,
Joel.

And using fluxbox instead of startfluxbox still works? Strange.
I had the same problem as well with slim and Xfce (sometimes SLiM would respawn after some minutes if I logged out normally), and ended up just giving up on SLiM.
I'll give it a try with my openbox-setup (should be similar enough to the fluxbox way).
What happens if you log out of your session instead of killing the xserver?
You could always give some other login manager a try, kdm/gdm or qingy if you want things lite.
[edit: I tried it, SLiM works fine with openbox-session. It needs rather a lot of time to start up after booting but that might have something to do with me having backgrounded daemons rather indiscriminately.
Probably a stupid idea, but have you tried waiting a bit? As I've mentioned, sometimes SLiM took a few minutes to respawn due to some bug or other.
Last edited by lastchancetosee (2009-05-16 20:51:31)

HDX 16 1370 us notebook/ Windows 7 upgrade/ Boot Manager Missing hit ctrl + alt _ delete to restart

Hard drive was going south. I replaced it with new one. The original OS was Vista but I had upgraded to windows 7 a year ago. I placed the Windows 7 CD into the optical drive and windows begin to load. I got past the point of the screen that ask for language and so forth then my dog jumped on me and pulled the power cord from the computer. I plugged the cord back in and tried to restart the process. Now the first thing that happens is I get the message Bootmgr missing hit ctrl alt delete to restart.
I do not know what to do now.
I can't get into command prompt from shift+ F10, so I am totally lost. Is there any hope??
Thanks

Are you saying that you inserted the Windows 7 upgrade disc to boot to? Was Windows Vista already installed on the hard drive? Have you run the hard drive test in BIOS?
I work for HP.
Please click the White Kudos star on the left to say thanks.
Please mark Accept As Solution if this resolves your issue.

Ctrl-alt-end on mac keyboard

Our system at work uses WIndows XP and I can now use Remote Office to get on the system from home. Previously, I had to run Parallels Desktop for windows. Now, I can run it from Safari, except to begin the login process, I must hit the combination of keys "Ctrl-Alt-END" I have looked at discussions and they say end is accessed using the command key and the left or right arrow. No luck with that.
Do I hit the control key, alt key, command key and right arrow at once? I tried that and it didn't work. Parallels for Windows has a virtual Windows keyboard, but there doesn't seem to be the same WIndows keyboard on Mac OS. Help!!

the options key on the mac keyboard should map to the windows alt key, so the key command should be control-options-end.
You should be able to enable "Remote Access" on the windows XP machine (get properties on My Computer and enable it in the "Remote" tab). Then download Microsoft's "Remote Desktop Connection" software and connect to your work PC by entering it's IP address.

CTRL, ALT and SHIFT keys are sticking (not physically)

I am having a problem with the T-61p I have been using for 2 years now.
About once every 2 days Windows thinks that either the CTRL, the ALT or the SHIFT key is held down. I only notice this when my mouse's left click or my arrow keys starts behaving funny (like opening dialogs when clicking on icons or highlighting text on a page in MS Word) instead of moving the cursor as they should.
When this starts happening, pressing the CTRL, ALT and SHIFT buttons causes the strange behavior to stop.
None of the keys are physically stuck down. I am using an external keyboard with my laptop closed and docked. I have tried switching keyboards, and I get the same results with brand new Logitech keyboards.
What could this be? Has anyone seen this problem before?
Your help is much appreciated.

Welcome to the forum!
It sounds like you've inadvertently turned on the Sticky Keys accessibility feature. Since you didn't mention which operating system you're using, I can't tell you how to turn it off. Trying searching for Sticky Keys in Help in the Start button menu.
Hope this helps!
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Jane
2015 X1 Carbon, ThinkPad Slate, T410s, X301, X200 Tablet, T60p, HP TouchPad, iPad Air 2, iPhone 5S, IdeaTab A2107A, Yoga Tablet, Yoga 3 Pro
I am not a Lenovo Employee.
I AM one of those crazy ThinkPad zealots!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!

Ctrl-Alt shortcuts to switch modules not working

I'm having trouble with LR 4.1 (Win 7 64 bit) recognizing keyboard input properly. Sometimes it just stops "seeing" ctrl-alt-n (where n=1, 2, 3...) to switch between modules (Library, Develop, etc.). I can do everything else with the keyboard (Tab to show/hide panels, rate, keyword, etc.), but it just doesn't recognize the module shortcuts (or the arrow key versions to move to next/previous). I can change modules with the mouse, but I'd prefer to use keyboard shortcuts. This is a US keyboard on an English-language system. Anyone else experiencing this issue?

Nope, can't say it's happened to me. But I tend to use "d" for develop, or "g" (or "e") for Library.
Could it be that your numeric lock got toggled somehow? What number keys are you using (keypad, or top row)?
Hal

Ctrl-Alt-drag for brushsize also moves Canvas. Bug/problem

Hi, I'm experiencing a weird problem with Adobe Photoshop Version: 12.0.1 on Mac OS 10.6.4 (Macbook Pro).
I've used the ctrl+alt+mousedrag shortcut for changing brush size for some time, but a few days ago it started acting weird. (I have no clue what provoked it)
If I hold ctrl+alt keys down and move my mouse around, the entire canvas follows the mouse (independent on fullscreen) around.
However if I hold ctrl+alt and click once with the left mousebutton before moving the mouse, then keep holding down ctrl+alt it will act as normal and I can use the cursor to get the brush-settings the way I want it without the canvas moving around. But it is still annoying me because this is something I do very often, and thus it is really messing with my workflow.. And I know it hasn't allways been like this.
I've tried dumping the settings file, but not yet a full reinstall as I am hoping there might be a fix for this.
Thanks,
Steffen

Hi, thanks for the reply. I just figured out what is causing this and came back to post it.. You were on the right track!!
I recently downloaded a beta of something called HyperDock (http://hyperdock.bahoom.de).. Disabling that application fixes the issue.
Goodbye hyperdock - welcome back ctrl+alt+drag!
//Edit: Seems there is a setting in hyperdock that I can turn off, so it can run witihout messing with the shortcuts.. It is actually a decent app if you tend to use a lot of windows.

Ctrl alt delete doesnt work anymore

Hi,
We have an HP probook G0 where the combination ctrl alt delete doesnt work anymore.
- The issue is only with the left ctrl Key. When we use the right ctrl key, ctrl alt delete works
- When I check the onscreen keyboard in windows, the left ctrl key does react, so the key is'nt hardware defected.
With external keyboard everything works also fine.
Laptop has the latest HP updates.
Any ideas how to solve this issue?
thx!

thx prob is solved just had to double-click on the window , also performed a virus-scan, but no viruses were found, i do use pc-cilin 2002 (up to date) i hope it's sufficient, because norton is way much better, i know, but i just don't want to spend any money on a damn anti-virus prog...just used the one that came with my mobo
MSI 875P NEO-FIS2R
Intel Pentium IV 2.6 C Ghz (HT running perfect)
2x256 MB DDR400 (Dual Channel)
Maxtor 80 GB S-ATA 150
CD-RW Lite-On 52x32x52
MSI Starforce NVIDIA Geforce FX 5900 Ultra 256 DDR
Windows XP Professional SP1
greetz

CTRL+ALT+TECH: The Walking Dead (In a Post-Server 2003 World)

You’ve been left behind. You’re still running Windows Server 2003 and now all help (from Microsoft) has abandoned you. Good news: You’ve still got your brains. Now it’s up to you (and the other survivors) to keep going and avoid all the zombies, er... exploits along the way. Luckily you’ve got strength in numbers.
Tune into CTRL+ALT+TECH to find out how fellow IT pro survivors are navigating the post-EOS apocalypse and what they’re doing to combat the forces of evil that await!
Sponsored by HP and Intel. Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.
This topic first appeared in the Spiceworks Community

I have a powershell script that is collecting AD accounts from within a certain OU that expire in the next 30 days. My problem is I cant get it to also display the displayName as a field as well as sort the formatting.
The fullname is coming up blank for me. I know if I add the following line it will sort it but having issues determining where to do so... Select-Object Name,AccountExpirationDate | Sort-Object AccountExpirationDatePowershellparam ($days = -30,$domainsearch = '',$dcServer = '',$emailto = '',$smtpserver = '',$fromaddress = '')$daysin = -$days$expiredaccounts = search-adaccount -AccountExpiring -TimeSpan "30" -Server $dcServer -SearchBase $domainsearch| where {$_.AccountExpirationDate -lt ((get-date).adddays($daysin)) }|select -Property samaccountname,displayName,AccountExpirationDate|Format-Table @{n="Userid";e={$_....

Revolve 810 G1 Unlock Computer when in Tablet Mode. Press CTRL-ALT-DEL or Windows Security Button

1. I have an Revolve 810 G1
Running Windows 7 Pro (64 Bit).
When I change the screen to Tablet Mode
(Folding tablet over keyboard and using as tablet).
I lock my computer.
2. What to know how to unlock without having to Open back up and use the CTL-Alt-DEL keys.
When Locked screen shows: Press CTRL-ALT-DEL or use the Windows Security Button to unlock this computer.
I would like to use the Windows Button on the bottom of the screen
(One Used in Windows 8 to change between Desktop and Metro) to Unlock screen And bring up on screen keyboard to put in my password.
This is probably how it should work, but it does not work.
Even bringing up the onscreen keyboard via the blue power button On the screen to Ease Of Access does not work.
The CLT-ALT-DEL on the on screen keyboard will not unlock the screen.
P.S.
Where is that Windows Security Button when you need it?
Thanks,
Rog

If you are using Windows 7 (not Windows 8), you should be able to touch the Ease of Access button at the lower left of the screen, then select Type without the keyboard (On-screen keyboard). When the on-screen keyboard pops-up, press CTRL, then ALT, then DEL. You should get a password prompt; the on-screen keyboard will stay visible unless and until you close it.
Although I am an HP employee, I am speaking for myself and not for HP.
Please click the little thumbs-up dealybopper to the lower right if my reply was helpful to you. Please mark Accept As Solution if it solves your problem. This will help others, too!

Ctrl/Alt Keys not Working in Parallels

Hi,
I'm running Illustrator CS6 using Parallels Desktop 8 and Windows 7. It appears that the ctrl/alt keys do not work. Has anyone found a solution? I've tried resetting my preferences and restarting my computer. Any help would be greatly appreciaed.

Although this is an old thread, I also seem to be having the same sort of issues with Illustrator CS2 in Snow Leopard running under Parallels Desktop 9.
Re. the proposed solution, there does not seem to be a 'Virtual Machine -> Configure -> Options -> Advanced -> Optimize modifier keys for games' option in Desktop 9 - or I've not found it.
I will pursue this in the Parallels forums, but if anyone here has found a solution, I'd be interested to hear it.

Firefox freezes about five seconds after I open it, and whenever I use Ctrl+alt+delete to close it I get told that it is waiting for a response from me.

I am having a problem with Firefox. Whenever I open it, it runs fine for about five seconds and then freezes. A small white rectangle appears in the upper left corner of the browser window. The screen still scrolls fine, but whenever I try clicking on anything (including the menus in the toolbar), it just gives me an unresponsive 'ding' sound. When I try closing the programme with Ctrl+alt+delete, I get a message saying 'The system cannot end this programme as it is waiting for a response from you'. I originally had this problem with an earlier version of Firefox and tried installing Firefox 4 to see if this helped. It worked for two days and began doing it again. I have already tried un- and re-installing Firefox and restarting my computer, and Firefox will not run properly for long enough to let me disable any add-ons or plug-ins. What can I do to fix this?
I've added a couple of screencaps of the problem. (or tried to)
[http://i53.tinypic.com/161hvh2.jpg The white rectangle]
[http://i51.tinypic.com/dwsq1.png Error message]

Have also since found out that to start FF4 in safe mode you just hold shift whilst double-clicking the icon. We only find these things out after the event, murphy's law!

Can't switch VT's with Ctrl+Alt+Fx or Ctrl+Alt+backspace terminate

Ctrl+Alt+F2 doesn't seem to register. It's been a long term issue I have had for years. I've tried all the various fixes.
I can manually change to virtual terminals without issues using:
sudo chvt 2
Once I'm in a VT I can use Alt+Fx to change between them, until I go back into Xorg. So it's unlikely to be a graphics driver problem, most other people with similar issues complain of getting a blank screen.
Although without sudo I get
# chvt 2
Couldn't get a file descriptor referring to the console.
I have the following in /etc/X11/xorg.conf.d/15-forcevt.conf
Section "ServerFlags"
Option "HandleSpecialKeys" "always"
Option "DontVTSwitch" "false"
Option "DontZap" "false"
EndSection
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
A also enabled the terminate option in gnome-tweak-tool.
xmodmap -pke has the following:
keycode 67 = F1 F1 F1 F1 F1 F1 XF86Switch_VT_1
keycode 68 = F2 F2 F2 F2 F2 F2 XF86Switch_VT_2
Nothing is printed in Xorg logs when I try pushing the keys.
I'm using SLIM (although I tried manually via startx), AwesomeWM (also tried fluxbox with a blank conf), nvidia (proprietary), UEFI.
[ 2490.220]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 2490.225] X Protocol Version 11, Revision 0
[ 2490.227] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 2490.229] Current Operating System: Linux ender 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
[ 2490.229] Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=ff84efeb-e43f-47fe-a14d-07894feb0013 rw rootflags=subvol=@ quiet
[ 2490.233] Build Date: 14 March 2015 06:45:50PM
[ 2490.234]
[ 2490.236] Current version of pixman: 0.32.6
[ 2490.240] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2490.240] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2490.247] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 1 10:44:03 2015
[ 2490.249] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 2490.250] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2490.250] (==) ServerLayout "Layout0"
[ 2490.250] (**) |-->Screen "Screen0" (0)
[ 2490.250] (**) | |-->Monitor "Monitor0"
[ 2490.251] (**) | |-->Device "Device0"
[ 2490.251] (**) |-->Input Device "Keyboard0"
[ 2490.251] (**) |-->Input Device "Mouse0"
[ 2490.251] (**) Option "DontVTSwitch" "false"
[ 2490.251] (**) Option "DontZap" "false"
[ 2490.251] (**) Option "Xinerama" "0"
[ 2490.251] (==) Automatically adding devices
[ 2490.251] (==) Automatically enabling devices
[ 2490.251] (==) Automatically adding GPU devices
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 2490.251] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 2490.251] Entry deleted from font path.
[ 2490.251] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 2490.251] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 2490.251] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2490.251] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 2490.251] (WW) Disabling Keyboard0
[ 2490.251] (WW) Disabling Mouse0
[ 2490.251] (II) Loader magic: 0x815d80
[ 2490.251] (II) Module ABI versions:
[ 2490.251] X.Org ANSI C Emulation: 0.4
[ 2490.251] X.Org Video Driver: 19.0
[ 2490.251] X.Org XInput driver : 21.0
[ 2490.251] X.Org Server Extension : 9.0
[ 2490.254] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 2490.254] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 2490.254] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[ 2490.258] (--) PCI:*(0:1:0:0) 10de:1180:10de:0969 rev 161, Mem @ 0xfa000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 2490.258] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 2490.258] (II) LoadModule: "glx"
[ 2490.258] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2490.268] (II) Module glx: vendor="NVIDIA Corporation"
[ 2490.268] compiled for 4.0.2, module version = 1.0.0
[ 2490.268] Module class: X.Org Server Extension
[ 2490.268] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 2490.268] (II) LoadModule: "nvidia"
[ 2490.268] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 2490.269] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 2490.269] compiled for 4.0.2, module version = 1.0.0
[ 2490.269] Module class: X.Org Video Driver
[ 2490.269] (II) NVIDIA dlloader X Driver 346.47 Thu Feb 19 17:47:18 PST 2015
[ 2490.269] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2490.269] (++) using VT number 1
[ 2490.269] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 2490.269] (II) Loading sub module "fb"
[ 2490.269] (II) LoadModule: "fb"
[ 2490.269] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 2490.269] (II) Module fb: vendor="X.Org Foundation"
[ 2490.269] compiled for 1.17.1, module version = 1.0.0
[ 2490.269] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.269] (II) Loading sub module "wfb"
[ 2490.269] (II) LoadModule: "wfb"
[ 2490.270] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 2490.270] (II) Module wfb: vendor="X.Org Foundation"
[ 2490.270] compiled for 1.17.1, module version = 1.0.0
[ 2490.270] ABI class: X.Org ANSI C Emulation, version 0.4
[ 2490.270] (II) Loading sub module "ramdac"
[ 2490.270] (II) LoadModule: "ramdac"
[ 2490.270] (II) Module "ramdac" already built-in
[ 2490.270] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 2490.270] (==) NVIDIA(0): RGB weight 888
[ 2490.270] (==) NVIDIA(0): Default visual is TrueColor
[ 2490.270] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2490.270] (**) NVIDIA(0): Option "Stereo" "0"
[ 2490.270] (**) NVIDIA(0): Option "SLI" "Off"
[ 2490.270] (**) NVIDIA(0): Option "MultiGPU" "Off"
[ 2490.270] (**) NVIDIA(0): Option "BaseMosaic" "off"
[ 2490.270] (**) NVIDIA(0): Stereo disabled by request
[ 2490.270] (**) NVIDIA(0): NVIDIA SLI disabled.
[ 2490.270] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[ 2490.271] (**) NVIDIA(0): Option "MetaModes" "DVI-I-1: nvidia-auto-select +1280+0, DVI-D-0: nvidia-auto-select +0+416"
[ 2490.271] (**) NVIDIA(0): Enabling 2D acceleration
[ 2490.690] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[ 2490.692] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 680 (GK104) at PCI:1:0:0 (GPU-0)
[ 2490.692] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 2490.692] (--) NVIDIA(0): VideoBIOS: 80.04.09.00.01
[ 2490.692] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 2490.709] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 680 at PCI:1:0:0
[ 2490.709] (--) NVIDIA(0): CRT-0
[ 2490.709] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0) (boot, connected)
[ 2490.709] (--) NVIDIA(0): DFP-1
[ 2490.709] (--) NVIDIA(0): DFP-2
[ 2490.709] (--) NVIDIA(0): Samsung SyncMaster (DFP-3) (connected)
[ 2490.709] (--) NVIDIA(0): DFP-4
[ 2490.709] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SMS27A850T (DFP-0): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SMS27A850T (DFP-0): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-1: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-2: Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): Samsung SyncMaster (DFP-3): Internal TMDS
[ 2490.710] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-3): 330.0 MHz maximum pixel clock
[ 2490.710] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 2490.710] (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
[ 2490.710] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.710] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2490.710] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2490.710] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2490.710] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2490.710] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2490.710] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2490.710] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
[ 2490.712] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2490.712] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2490.712] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2490.713] (II) NVIDIA(0): Validated MetaModes:
[ 2490.713] (II) NVIDIA(0):
[ 2490.713] (II) NVIDIA(0): "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.713] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1440
[ 2490.742] (--) NVIDIA(0): DPI set to (125, 114); computed from "UseEdidDpi" X config
[ 2490.742] (--) NVIDIA(0): option
[ 2490.742] (--) Depth 24 pixmap format is 32 bpp
[ 2490.743] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 2490.743] (II) NVIDIA: access.
[ 2490.746] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 2490.746] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 2490.746] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 2490.746] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 2490.746] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 2490.746] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 2490.746] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 2490.746] (II) NVIDIA(0): Config Options in the README.
[ 2490.761] (II) NVIDIA(0): Setting mode "DVI-I-1:nvidia-auto-select+1280+0,DVI-D-0:nvidia-auto-select+0+416"
[ 2490.853] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 2490.853] (==) NVIDIA(0): Backing store enabled
[ 2490.853] (==) NVIDIA(0): Silken mouse enabled
[ 2490.853] (**) NVIDIA(0): DPMS enabled
[ 2490.853] (II) Loading sub module "dri2"
[ 2490.853] (II) LoadModule: "dri2"
[ 2490.853] (II) Module "dri2" already built-in
[ 2490.853] (II) NVIDIA(0): [DRI2] Setup complete
[ 2490.853] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 2490.853] (--) RandR disabled
[ 2490.856] (II) Initializing extension GLX
[ 2490.856] (II) Indirect GLX disabled.(II) config/udev: Adding input device Power Button (/dev/input/event7)
[ 2490.914] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.914] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.914] (II) LoadModule: "evdev"
[ 2490.914] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 2490.914] (II) Module evdev: vendor="X.Org Foundation"
[ 2490.914] compiled for 1.17.1, module version = 2.9.2
[ 2490.914] Module class: X.Org XInput Driver
[ 2490.914] ABI class: X.Org XInput driver, version 21.0
[ 2490.915] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 30 paused 0
[ 2490.915] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.915] (**) Power Button: always reports core events
[ 2490.915] (**) evdev: Power Button: Device: "/dev/input/event7"
[ 2490.915] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.915] (--) evdev: Power Button: Found keys
[ 2490.915] (II) evdev: Power Button: Configuring as keyboard
[ 2490.915] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input9/event7"
[ 2490.915] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 2490.915] (**) Option "xkb_rules" "evdev"
[ 2490.915] (**) Option "xkb_model" "pc104"
[ 2490.915] (**) Option "xkb_layout" "us"
[ 2490.915] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.940] (II) config/udev: Adding input device Power Button (/dev/input/event6)
[ 2490.940] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 2490.940] (**) Power Button: Applying InputClass "Keyboard Defaults"
[ 2490.941] (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 31 paused 0
[ 2490.941] (II) Using input driver 'evdev' for 'Power Button'
[ 2490.941] (**) Power Button: always reports core events
[ 2490.941] (**) evdev: Power Button: Device: "/dev/input/event6"
[ 2490.941] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 2490.941] (--) evdev: Power Button: Found keys
[ 2490.941] (II) evdev: Power Button: Configuring as keyboard
[ 2490.941] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input8/event6"
[ 2490.941] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 2490.941] (**) Option "xkb_rules" "evdev"
[ 2490.941] (**) Option "xkb_model" "pc104"
[ 2490.941] (**) Option "xkb_layout" "us"
[ 2490.941] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event18)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event19)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event20)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event21)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.942] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event10)
[ 2490.942] (II) No input driver specified, ignoring this device.
[ 2490.942] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event11)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event12)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event14)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event15)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.943] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event16)
[ 2490.943] (II) No input driver specified, ignoring this device.
[ 2490.943] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event17)
[ 2490.944] (II) No input driver specified, ignoring this device.
[ 2490.944] (II) This device may have been added with another device file.
[ 2490.944] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event0)
[ 2490.944] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.944] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.944] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 32 paused 0
[ 2490.944] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.944] (**) HID 1017:0002: always reports core events
[ 2490.944] (**) evdev: HID 1017:0002: Device: "/dev/input/event0"
[ 2490.945] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.945] (--) evdev: HID 1017:0002: Found keys
[ 2490.945] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.945] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.0/0003:1017:0002.0001/input/input2/event0"
[ 2490.945] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 8)
[ 2490.945] (**) Option "xkb_rules" "evdev"
[ 2490.945] (**) Option "xkb_model" "pc104"
[ 2490.945] (**) Option "xkb_layout" "us"
[ 2490.945] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.945] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/event1)
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev pointer catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "evdev keyboard catchall"
[ 2490.945] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 33 paused 0
[ 2490.946] (II) Using input driver 'evdev' for 'HID 1017:0002'
[ 2490.946] (**) HID 1017:0002: always reports core events
[ 2490.946] (**) evdev: HID 1017:0002: Device: "/dev/input/event1"
[ 2490.946] (--) evdev: HID 1017:0002: Vendor 0x1017 Product 0x2
[ 2490.946] (--) evdev: HID 1017:0002: Found 9 mouse buttons
[ 2490.946] (--) evdev: HID 1017:0002: Found scroll wheel(s)
[ 2490.946] (--) evdev: HID 1017:0002: Found relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found x and y relative axes
[ 2490.946] (--) evdev: HID 1017:0002: Found absolute axes
[ 2490.946] (II) evdev: HID 1017:0002: Forcing absolute x/y axes to exist.
[ 2490.946] (--) evdev: HID 1017:0002: Found keys
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as mouse
[ 2490.946] (II) evdev: HID 1017:0002: Configuring as keyboard
[ 2490.946] (II) evdev: HID 1017:0002: Adding scrollwheel support
[ 2490.946] (**) evdev: HID 1017:0002: YAxisMapping: buttons 4 and 5
[ 2490.946] (**) evdev: HID 1017:0002: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.946] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb2/2-1/2-1:1.1/0003:1017:0002.0002/input/input3/event1"
[ 2490.946] (II) XINPUT: Adding extended input device "HID 1017:0002" (type: KEYBOARD, id 9)
[ 2490.946] (**) Option "xkb_rules" "evdev"
[ 2490.946] (**) Option "xkb_model" "pc104"
[ 2490.946] (**) Option "xkb_layout" "us"
[ 2490.946] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.946] (II) evdev: HID 1017:0002: initialized for relative axes.
[ 2490.946] (WW) evdev: HID 1017:0002: ignoring absolute axes.
[ 2490.946] (**) HID 1017:0002: (accel) keeping acceleration scheme 1
[ 2490.946] (**) HID 1017:0002: (accel) acceleration profile 0
[ 2490.946] (**) HID 1017:0002: (accel) acceleration factor: 2.000
[ 2490.946] (**) HID 1017:0002: (accel) acceleration threshold: 4
[ 2490.946] (II) config/udev: Adding input device HID 1017:0002 (/dev/input/mouse0)
[ 2490.946] (**) HID 1017:0002: Applying InputClass "Keyboard Defaults"
[ 2490.946] (II) No input driver specified, ignoring this device.
[ 2490.947] (II) This device may have been added with another device file.
[ 2490.947] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event2)
[ 2490.947] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev pointer catchall"
[ 2490.947] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 34 paused 0
[ 2490.947] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.947] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event2"
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found 20 mouse buttons
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.947] (--) evdev: Logitech G9x Laser Mouse: Found x and y relative axes
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.947] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.947] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.0/0003:046D:C066.0003/input/input4/event2"
[ 2490.947] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: MOUSE, id 10)
[ 2490.947] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.948] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/mouse1)
[ 2490.948] (II) No input driver specified, ignoring this device.
[ 2490.948] (II) This device may have been added with another device file.
[ 2490.948] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event3)
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev keyboard catchall"
[ 2490.948] (**) Logitech G9x Laser Mouse: Applying InputClass "Keyboard Defaults"
[ 2490.949] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 35 paused 0
[ 2490.949] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[ 2490.949] (**) Logitech G9x Laser Mouse: always reports core events
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event3"
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found 1 mouse buttons
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing relative x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found absolute axes
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Forcing absolute x/y axes to exist.
[ 2490.949] (--) evdev: Logitech G9x Laser Mouse: Found keys
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Configuring as keyboard
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[ 2490.949] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.949] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.3/5-1.3:1.1/0003:046D:C066.0004/input/input5/event3"
[ 2490.949] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: KEYBOARD, id 11)
[ 2490.949] (**) Option "xkb_rules" "evdev"
[ 2490.949] (**) Option "xkb_model" "pc104"
[ 2490.949] (**) Option "xkb_layout" "us"
[ 2490.949] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.949] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[ 2490.949] (WW) evdev: Logitech G9x Laser Mouse: ignoring absolute axes.
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[ 2490.949] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[ 2490.949] (II) config/udev: Adding input device USB Keyboard (/dev/input/event4)
[ 2490.949] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.949] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.950] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 36 paused 0
[ 2490.950] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.950] (**) USB Keyboard: always reports core events
[ 2490.950] (**) evdev: USB Keyboard: Device: "/dev/input/event4"
[ 2490.950] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.950] (--) evdev: USB Keyboard: Found keys
[ 2490.950] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.950] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.0/0003:04D9:0274.0005/input/input6/event4"
[ 2490.950] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 12)
[ 2490.950] (**) Option "xkb_rules" "evdev"
[ 2490.950] (**) Option "xkb_model" "pc104"
[ 2490.950] (**) Option "xkb_layout" "us"
[ 2490.950] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.951] (II) config/udev: Adding input device USB Keyboard (/dev/input/event5)
[ 2490.951] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
[ 2490.951] (**) USB Keyboard: Applying InputClass "Keyboard Defaults"
[ 2490.951] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 37 paused 0
[ 2490.951] (II) Using input driver 'evdev' for 'USB Keyboard'
[ 2490.951] (**) USB Keyboard: always reports core events
[ 2490.951] (**) evdev: USB Keyboard: Device: "/dev/input/event5"
[ 2490.951] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x274
[ 2490.951] (--) evdev: USB Keyboard: Found 1 mouse buttons
[ 2490.951] (--) evdev: USB Keyboard: Found scroll wheel(s)
[ 2490.951] (--) evdev: USB Keyboard: Found relative axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing relative x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found absolute axes
[ 2490.951] (II) evdev: USB Keyboard: Forcing absolute x/y axes to exist.
[ 2490.951] (--) evdev: USB Keyboard: Found keys
[ 2490.951] (II) evdev: USB Keyboard: Configuring as mouse
[ 2490.951] (II) evdev: USB Keyboard: Configuring as keyboard
[ 2490.951] (II) evdev: USB Keyboard: Adding scrollwheel support
[ 2490.951] (**) evdev: USB Keyboard: YAxisMapping: buttons 4 and 5
[ 2490.951] (**) evdev: USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 2490.951] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:07:00.0/usb5/5-1/5-1.4/5-1.4:1.1/0003:04D9:0274.0006/input/input7/event5"
[ 2490.951] (II) XINPUT: Adding extended input device "USB Keyboard" (type: KEYBOARD, id 13)
[ 2490.951] (**) Option "xkb_rules" "evdev"
[ 2490.951] (**) Option "xkb_model" "pc104"
[ 2490.951] (**) Option "xkb_layout" "us"
[ 2490.951] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.952] (II) evdev: USB Keyboard: initialized for relative axes.
[ 2490.952] (WW) evdev: USB Keyboard: ignoring absolute axes.
[ 2490.952] (**) USB Keyboard: (accel) keeping acceleration scheme 1
[ 2490.952] (**) USB Keyboard: (accel) acceleration profile 0
[ 2490.952] (**) USB Keyboard: (accel) acceleration factor: 2.000
[ 2490.952] (**) USB Keyboard: (accel) acceleration threshold: 4
[ 2490.952] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event9)
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 2490.952] (**) Eee PC WMI hotkeys: Applying InputClass "Keyboard Defaults"
[ 2490.952] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 38 paused 0
[ 2490.952] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[ 2490.952] (**) Eee PC WMI hotkeys: always reports core events
[ 2490.952] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event9"
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[ 2490.953] (--) evdev: Eee PC WMI hotkeys: Found keys
[ 2490.953] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[ 2490.953] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input12/event9"
[ 2490.953] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 14)
[ 2490.953] (**) Option "xkb_rules" "evdev"
[ 2490.953] (**) Option "xkb_model" "pc104"
[ 2490.953] (**) Option "xkb_layout" "us"
[ 2490.953] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[ 2490.953] (II) config/udev: Adding input device PC Speaker (/dev/input/event8)
[ 2490.953] (II) No input driver specified, ignoring this device.
[ 2490.953] (II) This device may have been added with another device file.
[ 2491.022] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.022] (**) NVIDIA(0): device Samsung SyncMaster (DFP-3) (Using EDID frequencies
[ 2491.022] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 2491.034] (**) NVIDIA(0): device Samsung SMS27A850T (DFP-0) (Using EDID frequencies
[ 2491.034] (**) NVIDIA(0): has been enabled on all display devices.)
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1920x1080" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1920x1080".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "1280x720" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "1280x720".
[ 2491.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMS27A850T (DFP-0) contradicts itself:
[ 2491.034] (WW) NVIDIA(GPU-0): mode "720x576" is specified in the EDID; however, the
[ 2491.034] (WW) NVIDIA(GPU-0): EDID's valid VertRefresh range (56.000-75.000 Hz) would
[ 2491.034] (WW) NVIDIA(GPU-0): exclude this mode's VertRefresh (50.0 Hz); ignoring
[ 2491.034] (WW) NVIDIA(GPU-0): VertRefresh check for mode "720x576".
Last edited by H3g3m0n (2015-04-01 00:11:52)

WonderWoofy wrote:I'm not sure about your VT issue, but if you set the 'terminate:ctrl_alt_bksp' option with setxkbmap or loginctl, does it work then?
I tried setxkbmap before without success.
Also tried:
localectl set-x11-keymap "us" "" "" "terminate:ctrl_alt_bksp"
Not sure how to go about using loginctl to do the same thing.
Last edited by H3g3m0n (2015-04-01 03:25:35)

Left ctrl+alt+u​p arrow issue

Similar Messages

Maybe you are looking for

Left ctrl+alt+up arrow issue