Restart X (ctrl-alt-backspace) doesn't respond

Subject says it all.  Under my old distro, ctrl-alt-backspace would restart X.  This doesn't seem to be the case w/ Arch.  How can I enable this behavior?
Thanks!

darthaxul wrote:
xorg claims that there are newer ways of closing the X server.
If im on openbox now. what do i put in the logout event?
<item label="logout">
<action name="Execute">
<command>kill `ps -e | grep startx| awk '{print $1}'`</command>
<startupnotify>
<enabled>yes</enabled>
</startupnotify>
</action>
</item>
i havent tried this yet but is that something anyone else is using?
I guess you could bind that output to a key and use it in place of Ctl+Alt+Bksp.

Similar Messages

  • Ctrl+alt+backspace doesn't work anymore after system update

    After a recent system update (xorg got updated among other packages), ctrl+alt+backspace doesn't restart gdm anymore.
    Before you say it, I have the following in my /etc/X11/xorg.conf
    Section "ServerFlags"
    Option "DontZap" "false"
    EndSection
    Here is the relevant portion from my /var/log/pacman.log and as you can see, xorg-server did get updated.
    [2009-05-29 18:37] starting full system upgrade
    [2009-05-29 18:39] upgraded dhcpcd (5.0.2-1 -> 5.0.4-1)
    [2009-05-29 18:39] NOTE
    [2009-05-29 18:39] ----
    [2009-05-29 18:39] Add your user to group 'camera' to use camera devices.
    [2009-05-29 18:39] upgraded libgphoto2 (2.4.5-1 -> 2.4.6-1)
    [2009-05-29 18:39] upgraded gphoto2 (2.4.4-1 -> 2.4.5-1)
    [2009-05-29 18:39] upgraded gtkam (0.1.15-1 -> 0.1.16.1-1)
    [2009-05-29 18:39] upgraded lib32-glibc (2.9-4 -> 2.10.1-2)
    [2009-05-29 18:39] upgraded lib32-alsa-lib (1.0.19-1 -> 1.0.20-1)
    [2009-05-29 18:39] upgraded lib32-gcc-libs (4.3.3-1 -> 4.4.0-2)
    [2009-05-29 18:39] upgraded lib32-libdrm (2.4.9-1 -> 2.4.11-1)
    [2009-05-29 18:39] upgraded lib32-libgl (7.4.1-1 -> 7.4.2-2)
    [2009-05-29 18:39] upgraded lib32-mesa (7.4.1-1 -> 7.4.2-1)
    [2009-05-29 18:39] upgraded libdrm (2.4.11-1 -> 2.4.11-2)
    [2009-05-29 18:39] upgraded live-media (2009.02.23-1 -> 2009.04.20-1)
    [2009-05-29 18:39] upgraded qt (4.5.1-2 -> 4.5.1-3)
    [2009-05-29 18:39] upgraded phonon (4.3.1-1 -> 4.3.1-2)
    [2009-05-29 18:39] upgraded pygobject (2.16.1-1 -> 2.18.0-1)
    [2009-05-29 18:39] upgraded python-numpy (1.3.0-1 -> 1.3.0-2)
    [2009-05-29 18:39] upgraded qt3 (3.3.8-10 -> 3.3.8-11)
    [2009-05-29 18:39] upgraded whois (4.7.33-1 -> 4.7.33-2)
    [2009-05-29 18:39] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
    [2009-05-29 18:39] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-1)

    Check out http://bbs.archlinux.org/viewtopic.php?id=73064

  • Getting SLiM to restart after ctrl-alt-backspace

    I recently installed SLiM (Simple Login Manager) and it's quite nice. My only problem with it is that if I do a ctrl-alt-backspace at the log-in prompt it will drop me into text-mode log-in without restarting X or SLiM.
    Can it be configured to respawn if X is killed?
    i have the following in my inittab:
    # /etc/inittab
    # Runlevels:
    # 0 Halt
    # 1(S) Single-user
    # 2 Not used
    # 3 Multi-user
    # 4 Not used
    # 5 X11
    # 6 Reboot
    id:5:initdefault:
    rc::sysinit:/etc/rc.sysinit
    rs:S1:wait:/etc/rc.single
    rm:2345:wait:/etc/rc.multi
    rh:06:wait:/etc/rc.shutdown
    su:S:wait:/sbin/sulogin -p
    c1:2345:respawn:/sbin/agetty 38400 vc/1 linux
    c2:2345:respawn:/sbin/agetty 38400 vc/2 linux
    c3:2345:respawn:/sbin/agetty 38400 vc/3 linux
    c4:2345:respawn:/sbin/agetty 38400 vc/4 linux
    c5:2345:respawn:/sbin/agetty 38400 vc/5 linux
    c6:2345:respawn:/sbin/agetty 38400 vc/6 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    x:5:respawn:/usr/bin/slim >& /dev/null
    # End of file

    Same problem here.
    I have this problem since 2007-10-14 and can't find a solution.
    There was a huge update amongst others "xkeyboard-config (0.9-2 -> 1.0-1)", and I think there is the problem.
    I use slim too, but I don't believe slim is the problem.
    EDIT:
    After a try ctrl-alt-backspace, my slim.log says this:
    X Window System Version 7.2.0
    Release Date: 22 January 2007
    X Protocol Version 11, Revision 0, Release 7.2
    Build Operating System: UNKNOWN
    Current Operating System: Linux arch 2.6.23-ARCH #1 SMP PREEMPT Sat Oct 27 09:04:14 UTC 2007 i686
    Build Date: 08 April 2007
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 30 21:44:55 2007
    (==) Using config file: "/etc/X11/xorg.conf"
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    /usr/bin/xauth: creating new authority file /home/jean/.Xauthority
    Warning: Only changing the first 14 of 20 buttons.
    ** Message: This build doesn't include support for XF86Misc extension
    ** Message: Querying Xkb extension
    ** Message: Xkb extension found
    ** Message: Querying Xkb extension
    ** Message: Xkb extension found
    Conky: desktop window (1000003) is subwindow of root window (1a5)
    Conky: window type - override
    Conky: drawing to created window (1800001)
    Conky: drawing to double buffer
    (xfwm4:8279): libxfcegui4-WARNING **: ICE I/O Error
    (xfwm4:8279): libxfcegui4-WARNING **: Disconnected from session manager.
    xfce-mcs-manager: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
    xfwm4: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
    xfdesktop: Fatal IO error 104 (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) on X server :0.0.
    xfce4-panel: Fatal IO error 4 (Unterbrechung während des Betriebssystemaufrufs) on X server :0.0.
    terminal: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.0.
    FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 3, should be 1; fixing.
    /usr/bin/xauth: creating new authority file /var/run/slim.auth
    Jean-Paul
    Last edited by jean-paul (2007-10-31 22:17:14)

  • [SOLVED] Ctrl+Alt+Backspace Wont restart X

    It just does nothing, is it disabled somewhere somehow?  I used to work before, broke from upgrade or something?
    Last edited by degmic71 (2009-04-15 13:45:54)

    man xorg
    Ctrl+Alt+Backspace
    Immediately kills the server -- no questions asked. This is
    disabled by default. It can be enabled with the -retro command
    line flag or by setting the DontZap xorg.conf(5) file option to
    a FALSE value.
    add this to you xorg.conf
    Section "serverFlags"
    Option "DontZap" "false"
    EndSection

  • 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)

  • Change Ctrl+Alt+Backspace to something else

    Hi
    Is there any way to change the Ctrl+Alt+Backspace key combination in X to something else, e.g. Ctrl+Alt+Windows+Backspace?
    Note that I don't want to disable the "zapping" behavior by changing DontZap, but simply change the combination.

    This _looks_ like it, but doesn't really make a lot of sense:
    xmodmap -pke | grep BackSpace
    keycode  22 = BackSpace Terminate_Server BackSpace Terminate_Server BackSpace Terminate_Server
    The first keysym is used when no modifier key is pressed in conjunction with this key, the second with Shift, the third when the Mode_switch key is used with this key and the fourth when both the Mode_switch and Shift keys are used. The last four are not used in any major X server implementation.

  • R60 shouts at me when pressing [ctrl+alt+backspace] in openSUSE

    Whenever I try to restart the X server in openSUSE 11.3, as I like to do with the [ctrl+alt+backspace]-shortcut, I just get a loud *beep* from the onboard speaker and nothing happens. I tried booting into Windows and pressing the key combination, same thing.
    Help?

    Are you getting the same beep from Windows?Or is it only OpenSuse?
    Every time I restart the system my 3000H system also gives me a loud beep from the board.Your X server might not be supported by the GPU which is causing the system to give out the beep sound..
    Cheers and regards,
    • » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
    ●๋•کáŕádhí'ک díáŕý ツ
    I am a volunteer here. I don't work for Lenovo

  • Something on my Gnome-Settings prevents Ctrl-Alt-Backspace

    Hi
    It is quite strange - I have Dontzap disabled in my xorg.conf, I told hal to zap X properly and added setxkbmap -option terminate:ctrl_alt_bksp to my .xinitrc.
    But when I log into a Gnome session I won't have a chance to use this key combination. The weird thing about this is that it only happens when I am logged in with my username and use Gnome. Using another user with Gnome or starting another wm with my username works perfectly.
    slightly confused
             strigyskow

    I can confirm there is something in gnome preventing from restarting x with ctrl-alt-backspace. I have both don't zap set in xorg.conf as adjusted my fdi keyboard file. I know that the configuration works because i can use ctrl-alt-backspace in the gdm login screen and xmonad, but in gnome. Executing setxkbmap after gnome has been started (more or less) solves the problem.

  • Ctrl+alt+backspace does not kill X

    I ran
    # nvidia-xconfig --logo-path=
    to set the logo that X starts with, but now I cannot kill X with the normal ctrl+alt+backspace.

    The point of users never reading stickies is just as valid . It is a good suggestion, but it will get lost in the myriad of stickies anyway - stickies that, by experience, everyone overlooks.
    Those who know where to look (and search) will find it - stickied or not. As said: there's coverage in the Arch wiki, on the BBS, and even on the world wide web.
    If you have SysRq enabled, you can always do AltGr + SysRq + K to restart X if needed.
    http://en.wikipedia.org/wiki/Magic_SysRq_key
    We're not stickying it, the information is all over the place. There's no point in discussing this.

  • 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)

  • [Solved]No X, No Ctrl+Alt+Backspace, cant get to console...HELP!

    I did a new install and went for the ext4 option, I installed everything I usually do but went with nvidia-xcofig rather than the usual Xorg -configure, now having set everything up all I get is a blank screen, I cant ctrl alt backspace to get to console and mt laptop just reboots after about 10 seconds or so.
    I have Mint installed on another partition hoping that I could get into rc.conf and ! out gdm but ext4 isn't supported! lol
    What do I do, I'm well and truely stumped!
    I left arch for 4 days as I got tired of things breaking but had to come back, I miss my arch, well until this peach of a problem came up
    Thanks
    Last edited by Andy Mack (2009-03-10 15:39:08)

    What would I need to edit rc.conf for?
    to comment out gdm!!
    I hope you have installed hal and  read the news about disabling autoadddevices, enabling ctrl alt backspace with DontZap etc

  • Kill Session with Ctrl+Alt+backspace+backspace, doens't kill but disconnect

    I've got 4 Oracle Solaris servers with SRS 5.1.2 installed. The servers are configured in failover configured in SRS. When I try to kill (terminate) a session with Ctrl+Alt+backspace+backspace the session will not be terminate. Instead of killing it will be in the state of disconnected on the Sun Ray Administration. I can only terminate the session if I'm on the Sun Ray Administration by selecting the session and click terminate. Does anybody has the same issue, if the sun ray servers are configured as failover?

    A simple google for "terminate:ctrl_alt_bksp" yields https://bbs.archlinux.org/viewtopic.php?pid=602885 as the first hit.
    You could also use an xorg configuration file as is mentioned in the link you posted (a bit higher than the part you linked) and there is an entry for "XkbOptions".

  • SRSS2.0 Sunray150 hangs at 26D after ctrl-alt-backspace-backspace

    After ctrl-alt-backspace-backspace the Sunray terminal (DTU) resets and intermittently hangs at 26D.
    Ctrl+moon has no effect. The only way to rectify is to remove the session, using utsession -k -t <token>.
    Software; SRSS2.0, Solaris 9 04/04, Sparc.

    If the sessions being killed are normal desktop login sessions then the dtlogin daemon should start a new X server for the session. Make sure that you have the most recent dtlogin patch installed. For Solaris 9 on SPARC that's patch 112807-17.
    If the sessions being killed are some other kind of session, perhaps CAM or NSCM,
    then make sure that you have the most recent SRSS patches installed or, even better,
    upgrade to a newer release of SRSS. 2.0 is old; 3.1 is current.
    OttoM.

  • X not terminated by ctrl+alt+backspace

    Whenever I hit ctrl+alt+backspace, it does not kill X. I have the serverflag DontZap set to false, but it still won't work.

    scv5 wrote:
    i thought you could put this in your xorg.conf and it would work? (not able to test right now)
    Section "ServerFlags"
    Option "DontZap" "false"
    EndSection
    In addition you need to add either:
    <merge key="input.xkb.options" type="string">terminate:ctrl_alt_bksp</merge>
    to the keyboard fdi file or run
    setxkbmap -option terminate:ctrl_alt_bksp
    as is indicated in the wiki.

  • Latest xkeyboard-config prevents ctrl-alt-backspace from killing X

    well, as I wrote in the topic latest xkeyboard-config (1.6-1) is preventing ctrl-alt-backspace combination from killing X.  I have DonZap option set to false in my xorg.conf. I don't know if it should be like that. Is it a bug? If not, is it any workaround to make it work again?

    karol wrote:@whoops
    How did you get that magic spell? RTFM or sth else?
    I searched for stuff in google, opened a lot of tabs and somewhere in between there was a site about some patch that said something like "this patch removes the ctrl+alt+backspace keyboard shortcut in xorg - to reenable it, you have to type...".
    So I pasted it into a terminal, hit strg+alt+backspace and it worked. Which is why I don't know, where I found that Information.
    Might have been an ubuntu patch... maybe I should have mentioned that (in case someone added an ubuntu patch to xorg recently to make it "safer" and this is the result...?). edit: no, it wasn't - just found the ubuntu page I was on, and the information isn't from there. But it was on a patch site. Mostly plain text, code, patch info & lots of stuff I didn't understand.
    edit2: Aaaah, there it was: http://lists.freedesktop.org/archives/x … 00627.html
    Last edited by whoops (2009-05-29 21:41:33)

Maybe you are looking for