Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
0 answers
19 views
Debian Trixie, xorg: No acceleration using intel driver
I used intel xorg driver (xserver-xorg-video-intel) plus i965-va-driver on Debian Bookworm; everything worked fine, 2D, 3D, video acceleration. After updating to Trixie, intel xorg driver (same setup as bookworm) doesn't provide acceleration. glxinfo shows LLVMpipe instead of Mesa Intel(R) HD Graphi...
I used intel xorg driver (xserver-xorg-video-intel) plus i965-va-driver on Debian Bookworm; everything worked fine, 2D, 3D, video acceleration. After updating to Trixie, intel xorg driver (same setup as bookworm) doesn't provide acceleration. glxinfo shows LLVMpipe instead of Mesa Intel(R) HD Graphics 630 (KBL GT2) (that's the graphic device on my laptop). I switched to modesetting as suggested for years on Debian; 2D, 3D acceleration works fine on modesetting, but as expected, I have screen tearing on videos. I'd prefer to avoid xorg compositors. Wayland is not an option for me due to certain apps I use and still don't work well on it. Any ideas how to have acceleration using intel driver on Trixie, as in Bookworm?
Krackout (2887 rep)
Aug 3, 2025, 06:38 AM
1 votes
2 answers
3201 views
xorg keyboard config not working (us altgr-intl no deadkeys)
I'm trying to get my keyboard to use the us layout with variation altr-intl and no deadkeys. Somehow my xorg-keyboard-config does not take effect. I looked up the config here [arch-wiki][1] but there seems to be a mistake in my config which I was unable to find. My current (not working) config looks...
I'm trying to get my keyboard to use the us layout with variation altr-intl and no deadkeys. Somehow my xorg-keyboard-config does not take effect. I looked up the config here arch-wiki but there seems to be a mistake in my config which I was unable to find. My current (not working) config looks like this: /etc/X11/xorg.conf.d/00-keyboard.conf # Written by systemd-localed(8), read by systemd-localed and Xorg. It's # probably wise not to edit this file manually. Use localectl(1) to # instruct systemd-localed to update it. Section "InputClass" Identifier "system-keyboard" MatchIsKeyboard "on" Option "XkbLayout" "us" Option "XkbModel" "pc105" Option "XkbVariant" "altgr-intl" Option "XkbOptions" "nodeadkeys" EndSection I get it to work by using the following command but as you might know this is not persistent: setxkbmap -layout us -variant altgr-intl -option nodeadkeys I don't want this command to end up in my xprofile file or such. I would prefere to do it in xorg as I did with my trackpad, mouse ect. The keyboard I'm using is a keychron k2 connected by cable. Here is the output of xinput, in case the keyboard doesn't get identified correclty: xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Synaptics TM3053-003 id=11 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=12 [slave pointer (2)] ⎜ ↳ Keytron Keychron K2 id=15 [slave pointer (2)] ⎜ ↳ Logitech Wireless Mouse id=17 [slave pointer (2)] ⎜ ↳ Logitech Wireless Keyboard PID:4023 id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)] ↳ ThinkPad Extra Buttons id=10 [slave keyboard (3)] ↳ Keytron Keychron K2 id=13 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=14 [slave keyboard (3)] ↳ Keytron Keychron K2 id=16 [slave keyboard (3)] ↳ Logitech Wireless Keyboard PID:4023 id=19 [slave keyboard (3)] I tried to identify the keyboard by using "MatchIsProduct" "Keytron Keychron K2" without any luck either. I'm running manjaro i3 community edition. The keyboard settings set in the manjaro-settings are also the wanted layout so I don't think that these settings would mess up my xorg config. I'm trying this on a thinkpad T550. With the current config I get the us keyboard without deadkeys but the altgr-intl variant is not active.
Elfie (111 rep)
Oct 20, 2021, 06:55 PM • Last activity: Jul 31, 2025, 10:07 AM
2 votes
2 answers
3463 views
Xorg and xrandr detect a connected monitor that doesn't exist
I'm on a laptop with no additional monitors connected, but when I run `xrandr -q`, the output lists two connected devices. Xfce's Display settings dialog also shows two monitors, and so does Xorg.0.log. Here's the `xrandr -q` output: ```Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384...
I'm on a laptop with no additional monitors connected, but when I run xrandr -q, the output lists two connected devices. Xfce's Display settings dialog also shows two monitors, and so does Xorg.0.log. Here's the xrandr -q output:
0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     60.00*+  59.97    59.96    59.93    48.00  
   1680x1050     59.95    59.88  
   1600x1024     60.17  
   (omitting many more resolutions)
DP-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      60.00*  
   800x600       60.32    56.25  
   848x480       60.00  
   640x480       59.94  
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
Is this normal? If not, what can I do to remove this imaginary monitor? Restarting the laptop (with no external monitors connected at any point) doesn't change anything. (My guess it that something about this is causing a weird display problem I have - my login screen starts at the wrong resolution, and afterward the resolution gets corrected but the virtual desktop sizes are wrong.) Here are related Xorg.0.log lines - DP-1 (the imaginary monitor) does not have an EDID, but it is listed as connected with initial mode 1024x768, and also seems to somehow cause eDP-1 (the actual laptop monitor) to use initial mode 1024x768 instead of 1920x1080; then it gets classified as a keyboard for some reason:
[    13.093] (II) modeset(0): Output eDP-1 has no monitor section
[    13.921] (II) modeset(0): Output DP-1 has no monitor section
[    13.921] (II) modeset(0): Output DP-2 has no monitor section
[    13.921] (II) modeset(0): Output DP-3 has no monitor section
[    13.923] (II) modeset(0): EDID for output eDP-1
[    13.923] (II) modeset(0): Manufacturer: BOE  Model: 853  Serial#: 0
[    13.923] (II) modeset(0): Year: 2018  Week: 48
[    13.923] (II) modeset(0): EDID Version: 1.4
(skipping a bunch more EDID information for eDP-1)
[    13.924] (II) modeset(0): Printing probed modes for output eDP-1
[    13.924] (II) modeset(0): Modeline "1920x1080"x60.0  141.72  1920 1968 2000 2124  1080 1083 1089 1112 +hsync -vsync (66.7 kHz eP)
[    13.924] (II) modeset(0): Modeline "1920x1080"x119.9  266.50  1920 1944 1960 2000  1080 1081 1084 1111 doublescan +hsync -vsync (133.2 kHz d)
[    13.924] (II) modeset(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz d)
(skipping a lot more modelines for eDP-1)
[    14.754] (II) modeset(0): EDID for output DP-1
[    14.754] (II) modeset(0): Printing probed modes for output DP-1
[    14.755] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    14.755] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    14.755] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    14.755] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    14.755] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    14.755] (II) modeset(0): EDID for output DP-2
[    14.755] (II) modeset(0): EDID for output DP-3
[    14.755] (II) modeset(0): Output eDP-1 connected
[    14.755] (II) modeset(0): Output DP-1 connected
[    14.755] (II) modeset(0): Output DP-2 disconnected
[    14.755] (II) modeset(0): Output DP-3 disconnected
[    14.755] (II) modeset(0): Using fuzzy aspect match for initial modes
[    14.755] (II) modeset(0): Output eDP-1 using initial mode 1024x768 +0+0
[    14.755] (II) modeset(0): Output DP-1 using initial mode 1024x768 +0+0
(skipping a bunch of lines that seem unrelated - let me know if I should paste the whole thing)
[    15.141] (II) config/udev: Adding input device DP-1 (/dev/input/event10)
[    15.142] (**) DP-1: Applying InputClass "libinput keyboard catchall"
[    15.142] (II) Using input driver 'libinput' for 'DP-1'
[    15.142] (**) DP-1: always reports core events
[    15.142] (**) Option "Device" "/dev/input/event10"
[    15.142] (**) Option "_source" "server/udev"
[    15.144] (II) event10 - DP-1: is tagged by udev as: Keyboard Pointingstick
[    15.144] (II) event10 - DP-1: device is a pointer
[    15.144] (II) event10 - DP-1: device is a keyboard
[    15.145] (II) event10 - DP-1: device removed
[    15.161] (II) libinput: DP-1: needs a virtual subdevice
[    15.162] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/rc/rc0/input11/event10"
[    15.162] (II) XINPUT: Adding extended input device "DP-1" (type: MOUSE, id 9)
[    15.162] (**) Option "AccelerationScheme" "none"
[    15.162] (**) DP-1: (accel) selected scheme none/0
[    15.162] (**) DP-1: (accel) acceleration factor: 2.000
[    15.162] (**) DP-1: (accel) acceleration threshold: 4
[    15.164] (II) event10 - DP-1: is tagged by udev as: Keyboard Pointingstick
[    15.165] (II) event10 - DP-1: device is a pointer
[    15.165] (II) event10 - DP-1: device is a keyboard
Unfortunately my Xorg.0.log.old is from the same day and has the same issues, but I found an Xorg.1.log.old from last year which doesn't. It lists the same eDP-1, but doesn't list any information for DP-1 or classify it as a keyboard or list it as connected, and the initial display mode was 1920x1080 (which is what it should be):
[   942.577] (II) modeset(0): EDID for output DP-1
    [   942.577] (II) modeset(0): EDID for output DP-2
    [   942.577] (II) modeset(0): EDID for output DP-3
    [   942.577] (II) modeset(0): Output eDP-1 connected
    [   942.577] (II) modeset(0): Output DP-1 disconnected
    [   942.577] (II) modeset(0): Output DP-2 disconnected
    [   942.577] (II) modeset(0): Output DP-3 disconnected
    [   942.577] (II) modeset(0): Using exact sizes for initial modes
    [   942.577] (II) modeset(0): Output eDP-1 using initial mode 1920x1080 +0+0
I'm on a ThinkPad P1 with Xubuntu 20.04 and Xfce 4.14.
weronika (365 rep)
Sep 23, 2021, 07:41 PM • Last activity: Jul 27, 2025, 04:03 AM
5 votes
2 answers
4653 views
Initiate a new (X11) desktop session on a remote host
I would like to start a new `Xorg` server on a **remote** host. At first, I tought this would be as easy as it is on the local host: $ xinit /usr/bin/startxfce4 -- :4 On a _local_ host, this command typed into a (non-graphic) login shell (vt/tty) will start _another_ `Xorg` server, i.e. I will have...
I would like to start a new Xorg server on a **remote** host. At first, I tought this would be as easy as it is on the local host: $ xinit /usr/bin/startxfce4 -- :4 On a _local_ host, this command typed into a (non-graphic) login shell (vt/tty) will start _another_ Xorg server, i.e. I will have a xfce4 desktop after this - and this desktop is _additional_ to my normal desktop started from login from the desktop manager (e.g. sddm). However, if I try that on a _remote_ (fedora) system from the ssh console: X.Org X Server 1.20.6 X Protocol Version 11, Revision 0 Build Operating System: 5.0.6-200.fc29.x86_64 Current Operating System: Linux noah.siteos-lokal.de 5.5.10-200.fc31.x86_64 #1 SMP Wed Mar 18 14:21:38 UTC 2020 x86_64 Kernel command line: BOOT_IMAGE=(hd0,msdos3)/vmlinuz-5.5.10-200.fc31.x86_64 root=/dev/mapper/vg_sdd-root ro rd.luks.uuid=luks-a9eba963-ff2e-499b-a298-0659c5e29359 rd.lvm.lv=vg_sdd/root rd.lvm.lv=vg_sdd/swap rhgb quiet resume=/dev/disk/by-uuid/73299393-6bdb-4230-a1ca-096e5ee32396 splash=silent quiet video.use_native_backlight=1 Build Date: 25 November 2019 12:00:00AM Build ID: xorg-x11-server 1.20.6-1.fc31 Current version of pixman: 0.38.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: "/home/tpasch/.local/share/xorg/Xorg.4.log", Time: Fri Apr 3 19:38:52 2020 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied) (EE) (EE) Please consult the Fedora Project support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/tpasch/.local/share/xorg/Xorg.4.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error I wonder why it is possible to start _another_ Xorg on the _local_ host but I get this error on a _remote_ host. I'm _not_ expecting to 'see' the new desktop from my ssh terminal. But I would expect that I could ‘export’ the new Xorg rendered desktop with e.g. x11vnc. It there easy way to get this running? The bounty is for: * Showing how to start _another_ Xorg server on a _remote_ fedora machine from a ssh terminal session. The following answers will not be considered: * Using Xvfb, Xvnc or the like. * Using some kind of remote desktop technology (RDP, VNC, Spice, TeamViewer, ...)
aanno (129 rep)
Apr 4, 2020, 05:57 AM • Last activity: Jul 25, 2025, 08:01 PM
0 votes
1 answers
4770 views
How can I change the screen resolution of Slax?
[Slax][1] uses X.org for managing its GUI. However, when I boot Slax (specifically in a VM), the resolution gets capped at 1024x768. How can I increase the resolution to more fully utilize the screen estate available on my display? I have already attempted to follow the old advice from the following...
Slax uses X.org for managing its GUI. However, when I boot Slax (specifically in a VM), the resolution gets capped at 1024x768. How can I increase the resolution to more fully utilize the screen estate available on my display? I have already attempted to follow the old advice from the following sources: - http://old.slax.org/forum.php?action=view&parentID=25516 - http://www.linuxquestions.org/questions/mandriva-30/changing-screen-resolution-552768 - http://slaxlive.blogspot.com/2005/07/slax-linux-step-by-step-first-step.html
warren (1920 rep)
Mar 25, 2014, 08:02 PM • Last activity: Jul 23, 2025, 11:04 PM
19 votes
4 answers
26617 views
Why is the Scroll Lock key disabled in Cinnamon/Linux/Xorg?
I recently purchased a backlit keyboard that was designed such that the Scroll Lock key was used to toggle the back light. I quickly found that Cinnamon does not respond properly when the Scroll Lock key is pressed. Originally, I thought the keyboard backlight was DOA because everything else worked...
I recently purchased a backlit keyboard that was designed such that the Scroll Lock key was used to toggle the back light. I quickly found that Cinnamon does not respond properly when the Scroll Lock key is pressed. Originally, I thought the keyboard backlight was DOA because everything else worked out of the box. After a reboot I found that before launching Xorg I was able to successfully toggle the backlight using the Scroll Lock key. Then, once again, after starting Xorg (and consequentially cinnamon_session), this functionality stopped working once again. In order to get the backlight working after launching Xorg I was forced to issue a: xset led named "Scroll Lock" to enabled and disable this functionality. After a bit of research I came across a program called xev that dumped key event information to the terminal after it was started. Upon pressing the Scroll Lock key the terminal was populated with this information: >KeyPress event, serial 34, synthetic NO, window 0x2c00001, root 0x2df, subw 0x0, time 2609824, (410,0), root:(1724,142), state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False >KeyRelease event, serial 37, synthetic NO, window 0x2c00001, root 0x2df, subw 0x0, time 2609912, (410,0), root:(1724,142), state 0x0, keycode 78 (keysym 0xff14, Scroll_Lock), same_screen YES, XLookupString gives 0 bytes: So I know the key event is being sent to the kernel. Also, interestingly, I observed strange behavior when in the terminal (still prior to launching Xorg or Cinnamon) and using Scroll Lock. Namely, at this point my backlight was toggling as expected, but when Scroll Lock was enabled nothing I typed was written to the screen. After disabling Scroll Lock everything I had written was immediately dumped to the terminal as if it was previously being buffered. **tl;dr** What is the deal with Scroll Lock and Xorg?
sherrellbc (2601 rep)
Oct 25, 2014, 11:09 PM • Last activity: Jul 20, 2025, 10:37 AM
0 votes
1 answers
2313 views
failed to start the x server (your interface). it is likely not set up correctly (Mint)
I was trying to configure mouse properties following this guide. I restarted my computer and got this message : > Failed to start the x server (your interface). It is likely not set up > correctly I have tried many methods including this thread on Linux Mint: *[ Failed to Start the X server][1]*. Th...
I was trying to configure mouse properties following this guide. I restarted my computer and got this message : > Failed to start the x server (your interface). It is likely not set up > correctly I have tried many methods including this thread on Linux Mint: * Failed to Start the X server *. The error in question is : > Parse error on line 19 of section InputClass in file > /etc/x11/xorf.conf.d/50-synaptics.conf "..." is not a valid keyword in > this section. Section "InputClass" Identifier "touchpad" Driver "synaptics" MatchIsTouchpad "on" Option "TapButton1" "1" Option "TapButton2" "2" Option "TapButton3" "3" Option "VertEdgeScroll" "on" Option "VertTwoFingerScroll" "on" Option "HorizEdgeScroll" "on" Option "HorizTwoFingerScroll" "on" Option "CircularScrolling" "on" Option "CircScrollTrigger" "2" Option "EmulateTwoFingerMinZ" "40" Option "EmulateTwoFingerMinW" "8" Option "CoastingSpeed" "0" Option "FingerLow" "35" Option "FingerHigh" "40" ... //line 19 I assume EndSection I am currently locked out of my desktop. It blue-screens and shows the above message. There is nothing in /etc/share/X11/xorg.conf.d/50-synaptics.conf What can I do to fix this ?
user74096 (11 rep)
Sep 1, 2015, 09:17 AM • Last activity: Jul 15, 2025, 03:07 PM
1 votes
1 answers
3876 views
Black screen after installing Nvidia drivers on Debian Stretch
I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card. I followed this guide on Debian's wiki: https://wiki.debian.org/NvidiaGraphicsDrivers. Here are the steps I followed on my fresh install: First I added stretch-back...
I have installed latest Debian Stretch on my MSI laptop and I want to install Nvidia proprietary drivers for my GTX 1060 graphics card. I followed this guide on Debian's wiki: https://wiki.debian.org/NvidiaGraphicsDrivers . Here are the steps I followed on my fresh install: First I added stretch-backports and 'contrib non-free' postfix. My /etc/apt/sources.list dump: # # deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main #deb cdrom:[Debian GNU/Linux 9.7.0 _Stretch_ - Official amd64 NETINST 20190123-19:36]/ stretch main deb http://ftp.hu.debian.org/debian/ stretch main contrib non-free deb-src http://ftp.hu.debian.org/debian/ stretch main deb http://security.debian.org/debian-security stretch/updates main contrib non-free deb-src http://security.debian.org/debian-security stretch/updates main # stretch-updates, previously known as 'volatile' deb http://ftp.hu.debian.org/debian/ stretch-updates main contrib non-free deb-src http://ftp.hu.debian.org/debian/ stretch-updates main # stretch-backports deb http://httpredir.debian.org/debian stretch-backports main contrib non-free Then I ran the followings as root: $ dpkg --add-architecture i386 $ apt-get update $ apt-get install build-essential $ apt-get install linux-headers-$(uname -r|sed 's/[^-]*-[^-]*-//') $ apt-get -t stretch-backports install nvidia-driver I rebooted the system but on boot where gnome should have started I see a black screen without a cursor. I do have access to other terminals. Here is my Xorg.0.log: [ 23.138] (--) Log file renamed from "/var/log/Xorg.pid-823.log" to "/var/log/Xorg.0.log" [ 23.140] X.Org X Server 1.19.2 Release Date: 2017-03-02 [ 23.140] X Protocol Version 11, Revision 0 [ 23.140] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian [ 23.140] Current Operating System: Linux zion 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 [ 23.140] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=79569e63-703c-4939-ae49-32f4997c9c72 ro quiet [ 23.140] Build Date: 03 November 2018 03:09:11AM [ 23.140] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) [ 23.140] Current version of pixman: 0.34.0 [ 23.140] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 23.140] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 23.140] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 13 20:06:40 2019 [ 23.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 23.145] (==) No Layout section. Using the first Screen section. [ 23.145] (==) No screen section available. Using defaults. [ 23.145] (**) |-->Screen "Default Screen Section" (0) [ 23.145] (**) | |-->Monitor "" [ 23.146] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 23.146] (==) Automatically adding devices [ 23.146] (==) Automatically enabling devices [ 23.146] (==) Automatically adding GPU devices [ 23.146] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 23.148] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 23.148] Entry deleted from font path. [ 23.152] (==) 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 [ 23.152] (**) ModulePath set to "/usr/lib/xorg/modules/linux,/usr/lib/xorg/modules" [ 23.152] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 23.152] (II) Loader magic: 0x555783fdbe00 [ 23.152] (II) Module ABI versions: [ 23.152] X.Org ANSI C Emulation: 0.4 [ 23.152] X.Org Video Driver: 23.0 [ 23.152] X.Org XInput driver : 24.1 [ 23.152] X.Org Server Extension : 10.0 [ 23.154] (++) using VT number 1 [ 23.159] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2 [ 23.159] (II) xfree86: Adding drm device (/dev/dri/card0) [ 23.161] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 [ 23.165] (--) PCI:*(0:0:2:0) 8086:3e9b:1462:1223 rev 0, Mem @ 0xa2000000/16777216, 0x80000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072 [ 23.165] (--) PCI: (0:1:0:0) 10de:1c20:1462:1223 rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288 [ 23.165] (II) LoadModule: "glx" [ 23.167] (II) Loading /usr/lib/xorg/modules/linux/libglx.so [ 23.215] (II) Module glx: vendor="NVIDIA Corporation" [ 23.215] compiled for 4.0.2, module version = 1.0.0 [ 23.215] Module class: X.Org Server Extension [ 23.215] (II) NVIDIA GLX Module 390.87 Tue Aug 21 16:10:56 PDT 2018 [ 23.216] (II) Applying OutputClass "nvidia" to /dev/dri/card0 [ 23.216] loading driver: nvidia [ 23.216] (==) Matched nvidia as autoconfigured driver 0 [ 23.216] (==) Matched nouveau as autoconfigured driver 1 [ 23.216] (==) Matched nv as autoconfigured driver 2 [ 23.216] (==) Matched modesetting as autoconfigured driver 3 [ 23.216] (==) Matched fbdev as autoconfigured driver 4 [ 23.216] (==) Matched vesa as autoconfigured driver 5 [ 23.216] (==) Assigned the driver to the xf86ConfigLayout [ 23.216] (II) LoadModule: "nvidia" [ 23.216] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [ 23.221] (II) Module nvidia: vendor="NVIDIA Corporation" [ 23.221] compiled for 4.0.2, module version = 1.0.0 [ 23.221] Module class: X.Org Video Driver [ 23.221] (II) LoadModule: "nouveau" [ 23.221] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [ 23.223] (II) Module nouveau: vendor="X.Org Foundation" [ 23.223] compiled for 1.19.3, module version = 1.0.13 [ 23.223] Module class: X.Org Video Driver [ 23.223] ABI class: X.Org Video Driver, version 23.0 [ 23.223] (II) LoadModule: "nv" [ 23.223] (WW) Warning, couldn't open module nv [ 23.223] (II) UnloadModule: "nv" [ 23.223] (II) Unloading nv [ 23.223] (EE) Failed to load module "nv" (module does not exist, 0) [ 23.223] (II) LoadModule: "modesetting" [ 23.223] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 23.224] (II) Module modesetting: vendor="X.Org Foundation" [ 23.224] compiled for 1.19.2, module version = 1.19.2 [ 23.224] Module class: X.Org Video Driver [ 23.224] ABI class: X.Org Video Driver, version 23.0 [ 23.224] (II) LoadModule: "fbdev" [ 23.224] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 23.224] (II) Module fbdev: vendor="X.Org Foundation" [ 23.224] compiled for 1.19.0, module version = 0.4.4 [ 23.224] Module class: X.Org Video Driver [ 23.224] ABI class: X.Org Video Driver, version 23.0 [ 23.224] (II) LoadModule: "vesa" [ 23.224] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 23.225] (II) Module vesa: vendor="X.Org Foundation" [ 23.225] compiled for 1.19.0, module version = 2.3.4 [ 23.225] Module class: X.Org Video Driver [ 23.225] ABI class: X.Org Video Driver, version 23.0 [ 23.225] (II) NVIDIA dlloader X Driver 390.87 Tue Aug 21 15:44:49 PDT 2018 [ 23.225] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 23.225] (II) NOUVEAU driver Date: Tue Sep 20 00:31:06 2016 -0400 [ 23.225] (II) NOUVEAU driver for NVIDIA chipset families : [ 23.225] RIVA TNT (NV04) [ 23.225] RIVA TNT2 (NV05) [ 23.226] GeForce 256 (NV10) [ 23.226] GeForce 2 (NV11, NV15) [ 23.226] GeForce 4MX (NV17, NV18) [ 23.226] GeForce 3 (NV20) [ 23.226] GeForce 4Ti (NV25, NV28) [ 23.226] GeForce FX (NV3x) [ 23.226] GeForce 6 (NV4x) [ 23.226] GeForce 7 (G7x) [ 23.226] GeForce 8 (G8x) [ 23.226] GeForce GTX 200 (NVA0) [ 23.226] GeForce GTX 400 (NVC0) [ 23.226] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 23.226] (II) FBDEV: driver for framebuffer: fbdev [ 23.226] (II) VESA: driver for VESA chipsets: vesa [ 23.226] (II) systemd-logind: releasing fd for 226:0 [ 23.226] (EE) [drm] Failed to open DRM device for (null): -2 [ 23.226] (WW) Falling back to old probe method for modesetting [ 23.226] (II) Loading sub module "fbdevhw" [ 23.226] (II) LoadModule: "fbdevhw" [ 23.226] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 23.227] (II) Module fbdevhw: vendor="X.Org Foundation" [ 23.227] compiled for 1.19.2, module version = 0.0.2 [ 23.227] ABI class: X.Org Video Driver, version 23.0 [ 23.227] (**) FBDEV(1): claimed PCI slot 0@0:2:0 [ 23.227] (II) FBDEV(1): using default device [ 23.227] (WW) Falling back to old probe method for vesa [ 23.227] (EE) Screen 0 deleted because of no matching config section. [ 23.227] (II) UnloadModule: "modesetting" [ 23.227] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 23.227] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 [ 23.227] (==) FBDEV(0): RGB weight 888 [ 23.227] (==) FBDEV(0): Default visual is TrueColor [ 23.227] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 23.227] (II) FBDEV(0): hardware: EFI VGA (video memory: 1920kB) [ 23.227] (II) FBDEV(0): checking modes against framebuffer device... [ 23.227] (II) FBDEV(0): checking modes against monitor... [ 23.227] (--) FBDEV(0): Virtual size is 800x600 (pitch 800) [ 23.227] (**) FBDEV(0): Built-in mode "current": 48.0 MHz, 46.9 kHz, 75.1 Hz [ 23.227] (II) FBDEV(0): Modeline "current"x0.0 48.00 800 832 928 1024 600 604 608 624 -hsync -vsync -csync (46.9 kHz b) [ 23.227] (==) FBDEV(0): DPI set to (96, 96) [ 23.227] (II) Loading sub module "fb" [ 23.227] (II) LoadModule: "fb" [ 23.227] (II) Loading /usr/lib/xorg/modules/libfb.so [ 23.228] (II) Module fb: vendor="X.Org Foundation" [ 23.228] compiled for 1.19.2, module version = 1.0.0 [ 23.228] ABI class: X.Org ANSI C Emulation, version 0.4 [ 23.228] (**) FBDEV(0): using shadow framebuffer [ 23.228] (II) Loading sub module "shadow" [ 23.228] (II) LoadModule: "shadow" [ 23.228] (II) Loading /usr/lib/xorg/modules/libshadow.so [ 23.228] (II) Module shadow: vendor="X.Org Foundation" [ 23.228] compiled for 1.19.2, module version = 1.1.0 [ 23.228] ABI class: X.Org ANSI C Emulation, version 0.4 [ 23.228] (II) UnloadModule: "vesa" [ 23.228] (II) Unloading vesa [ 23.228] (==) Depth 24 pixmap format is 32 bpp [ 23.228] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling) [ 23.230] (==) FBDEV(0): Backing store enabled [ 23.231] (==) FBDEV(0): DPMS enabled [ 23.231] (==) RandR enabled [ 23.233] (II) SELinux: Disabled on system [ 23.233] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) [ 23.283] (II) config/udev: Adding input device Power Button (/dev/input/event5) [ 23.283] (**) Power Button: Applying InputClass "libinput keyboard catchall" [ 23.283] (II) LoadModule: "libinput" [ 23.283] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so [ 23.284] (II) Module libinput: vendor="X.Org Foundation" [ 23.284] compiled for 1.19.0, module version = 0.23.0 [ 23.284] Module class: X.Org XInput Driver [ 23.284] ABI class: X.Org XInput driver, version 24.1 [ 23.284] (II) Using input driver 'libinput' for 'Power Button' [ 23.285] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 22 paused 0 [ 23.285] (**) Power Button: always reports core events [ 23.285] (**) Option "Device" "/dev/input/event5" [ 23.285] (**) Option "_source" "server/udev" [ 23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard [ 23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard [ 23.285] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5" [ 23.285] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6) [ 23.285] (**) Option "xkb_model" "pc105" [ 23.285] (**) Option "xkb_layout" "us" [ 23.285] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard [ 23.285] (II) input device 'Power Button', /dev/input/event5 is a keyboard [ 23.286] (II) config/udev: Adding input device Lid Switch (/dev/input/event2) [ 23.286] (II) No input driver specified, ignoring this device. [ 23.286] (II) This device may have been added with another device file. [ 23.286] (II) config/udev: Adding input device Power Button (/dev/input/event4) [ 23.286] (**) Power Button: Applying InputClass "libinput keyboard catchall" [ 23.286] (II) Using input driver 'libinput' for 'Power Button' [ 23.286] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 25 paused 0 [ 23.286] (**) Power Button: always reports core events [ 23.286] (**) Option "Device" "/dev/input/event4" [ 23.286] (**) Option "_source" "server/udev" [ 23.286] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard [ 23.286] (II) input device 'Power Button', /dev/input/event4 is a keyboard [ 23.286] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5/event4" [ 23.286] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7) [ 23.286] (**) Option "xkb_model" "pc105" [ 23.286] (**) Option "xkb_layout" "us" [ 23.287] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard [ 23.287] (II) input device 'Power Button', /dev/input/event4 is a keyboard [ 23.287] (II) config/udev: Adding input device Sleep Button (/dev/input/event3) [ 23.287] (**) Sleep Button: Applying InputClass "libinput keyboard catchall" [ 23.287] (II) Using input driver 'libinput' for 'Sleep Button' [ 23.287] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 26 paused 0 [ 23.287] (**) Sleep Button: always reports core events [ 23.287] (**) Option "Device" "/dev/input/event3" [ 23.287] (**) Option "_source" "server/udev" [ 23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard [ 23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard [ 23.287] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event3" [ 23.287] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8) [ 23.287] (**) Option "xkb_model" "pc105" [ 23.287] (**) Option "xkb_layout" "us" [ 23.287] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard [ 23.287] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard [ 23.288] (II) config/udev: Adding input device HDA Intel Headphone (/dev/input/event9) [ 23.288] (II) No input driver specified, ignoring this device. [ 23.288] (II) This device may have been added with another device file. [ 23.288] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8) [ 23.288] (II) No input driver specified, ignoring this device. [ 23.288] (II) This device may have been added with another device file. [ 23.288] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0) [ 23.288] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall" [ 23.288] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard' [ 23.288] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 27 paused 0 [ 23.289] (**) AT Translated Set 2 keyboard: always reports core events [ 23.289] (**) Option "Device" "/dev/input/event0" [ 23.289] (**) Option "_source" "server/udev" [ 23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard [ 23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard [ 23.289] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0" [ 23.289] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9) [ 23.289] (**) Option "xkb_model" "pc105" [ 23.289] (**) Option "xkb_layout" "us" [ 23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard [ 23.289] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard [ 23.289] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event1) [ 23.289] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall" [ 23.289] (II) Using input driver 'libinput' for 'SynPS/2 Synaptics TouchPad' [ 23.290] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 28 paused 0 [ 23.290] (**) SynPS/2 Synaptics TouchPad: always reports core events [ 23.290] (**) Option "Device" "/dev/input/event1" [ 23.290] (**) Option "_source" "server/udev" [ 23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad [ 23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad [ 23.290] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1" [ 23.290] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 10) [ 23.290] (**) Option "AccelerationScheme" "none" [ 23.290] (**) SynPS/2 Synaptics TouchPad: (accel) selected scheme none/0 [ 23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000 [ 23.290] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4 [ 23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad [ 23.290] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad [ 23.290] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [ 23.290] (II) No input driver specified, ignoring this device. [ 23.290] (II) This device may have been added with another device file. [ 23.290] (II) config/udev: Adding input device PC Speaker (/dev/input/event6) [ 23.291] (II) No input driver specified, ignoring this device. [ 23.291] (II) This device may have been added with another device file. [ 23.291] (II) config/udev: Adding input device MSI WMI hotkeys (/dev/input/event7) [ 23.291] (**) MSI WMI hotkeys: Applying InputClass "libinput keyboard catchall" [ 23.291] (II) Using input driver 'libinput' for 'MSI WMI hotkeys' [ 23.291] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 29 paused 0 [ 23.291] (**) MSI WMI hotkeys: always reports core events [ 23.291] (**) Option "Device" "/dev/input/event7" [ 23.291] (**) Option "_source" "server/udev" [ 23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard [ 23.291] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard [ 23.291] (**) Option "config_info" "udev:/sys/devices/virtual/input/input8/event7" [ 23.291] (II) XINPUT: Adding extended input device "MSI WMI hotkeys" (type: KEYBOARD, id 11) [ 23.291] (**) Option "xkb_model" "pc105" [ 23.291] (**) Option "xkb_layout" "us" [ 23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard [ 23.292] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard [ 36.511] (**) Option "fd" "22" [ 36.511] (**) Option "fd" "25" [ 36.511] (**) Option "fd" "26" [ 36.512] (**) Option "fd" "27" [ 36.512] (**) Option "fd" "28" [ 36.512] (**) Option "fd" "29" [ 36.515] (II) systemd-logind: got pause for 13:64 [ 36.515] (II) systemd-logind: got pause for 13:67 [ 36.515] (II) systemd-logind: got pause for 13:69 [ 36.515] (II) systemd-logind: got pause for 13:68 [ 36.515] (II) systemd-logind: got pause for 13:65 [ 36.515] (II) systemd-logind: got pause for 13:71 [ 55.096] (II) systemd-logind: got resume for 13:64 [ 55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard [ 55.097] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard [ 55.120] (II) systemd-logind: got resume for 13:67 [ 55.121] (II) input device 'Sleep Button', /dev/input/event3 is tagged by udev as: Keyboard [ 55.121] (II) input device 'Sleep Button', /dev/input/event3 is a keyboard [ 55.140] (II) systemd-logind: got resume for 13:69 [ 55.141] (II) input device 'Power Button', /dev/input/event5 is tagged by udev as: Keyboard [ 55.141] (II) input device 'Power Button', /dev/input/event5 is a keyboard [ 55.156] (II) systemd-logind: got resume for 13:68 [ 55.157] (II) input device 'Power Button', /dev/input/event4 is tagged by udev as: Keyboard [ 55.157] (II) input device 'Power Button', /dev/input/event4 is a keyboard [ 55.176] (II) systemd-logind: got resume for 13:65 [ 55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is tagged by udev as: Touchpad [ 55.177] (II) input device 'SynPS/2 Synaptics TouchPad', /dev/input/event1 is a touchpad [ 55.192] (II) systemd-logind: got resume for 13:71 [ 55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is tagged by udev as: Keyboard [ 55.193] (II) input device 'MSI WMI hotkeys', /dev/input/event7 is a keyboard [ 57.379] (**) Option "fd" "26" [ 57.379] (**) Option "fd" "27" [ 57.379] (**) Option "fd" "25" [ 57.379] (**) Option "fd" "22" [ 57.379] (**) Option "fd" "28" [ 57.380] (**) Option "fd" "29" [ 57.383] (II) systemd-logind: got pause for 13:64 [ 57.383] (II) systemd-logind: got pause for 13:67 [ 57.383] (II) systemd-logind: got pause for 13:69 [ 57.383] (II) systemd-logind: got pause for 13:68 [ 57.383] (II) systemd-logind: got pause for 13:65 [ 57.383] (II) systemd-logind: got pause for 13:71 And related messages from dmesg: . . [ 20.051031] nvidia: loading out-of-tree module taints kernel. [ 20.051034] nvidia: module license 'NVIDIA' taints kernel. [ 20.051035] Disabling lock debugging due to kernel taint [ 20.058235] nvidia-nvlink: Nvlink Core is being initialized, major device number 248 [ 20.058370] nvidia 0000:01:00.0: enabling device (0006 -> 0007) [ 20.058443] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none [ 20.058489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 (using threaded interrupts) [ 20.069920] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.87 Tue Aug 21 16:16:14 PDT 2018 [ 20.075365] [drm] Initialized [ 20.079182] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:18/PNP0C09:00/PNP0C0D:00/input/input3 [ 20.079488] ACPI: Lid Switch [LID0] [ 20.079844] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4 [ 20.079848] ACPI: Sleep Button [SLPB] [ 20.079889] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5 [ 20.079891] ACPI: Power Button [PWRB] [ 20.079937] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6 [ 20.079938] ACPI: Power Button [PWRF] [ 20.087606] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [ 20.087913] ACPI: AC Adapter [ADP1] (on-line) . . . [ 22.621804] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 22.622573] alx 0000:02:00.0 enp2s0: NIC Up: 100 Mbps Full [ 22.622829] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready [ 23.754442] gnome-session-f: segfault at 0 ip 00007f7cef889e19 sp 00007ffd529ea4e0 error 4 in libgtk-3.so.0.2200.11[7f7cef5a7000+700000] [ 33.821642] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 33.821643] Bluetooth: BNEP filters: protocol multicast [ 33.821645] Bluetooth: BNEP socket layer initialized Do you have any idea what may be the problem? Update: If I wait long enough on black screen, I get a curser.
paddlesteamer (11 rep)
Feb 13, 2019, 05:47 PM • Last activity: Jul 10, 2025, 02:08 AM
6 votes
1 answers
2159 views
XRandR crops displayed area on certain multi-monitor configurations
I have total of four monitors. One (1680x1050) is connected to integrated Intel display adapter, and three (1440x900 and two 1920x1080) are connected to dedicated ATI display adapter. With certain XRandR configurations some monitors have their display area cropped, so that for example lower part of...
I have total of four monitors. One (1680x1050) is connected to integrated Intel display adapter, and three (1440x900 and two 1920x1080) are connected to dedicated ATI display adapter. With certain XRandR configurations some monitors have their display area cropped, so that for example lower part of the screen is not usable. I'd like to use configuration like this one: xrandr \ --output VGA-1 --mode 1440x900 --pos 780x1080 --rotate left \ --output HDMI2 --mode 1680x1050 --pos 0x30 --rotate normal \ --output HDMI-3 --mode 1920x1080 --pos 1680x1080 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x0 --rotate normal But the lower part (below the bottom edge of the bottom right screen) of the bottom left screen is cut off: Failure On the other hand, this configuration works: xrandr \ --output VGA-1 --mode 1440x900 --pos 780x1050 --rotate left \ --output HDMI2 --mode 1680x1050 --pos 0x0 --rotate normal \ --output HDMI-3 --mode 1920x1080 --pos 1680x1080 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x0 --rotate normal , as shown here: Success 1 Also this configuration works: xrandr \ --output VGA-1 --mode 1440x900 --pos 780x0 --rotate left \ --output HDMI2 --mode 1680x1050 --pos 0x1440 --rotate normal \ --output HDMI-3 --mode 1920x1080 --pos 1680x1440 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x360 --rotate normal , as shown here: Success 2 In addition, the configuration below works xrandr \ --output VGA-1 --mode 1440x900 --pos 780x1080 --rotate left \ --output HDMI2 --mode 1680x1050 --pos 0x30 --rotate normal \ --output HDMI-3 --mode 1920x1080 --pos 1680x1440 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x0 --rotate normal as shown here: Success 3 **UPDATE:** Strangely, I managed to get the wanted layout by command sequence: xrandr \ --output VGA-1 --mode 1440x900 --pos 780x1080 --rotate left \ --output HDMI2 --mode 1680x1050 --pos 0x30 --rotate normal \ --output HDMI-3 --mode 1920x1080 --pos 1680x1440 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x0 --rotate normal xrandr \ --output HDMI2 --mode 1680x1050 --pos 0x30 --rotate normal \ --output DVI-0 --mode 1920x1080 --pos 1680x0 --rotate normal \ --output VGA-1 --mode 1440x900 --pos 780x1080 --rotate left \ --output HDMI-3 --mode 1920x1080 --pos 1680x1080 --rotate normal \ --primary so that it works on freshly started Xorg instance, but I don't have a clue why it works. Besides, that solution seems a bit ugly. Can anybody enlighten me on this issue, please? My OS is Arch Linux, window manager is i3, and the version of XRandR is 1.4.2. Xorg configuration files have only InputClass and Files sections.
montiainen (163 rep)
May 31, 2014, 05:03 PM • Last activity: Jul 9, 2025, 08:02 AM
7 votes
1 answers
2697 views
syndaemon won't disable touchpad while typing
I am trying to use syndaemon to disable my touchpad while I type. I know that the GUI for this doesn't work for many people but all the posts I've seen online suggest that using syndaemon from the command line should work. It doesn't work for me, however. To test whether the touchpad is off while I...
I am trying to use syndaemon to disable my touchpad while I type. I know that the GUI for this doesn't work for many people but all the posts I've seen online suggest that using syndaemon from the command line should work. It doesn't work for me, however. To test whether the touchpad is off while I type, I type with one hand while moving the mouse and clicking with the other. I've also tried turning on palm detection, which I test just by typing for a while and seeing if I get a touchpad click (I always do, pretty promptly). Linux Mint 17.2 Rafaela (installed it yesterday) Dell Inspiron 11 3000 series * Output of xinput list: > xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ DLL064D:00 06CB:2985 id=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Video Bus id=8 [slave keyboard (3)] ↳ Power Button id=9 [slave keyboard (3)] ↳ Sleep Button id=10 [slave keyboard (3)] ↳ Integrated_Webcam_HD id=11 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] What I've tried so far: * Control Center -> Mouse -> disable touchpad while typing: no effect * gpointing-device-settings: shows two touchpads: * DLL0446:00 06CB:2985: enable palm detection -> no effect; when I disable this touchpad, my touchpad becomes unresponsive * SynPS/2 Synaptics Touchpad: disabled (turning it on and modifying settings seems to have no effect) * syndaemon: killall syndaemon; syndaemon -i 10 -K -d: no effect (also tried with -R). ps aux | egrep syndaemon shows that no other syndaemon processes are running. I have tried this with and without the "disable touchpad while typing" checkbox set in Mouse Preferences. * synclient: synclient PalmDetect=1 PalmMinWidth=10 PalmMinZ=200: no effect I am at my wit's end. The solutions attempted above seem to work for everyone else! Why can't I get syndaemon to work for me?
Jessica Hekman (71 rep)
Jul 19, 2015, 07:00 PM • Last activity: Jul 5, 2025, 02:02 AM
0 votes
1 answers
48 views
Context menu makes window focus stuck with MX Master 3 on GNOME Wayland
I am running Fedora Work Station 41 on GNOME and Wayland. I am using a Logitech MX Master 3 Wireless mouse with the provided dongle. I also have Solaar installed. If I right click on a System Window control (this wording may be incorrect) and it opens the context menu, I cannot click on any other wi...
I am running Fedora Work Station 41 on GNOME and Wayland. I am using a Logitech MX Master 3 Wireless mouse with the provided dongle. I also have Solaar installed. If I right click on a System Window control (this wording may be incorrect) and it opens the context menu, I cannot click on any other window or interact with anything else, using this mouse, until I either close the context menu by clicking inside the same window (as where I clicked to open the context menu) or if I choose an option from the menu. In other words, the focus is stuck on the parent window owning the right click menu, but only for the Logitech Mouse... I also have a USB Corsair mouse connected with which this problem does not reproduce. I tried installing solaar to get full control and drivers for the mouse, but no change. This works on X11, not on wayland. I have tried searching for hours for a solution, but found nothing. I found some similar issues for other mice, but those were for X11 and editing xorg.conf. On X11 I have no issue. Anyone have any ideas? For example here, I can only click inside the terminal or choose an action. Clicking on the window in the background or on my second monitor will not close the context menu, nor change the window focus. As I said, this works fine with a regular USB mouse. The issue also does not reproduce on "third party" context menus, such as google chrome right click. I am mainly seeing the issue with my terminal emulator (gnome terminal) and the default (nautilus) file manager context menus. enter image description here
Matheos (101 rep)
Dec 31, 2024, 11:58 AM • Last activity: Jun 27, 2025, 10:15 AM
3 votes
1 answers
2010 views
Start two X servers on boot on RHEL
I have a powerful machine that I want to use as a multi-seat system. It has two graphic cards and two pairs of keyboards and mice. I've been able to successfully configure two "seats" using udev and Xorg.conf, and launch two X servers from a script so two users can have independent sessions. Just fo...
I have a powerful machine that I want to use as a multi-seat system. It has two graphic cards and two pairs of keyboards and mice. I've been able to successfully configure two "seats" using udev and Xorg.conf, and launch two X servers from a script so two users can have independent sessions. Just for the record, here's my udev rules file, where I identify each USB hub and label the devices and the seats: SUBSYSTEM=="drm", KERNEL=="card[0-9]*", ATTRS{vendor}=="0x10de", DRIVERS=="nvidia", TAG+="master-of-seat" # SUBSYSTEM=="drm", KERNEL=="card0", ENV{ID_SEAT}="seat0" # SUBSYSTEM=="drm", KERNEL=="card1", ENV{ID_SEAT}="seat1" SUBSYSTEM=="input", ENV{ID_INPUT.tags}="input_default" # KVM HUBS KERNELS=="3-2", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="1", ENV{ID_SEAT}="seat0" KERNELS=="3-8", ATTRS{bDeviceClass}=="09", ENV{KVM_HUB}="2", ENV{ID_SEAT}="seat1" # Devices of HUB 1 KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_1" KERNEL=="event*", ENV{KVM_HUB}=="1", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_1" # Devices of HUB 2 KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="01" SYMLINK+="kvm_keyboard_2" KERNEL=="event*", ENV{KVM_HUB}=="2", ATTRS{bInterfaceProtocol}=="02" SYMLINK+="kvm_mouse_2" # Default seat SUBSYSTEM=="input", TAG=="seat", ENV{ID_SEAT}=="" , ENV{ID_SEAT}="seat0" # set all tags accordingly ENV{ID_SEAT}!="", ENV{ID_INPUT.tags}+="$env{ID_SEAT}" TAG+="$env{ID_SEAT}" The relevant part of my xorg.conf file looks like this: Section "ServerFlags" # Option "AutoAddDevices" "false" # Option "AutoEnableDevices" "false" Option "DefaultServerLayout" "Layout0" Option "AllowMouseOpenFail" "true" Option "Xinerama" "0" EndSection # --------------------------------------------------------------- # LAYOUT Section "ServerLayout" Identifier "Layout0" Screen "Screen0" MatchSeat "seat0" Option "Clone" "off" EndSection Section "ServerLayout" Identifier "Layout1" Screen "Screen1" MatchSeat "seat1" Option "Clone" "off" EndSection As I said, **I can successfully launch** two independent sessions using the following script, but I'd like this to happen automatically on boot. #!/bin/bash set +x rm /etc/X11/xorg.conf cp ./xorg_independientes /etc/X11/xorg.conf # X (:0) systemctl stop gdm killall Xorg killall X systemctl restart gdm sleep 7 # X (:1) su - sit -c "startx /usr/bin/gnome-session -- :1 vt4 -layout Layout1 -seat seat1 -sharevts" & sleep 10 DISPLAY=:1 xhost + My approach would be setting the default target runlevel to 4 (so it has everything but graphics) and then placing these commands in a script somewhere.
José Tomás Tocino (170 rep)
Dec 12, 2016, 09:02 AM • Last activity: Jun 25, 2025, 10:09 PM
2 votes
1 answers
3392 views
How do I correctly transfer xrandr settings to xorg.conf?
I have run multiple `xrandr` commands to set all my monitors settings as I want them. Then I used `autorandr` to save the state to a config file printed here: ``` hanke@debian ~ » cat .config/autorandr/3-displays/config output DP-1 off output DP-2 off output DP-3 off output DP-4 off output DP-5...
I have run multiple xrandr commands to set all my monitors settings as I want them. Then I used autorandr to save the state to a config file printed here:
hanke@debian ~ » cat .config/autorandr/3-displays/config 
output DP-1
off
output DP-2
off
output DP-3
off
output DP-4
off
output DP-5
off
output DVI-D-0
crtc 1
mode 1600x900
pos 3840x0
rate 59.98
rotate left
output DP-0
crtc 0
mode 1920x1080
pos 1920x191
primary
rate 144.00
output HDMI-0
crtc 2
mode 1920x1080
pos 0x260
rate 60.00
I have been using autorandr --change 3-displays in my window managers startup script to configure the displays, but I run into problems with this approach if I enable lightdm to get the greeter/login screen, which is run before my window manager, and in extension before my monitors are configured correctly. Because of this, the login screen is displayed on the wrong monitors in the wrong resolutions and orientations. Because of this I now wish to transfer these settings to the /etc/X11/xorg.conf config file. Here is my attempt so far:
Section "Monitor"
        Identifier      "DP-0"
        Option          "Position"      "1920 191"
        Option          "Primary"       "true"
        Option          "PreferredMode" "1920x1080_144.00"
        Option          "Enable"        "true"
EndSection

Section "Monitor"
        Identifier      "HDMI-0"
        Option          "Position"      "0 260"
        Option          "PreferredMode" "1920x1080_60.00"
        Option          "Enable"        "true"
EndSection

Section "Monitor"
        Identifier      "DVI D-0"
        Option          "Rotate"        "left"
        Option          "Position"      "3840 900"
        Option          "PreferredMode" "1600x900_59.98"
        Option          "Enable"        "true"
EndSection

Section "Monitor"
        Identifier      "DP-1"
        Option          "Enable"        "false"
EndSection

Section "Monitor"
        Identifier      "DP-2"
        Option          "Enable"        "false"
EndSection

Section "Monitor"
        Identifier      "DP-3"
        Option          "Enable"        "false"
EndSection

Section "Monitor"
        Identifier      "DP-4"
        Option          "Enable"        "false"
EndSection

Section "Monitor"
        Identifier      "DP-5"
        Option          "Enable"        "false"
EndSection
Sadly, this does not seem to work. My gaming display is not getting set to 144 Hz refresh rate, the orientation on my DVI screen is all wrong and the positions seem to be ignored as well. I have previously had startx fail because of bad xorg.conf values, but using this config it starts without crashing. Am I missing something here? I just want my screens to be correctly configured in a nice and declarative way. Running a bunch of xrandr commands in scripts feels hacky. The xorg.conf file seems like the correct way to do it, but I am failing to get it to work correctly. Any help is appreciated.
Hannes Knutsson (33 rep)
Feb 6, 2022, 05:34 PM • Last activity: Jun 21, 2025, 10:02 AM
1 votes
1 answers
5260 views
Failed to load module "nv" (module does not exist, 0)
I get this error when running 'startx'. What is this 'nv' module, and how do I stop Xorg from trying to load it? EDIT: I am going to try to blacklist the module 'nv' using the kernel command line. I'll update this post if that works. I installed the Nvidia drivers, nouveau drivers and intel drivers....
I get this error when running 'startx'. What is this 'nv' module, and how do I stop Xorg from trying to load it? EDIT: I am going to try to blacklist the module 'nv' using the kernel command line. I'll update this post if that works. I installed the Nvidia drivers, nouveau drivers and intel drivers. I also added the Nvidia drivers to /etc/mkinitcpio.conf (in MODULES). I'm on the latest version of Arch Linux. What I tried: - Created the xorg.conf file using nvidia-xconfig. On doing 'startx', nothing happens until I type 'exit' - Deleted the xorg.conf file. It yields the nv module error Also, is there a way to use the intel drivers instead of the nvidia drivers? I'd like to use this as a last resort.
Alsan Ali (11 rep)
Mar 4, 2019, 05:21 PM • Last activity: Jun 21, 2025, 08:01 AM
2 votes
0 answers
154 views
DRM: Artificially simulating a monitor Disconnect+Reconnect event, or a HOTPLUG uevent
Is there a way to simulate a physical HDMI cable unplugging and replugging on a Linux system running Xorg with AMDGPU driver? In my Xfce system on X11, I have trouble with monitor output/connector detection. In particular, when the system transitions from the Rescueshell/GRUB to the distro login man...
Is there a way to simulate a physical HDMI cable unplugging and replugging on a Linux system running Xorg with AMDGPU driver? In my Xfce system on X11, I have trouble with monitor output/connector detection. In particular, when the system transitions from the Rescueshell/GRUB to the distro login manager (lightdm), the monitor turns blackish grey, and the only fix I've found so far is by unplugging the monitor's HDMI and replugging, or by changing the monitor's own FreeSync setting (Options: Standard Engine, Ultimate Engine, Off) in that black screen state and doing Ctrl+Alt+F2, which I think effectively "resets" the HDMI connection. Using drm.edid= as a kernel boot option can help with the issue, but having a valid Xorg.conf in /usr/share/X11/xorg.conf.d/ basically makes it useless and recreates the blackscreen, as I think Xorg/AMDGPU (my graphics driver) takes over control of the graphical output and uses the edid or modeline in the Xorg.conf, once it gets to the initial pre-login/post-login stage in lightdm. This switchup probably confuses my monitor. But I want to have a Xorg.conf for proper functionality. The blackscreen isn't completely black, as in a no signal, but it's somewhat grey. If I switch TTYs, the screen will flicker and go grey again, but there'll be no display at this stage. It's like the monitor is detected, but there the signal isn't interpreted right. I want to know if there is any way to make the KMS/DRM driver think that the monitor has been disconnected and reconnected, without a real physical disconnect, so the driver refreshes all "connectors" and hopefully gives output to the monitor, possibly using a udev HOTPLUG event. According to the answers in this question: , it is possible to use udevadm trigger to masquerade udev events to specific devices in /sys subsystems. Or by directly using echo ACTION > /sys/class/SUBSYTEM/DEVICE/uevent From udevadm trigger --verbose --action=help /sys/class/drm/card0-HDMI-A-1 I get a list of all possible 'trigger' options:
add
remove
change
move
online
offline
bind
unbind
I've tried using all of them, but they don't do anything equivalent to a full replugging. The screen stays on the whole time. However 'change' using udevadm trigger --verbose --action=change /sys/class/drm/card0-HDMI-A-1 forces a rescan for the device EDID in dmesg:
[34870.335496] Registering platform device 'HDMI-A-1'. Parent at platform
[34870.335523] device: 'HDMI-A-1': device_add
[34870.335545] platform HDMI-A-1: No ACPI support
[34870.335553] bus: 'platform': add device HDMI-A-1
[34870.335720] bus: 'platform': remove device HDMI-A-1
[34870.335746] [drm] Got external EDID base block and 0 extensions from "edid/1920x1080.bin" for connector "HDMI-A-1"
This does not turn off the screen though, and so doesn't help with the problem. Is there any way to mention a specific key / ENV{ATTRIBUTE} when triggering a udev event? For example someone else's udev logs during a monitor unplug and replug cycle:
udevadm monitor --environment --udev 
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [1370.249130] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
ACTION=change
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci0000:00/0000:00:02.0/drm/card0
DEVTYPE=drm_minor
HOTPLUG=1
ID_FOR_SEAT=drm-pci-0000_00_02_0
ID_PATH=pci-0000:00:02.0
ID_PATH_TAG=pci-0000_00_02_0
MAJOR=226
MINOR=0
SEQNUM=1884
SUBSYSTEM=drm
TAGS=:seat:uaccess:
USEC_INITIALIZED=715
Here the main ACTION is "change", but is there a way *I* can specify that HOTPLUG=1 parameter? It's noteworthy that when *I* use udevadm monitor and do an unplug cycle, nothing shows up in output. But when switching TTYs to F2 then F7 (my GUI) using Ctrl+Alt+..., then I get this:
udevadm monitor --environment --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [4315.550505] add      /devices/platform/HDMI-A-1 (platform)
ACTION=add
DEVPATH=/devices/platform/HDMI-A-1
SUBSYSTEM=platform
MODALIAS=platform:HDMI-A-1
SEQNUM=3714
USEC_INITIALIZED=4315229577
ID_PATH=platform-HDMI-A-1
ID_PATH_TAG=platform-HDMI-A-1

UDEV  [4315.551278] remove   /devices/platform/HDMI-A-1 (platform)
ACTION=remove
DEVPATH=/devices/platform/HDMI-A-1
SUBSYSTEM=platform
MODALIAS=platform:HDMI-A-1
SEQNUM=3715
USEC_INITIALIZED=4315229577
ID_PATH=platform-HDMI-A-1
ID_PATH_TAG=platform-HDMI-A-1
which could indicate that hotplugging is not supported or triggered properly in my system, leading to my issues. I found a Gentoo forum post: which had my same question regarding unplug and replug, but there was not a solution there. I have tried echo off > /sys/class/drm/card0-HDMI-A-1/status and echo on > /sys/class/drm/card0-HDMI-A-1/status but it doesn't cause the monitor to turn off, only an EDID rescan in dmesg. The same thing as a udevadm trigger --action=change. echoing to enabled or dpms in that same directory doesn't seem to be allowed. I have tried xset -display :0 dpms force off (or -display :0.0) from a TTY/shell script, but it doesn't turn off the monitor. Though it works in a GUI of course, after I've already unplugged the monitor once. I tried
sudo mount -o remount,exec /dev
sudo vbetool dpms off
sudo mount -o remount,noexec /dev
from [this](https://old.reddit.com/r/linux4noobs/comments/vo7u7l/how_can_i_turn_the_display_off_in_a_tty/) and [this](https://askubuntu.com/questions/1384221/real-mode-call-failed-on-macbook-pro-when-trying-to-turn-screen-off-ubuntu-serve) , but it outputs Real mode call failed. So now I tried setterm --blank 1 from and consoleblank=200 (approximate bootup time for my device in seconds) as a kernel commandline parameter, and they also don't work as I want them to. They can turn off the screen, but it's not a hard enough reset that makes the monitor redetected like in a physical replugging. I've tried a systemd service like this ExecStart=/bin/sh -c 'while [ -n "$(pidof lightdm)" ] || [ -n "$(pidof X)" ] || [ -n "$(pidof Xorg)" ]; do sleep 10; done; sleep 15; echo '' > /sys/module/drm/parameters/edid_firmware && pkill X' to restart X at the login prompt, but it doesn't help either. I came across this guide , which mentioned > void (*output_poll_changed)(struct drm_device *dev); > >This operation notifies the driver that the status of one or more connectors has changed. Drivers that use the fb helper can just call the drm_fb_helper_hotplug_event function to handle this operation. Is there a way I can compile a binary and call this function manually at X startup, to achieve what I'm looking for? Or is there any other solution to address this? I am having this issue on a PS4 system running Arch Linux, and I think the monitor might have trouble with EDID communication. So the hardware situation is a bit flaky, but most of the underlying mechanics are still the same.
feearent (61 rep)
Jun 17, 2025, 08:00 PM • Last activity: Jun 18, 2025, 10:39 AM
0 votes
2 answers
3717 views
X11 not setting primary monitor according to config file
^\_^ ### Synopsis I want to specify my primary monitor using system-wide X11 configuration files, but my present configuration files don't seem to do anything! 0_0 ### My situation I'm coming from the same place as this question here: https://unix.stackexchange.com/questions/565553/why-doesnt-x11-se...
^\_^ ### Synopsis I want to specify my primary monitor using system-wide X11 configuration files, but my present configuration files don't seem to do anything! 0_0 ### My situation I'm coming from the same place as this question here: https://unix.stackexchange.com/questions/565553/why-doesnt-x11-set-the-only-monitor-as-primary-by-default Namely, I need the only monitor I have connected to be recognized as my primary monitor so that my tray icons in i3 work. That said, I don't want to solve this using using xrandr, because I'm trying to use as much as possible the same dotfiles on two different machines which have different hardware configurations. Therefore, I would like to solve this using the system-wide X11 configuration files. However, it doesn't seem to work as expected. :o ### My present setup At present I have no xorg.conf file, and I do have a xorg.conf.d/10-monitor.conf, the contents of which (following [this Arch Linux wiki page](https://wiki.archlinux.org/index.php/Multihead#Configuration_using_xorg.conf)) are here:
Section "Monitor"
    Identifier  "HDMI2"
    Option      "Primary" "true"
EndSection
In light of this configuration file, here is my xrandr output for a fresh X session:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 disconnected primary (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm
   1920x1080     60.00*+
   1600x1200     60.00  
   1680x1050     59.88  
   1400x1050     59.95  
   1600x900      60.00  
   1280x1024     75.02    60.02  
   1440x900      59.90  
   1280x800      59.91  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   832x624       74.55  
   800x600       72.19    75.00    60.32    56.25  
   640x480       75.00    72.81    66.67    59.94  
   720x400       70.08  
HDMI3 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
As you can see, despite having specified HDMI2 in the configuration files as my primary monitor, DP1 is set as the primary. ### Stuff I've tried I've verified that my configuration file is being processed by X11 by introducing typos and observing that X11 fails to launch due to errors. I've tried placing the configuration file above in /etc/X11/xorg.conf instead of /etc/X11/xorg.conf.d/10-monitor.conf. I've tried including the following in an attempt to specify the default primary monitor as not primary:
Section "Monitor"
    Identifier  "DP1"
    Option      "Primary" "false"
EndSection
I've tried launching with the default xorg.conf generated by X -configure alongside my 10-monitor.conf. ### Miscellaneous information
$ uname -a
Linux cheesy-6600k 5.9.8-arch1-1 #1 SMP PREEMPT Tue, 10 Nov 2020 22:44:11 +0000 x86_64 GNU/Linux
$ lscpu | grep name
Model name:                      Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Aardbei (101 rep)
Nov 14, 2020, 06:15 PM • Last activity: Jun 13, 2025, 03:09 PM
8 votes
3 answers
3272 views
Is it possible to tell Xorg not to listen on the abstract socket
On Linux (in recent versions), Xorg listens on both a Unix domain socket on the filesystem ( /tmp/.X11-unix/X ) and in the _abstract_ domain (shown as @/tmp/.X11-unix/X in netstat output). It also listens on TCP (port 6000 + ). One can stop it from listening on TCP by adding a `-nolisten tcp`, but h...
On Linux (in recent versions), Xorg listens on both a Unix domain socket on the filesystem (/tmp/.X11-unix/X) and in the _abstract_ domain (shown as @/tmp/.X11-unix/X in netstat output). It also listens on TCP (port 6000 + ). One can stop it from listening on TCP by adding a -nolisten tcp, but how can we tell it not to listen on the abstract namespace?
Stéphane Chazelas (579252 rep)
Feb 3, 2014, 03:48 PM • Last activity: Jun 13, 2025, 11:47 AM
3 votes
1 answers
2299 views
BLFS Xorg: Fatal server error no screens found
I'm trying to build the Xorg X Window System Environment as outlined in Beyond Linux From Scratch Version 8.0. My BLFS system resides in a Virtual Machine using VirtualBox Version 5.0.10 r104061. I followed the steps as outlined in Chapter 24. X Window System Environment. However, when I finished my...
I'm trying to build the Xorg X Window System Environment as outlined in Beyond Linux From Scratch Version 8.0. My BLFS system resides in a Virtual Machine using VirtualBox Version 5.0.10 r104061. I followed the steps as outlined in Chapter 24. X Window System Environment. However, when I finished my installation and tried startx, I got the output below:- Release Date: 2017-01-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.9.5 x86_64 Current Operating System: Linux LFS 4.9.5 #1 SMP Thu Feb 23 22:59:41 GMT 2017 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.5-lfs-SVN-20170122 root=/dev/sda1 ro Build Date: 01 March 2017 10:04:52PM Current version of pixman: 0.34.0 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: Wed Mar 22 21:42:24 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error And I see the following log in /var/log/Xorg.0.log 57.972] X.Org X Server 1.19.1 Release Date: 2017-01-11 [ 57.974] X Protocol Version 11, Revision 0 [ 57.974] Build Operating System: Linux 4.9.5 x86_64 [ 57.975] Current Operating System: Linux LFS 4.9.5 #1 SMP Thu Feb 23 22:59:41 GMT 2017 x86_64 [ 57.975] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.5-lfs-SVN-20170122 root=/dev/sda1 ro [ 57.975] Build Date: 01 March 2017 10:04:52PM [ 57.975] [ 57.975] Current version of pixman: 0.34.0 [ 57.975] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 57.975] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 57.978] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 22 21:42:24 2017 [ 57.990] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 57.992] (==) No Layout section. Using the first Screen section. [ 57.992] (==) No screen section available. Using defaults. [ 57.992] (**) |-->Screen "Default Screen Section" (0) [ 57.992] (**) | |-->Monitor "" [ 57.992] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 57.992] (**) | |-->Device "radeon" [ 57.992] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 57.992] (==) Automatically adding devices [ 57.992] (==) Automatically enabling devices [ 57.992] (==) Automatically adding GPU devices [ 57.994] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 57.999] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/misc/". [ 57.999] Entry deleted from font path. [ 57.999] (Run 'mkfontdir' on "/usr/share/fonts/X11/misc/"). [ 58.002] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/100dpi/". [ 58.002] Entry deleted from font path. [ 58.002] (Run 'mkfontdir' on "/usr/share/fonts/X11/100dpi/"). [ 58.003] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/X11/75dpi/". [ 58.003] Entry deleted from font path. [ 58.003] (Run 'mkfontdir' on "/usr/share/fonts/X11/75dpi/"). [ 58.003] (==) FontPath set to: /usr/share/fonts/X11/TTF/, /usr/share/fonts/X11/OTF/, /usr/share/fonts/X11/Type1/ [ 58.003] (==) ModulePath set to "/usr/lib/xorg/modules" [ 58.003] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 58.003] (II) Loader magic: 0x810c40 [ 58.003] (II) Module ABI versions: [ 58.003] X.Org ANSI C Emulation: 0.4 [ 58.003] X.Org Video Driver: 23.0 [ 58.003] X.Org XInput driver : 24.1 [ 58.003] X.Org Server Extension : 10.0 [ 58.007] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216, BIOS @ 0x????????/131072 [ 58.007] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 58.007] (II) LoadModule: "glx" [ 58.008] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 58.040] (II) Module glx: vendor="X.Org Foundation" [ 58.040] compiled for 1.19.1, module version = 1.0.0 [ 58.040] ABI class: X.Org Server Extension, version 10.0 [ 58.040] (II) LoadModule: "ati" [ 58.041] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [ 58.042] (II) Module ati: vendor="X.Org Foundation" [ 58.042] compiled for 1.19.1, module version = 7.8.0 [ 58.042] Module class: X.Org Video Driver [ 58.042] ABI class: X.Org Video Driver, version 23.0 [ 58.042] (EE) No drivers available. [ 58.042] (EE) Fatal server error: [ 58.044] (EE) no screens found(EE) [ 58.045] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 58.046] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 58.046] (EE) [ 58.046] (EE) Server terminated with error (1). Closing log file. I've tried rebuilding the kernel with Device Drivers ---> Graphics support ---> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM] DRM driver for VMware Virtual GPU [CONFIG_DRM_VMWGFX] [*] Enable framebuffer console under vmwgfx by default [CONFIG_DRM_VMWGFX_FBCON] and Device Drivers ---> Graphics support ---> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM] and in both cases got the same error message. This is the output of lspci for the graphics adapter 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter Any idea why the screens are failing to load?
Youssif Saeed (141 rep)
Mar 22, 2017, 10:00 PM • Last activity: Jun 11, 2025, 02:06 PM
1 votes
1 answers
75 views
Recompiling Vim with +clipboard on Arch Linux (DWM/X11)
I use Arch Linux + DWM on the X Window System. I can't copy from Vim to an external application, and the `vim --version` command returns `-xterm_clipboard`. As I understand it, I need to recompile my Vim and add clipboard support into the config file, but I don't know where to find it. Is it the `~/...
I use Arch Linux + DWM on the X Window System. I can't copy from Vim to an external application, and the vim --version command returns -xterm_clipboard. As I understand it, I need to recompile my Vim and add clipboard support into the config file, but I don't know where to find it. Is it the ~/.vimrc file? I can't find the original PKGBUILD in my ~/vim/ directory either. I've tried to use **pacbuilder-svn** and ran:
$ pacbuilder --install --edit vim vim-runtime
But the script doesn't ask me whether I want to edit the PKGBUILD file; it just builds the packages and that's it. I've also tried to use **devtools** and ran:
$ sudo pkgctl repo clone https://github.com/vim/vim.git 
But it says:
failed to clone https://github.com/vim/vim.git 
How can I recompile my Vim with clipboard support? I would be grateful for your help.
Bernadette (13 rep)
Jun 8, 2025, 06:33 AM • Last activity: Jun 8, 2025, 07:53 AM
1 votes
1 answers
2886 views
How to recover from a failing Nvidia driver to load?
I have a server (running Debian 9 Stretch) with proprietary Nvidia driver installed. It is for scientific computation so headless. So, the Nvidia driver is installed for using CUDA (during CUDA installation with a package file `cuda_10.0.130_410.48_linux.run` downloaded from Nvidia website). It used...
I have a server (running Debian 9 Stretch) with proprietary Nvidia driver installed. It is for scientific computation so headless. So, the Nvidia driver is installed for using CUDA (during CUDA installation with a package file cuda_10.0.130_410.48_linux.run downloaded from Nvidia website). It used to work well. Two days ago, I rebooted the system to enter into the BIOS to disable HyperThreading. After rebooting, the Nvidia driver was not loading. I rebooted the system several times and it was the same. How can I bring it back? Here is some information for your reference. # lspci -v|grep VGA 05:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6G B] (rev a1) (prog-if 00 [VGA controller]) # nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Ma ke sure that the latest NVIDIA driver is installed and running. # modprobe nvidia modprobe: FATAL: Module nvidia not found in directory /lib/modules/4.9.0-9-amd64 # nvidia-settings ERROR: libgtk-3.so.0: cannot open shared object file: No such file or directory libnvidia-gtk3.so: cannot open shared object file: No such file or directory libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory libnvidia-gtk2.so: cannot open shared object file: No such file or directory ERROR: A problem occured when loading the GUI library. Please check your installation and library path. You may need to specify this library when calling nvidia-settings. Please run nvidia-settings --help for usage information.
michael morgan (271 rep)
Jul 17, 2019, 04:37 AM • Last activity: Jun 6, 2025, 12:06 PM
Showing page 1 of 20 total questions