Startx linux error

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1]   Вверх

0

1

[    94.590] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[    94.590] X Protocol Version 11, Revision 0
[    94.590] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[    94.590] Current Operating System: Linux alx64 4.9.0-0.bpo.2-amd64 #1 SMP Debian 4.9.13-1~bpo8+1 (2017-02-27) x86_64
[    94.590] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.2-amd64 root=UUID=10a8345e-0e1c-4ac3-8ae5-a097be1539e8 ro single nomodeset nouveau.modeset=0
[    94.591] Build Date: 11 February 2015  12:32:02AM
[    94.591] xorg-server 2:1.16.4-1 (http://www.debian.org/support) 
[    94.591] Current version of pixman: 0.32.6
[    94.591] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    94.591] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    94.592] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun  2 13:43:27 2017
[    94.593] (==) Using config file: "/etc/X11/xorg.conf"
[    94.593] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    94.593] (==) ServerLayout "X.org Configured"
[    94.593] (**) |-->Screen "Screen0" (0)
[    94.593] (**) |   |-->Monitor "Monitor0"
[    94.593] (**) |   |-->Device "Card0"
[    94.593] (==) Automatically adding devices
[    94.593] (==) Automatically enabling devices
[    94.593] (==) Automatically adding GPU devices
[    94.593] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    94.593] 	Entry deleted from font path.
[    94.593] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[    94.593] (==) ModulePath set to "/usr/lib/xorg/modules"
[    94.593] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    94.593] (II) Loader magic: 0x56232cee2d80
[    94.593] (II) Module ABI versions:
[    94.593] 	X.Org ANSI C Emulation: 0.4
[    94.593] 	X.Org Video Driver: 18.0
[    94.593] 	X.Org XInput driver : 21.0
[    94.593] 	X.Org Server Extension : 8.0
[    94.594] (II) xfree86: Adding drm device (/dev/dri/card0)
[    94.595] (--) PCI:*(0:1:0:0) 10de:0de1:10b0:0401 rev 161, Mem @ 0xfd000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000d800/128, BIOS @ 0x????????/131072
[    94.595] (II) LoadModule: "glx"
[    94.595] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    94.596] (II) Module glx: vendor="X.Org Foundation"
[    94.596] 	compiled for 1.16.4, module version = 1.0.0
[    94.596] 	ABI class: X.Org Server Extension, version 8.0
[    94.596] (==) AIGLX enabled
[    94.596] (II) LoadModule: "nvidia"
[    94.597] (WW) Warning, couldn't open module nvidia
[    94.597] (II) UnloadModule: "nvidia"
[    94.597] (II) Unloading nvidia
[    94.597] (EE) Failed to load module "nvidia" (module does not exist, 0)
[    94.597] (EE) No drivers available.
[    94.597] (EE) 
Fatal server error:
[    94.597] (EE) no screens found(EE) 
[    94.597] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    94.598] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    94.598] (EE) 

1. Problems with startx
   

   I’m setting up a new ubuntu box to act as a home web server and I believe I messed something up.

   I’m a semi-newbie and I’m not sure how to explain the problem, so I’ll simply say what I wanted to do, what I did and the result.

   What I wanted to do:
   Have the ability to telnet into this machine and start xwindows so I can later vnc into it when I wished. Basically the only thing I wanted to do is startx so it would use the machine’s physical display, keyboard, mouse, ect and allow me to connect via vnc later if I wanted it to.

   What I did:
   I telneted in from a windows machine and attempted startx (I knew this would most likely try to use my windows machine as the display and would kick out an error, but I figured it was worth a shot.
   I then tried startx &. No luck there either. I then tried sudo startx. I think that’s where I screwed something up.

   Result:
   Now, not only does it not work, but if I attempt to startx on the machine normally I get a blank screen.

   I understand that I most likely somehow set the display incorrectly but I have no idea how to fix this.

   Can I get some help with both fixing my screwup and getting things to work as I originally wanted?

   ---

2. Re: Problems with startx
   

   Originally Posted by Ghosthaven
   

   Result:
   Now, not only does it not work, but if I attempt to startx on the machine normally I get a blank screen.

   Check «/var/log/Xorg.0.log» for error messages.

   Also, why don’t you simply set it up to run startx at startup?
   This way you wouldn’t have to find a way to launch it through the remote machine.

   ---

3. Re: Problems with startx
   

   I want to run it without a gui most of the time to conserve resources but I want to be able to vnc into x when I want to as well.

   As far as the log file… its pretty much all greek to me.
   I’m attaching it here so hopefully one of you gurus can help me
   figure out whats wrong. (added the .doc extension so I could upload it)

   I really don’t want to have to wipe the drive and start from scratch.

   ---

4. Re: Problems with startx
   

   I figured you have Maverick 10.10 installed, right?

   1.) There is an error message (although not stated as such) that a video driver library file is missing.

   2.) The xserver apparently thinks all is well, but in fact nothing gets displayed.

   Conclusion: It seems to an issue with the video driver (nouveau), and not related to the previous launch of startx with sudo.

   Suggestion: Upgrade the video driver through Xorg-Edgers’ PPA, it offers more recent drivers than the offical repos:
   https://launchpad.net/~xorg-edgers/+archive/ppa

   Code:

   sudo add-apt-repository ppa:xorg-edgers/ppa
   sudo apt-get update
   sudo apt-get upgrade

   ---

5. Re: Problems with startx
   

   Yes, I have 10.10 installed. Actually a server install with the
   ubuntu-desktop package installed on top of it.

   I don’t understand how it could be a driver issue, as X was
   working perfectly fine before. I did what you said though with
   no change.

   I am able to reproduce the effect in a virtual machine. Telneting
   into a ubuntu 10.10 box from windows xp and running sudo startx
   will reproduce the problem.

   I noticed something new in the VM (and later confirmed on the
   actual server) if left long enough, it’ll time out and scroll a
   good bit of text over the screen thats not in the logs. I didn’t
   see all of it but I did get the end of it from the VM:

   Code:

   ..
   No protocol specified
   ..
   No protocol specified
   ..
   No protocol specified
   ..
   No protocol specified
   ..
   No protocol specified
   ..
   No protocol specified
   ..
   No protocol specified
   ..
   giving up.
   xinit: Resource temporarily unavailable (errno 11): unable to connect to X server
   
   waiting for X server to shut down error setting MTRR (base = 0xe0000000, size = 0x04000000, type = 1) Invalid argument (22)
    ddxSigGiveUp: Closing log
   xinit: Server error.
   xauth: error in locking authority file /home/andy/.Xauthority

   Then it drops me back to my shell. To be clear, this is from
   running startx from the virtual machine’s main screen. Not from
   telnet.

   I also copied the output of my sudo startx over telnet attempt
   that actually caused this error on the VM:

   Code:

   X.Org X Server 1.9.0
   Release Date: 2010-08-20
   X Protocol Version 11, Revision 0
   Build Operating System: Linux 2.6.24-28-server i686 Ubuntu
   Current Operating System: Linux virtual-server 2.6.35-28-generic-pae #49-Ubuntu
   SMP Tue Mar 1 14:58:06 UTC 2011 i686
   Kernal command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic-pae root=UUID=ce56f82e-5bb5-42c2-9358-bb9b2723a3d3 ro quiet
   Build Date: 09 January 2011 12:14:58PM
   xorg-server 2:1.9.0-0ubuntu7.3 (For technical support please see http://www.ubun
   tu.com/support)
   Current version of pixman: 0.18.4
           Before reporting problems, check http://wiki.x.org
           to make sure that you have the latest version.
   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: Thu Mar 31 10:46:13 2011
   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
   (EE) Failed to load module "vboxvideo" (module does not exist, 0)
   (EE) open /dev/fb0: No such file or directory
   (EE) VirtualBox USB Tablet: failed to initialize for relative axes.
   ^C
   waiting for X server to shut down error setting MTRR (base = 0xe0000000, size =
   0x04000000, type = 1) Invalid argument (22)
    ddxSigGiveUp: Closing log

   At this point it started X normally on the main display of the VM
   as I wanted, but I wanted to reproduce what I did on the actual
   server so in the telnet window I terminated with ctrl+c and got
   this:

   Code:

   xinit:  unexpected signal 2.

   I don’t know what exactly is going on. I’m guessing that either
   some permissions were changed when I ran it with sudo, or its
   now looking for that .Xauthority file in root somewhere or…
   I don’t know.

   UPDATE:
   It seems I CAN run X from both the vm and the server if I use
   sudo… this proves that its screwing up permissions or something… right? How do I correct this?

   Side note: It seems that installing those updated drivers that
   Krytarik recommended totally messed up X’s display on the server.
   Is there a way I can rollback to the previous drivers without
   reinstalling everything?

   ---

6. Re: Problems with startx
   

   Ok, now we have a somewhat clearer picture.

   It maybe that when you did run startx with sudo, that changed the ownership of «/home/andy/.Xauthority» to those of root. Check that, and if so, revert it to yourself.

   As for the nouveau driver, it is still under development, and thus may cause issues at some systems or setups.
   So, would you like to install the proprietary driver instead?

   If you want to purge Xorg-Edgers’ PPA and downgrade all concerning packages, you could use the tool «ppa-purge» for that:

   Code:

   sudo apt-get install ppa-purge
   sudo ppa-purge ppa:xorg-edgers/ppa

   However, if you choose to use the proprietary driver, you shouldn’t remove the PPA, since it also offers the most recent version of those.

   To install those, assuming that you don’t have it already installed, you could run:

   Code:

   sudo apt-get install nvidia-current

   Make sure that a proper xorg.conf is present:

   Code:

   sudo nvidia-xconfig --add-argb-glx-visuals --no-logo --force-generate

   But if you are able to get to the desktop after possibly fixing the mentioned file permissions, you should install it via «System -> Administration -> Additional Drivers».

   ---

7. Re: Problems with startx
   

   I am having similar problems.

   However, mine started with some update or other. I had 10.10, 8.04 and PinguyOS 10.01 installed.

   Pinguy was the first to abort the GUI on startup. I had similar problems when trying startx. Then, 10.10 did the same to me. Working one day, no GUI next. So I started 8.04. It worked. Tried to upgrade to 10.04. Had errors about Nvidia driver show up. Won’t show GUI. Same starx problems

   Unfortunately, I then erased all the Linux’s (yes, I’m a newbie) and tried to reload from CD.

   Same problem on startup — no GUI So -I can’t display the log files, since none are created.

   System. HP Pavilion m9040n Nvidia Gforce 8400

   Knoppix still loads and runs, so it seems to be a problem with the current Nvidia driver included in the CD (or update).

   Any suggestions as how to get a working driver onto the ISO?

   ---

8. Re: Problems with startx
   

   Got everything fixed For some reason it did change the ownership
   of .Xauthority.

   I went ahead and did the ppa_purge thing but after everything got
   working I installed the new drivers via the GUI.

   Now that you’ve helped me fix my screwups… is there a way to do
   what I originally wanted and trigger X to start on the main
   display?

   The only way I can figure out to do it is really insane… a shell
   script to add a cron job to startx in 1 minute… or something like
   that.

   Being a newbie sucks

   ---

9. Re: Problems with startx
   

   @FOBS1: Your issue is actually quite different to those this thread is basically about. Although Ghosthaven indeed had a temporary issue with running Xwindows (GUI) at all, just like you, it is basically about launching startx through remote control.

   But nevertheless I will give a first shot: Try adding «nomodeset» to the kernel boot options. To do so, edit the kernel options while at the boot menu, you need to press the Shift key to make it appear, if you have only those single Ubuntu installed. Highlight the first boot option, that is usually the most recent kernel, then press «e» to edit its options. Add «nomodeset» right after «quiet splash», then press «Ctrl+X» to boot with those options. Those modification affects only those single boot process, it will not get saved.
   Also see here: https://help.ubuntu.com/community/Gr…0During%20Boot

   If that works, you can set those option permanently by following this guide, add it again right after «quiet splash» as the value for «GRUB_CMDLINE_LINUX_DEFAULT»:
   https://help.ubuntu.com/community/Grub2#/etc/default/grub%20(file)

   If that doesn’t work and you need more help, please start an own thread about that matter.

   Also, the default driver being used during and right after the installation isn’t the proprietary Nvidia driver, it isn’t even included by the installCD. Your issue is actually more about the basic handling of your video card.

   __________________________________________________ _________________________________________________

   @Ghosthaven: Keep in mind that, like I said, that Xorg-Edgers’ PPA offers the most recent packaged version of the proprietary driver. So, if you at any later time want to upgrade to those, you know the proper commands for that.

   As for your actual startx launch matter, try this command:

   Code:

   DISPLAY=:0.0 startx

   Hope it works, for both of you!

   Last edited by Krytarik; March 31st, 2011 at 08:30 PM.

   ---

10. Re: Problems with startx
    

    Thank you Krytarik, for your thoughtful reply.

    While working with your suggestions, I saw some errors that referenced my wacom (tablet) drivers. I unplugged that tablet and things proceeded properly. I feel a bit silly, but am happy to be proceeding again.

    ---

Section "InputClass"
    Identifier "SynPS/2 Synaptics TouchPad"
    Driver "libinput"
    MatchIsTouchpad "on"
    Option "TapButton1" "1"
    Option "TapButton2" "3"
    Option "TapButton3" "2"

[ 15516.038] (WW) Failed to open protocol names file lib/xorg/protocol.txt
[ 15516.038] 
X.Org X Server 1.20.0
X Protocol Version 11, Revision 0
[ 15516.038] Build Operating System: Linux Arch Linux
[ 15516.038] Current Operating System: Linux sys76-gazelle 4.17.5-1-ARCH #1 SMP PREEMPT Sun Jul 8 17:27:31 UTC 2018 x86_64
[ 15516.038] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/VolGroup00-lvolroot rw cryptdevice=/dev/sda3:VolGroup00 resume=/dev/VolGroup00/lvolswap quiet acpi_os_name=Linux acpi_osi=
[ 15516.038] Build Date: 18 June 2018  03:12:37PM
[ 15516.038]  
[ 15516.039] Current version of pixman: 0.34.0
[ 15516.039] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 15516.039] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15516.039] (==) Log file: "/home/daniel/.local/share/xorg/Xorg.0.log", Time: Sun Jul 15 00:07:25 2018
[ 15516.039] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 15516.039] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 15516.042] (==) No Layout section.  Using the first Screen section.
[ 15516.042] (==) No screen section available. Using defaults.
[ 15516.042] (**) |-->Screen "Default Screen Section" (0)
[ 15516.042] (**) |   |-->Monitor "<default monitor>"
[ 15516.043] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 15516.043] (==) Automatically adding devices
[ 15516.043] (==) Automatically enabling devices
[ 15516.043] (==) Automatically adding GPU devices
[ 15516.043] (==) Automatically binding GPU devices
[ 15516.043] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 15516.045] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[ 15516.045] 	Entry deleted from font path.
[ 15516.045] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[ 15516.045] 	Entry deleted from font path.
[ 15516.046] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/100dpi,
	/usr/share/fonts/75dpi
[ 15516.046] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 15516.046] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 15516.046] (II) Module ABI versions:
[ 15516.046] 	X.Org ANSI C Emulation: 0.4
[ 15516.046] 	X.Org Video Driver: 24.0
[ 15516.046] 	X.Org XInput driver : 24.1
[ 15516.046] 	X.Org Server Extension : 10.0
[ 15516.048] (++) using VT number 1

[ 15516.051] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
[ 15516.053] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 15516.054] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0
[ 15516.058] (--) PCI:*(0@0:2:0) 8086:591b:1558:8509 rev 4, Mem @ 0xde000000/16777216, 0xa0000000/536870912, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[ 15516.058] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 15516.058] (II) LoadModule: "glx"
[ 15516.058] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 15516.070] (II) Module glx: vendor="X.Org Foundation"
[ 15516.070] 	compiled for 1.20.0, module version = 1.0.0
[ 15516.070] 	ABI class: X.Org Server Extension, version 10.0
[ 15516.070] (==) Matched intel as autoconfigured driver 0
[ 15516.070] (==) Matched modesetting as autoconfigured driver 1
[ 15516.070] (==) Matched fbdev as autoconfigured driver 2
[ 15516.070] (==) Matched vesa as autoconfigured driver 3
[ 15516.070] (==) Assigned the driver to the xf86ConfigLayout
[ 15516.070] (II) LoadModule: "intel"
[ 15516.070] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 15516.076] (II) Module intel: vendor="X.Org Foundation"
[ 15516.076] 	compiled for 1.20.0, module version = 2.99.917
[ 15516.076] 	Module class: X.Org Video Driver
[ 15516.076] 	ABI class: X.Org Video Driver, version 24.0
[ 15516.076] (II) LoadModule: "modesetting"
[ 15516.076] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 15516.079] (II) Module modesetting: vendor="X.Org Foundation"
[ 15516.079] 	compiled for 1.20.0, module version = 1.20.0
[ 15516.079] 	Module class: X.Org Video Driver
[ 15516.079] 	ABI class: X.Org Video Driver, version 24.0
[ 15516.079] (II) LoadModule: "fbdev"
[ 15516.080] (WW) Warning, couldn't open module fbdev
[ 15516.080] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 15516.080] (II) LoadModule: "vesa"
[ 15516.080] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 15516.081] (II) Module vesa: vendor="X.Org Foundation"
[ 15516.081] 	compiled for 1.20.0, module version = 2.4.0
[ 15516.081] 	Module class: X.Org Video Driver
[ 15516.081] 	ABI class: X.Org Video Driver, version 24.0
[ 15516.081] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 15516.082] (II) intel: Driver for Intel(R) HD Graphics
[ 15516.082] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 15516.082] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 15516.082] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 15516.082] (II) VESA: driver for VESA chipsets: vesa
[ 15516.082] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[ 15516.083] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20180308
[ 15516.083] (II) intel(0): SNA compiled from 2.99.917-831-ge7bfc906
[ 15516.099] (WW) Falling back to old probe method for modesetting
[ 15516.099] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 15516.100] (--) intel(0): gen9 engineering sample
[ 15516.100] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 4 threads
[ 15516.100] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[ 15516.100] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 15516.100] (==) intel(0): RGB weight 888
[ 15516.100] (==) intel(0): Default visual is TrueColor
[ 15516.102] (II) intel(0): Output eDP1 has no monitor section
[ 15516.103] (**) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[ 15516.103] (II) intel(0): Enabled output eDP1
[ 15516.103] (II) intel(0): Output DP1 has no monitor section
[ 15516.103] (II) intel(0): Enabled output DP1
[ 15516.103] (II) intel(0): Output HDMI1 has no monitor section
[ 15516.104] (II) intel(0): Enabled output HDMI1
[ 15516.104] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 15516.104] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 15516.104] (II) intel(0): Enabled output VIRTUAL1
[ 15516.104] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[ 15516.104] (==) intel(0): TearFree disabled
[ 15516.104] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 15516.104] (==) intel(0): DPI set to (96, 96)
[ 15516.104] (II) Loading sub module "dri3"
[ 15516.104] (II) LoadModule: "dri3"
[ 15516.104] (II) Module "dri3" already built-in
[ 15516.104] (II) Loading sub module "dri2"
[ 15516.104] (II) LoadModule: "dri2"
[ 15516.104] (II) Module "dri2" already built-in
[ 15516.104] (II) Loading sub module "present"
[ 15516.104] (II) LoadModule: "present"
[ 15516.104] (II) Module "present" already built-in
[ 15516.104] (II) UnloadModule: "modesetting"
[ 15516.104] (II) Unloading modesetting
[ 15516.105] (II) UnloadModule: "vesa"
[ 15516.105] (II) Unloading vesa
[ 15516.108] (II) intel(0): SNA initialized with Kabylake (gen9) backend
[ 15516.108] (==) intel(0): Backing store enabled
[ 15516.108] (==) intel(0): Silken mouse disabled
[ 15516.108] (II) intel(0): HW Cursor enabled
[ 15516.108] (==) intel(0): DPMS enabled
[ 15516.108] (==) intel(0): Display hotplug detection enabled
[ 15516.109] (II) intel(0): [DRI2] Setup complete
[ 15516.109] (II) intel(0): [DRI2]   DRI driver: i965
[ 15516.109] (II) intel(0): [DRI2]   VDPAU driver: va_gl
[ 15516.109] (II) intel(0): direct rendering: DRI2 DRI3 enabled
[ 15516.109] (II) intel(0): hardware support for Present enabled
[ 15516.109] (II) Initializing extension Generic Event Extension
[ 15516.109] (II) Initializing extension SHAPE
[ 15516.109] (II) Initializing extension MIT-SHM
[ 15516.109] (II) Initializing extension XInputExtension
[ 15516.109] (II) Initializing extension XTEST
[ 15516.109] (II) Initializing extension BIG-REQUESTS
[ 15516.109] (II) Initializing extension SYNC
[ 15516.109] (II) Initializing extension XKEYBOARD
[ 15516.109] (II) Initializing extension XC-MISC
[ 15516.109] (II) Initializing extension SECURITY
[ 15516.109] (II) Initializing extension XFIXES
[ 15516.109] (II) Initializing extension RENDER
[ 15516.109] (II) Initializing extension RANDR
[ 15516.109] (II) Initializing extension COMPOSITE
[ 15516.109] (II) Initializing extension DAMAGE
[ 15516.109] (II) Initializing extension MIT-SCREEN-SAVER
[ 15516.109] (II) Initializing extension DOUBLE-BUFFER
[ 15516.109] (II) Initializing extension RECORD
[ 15516.109] (II) Initializing extension DPMS
[ 15516.109] (II) Initializing extension Present
[ 15516.109] (II) Initializing extension DRI3
[ 15516.109] (II) Initializing extension X-Resource
[ 15516.109] (II) Initializing extension XVideo
[ 15516.109] (II) Initializing extension XVideo-MotionCompensation
[ 15516.109] (II) Initializing extension GLX
[ 15516.168] (II) AIGLX: Loaded and initialized i965
[ 15516.168] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 15516.168] (II) Initializing extension XFree86-VidModeExtension
[ 15516.168] (II) Initializing extension XFree86-DGA
[ 15516.168] (II) Initializing extension XFree86-DRI
[ 15516.168] (II) Initializing extension DRI2
[ 15516.175] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 15516.185] (II) intel(0): Setting screen physical size to 508 x 285
[ 15516.236] (EE) XKB: Couldn't open rules file /usr/share/X11/xkb/rules/evdev
[ 15516.236] (EE) XKB: Failed to load keymap. Loading default keymap instead.
[ 15516.236] (EE) XKB: Couldn't open rules file /usr/share/X11/xkb/rules/evdev
[ 15516.236] XKB: Failed to compile keymap
[ 15516.236] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
[ 15516.236] (EE) 
Fatal server error:
[ 15516.236] (EE) Failed to activate virtual core keyboard: 2(EE) 
[ 15516.236] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[ 15516.236] (EE) Please also check the log file at "/home/daniel/.local/share/xorg/Xorg.0.log" for additional information.
[ 15516.236] (EE) 
[ 15516.236] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 15516.272] (EE) Server terminated with error (1). Closing log file.