mupdf-gl not responsive to keyboard anymore

lithium · 2022-11-30 23:18:19

Hi all,

After a recent upgrade, mupdf is no longer responding to keyboard input. I have mupdf-gl 1.21.0-1 installed, currently the latest version. It will open the PDF file to either the first page or the last viewed page but will not respond to *anything* after that. Not even 'q' to quit or 'F1' for help.

Tried uninstalling and re-installing to no avail.

mupdf has worked for me for years with no issue. This same version is working for me on my laptop, also running arch with openbox and no GNOME/KDE/other DM.

No other programs are having problems with keyboard input.

Google reveals some old issues (from 2016 and 2018) but they don't seem relevant.

Any ideas? Anyone else having this issue?

Last edited by lithium (2022-12-01 21:49:07)

seth · 2022-11-30 23:31:39

Did you try to downgrade mupdf and if that doesn't help: did the recent upgrade include https://archlinux.org/packages/extra/x86_64/libx11/ ?

lithium · 2022-12-01 04:41:37

seth wrote:

Did you try to downgrade mupdf and if that doesn't help: did the recent upgrade include https://archlinux.org/packages/extra/x86_64/libx11/ ?

I did try downgrading but the dependencies became a mess so I reverted it to the latest. Also, my laptop has this latest version and is nearly-identical setup (except drivers, of course) and it has no such issues.

Yes, I have the latest libx11: 1.8.2-2

seth · 2022-12-01 08:08:34

Wild guess:
https://gitlab.freedesktop.org/xorg/lib … issues/168
You could try
https://archive.archlinux.org/packages/ … kg.tar.zst

lithium · 2022-12-01 21:47:58

seth wrote:

Wild guess:
https://gitlab.freedesktop.org/xorg/lib … issues/168
You could try
https://archive.archlinux.org/packages/ … kg.tar.zst

Thanks, I tried downgrading but that did not resolve it unfortunately. I ran ldconfig, closed X and logged out then logged back in after downgrading. The same thing happens.

If install the non-GL version of mupdf, this issue doesn't happen at all. Even with the latest libx11. The keyboard works perfectly. So maybe it's something with GL or my graphics setup. I am using really old nvidia-340xx drivers since I have a really old graphics card in this computer (built circa 2009). But I'm not really sure if that would matter.

Last edited by lithium (2022-12-01 21:48:29)

seth · 2022-12-01 22:01:31

What dependency issues did you encounter w/ downgrading mupdf-gl?
1.20.3 has an openssl-3 rebuild, https://github.com/archlinux/svntogit-c … 11a51f1160
So this should not be an issue at all?

lithium · 2022-12-01 22:42:51

If I downgrade to 1.20.3-1 and try to open a file I get this error:

mupdf: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

I don't yet understand what you mean by the openssl-3 rebuild. I ran "sudo pacman -U /var/cache/pacman/pkg/mupdf-gl-1.20.3-1-x86_64.pkg.tar.zst" and that installed the old version of mupdf-gl but didn't do anything else.

I also tried using the downgrade tool from the AUR and the same thing happens. Tried downgrading to 1.18.0 even.

Last edited by lithium (2022-12-01 23:03:10)

seth · 2022-12-02 08:24:02

I don't yet understand what you mean by the openssl-3 rebuild.

The package was rebuilt against openssl-3 w/ 1.20.3-2 - that's why you're getting an error w/ the previous 1.20.3-1 build.

=> https://archive.archlinux.org/packages/ … kg.tar.zst

lithium · 2022-12-02 22:52:45

Thanks, I downloaded and installed that version. It is able to open the file but the same keyboard issue persists.

Any more ideas? I appreciate it.

seth · 2022-12-03 08:27:04

Does the mouse still work?
Does https://aur.archlinux.org/packages/llpp work?
glxgears? (speculating that this is maybe not a keyboard/input thing but the GL context is frozen)

mupdf-gl uses https://archlinux.org/packages/extra/x86_64/freeglut/ which saw it's last update mid-october; was that included in the recent upgrade?

lithium · 2022-12-05 18:30:17

I am able to select text with the right mouse button!
llpp DOES work.
glxgears DOES work (displays the gears).
freeglut is version 3.4.0-1, the latest.

Does that help?

Last edited by lithium (2022-12-05 18:31:01)

seth · 2022-12-05 19:08:03

freeglut is version 3.4.0-1, the latest.

The question is

seth wrote:

was that included in the recent upgrade?

'cause it handles input and since mupdf processes events and along llpp/glxgears it's not just a frozen context, I'd strongly look there.

lithium · 2022-12-05 22:36:49

Sorry, I'm confused. I have freeglut version 3.4.0-1 installed. I don't know if it was installed at the same time as the mupdf upgrade. But it definitely is now. Is that what you mean? Or are you saying that I should try to downgrade that as well?

From my pacman log

[2022-09-12T11:16:49-0700] [ALPM] upgraded mupdf-gl (1.20.0-1 -> 1.20.3-1)
...
[2022-10-31T12:54:08-0700] [ALPM] upgraded freeglut (3.2.2-2 -> 3.4.0-1)
...
[2022-11-12T12:35:55-0800] [ALPM] reinstalled mupdf-gl (1.20.3-1)
...
[2022-11-28T14:48:42-0800] [ALPM] upgraded mupdf-gl (1.20.3-1 -> 1.21.0-1)

So freeglut was upgraded before the latest mupdf. However, it's quite possible that the same issue existed with the older mupdf, hence my reinstall attempt on November 12.

EDIT:

I just did a pacman -Syu today and now mupdf now works!

The following packages were installed:

Packages (99) adwaita-cursors-43-2  adwaita-icon-theme-43-2  bind-9.18.9-1  cmake-3.25.1-1
              cryptsetup-2.6.0-1  default-cursors-1-1  elfutils-0.188-1  firefox-107.0.1-1
              glib2-2.74.3-1  graphviz-7.0.4-1  http-parser-2.9.4-1  imagemagick-7.1.0.53-1
              libass-0.17.0-1  libbluray-1.3.4-1  libcamera-0.0.2-1  libelf-0.188-1  libgit2-1:1.5.0-2
              libice-1.1.0-1  libnautilus-extension-43.1-1  libnftnl-1.2.4-1  libreoffice-still-7.3.7-2
              libreoffice-still-sdk-7.3.7-2  libxcomposite-0.4.6-1  libxcursor-1.2.1-3
              libxdamage-1.1.6-1  libxv-1.0.12-1  linux-6.0.11.arch1-1  linux-headers-6.0.11.arch1-1
              luajit-2.1.0.beta3.r457.g637721d0-1  mpfr-4.1.1.p1-1  mplayer-38407-1  mupdf-gl-1.21.0-1
              netpbm-10.73.41-1  pacman-mirrorlist-20221204-1  pipewire-1:0.3.61-1  poppler-22.12.0-1
              poppler-glib-22.12.0-1  protobuf-21.10-1  python-asttokens-2.2.1-1  python-chardet-5.1.0-1
              python-protobuf-21.10-1  python-setuptools-1:65.6.3-1  python-traitlets-5.6.0-1
              python-trove-classifiers-2022.12.1-1  python-zipp-3.11.0-1  rav1e-0.6.1-1
              remmina-1:1.4.28-1  ruby-abbrev-0.1.0-4  ruby-base64-0.1.1-4  ruby-benchmark-0.2.0-4
              ruby-bigdecimal-3.1.2-4  ruby-bundler-2.3.25-1  ruby-cgi-0.3.6-1  ruby-csv-3.2.5-4
              ruby-date-3.2.2-4  ruby-delegate-0.2.0-4  ruby-did_you_mean-1.6.1-4  ruby-digest-3.1.0-6
              ruby-drb-2.1.0-5  ruby-english-0.7.1-5  ruby-erb-4.0.2-1  ruby-etc-1.3.0-6
              ruby-fcntl-1.0.1-4  ruby-fiddle-1.1.0-4  ruby-fileutils-1.6.0-4  ruby-find-0.1.1-4
              ruby-forwardable-1.3.2-6  ruby-getoptlong-0.1.1-3  ruby-io-console-0.5.11-3
              ruby-io-nonblock-0.1.0-3  ruby-io-wait-0.2.3-4  ruby-ipaddr-1.2.4-3  ruby-logger-1.5.1-3
              ruby-mutex_m-0.1.1-3  sdl2-2.26.1-1  sed-4.9-1  sqlite-3.40.0-2  svt-av1-1.4.0-1
              systemd-252.2-3  systemd-libs-252.2-3  systemd-sysvcompat-252.2-3  tracker3-3.4.2-1
              tzdata-2022g-1  usbutils-015-2  vlc-3.0.18-4  vte-common-0.70.2-1  vte3-0.70.2-1
              wavpack-5.6.0-1  wayland-1.21.0-2  wayland-protocols-1.31-1  webkit2gtk-2.38.2-2
              webkit2gtk-4.1-2.38.2-2  xmlsec-1.2.37-1  xorg-xgamma-1.0.7-1  xorg-xinit-1.4.2-1
              xorg-xprop-1.2.6-1  xorg-xrandr-1.5.2-1  xorg-xset-1.2.5-1  xz-5.2.9-1

Last edited by lithium (2022-12-05 23:02:11)

seth · 2022-12-06 07:13:41

The only thing in there that remotely looks like it could have had impact (aside the mupdf-gl update, but that's just returning to 1.21.0-1) would be glib2, though it's questionable how that would really impact mupdf's event loop. Especially in a way that non-gl mupdf isn't.

This might have been a side-channel issue, depending on how mupdf was started - or heuristic behavior.

lithium · 2022-12-06 17:59:44

seth wrote:

This might have been a side-channel issue, depending on how mupdf was started - or heuristic behavior.

Thanks, can you explain what you mean by this?

I start it from an urxvt window.

seth · 2022-12-06 20:48:35

The shell would be more relevant than teh TE then - and also whether you fork/disown the process.
Though tbh. the typical problem would be that a process gets SIGSTOP'd, what's not the case (since the mouse still works) - and it should™ probably have impacted mupdf as well.

Did you restart the system during the phase where things didn't work?
(I assume you did now as the kernel was updated)

lithium · 2022-12-06 21:47:56

It's running bash. No, I just ran "mupdf <FILE>", no forks or disowning.

I have restarted my computer many times during the course of this issue occuring. I have NOT restarted since this last update yesterday even though the kernel was updated. It's a bit of a hassle to restart after upgrading my kernel since I have to rebuild and re-install nvidia-340xx every time. Yes, it's that old. I will do it later today probably.

Last edited by lithium (2022-12-06 21:54:42)

lithium · 2022-12-12 17:49:25

After restarting this morning (first time since above update), mupdf again is NOT responding to keyboard input.

Last edited by lithium (2022-12-12 17:51:31)

seth · 2022-12-12 18:48:28

"Great"

So to get that straight:
- didn't work
- you updated the packages in #13
- did not reboot (nor restart X11?)
- did work after the update
- kept working after the update
- rebooted
- doesn't work

glxinfo -B
pacman -Qs 'xf86-'

And please post your xorg log, https://wiki.archlinux.org/title/Xorg#General
With a little luck, there's also still the Xorg.0.log.old ?

lithium · 2022-12-12 20:19:03

seth wrote:

"Great"
So to get that straight:
- didn't work
- you updated the packages in #13
- did not reboot (nor restart X11?)
- did work after the update
- kept working after the update
- rebooted
- doesn't work

Yep, that's what happened. Since Xorg.0.log.old was created on Dec 1 and Xorg.0.log was created today, I did restart X after creating this post but not after the update. I do regularly suspend to RAM and occasionally to disk.

seth wrote:

glxinfo -B
pacman -Qs 'xf86-'
And please post your xorg log, https://wiki.archlinux.org/title/Xorg#General
With a little luck, there's also still the Xorg.0.log.old ?

[ ~ ] $ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 512 MB
    Total available memory: 512 MB
    Currently available dedicated video memory: 487 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 9500 GT/PCIe/SSE2
OpenGL core profile version string: 3.3.0 NVIDIA 340.108
OpenGL core profile shading language version string: 3.30 NVIDIA via Cg compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.3.0 NVIDIA 340.108
OpenGL shading language version string: 3.30 NVIDIA via Cg compiler
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 2.0 NVIDIA 340.108 340.108
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.00

[ ~ ] $ pacman -Qs 'xf86-'
local/xf86-input-evdev 2.10.6-3 (xorg-drivers)
    X.org evdev input driver
local/xf86-input-libinput 1.2.1-1 (xorg-drivers)
    Generic input driver for the X.Org server based on libinput

Xorg.0.log:

[   259.926] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[   259.927] Current Operating System: Linux quark 6.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 02 Dec 2022 17:25:31 +0000 x86_64
[   259.927] Kernel command line: root=/dev/sda3 rw resume=UUID=5b82083b-0a88-4b2f-941c-8d0f07f8de60 resume_offset=58128384 initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux 
[   259.927]  
[   259.927] Current version of pixman: 0.42.2
[   259.927] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   259.927] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   259.928] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 12 09:46:50 2022
[   259.975] (==) Using config file: "/etc/X11/xorg.conf"
[   259.975] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   259.975] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   260.038] (==) ServerLayout "Layout0"
[   260.038] (**) |-->Screen "Screen0" (0)
[   260.038] (**) |   |-->Monitor "Monitor0"
[   260.039] (**) |   |-->Device "Device0"
[   260.039] (**) |   |-->GPUDevice "Nvidia Card"
[   260.039] (**) |   |-->GPUDevice "Device1"
[   260.039] (**) |-->Input Device "Keyboard0"
[   260.039] (**) |-->Input Device "Mouse0"
[   260.039] (**) Option "Xinerama" "0"
[   260.039] (**) Option "IgnoreABI" "1"
[   260.039] (**) Ignoring ABI Version
[   260.039] (==) Automatically adding devices
[   260.039] (==) Automatically enabling devices
[   260.039] (==) Automatically adding GPU devices
[   260.039] (==) Automatically binding GPU devices
[   260.039] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   260.089] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[   260.089] 	Entry deleted from font path.
[   260.118] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[   260.118] 	Entry deleted from font path.
[   260.118] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[   260.118] 	Entry deleted from font path.
[   260.118] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/Type1
[   260.118] (**) ModulePath set to "/usr/lib64/nvidia/xorg,/usr/lib64/xorg/modules"
[   260.118] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   260.118] (WW) Disabling Keyboard0
[   260.118] (WW) Disabling Mouse0
[   260.118] (II) Module ABI versions:
[   260.118] 	X.Org ANSI C Emulation: 0.4
[   260.118] 	X.Org Video Driver: 25.2
[   260.118] 	X.Org XInput driver : 24.4
[   260.118] 	X.Org Server Extension : 10.0
[   260.119] (++) using VT number 1

[   260.121] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[   260.128] (--) PCI:*(1@0:0:0) 10de:0640:3842:c954 rev 161, Mem @ 0xe6000000/16777216, 0xd0000000/268435456, 0xe4000000/33554432, I/O @ 0x00009000/128, BIOS @ 0x????????/131072
[   260.128] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   260.128] (II) LoadModule: "glx"
[   260.144] (II) Loading /usr/lib64/nvidia/xorg/libglx.so
[   260.971] (II) Module glx: vendor="NVIDIA Corporation"
[   260.971] 	compiled for 4.0.2, module version = 1.0.0
[   260.971] 	Module class: X.Org Server Extension
[   260.976] (II) NVIDIA GLX Module  340.108  Wed Dec 11 14:26:50 PST 2019
[   260.985] (II) LoadModule: "nvidia"
[   261.019] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[   261.099] (II) Module nvidia: vendor="NVIDIA Corporation"
[   261.099] 	compiled for 4.0.2, module version = 1.0.0
[   261.099] 	Module class: X.Org Video Driver
[   261.099] ================ WARNING WARNING WARNING WARNING ================
[   261.099] This server has a video driver ABI version of 25.2 that this
driver does not officially support.  Please check
http://www.nvidia.com/ for driver updates or downgrade to an X
server with a supported driver ABI.
[   261.099] =================================================================
[   261.099] (WW) NVIDIA: The driver will continue to load, but may behave strangely.
[   261.099] (WW) NVIDIA: This driver was compiled against the X.Org server SDK from commit e6ef2b12404dfec7f23592a3524d2a63d9d25802 and may not be compatible with the final version of this SDK.
[   261.104] (II) NVIDIA dlloader X Driver  340.108  Wed Dec 11 14:06:00 PST 2019
[   261.104] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   261.110] (II) Loading sub module "fb"
[   261.110] (II) LoadModule: "fb"
[   261.111] (II) Module "fb" already built-in
[   261.111] (WW) Unresolved symbol: fbGetGCPrivateKey
[   261.111] (II) Loading sub module "wfb"
[   261.111] (II) LoadModule: "wfb"
[   261.119] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[   261.126] (II) Module wfb: vendor="X.Org Foundation"
[   261.126] 	compiled for 1.21.1.4, module version = 1.0.0
[   261.126] 	ABI class: X.Org ANSI C Emulation, version 0.4
[   261.126] (II) Loading sub module "ramdac"
[   261.126] (II) LoadModule: "ramdac"
[   261.126] (II) Module "ramdac" already built-in
[   261.380] (EE) Screen 1 deleted because of no matching config section.
[   261.380] (II) UnloadModule: "nvidia"
[   261.380] (II) UnloadSubModule: "wfb"
[   261.380] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[   261.380] (==) NVIDIA(0): RGB weight 888
[   261.380] (==) NVIDIA(0): Default visual is TrueColor
[   261.380] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[   261.380] (**) NVIDIA(0): Option "Stereo" "0"
[   261.380] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-0"
[   261.380] (**) NVIDIA(0): Option "SLI" "Off"
[   261.380] (**) NVIDIA(0): Option "MultiGPU" "Off"
[   261.380] (**) NVIDIA(0): Option "BaseMosaic" "off"
[   261.380] (**) NVIDIA(0): Stereo disabled by request
[   261.380] (**) NVIDIA(0): NVIDIA SLI disabled.
[   261.380] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[   261.380] (**) NVIDIA(0): Option "MetaModes" "DVI-I-2: nvidia-auto-select +0+0"
[   261.380] (**) NVIDIA(0): Enabling 2D acceleration
[   262.509] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[   262.509] (II) NVIDIA(0):     3D Vision stereo.
[   262.509] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
[   262.511] (II) NVIDIA(0): NVIDIA GPU GeForce 9500 GT (G96) at PCI:1:0:0 (GPU-0)
[   262.511] (--) NVIDIA(0): Memory: 524288 kBytes
[   262.511] (--) NVIDIA(0): VideoBIOS: 62.94.29.00.50
[   262.511] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[   262.513] (--) NVIDIA(0): Valid display device(s) on GeForce 9500 GT at PCI:1:0:0
[   262.513] (--) NVIDIA(0):     CRT-0
[   262.513] (--) NVIDIA(0):     CRT-1
[   262.513] (--) NVIDIA(0):     TV-0
[   262.513] (--) NVIDIA(0):     DFP-0
[   262.513] (--) NVIDIA(0):     Samsung SyncMaster (DFP-1) (boot, connected)
[   262.513] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[   262.513] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[   262.513] (--) NVIDIA(GPU-0): TV-0: 400.0 MHz maximum pixel clock
[   262.513] (--) NVIDIA(0): DFP-0: Internal TMDS
[   262.514] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[   262.514] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[   262.514] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
[   262.514] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[   262.514] (**) NVIDIA(0):     device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[   262.514] (**) NVIDIA(0):     has been enabled on all display devices.)
[   262.516] (WW) NVIDIA(0): No valid modes for "DVI-I-2:nvidia-auto-select+0+0";
[   262.516] (WW) NVIDIA(0):     removing.
[   262.516] (WW) NVIDIA(0): 
[   262.516] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[   262.516] (WW) NVIDIA(0):     "nvidia-auto-select".
[   262.516] (WW) NVIDIA(0): 
[   262.516] (II) NVIDIA(0): Validated MetaModes:
[   262.516] (II) NVIDIA(0):     "DFP-1:nvidia-auto-select"
[   262.516] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[   262.552] (--) NVIDIA(0): DPI set to (85, 86); computed from "UseEdidDpi" X config
[   262.552] (--) NVIDIA(0):     option
[   262.552] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[   262.555] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   262.555] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   262.555] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   262.555] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   262.555] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   262.555] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   262.555] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   262.555] (II) NVIDIA(0):     Config Options in the README.
[   262.557] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[   262.677] (==) NVIDIA(0): Disabling shared memory pixmaps
[   262.677] (==) NVIDIA(0): Backing store enabled
[   262.677] (==) NVIDIA(0): Silken mouse enabled
[   262.677] (**) NVIDIA(0): DPMS enabled
[   262.677] (II) Loading sub module "dri2"
[   262.677] (II) LoadModule: "dri2"
[   262.677] (II) Module "dri2" already built-in
[   262.677] (II) NVIDIA(0): [DRI2] Setup complete
[   262.677] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   262.678] (II) Initializing extension Generic Event Extension
[   262.678] (II) Initializing extension SHAPE
[   262.679] (II) Initializing extension MIT-SHM
[   262.679] (II) Initializing extension XInputExtension
[   262.679] (II) Initializing extension XTEST
[   262.679] (II) Initializing extension BIG-REQUESTS
[   262.680] (II) Initializing extension SYNC
[   262.680] (II) Initializing extension XKEYBOARD
[   262.680] (II) Initializing extension XC-MISC
[   262.680] (II) Initializing extension SECURITY
[   262.680] (II) Initializing extension XFIXES
[   262.681] (II) Initializing extension RENDER
[   262.681] (II) Initializing extension RANDR
[   262.681] (II) Initializing extension COMPOSITE
[   262.681] (II) Initializing extension DAMAGE
[   262.682] (II) Initializing extension MIT-SCREEN-SAVER
[   262.682] (II) Initializing extension DOUBLE-BUFFER
[   262.682] (II) Initializing extension RECORD
[   262.682] (II) Initializing extension DPMS
[   262.683] (II) Initializing extension Present
[   262.683] (II) Initializing extension DRI3
[   262.683] (II) Initializing extension X-Resource
[   262.683] (II) Initializing extension XVideo
[   262.683] (II) Initializing extension XVideo-MotionCompensation
[   262.683] (II) Initializing extension XFree86-VidModeExtension
[   262.683] (II) Initializing extension XFree86-DGA
[   262.684] (II) Initializing extension XFree86-DRI
[   262.684] (II) Initializing extension DRI2
[   262.684] (II) Initializing extension GLX
[   262.684] (II) Initializing extension GLX
[   262.684] (II) Indirect GLX disabled.(II) Initializing extension NV-GLX
[   262.684] (II) Initializing extension NV-CONTROL
[   262.685] (II) Initializing extension XINERAMA
[   263.126] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   263.126] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   263.126] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   263.126] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   263.126] (II) LoadModule: "evdev"
[   263.127] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[   263.152] (II) Module evdev: vendor="X.Org Foundation"
[   263.152] 	compiled for 1.21.1.1, module version = 2.10.6
[   263.152] 	Module class: X.Org XInput Driver
[   263.153] 	ABI class: X.Org XInput driver, version 24.4
[   263.153] (II) Using input driver 'evdev' for 'Power Button'
[   263.154] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 37 paused 0
[   263.154] (**) Power Button: always reports core events
[   263.154] (**) evdev: Power Button: Device: "/dev/input/event1"
[   263.154] (--) evdev: Power Button: Vendor 0 Product 0x1
[   263.154] (--) evdev: Power Button: Found keys
[   263.154] (II) evdev: Power Button: Configuring as keyboard
[   263.154] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[   263.154] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   263.154] (**) Option "xkb_rules" "evdev"
[   263.155] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[   263.155] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   263.155] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[   263.155] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   263.155] (II) Using input driver 'evdev' for 'Power Button'
[   263.156] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 38 paused 0
[   263.156] (**) Power Button: always reports core events
[   263.156] (**) evdev: Power Button: Device: "/dev/input/event0"
[   263.156] (--) evdev: Power Button: Vendor 0 Product 0x1
[   263.157] (--) evdev: Power Button: Found keys
[   263.157] (II) evdev: Power Button: Configuring as keyboard
[   263.157] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[   263.157] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[   263.157] (**) Option "xkb_rules" "evdev"
[   263.157] (II) config/udev: Adding drm device (/dev/dri/card0)
[   263.157] (II) xfree86: Adding drm device (/dev/dri/card0)
[   263.157] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[   263.158] (EE) systemd-logind: failed to take device /dev/dri/card0: Device or resource busy
[   263.158] (II) LoadModule: "modesetting"
[   263.158] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   263.198] (II) Module modesetting: vendor="X.Org Foundation"
[   263.198] 	compiled for 1.21.1.4, module version = 1.21.1
[   263.198] 	Module class: X.Org Video Driver
[   263.198] 	ABI class: X.Org Video Driver, version 25.2
[   263.198] xf86: found device 0
[   263.199] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/event2)
[   263.199] (**) Logitech USB Trackball: Applying InputClass "evdev pointer catchall"
[   263.199] (**) Logitech USB Trackball: Applying InputClass "libinput pointer catchall"
[   263.199] (**) Logitech USB Trackball: Applying InputClass "evdev pointer catchall"
[   263.199] (**) Logitech USB Trackball: Applying InputClass "Marble Mouse"
[   263.199] (II) Using input driver 'evdev' for 'Logitech USB Trackball'
[   263.256] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 39 paused 0
[   263.256] (**) Logitech USB Trackball: always reports core events
[   263.256] (**) evdev: Logitech USB Trackball: Device: "/dev/input/event2"
[   263.256] (--) evdev: Logitech USB Trackball: Vendor 0x46d Product 0xc408
[   263.256] (--) evdev: Logitech USB Trackball: Found 9 mouse buttons
[   263.256] (--) evdev: Logitech USB Trackball: Found relative axes
[   263.256] (--) evdev: Logitech USB Trackball: Found x and y relative axes
[   263.256] (II) evdev: Logitech USB Trackball: Configuring as mouse
[   263.256] (**) Option "Emulate3Buttons" "true"
[   263.256] (**) Option "EmulateWheel" "true"
[   263.256] (**) Option "EmulateWheelButton" "8"
[   263.256] (**) Option "YAxisMapping" "4 5"
[   263.256] (**) evdev: Logitech USB Trackball: YAxisMapping: buttons 4 and 5
[   263.256] (**) Option "XAxisMapping" "6 7"
[   263.256] (**) evdev: Logitech USB Trackball: XAxisMapping: buttons 6 and 7
[   263.256] (**) evdev: Logitech USB Trackball: EmulateWheelButton: 8, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   263.256] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/0003:046D:C408.0001/input/input2/event2"
[   263.257] (II) XINPUT: Adding extended input device "Logitech USB Trackball" (type: MOUSE, id 8)
[   263.257] (II) evdev: Logitech USB Trackball: initialized for relative axes.
[   263.257] (**) Logitech USB Trackball: (accel) keeping acceleration scheme 1
[   263.257] (**) Logitech USB Trackball: (accel) acceleration profile 0
[   263.257] (**) Logitech USB Trackball: (accel) acceleration factor: 2.000
[   263.257] (**) Logitech USB Trackball: (accel) acceleration threshold: 4
[   263.258] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/mouse0)
[   263.258] (II) No input driver specified, ignoring this device.
[   263.258] (II) This device may have been added with another device file.
[   263.259] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event10)
[   263.259] (II) No input driver specified, ignoring this device.
[   263.259] (II) This device may have been added with another device file.
[   263.260] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event11)
[   263.260] (II) No input driver specified, ignoring this device.
[   263.260] (II) This device may have been added with another device file.
[   263.260] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event12)
[   263.260] (II) No input driver specified, ignoring this device.
[   263.260] (II) This device may have been added with another device file.
[   263.261] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event5)
[   263.261] (II) No input driver specified, ignoring this device.
[   263.261] (II) This device may have been added with another device file.
[   263.262] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event6)
[   263.262] (II) No input driver specified, ignoring this device.
[   263.262] (II) This device may have been added with another device file.
[   263.262] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
[   263.262] (II) No input driver specified, ignoring this device.
[   263.262] (II) This device may have been added with another device file.
[   263.263] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event8)
[   263.263] (II) No input driver specified, ignoring this device.
[   263.263] (II) This device may have been added with another device file.
[   263.264] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event9)
[   263.264] (II) No input driver specified, ignoring this device.
[   263.264] (II) This device may have been added with another device file.
[   263.265] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[   263.265] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[   263.265] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[   263.265] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[   263.265] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[   263.266] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 40 paused 0
[   263.266] (**) AT Translated Set 2 keyboard: always reports core events
[   263.266] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[   263.266] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[   263.266] (--) evdev: AT Translated Set 2 keyboard: Found keys
[   263.266] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[   263.266] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[   263.266] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[   263.266] (**) Option "xkb_rules" "evdev"
[   263.267] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[   263.267] (II) No input driver specified, ignoring this device.
[   263.267] (II) This device may have been added with another device file.
[   263.280] (II) config/udev: removing GPU device /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0 /dev/dri/card0
[   263.280] (II) config/udev: Adding drm device (/dev/dri/card0)
[   263.280] (II) xfree86: Adding drm device (/dev/dri/card0)
[   263.280] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[   263.281] (EE) systemd-logind: failed to take device /dev/dri/card0: Device or resource busy
[   263.281] (II) LoadModule: "modesetting"
[   263.281] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   263.281] (II) Module modesetting: vendor="X.Org Foundation"
[   263.281] 	compiled for 1.21.1.4, module version = 1.21.1
[   263.281] 	Module class: X.Org Video Driver
[   263.281] 	ABI class: X.Org Video Driver, version 25.2
[   263.281] (II) UnloadModule: "modesetting"
[   263.281] (II) Unloading modesetting
[   263.281] (II) Failed to load module "modesetting" (already loaded, 0)
[   263.281] xf86: found device 0
[   831.030] (II) systemd-logind: got pause for 13:66
[   831.030] (II) systemd-logind: got pause for 13:67
[   831.030] (II) systemd-logind: got pause for 13:65
[   831.030] (II) systemd-logind: got pause for 13:64
[   831.076] (II) systemd-logind: got resume for 13:66
[   831.135] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[   831.211] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   831.211] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   831.211] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   831.211] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   831.211] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   831.211] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   831.211] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   831.211] (II) NVIDIA(0):     Config Options in the README.
[   831.277] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[   831.277] (II) NVIDIA(GPU-0):     3D Vision stereo.
[   831.285] (II) systemd-logind: got resume for 13:67
[   831.286] (II) systemd-logind: got resume for 13:65
[   831.286] (II) systemd-logind: got resume for 13:64

Xorg.0.log.old:

[ 52455.141] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[ 52455.141] Current Operating System: Linux quark 6.0.10-arch2-1 #1 SMP PREEMPT_DYNAMIC Sat, 26 Nov 2022 16:51:18 +0000 x86_64
[ 52455.141] Kernel command line: root=/dev/sda3 rw resume=UUID=5b82083b-0a88-4b2f-941c-8d0f07f8de60 resume_offset=58128384 initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux 
[ 52455.141]  
[ 52455.142] Current version of pixman: 0.42.2
[ 52455.142] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 52455.142] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 52455.142] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec  1 13:41:46 2022
[ 52455.181] (==) Using config file: "/etc/X11/xorg.conf"
[ 52455.182] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 52455.182] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 52455.260] (==) ServerLayout "Layout0"
[ 52455.260] (**) |-->Screen "Screen0" (0)
[ 52455.260] (**) |   |-->Monitor "Monitor0"
[ 52455.260] (**) |   |-->Device "Device0"
[ 52455.260] (**) |   |-->GPUDevice "Nvidia Card"
[ 52455.260] (**) |   |-->GPUDevice "Device1"
[ 52455.260] (**) |-->Input Device "Keyboard0"
[ 52455.260] (**) |-->Input Device "Mouse0"
[ 52455.260] (**) Option "Xinerama" "0"
[ 52455.260] (**) Option "IgnoreABI" "1"
[ 52455.261] (**) Ignoring ABI Version
[ 52455.261] (==) Automatically adding devices
[ 52455.261] (==) Automatically enabling devices
[ 52455.261] (==) Automatically adding GPU devices
[ 52455.261] (==) Automatically binding GPU devices
[ 52455.261] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 52455.261] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[ 52455.261] 	Entry deleted from font path.
[ 52455.261] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[ 52455.261] 	Entry deleted from font path.
[ 52455.261] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[ 52455.261] 	Entry deleted from font path.
[ 52455.261] (==) FontPath set to:
	/usr/share/fonts/misc,
	/usr/share/fonts/TTF,
	/usr/share/fonts/Type1
[ 52455.261] (**) ModulePath set to "/usr/lib64/nvidia/xorg,/usr/lib64/xorg/modules"
[ 52455.261] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 52455.261] (WW) Disabling Keyboard0
[ 52455.261] (WW) Disabling Mouse0
[ 52455.261] (II) Module ABI versions:
[ 52455.261] 	X.Org ANSI C Emulation: 0.4
[ 52455.261] 	X.Org Video Driver: 25.2
[ 52455.261] 	X.Org XInput driver : 24.4
[ 52455.261] 	X.Org Server Extension : 10.0
[ 52455.262] (++) using VT number 1

[ 52455.264] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_33
[ 52455.265] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 52455.265] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[ 52455.266] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[ 52455.269] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib64/nvidia/xorg,/usr/lib64/xorg/modules"
[ 52455.269] (**) OutputClass "nvidia" setting /dev/dri/card0 as PrimaryGPU
[ 52455.272] (--) PCI:*(1@0:0:0) 10de:0640:3842:c954 rev 161, Mem @ 0xe6000000/16777216, 0xd0000000/268435456, 0xe4000000/33554432, I/O @ 0x00009000/128, BIOS @ 0x????????/131072
[ 52455.272] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 52455.272] (II) LoadModule: "glx"
[ 52455.283] (II) Loading /usr/lib/nvidia/xorg/libglx.so
[ 52455.491] (II) Module glx: vendor="NVIDIA Corporation"
[ 52455.491] 	compiled for 4.0.2, module version = 1.0.0
[ 52455.492] 	Module class: X.Org Server Extension
[ 52455.499] (II) NVIDIA GLX Module  340.108  Wed Dec 11 14:26:50 PST 2019
[ 52455.500] (II) LoadModule: "nvidia"
[ 52455.531] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 52455.566] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 52455.566] 	compiled for 4.0.2, module version = 1.0.0
[ 52455.566] 	Module class: X.Org Video Driver
[ 52455.566] ================ WARNING WARNING WARNING WARNING ================
[ 52455.566] This server has a video driver ABI version of 25.2 that this
driver does not officially support.  Please check
http://www.nvidia.com/ for driver updates or downgrade to an X
server with a supported driver ABI.
[ 52455.566] =================================================================
[ 52455.566] (WW) NVIDIA: The driver will continue to load, but may behave strangely.
[ 52455.566] (WW) NVIDIA: This driver was compiled against the X.Org server SDK from commit e6ef2b12404dfec7f23592a3524d2a63d9d25802 and may not be compatible with the final version of this SDK.
[ 52455.566] (II) NVIDIA dlloader X Driver  340.108  Wed Dec 11 14:06:00 PST 2019
[ 52455.566] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 52455.567] (II) Loading sub module "fb"
[ 52455.567] (II) LoadModule: "fb"
[ 52455.567] (II) Module "fb" already built-in
[ 52455.567] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 52455.567] (II) Loading sub module "wfb"
[ 52455.567] (II) LoadModule: "wfb"
[ 52455.587] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 52455.587] (II) Module wfb: vendor="X.Org Foundation"
[ 52455.587] 	compiled for 1.21.1.4, module version = 1.0.0
[ 52455.587] 	ABI class: X.Org ANSI C Emulation, version 0.4
[ 52455.587] (II) Loading sub module "ramdac"
[ 52455.587] (II) LoadModule: "ramdac"
[ 52455.587] (II) Module "ramdac" already built-in
[ 52455.588] (EE) Screen 1 deleted because of no matching config section.
[ 52455.588] (II) UnloadModule: "nvidia"
[ 52455.588] (II) UnloadSubModule: "wfb"
[ 52455.588] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 52455.588] (==) NVIDIA(0): RGB weight 888
[ 52455.588] (==) NVIDIA(0): Default visual is TrueColor
[ 52455.588] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 52455.588] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[ 52455.588] (**) NVIDIA(0): Option "Stereo" "0"
[ 52455.588] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-0"
[ 52455.588] (**) NVIDIA(0): Option "SLI" "Off"
[ 52455.588] (**) NVIDIA(0): Option "MultiGPU" "Off"
[ 52455.588] (**) NVIDIA(0): Option "BaseMosaic" "off"
[ 52455.588] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[ 52455.588] (**) NVIDIA(0): Stereo disabled by request
[ 52455.588] (**) NVIDIA(0): NVIDIA SLI disabled.
[ 52455.588] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[ 52455.588] (**) NVIDIA(0): Option "MetaModes" "DVI-I-2: nvidia-auto-select +0+0"
[ 52455.588] (**) NVIDIA(0): Enabling 2D acceleration
[ 52456.280] (II) NVIDIA(0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 52456.280] (II) NVIDIA(0):     3D Vision stereo.
[ 52456.282] (II) NVIDIA(0): NVIDIA GPU GeForce 9500 GT (G96) at PCI:1:0:0 (GPU-0)
[ 52456.282] (--) NVIDIA(0): Memory: 524288 kBytes
[ 52456.282] (--) NVIDIA(0): VideoBIOS: 62.94.29.00.50
[ 52456.282] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 52456.284] (--) NVIDIA(0): Valid display device(s) on GeForce 9500 GT at PCI:1:0:0
[ 52456.284] (--) NVIDIA(0):     CRT-0
[ 52456.284] (--) NVIDIA(0):     CRT-1
[ 52456.284] (--) NVIDIA(0):     TV-0
[ 52456.284] (--) NVIDIA(0):     DFP-0
[ 52456.284] (--) NVIDIA(0):     Samsung SyncMaster (DFP-1) (boot, connected)
[ 52456.284] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[ 52456.284] (--) NVIDIA(GPU-0): CRT-1: 400.0 MHz maximum pixel clock
[ 52456.284] (--) NVIDIA(GPU-0): TV-0: 400.0 MHz maximum pixel clock
[ 52456.284] (--) NVIDIA(0): DFP-0: Internal TMDS
[ 52456.284] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 52456.284] (--) NVIDIA(0): Samsung SyncMaster (DFP-1): Internal TMDS
[ 52456.284] (--) NVIDIA(GPU-0): Samsung SyncMaster (DFP-1): 330.0 MHz maximum pixel clock
[ 52456.284] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 52456.284] (**) NVIDIA(0):     device Samsung SyncMaster (DFP-1) (Using EDID frequencies
[ 52456.284] (**) NVIDIA(0):     has been enabled on all display devices.)
[ 52456.296] (WW) NVIDIA(0): No valid modes for "DVI-I-2:nvidia-auto-select+0+0";
[ 52456.296] (WW) NVIDIA(0):     removing.
[ 52456.297] (WW) NVIDIA(0): 
[ 52456.297] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
[ 52456.297] (WW) NVIDIA(0):     "nvidia-auto-select".
[ 52456.297] (WW) NVIDIA(0): 
[ 52456.297] (II) NVIDIA(0): Validated MetaModes:
[ 52456.297] (II) NVIDIA(0):     "DFP-1:nvidia-auto-select"
[ 52456.297] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
[ 52456.321] (--) NVIDIA(0): DPI set to (85, 86); computed from "UseEdidDpi" X config
[ 52456.322] (--) NVIDIA(0):     option
[ 52456.322] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
[ 52456.325] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 52456.325] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 52456.325] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 52456.325] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 52456.325] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 52456.325] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 52456.325] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 52456.325] (II) NVIDIA(0):     Config Options in the README.
[ 52456.326] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 52456.418] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 52456.418] (==) NVIDIA(0): Backing store enabled
[ 52456.418] (==) NVIDIA(0): Silken mouse enabled
[ 52456.418] (**) NVIDIA(0): DPMS enabled
[ 52456.418] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[ 52456.418] (II) Loading sub module "dri2"
[ 52456.418] (II) LoadModule: "dri2"
[ 52456.418] (II) Module "dri2" already built-in
[ 52456.418] (II) NVIDIA(0): [DRI2] Setup complete
[ 52456.418] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[ 52456.419] (II) Initializing extension Generic Event Extension
[ 52456.419] (II) Initializing extension SHAPE
[ 52456.419] (II) Initializing extension MIT-SHM
[ 52456.419] (II) Initializing extension XInputExtension
[ 52456.419] (II) Initializing extension XTEST
[ 52456.420] (II) Initializing extension BIG-REQUESTS
[ 52456.420] (II) Initializing extension SYNC
[ 52456.420] (II) Initializing extension XKEYBOARD
[ 52456.420] (II) Initializing extension XC-MISC
[ 52456.421] (II) Initializing extension SECURITY
[ 52456.421] (II) Initializing extension XFIXES
[ 52456.421] (II) Initializing extension RENDER
[ 52456.421] (II) Initializing extension RANDR
[ 52456.422] (II) Initializing extension COMPOSITE
[ 52456.422] (II) Initializing extension DAMAGE
[ 52456.422] (II) Initializing extension MIT-SCREEN-SAVER
[ 52456.422] (II) Initializing extension DOUBLE-BUFFER
[ 52456.423] (II) Initializing extension RECORD
[ 52456.423] (II) Initializing extension DPMS
[ 52456.423] (II) Initializing extension Present
[ 52456.423] (II) Initializing extension DRI3
[ 52456.423] (II) Initializing extension X-Resource
[ 52456.423] (II) Initializing extension XVideo
[ 52456.424] (II) Initializing extension XVideo-MotionCompensation
[ 52456.424] (II) Initializing extension XFree86-VidModeExtension
[ 52456.424] (II) Initializing extension XFree86-DGA
[ 52456.424] (II) Initializing extension XFree86-DRI
[ 52456.424] (II) Initializing extension DRI2
[ 52456.424] (II) Initializing extension GLX
[ 52456.424] (II) Initializing extension GLX
[ 52456.424] (II) Indirect GLX disabled.(II) Initializing extension NV-GLX
[ 52456.425] (II) Initializing extension NV-CONTROL
[ 52456.425] (II) Initializing extension XINERAMA
[ 52456.727] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 52456.727] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 52456.727] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 52456.727] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 52456.727] (II) LoadModule: "evdev"
[ 52456.727] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 52456.758] (II) Module evdev: vendor="X.Org Foundation"
[ 52456.758] 	compiled for 1.21.1.1, module version = 2.10.6
[ 52456.758] 	Module class: X.Org XInput Driver
[ 52456.758] 	ABI class: X.Org XInput driver, version 24.4
[ 52456.758] (II) Using input driver 'evdev' for 'Power Button'
[ 52456.759] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 37 paused 0
[ 52456.759] (**) Power Button: always reports core events
[ 52456.759] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 52456.759] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 52456.759] (--) evdev: Power Button: Found keys
[ 52456.759] (II) evdev: Power Button: Configuring as keyboard
[ 52456.759] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 52456.759] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 52456.759] (**) Option "xkb_rules" "evdev"
[ 52456.761] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 52456.761] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 52456.761] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 52456.761] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 52456.761] (II) Using input driver 'evdev' for 'Power Button'
[ 52456.762] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 38 paused 0
[ 52456.762] (**) Power Button: always reports core events
[ 52456.762] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 52456.762] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 52456.762] (--) evdev: Power Button: Found keys
[ 52456.762] (II) evdev: Power Button: Configuring as keyboard
[ 52456.762] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[ 52456.762] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 52456.762] (**) Option "xkb_rules" "evdev"
[ 52456.764] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/event2)
[ 52456.764] (**) Logitech USB Trackball: Applying InputClass "evdev pointer catchall"
[ 52456.764] (**) Logitech USB Trackball: Applying InputClass "libinput pointer catchall"
[ 52456.764] (**) Logitech USB Trackball: Applying InputClass "evdev pointer catchall"
[ 52456.764] (**) Logitech USB Trackball: Applying InputClass "Marble Mouse"
[ 52456.764] (II) Using input driver 'evdev' for 'Logitech USB Trackball'
[ 52456.821] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 39 paused 0
[ 52456.821] (**) Logitech USB Trackball: always reports core events
[ 52456.821] (**) evdev: Logitech USB Trackball: Device: "/dev/input/event2"
[ 52456.821] (--) evdev: Logitech USB Trackball: Vendor 0x46d Product 0xc408
[ 52456.821] (--) evdev: Logitech USB Trackball: Found 9 mouse buttons
[ 52456.821] (--) evdev: Logitech USB Trackball: Found relative axes
[ 52456.821] (--) evdev: Logitech USB Trackball: Found x and y relative axes
[ 52456.821] (II) evdev: Logitech USB Trackball: Configuring as mouse
[ 52456.821] (**) Option "Emulate3Buttons" "true"
[ 52456.821] (**) Option "EmulateWheel" "true"
[ 52456.822] (**) Option "EmulateWheelButton" "8"
[ 52456.822] (**) Option "YAxisMapping" "4 5"
[ 52456.822] (**) evdev: Logitech USB Trackball: YAxisMapping: buttons 4 and 5
[ 52456.822] (**) Option "XAxisMapping" "6 7"
[ 52456.822] (**) evdev: Logitech USB Trackball: XAxisMapping: buttons 6 and 7
[ 52456.822] (**) evdev: Logitech USB Trackball: EmulateWheelButton: 8, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 52456.822] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/0003:046D:C408.0001/input/input2/event2"
[ 52456.822] (II) XINPUT: Adding extended input device "Logitech USB Trackball" (type: MOUSE, id 8)
[ 52456.822] (II) evdev: Logitech USB Trackball: initialized for relative axes.
[ 52456.822] (**) Logitech USB Trackball: (accel) keeping acceleration scheme 1
[ 52456.822] (**) Logitech USB Trackball: (accel) acceleration profile 0
[ 52456.822] (**) Logitech USB Trackball: (accel) acceleration factor: 2.000
[ 52456.822] (**) Logitech USB Trackball: (accel) acceleration threshold: 4
[ 52456.823] (II) config/udev: Adding input device Logitech USB Trackball (/dev/input/mouse0)
[ 52456.823] (II) No input driver specified, ignoring this device.
[ 52456.823] (II) This device may have been added with another device file.
[ 52456.824] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event10)
[ 52456.824] (II) No input driver specified, ignoring this device.
[ 52456.824] (II) This device may have been added with another device file.
[ 52456.825] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event11)
[ 52456.825] (II) No input driver specified, ignoring this device.
[ 52456.825] (II) This device may have been added with another device file.
[ 52456.826] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event12)
[ 52456.826] (II) No input driver specified, ignoring this device.
[ 52456.826] (II) This device may have been added with another device file.
[ 52456.826] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event5)
[ 52456.826] (II) No input driver specified, ignoring this device.
[ 52456.826] (II) This device may have been added with another device file.
[ 52456.827] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event6)
[ 52456.827] (II) No input driver specified, ignoring this device.
[ 52456.827] (II) This device may have been added with another device file.
[ 52456.828] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
[ 52456.828] (II) No input driver specified, ignoring this device.
[ 52456.828] (II) This device may have been added with another device file.
[ 52456.828] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event8)
[ 52456.828] (II) No input driver specified, ignoring this device.
[ 52456.828] (II) This device may have been added with another device file.
[ 52456.829] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event9)
[ 52456.829] (II) No input driver specified, ignoring this device.
[ 52456.829] (II) This device may have been added with another device file.
[ 52456.830] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[ 52456.830] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 52456.830] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 52456.830] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 52456.830] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 52456.831] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 40 paused 0
[ 52456.831] (**) AT Translated Set 2 keyboard: always reports core events
[ 52456.831] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event3"
[ 52456.831] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 52456.831] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 52456.831] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 52456.831] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[ 52456.831] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 52456.831] (**) Option "xkb_rules" "evdev"
[ 52456.832] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 52456.832] (II) No input driver specified, ignoring this device.
[ 52456.832] (II) This device may have been added with another device file.
[ 69219.958] (II) systemd-logind: got pause for 13:67
[ 69219.958] (II) systemd-logind: got pause for 13:65
[ 69219.958] (II) systemd-logind: got pause for 13:64
[ 69219.958] (II) systemd-logind: got pause for 13:66
[ 69219.964] (II) systemd-logind: got resume for 226:0
[ 69220.036] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 69220.120] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 69220.120] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 69220.120] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 69220.120] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 69220.120] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 69220.120] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 69220.120] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 69220.120] (II) NVIDIA(0):     Config Options in the README.
[ 69220.188] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 69220.298] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 69220.308] (II) systemd-logind: got resume for 13:67
[ 69220.308] (II) systemd-logind: got resume for 13:65
[ 69220.308] (II) systemd-logind: got resume for 13:64
[ 69220.308] (II) systemd-logind: got resume for 13:66
[ 71953.589] (II) systemd-logind: got pause for 13:67
[ 71953.589] (II) systemd-logind: got pause for 13:65
[ 71953.589] (II) systemd-logind: got pause for 13:64
[ 71953.589] (II) systemd-logind: got pause for 13:66
[ 71953.604] (II) systemd-logind: got resume for 226:0
[ 71953.672] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 71953.755] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 71953.755] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 71953.755] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 71953.755] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 71953.755] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 71953.755] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 71953.755] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 71953.755] (II) NVIDIA(0):     Config Options in the README.
[ 71953.825] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 71953.825] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 71953.844] (II) systemd-logind: got resume for 13:67
[ 71953.845] (II) systemd-logind: got resume for 13:65
[ 71953.845] (II) systemd-logind: got resume for 13:64
[ 71953.845] (II) systemd-logind: got resume for 13:66
[ 84252.158] (II) systemd-logind: got pause for 13:67
[ 84257.248] (II) systemd-logind: got pause for 13:65
[ 84257.275] (II) systemd-logind: got pause for 13:64
[ 84257.298] (II) systemd-logind: got pause for 13:66
[ 84257.321] (II) systemd-logind: got resume for 226:0
[ 84257.382] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 84257.460] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 84257.460] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 84257.460] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 84257.460] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 84257.460] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 84257.460] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 84257.460] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 84257.460] (II) NVIDIA(0):     Config Options in the README.
[ 84257.526] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 84257.526] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 84257.535] (II) systemd-logind: got resume for 13:67
[ 84257.535] (II) systemd-logind: got resume for 13:65
[ 84257.535] (II) systemd-logind: got resume for 13:64
[ 84257.535] (II) systemd-logind: got resume for 13:66
[ 85504.282] (II) systemd-logind: got pause for 13:67
[ 85504.282] (II) systemd-logind: got pause for 13:65
[ 85504.282] (II) systemd-logind: got pause for 13:64
[ 85504.282] (II) systemd-logind: got pause for 13:66
[ 85509.441] (II) systemd-logind: got resume for 226:0
[ 85509.513] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 85509.603] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 85509.603] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 85509.603] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 85509.603] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 85509.603] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 85509.603] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 85509.603] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 85509.603] (II) NVIDIA(0):     Config Options in the README.
[ 85509.672] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 85509.672] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 85509.681] (II) systemd-logind: got resume for 13:67
[ 85509.681] (II) systemd-logind: got resume for 13:65
[ 85509.681] (II) systemd-logind: got resume for 13:64
[ 85509.682] (II) systemd-logind: got resume for 13:66
[ 87253.226] (II) systemd-logind: got pause for 13:67
[ 87253.226] (II) systemd-logind: got pause for 13:65
[ 87253.226] (II) systemd-logind: got pause for 13:64
[ 87253.226] (II) systemd-logind: got pause for 13:66
[ 87258.337] (II) systemd-logind: got resume for 226:0
[ 87258.393] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 87258.477] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 87258.477] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 87258.477] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 87258.477] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 87258.477] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 87258.477] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 87258.477] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 87258.477] (II) NVIDIA(0):     Config Options in the README.
[ 87258.543] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 87258.543] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 87258.552] (II) systemd-logind: got resume for 13:67
[ 87258.552] (II) systemd-logind: got resume for 13:65
[ 87258.552] (II) systemd-logind: got resume for 13:64
[ 87258.552] (II) systemd-logind: got resume for 13:66
[ 92466.222] (II) systemd-logind: got pause for 13:67
[ 92466.315] (II) systemd-logind: got pause for 13:65
[ 92466.330] (II) systemd-logind: got pause for 13:64
[ 92466.364] (II) systemd-logind: got pause for 13:66
[ 92466.381] (II) systemd-logind: got resume for 226:0
[ 92466.448] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 92466.533] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 92466.533] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 92466.533] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 92466.533] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 92466.533] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 92466.533] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 92466.533] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 92466.533] (II) NVIDIA(0):     Config Options in the README.
[ 92466.601] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 92466.601] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 92466.611] (II) systemd-logind: got resume for 13:67
[ 92466.611] (II) systemd-logind: got resume for 13:65
[ 92466.611] (II) systemd-logind: got resume for 13:64
[ 92466.612] (II) systemd-logind: got resume for 13:66
[ 94489.043] (II) systemd-logind: got pause for 13:67
[ 94489.043] (II) systemd-logind: got pause for 13:65
[ 94489.043] (II) systemd-logind: got pause for 13:64
[ 94489.043] (II) systemd-logind: got pause for 13:66
[ 94489.067] (II) systemd-logind: got resume for 226:0
[ 94489.123] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 94489.202] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 94489.203] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 94489.203] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 94489.203] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 94489.203] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 94489.203] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 94489.203] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 94489.203] (II) NVIDIA(0):     Config Options in the README.
[ 94489.269] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 94489.269] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 94489.278] (II) systemd-logind: got resume for 13:67
[ 94489.278] (II) systemd-logind: got resume for 13:65
[ 94489.278] (II) systemd-logind: got resume for 13:64
[ 94489.278] (II) systemd-logind: got resume for 13:66
[ 99657.047] (II) systemd-logind: got pause for 13:67
[ 99657.047] (II) systemd-logind: got pause for 13:65
[ 99657.047] (II) systemd-logind: got pause for 13:64
[ 99657.047] (II) systemd-logind: got pause for 13:66
[ 99657.063] (II) systemd-logind: got resume for 226:0
[ 99657.134] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 99657.211] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 99657.211] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 99657.211] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 99657.211] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 99657.211] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 99657.211] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 99657.211] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 99657.211] (II) NVIDIA(0):     Config Options in the README.
[ 99657.283] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 99657.283] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 99657.293] (II) systemd-logind: got resume for 13:67
[ 99657.293] (II) systemd-logind: got resume for 13:65
[ 99657.294] (II) systemd-logind: got resume for 13:64
[ 99657.294] (II) systemd-logind: got resume for 13:66
[ 99775.667] (II) systemd-logind: got pause for 13:67
[ 99775.667] (II) systemd-logind: got pause for 13:65
[ 99775.667] (II) systemd-logind: got pause for 13:64
[ 99775.667] (II) systemd-logind: got pause for 13:66
[ 99775.672] (II) systemd-logind: got resume for 226:0
[ 99775.737] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[ 99775.822] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 99775.822] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[ 99775.822] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[ 99775.822] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[ 99775.822] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[ 99775.822] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[ 99775.822] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[ 99775.822] (II) NVIDIA(0):     Config Options in the README.
[ 99775.888] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[ 99775.888] (II) NVIDIA(GPU-0):     3D Vision stereo.
[ 99775.897] (II) systemd-logind: got resume for 13:67
[ 99775.897] (II) systemd-logind: got resume for 13:65
[ 99775.897] (II) systemd-logind: got resume for 13:64
[ 99775.897] (II) systemd-logind: got resume for 13:66
[102115.706] (II) systemd-logind: got pause for 13:67
[102115.706] (II) systemd-logind: got pause for 13:65
[102115.707] (II) systemd-logind: got pause for 13:64
[102115.707] (II) systemd-logind: got pause for 13:66
[102115.749] (II) systemd-logind: got resume for 226:0
[102115.834] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[102115.912] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[102115.912] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[102115.912] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[102115.912] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[102115.912] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[102115.912] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[102115.912] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[102115.912] (II) NVIDIA(0):     Config Options in the README.
[102115.978] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[102115.978] (II) NVIDIA(GPU-0):     3D Vision stereo.
[102115.987] (II) systemd-logind: got resume for 13:67
[102115.987] (II) systemd-logind: got resume for 13:65
[102115.988] (II) systemd-logind: got resume for 13:64
[102115.988] (II) systemd-logind: got resume for 13:66
[105661.957] (II) systemd-logind: got pause for 13:67
[105661.957] (II) systemd-logind: got pause for 13:65
[105661.957] (II) systemd-logind: got pause for 13:64
[105661.957] (II) systemd-logind: got pause for 13:66
[105661.973] (II) systemd-logind: got resume for 226:0
[105662.084] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[105662.163] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[105662.255] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[105662.255] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[105662.255] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[105662.255] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[105662.255] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[105662.255] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[105662.255] (II) NVIDIA(0):     Config Options in the README.
[105662.321] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[105662.321] (II) NVIDIA(GPU-0):     3D Vision stereo.
[105662.330] (II) systemd-logind: got resume for 13:67
[105662.330] (II) systemd-logind: got resume for 13:65
[105662.331] (II) systemd-logind: got resume for 13:64
[105662.331] (II) systemd-logind: got resume for 13:66
[107337.467] (II) systemd-logind: got pause for 13:67
[107337.467] (II) systemd-logind: got pause for 13:65
[107337.467] (II) systemd-logind: got pause for 13:64
[107337.467] (II) systemd-logind: got pause for 13:66
[107337.485] (II) systemd-logind: got resume for 226:0
[107337.554] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[107337.631] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[107337.631] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[107337.631] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[107337.631] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[107337.631] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[107337.631] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[107337.632] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[107337.632] (II) NVIDIA(0):     Config Options in the README.
[107337.698] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[107337.699] (II) NVIDIA(GPU-0):     3D Vision stereo.
[107337.707] (II) systemd-logind: got resume for 13:67
[107337.707] (II) systemd-logind: got resume for 13:65
[107337.707] (II) systemd-logind: got resume for 13:64
[107337.708] (II) systemd-logind: got resume for 13:66
[109665.359] (II) systemd-logind: got pause for 13:67
[109665.359] (II) systemd-logind: got pause for 13:65
[109665.359] (II) systemd-logind: got pause for 13:64
[109665.360] (II) systemd-logind: got pause for 13:66
[109665.386] (II) systemd-logind: got resume for 226:0
[109665.452] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[109665.525] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[109665.525] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[109665.525] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[109665.525] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[109665.525] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[109665.525] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[109665.525] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[109665.525] (II) NVIDIA(0):     Config Options in the README.
[109665.592] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[109665.592] (II) NVIDIA(GPU-0):     3D Vision stereo.
[109665.602] (II) systemd-logind: got resume for 13:67
[109665.602] (II) systemd-logind: got resume for 13:65
[109665.602] (II) systemd-logind: got resume for 13:64
[109665.602] (II) systemd-logind: got resume for 13:66
[135901.731] (II) systemd-logind: got pause for 13:67
[135901.829] (II) systemd-logind: got pause for 13:65
[135901.863] (II) systemd-logind: got pause for 13:64
[135901.889] (II) systemd-logind: got pause for 13:66
[135901.910] (II) systemd-logind: got resume for 226:0
[135901.969] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[135902.046] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[135902.046] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[135902.046] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[135902.046] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[135902.046] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[135902.046] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[135902.046] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[135902.046] (II) NVIDIA(0):     Config Options in the README.
[135902.113] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[135902.114] (II) NVIDIA(GPU-0):     3D Vision stereo.
[135902.122] (II) systemd-logind: got resume for 13:67
[135902.123] (II) systemd-logind: got resume for 13:65
[135902.123] (II) systemd-logind: got resume for 13:64
[135902.123] (II) systemd-logind: got resume for 13:66
[145438.172] (II) systemd-logind: got pause for 13:67
[145438.189] (II) systemd-logind: got pause for 13:65
[145438.202] (II) systemd-logind: got pause for 13:64
[145438.219] (II) systemd-logind: got pause for 13:66
[145438.235] (II) systemd-logind: got resume for 226:0
[145438.291] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[145438.365] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[145438.365] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[145438.365] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[145438.365] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[145438.365] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[145438.366] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[145438.366] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[145438.366] (II) NVIDIA(0):     Config Options in the README.
[145438.431] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[145438.431] (II) NVIDIA(GPU-0):     3D Vision stereo.
[145438.440] (II) systemd-logind: got resume for 13:67
[145438.440] (II) systemd-logind: got resume for 13:65
[145438.441] (II) systemd-logind: got resume for 13:64
[145438.441] (II) systemd-logind: got resume for 13:66
[188433.362] (II) systemd-logind: got pause for 13:67
[188433.378] (II) systemd-logind: got pause for 13:65
[188433.391] (II) systemd-logind: got pause for 13:64
[188433.408] (II) systemd-logind: got pause for 13:66
[188433.424] (II) systemd-logind: got resume for 226:0
[188433.474] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[188433.695] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[188433.695] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[188433.695] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[188433.695] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[188433.695] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[188433.695] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[188433.695] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[188433.695] (II) NVIDIA(0):     Config Options in the README.
[188433.761] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[188433.761] (II) NVIDIA(GPU-0):     3D Vision stereo.
[188433.767] (II) systemd-logind: got resume for 13:67
[188433.767] (II) systemd-logind: got resume for 13:65
[188433.767] (II) systemd-logind: got resume for 13:64
[188433.768] (II) systemd-logind: got resume for 13:66
[192684.254] (II) systemd-logind: got pause for 13:67
[192684.254] (II) systemd-logind: got pause for 13:65
[192684.254] (II) systemd-logind: got pause for 13:64
[192684.254] (II) systemd-logind: got pause for 13:66
[192684.280] (II) systemd-logind: got resume for 226:0
[192684.375] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[192684.449] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[192684.449] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[192684.449] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[192684.449] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[192684.449] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[192684.449] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[192684.449] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[192684.449] (II) NVIDIA(0):     Config Options in the README.
[192684.521] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-1)) does not support NVIDIA
[192684.521] (II) NVIDIA(GPU-0):     3D Vision stereo.
[192684.531] (II) systemd-logind: got resume for 13:67
[192684.531] (II) systemd-logind: got resume for 13:65
[192684.532] (II) systemd-logind: got resume for 13:64
[192684.532] (II) systemd-logind: got resume for 13:66
[192829.988] (II) evdev: Logitech USB Trackball: Close
[192829.997] (II) UnloadModule: "evdev"
[192829.997] (II) systemd-logind: releasing fd for 13:66
[192830.047] (II) evdev: Power Button: Close
[192830.047] (II) UnloadModule: "evdev"
[192830.047] (II) systemd-logind: releasing fd for 13:64
[192830.067] (II) evdev: Power Button: Close
[192830.067] (II) UnloadModule: "evdev"
[192830.067] (II) systemd-logind: releasing fd for 13:65
[192830.084] (II) evdev: AT Translated Set 2 keyboard: Close
[192830.084] (II) UnloadModule: "evdev"
[192830.084] (II) systemd-logind: releasing fd for 13:67
[192830.472] (II) NVIDIA(GPU-0): Deleting GPU-0
[192830.494] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[192830.494] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[192830.494] (WW) xf86OpenConsole: VT_GETSTATE failed: Input/output error
[192830.495] (II) Server terminated successfully (0). Closing log file.

Last edited by lithium (2022-12-12 20:24:29)

seth · 2022-12-12 20:46:53

You are and were running on the nvidia GL implementation, there're no vesa nor fbdev drivers installed so there's no chance in that direction.
The old X11 server (you started a new one w/ the reboot) predates the update, so the "sanitizing" update and "good" tries ran on the same X11 server instance as the "bad" tries.
You also didn't somehow switch the input drivers (though libinput and evdev are available)

Though I will point out that

[   263.157] (II) xfree86: Adding drm device (/dev/dri/card0)
[   263.157] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[   263.158] (EE) systemd-logind: failed to take device /dev/dri/card0: Device or resource busy
[   263.158] (II) LoadModule: "modesetting"
[   263.158] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so

didn't exist in the old log.

Try to restart the X11 server and test the impact.
Then, though it's a far stretch, remove /etc/X11/xorg.conf and restart the server again
(it's an nvidia-settings generated one, full of cruft and references to dated and dead in the water input drivers - I do not hope this to be it, but the entire thing is strange AF)

/usr/bin/reflect from https://archlinux.org/packages/extra/x86_64/mesa-demos/ allows input and uses freeglut as well - might be an interesting cross-test…

lithium · 2022-12-12 22:32:09

seth wrote:

Try to restart the X11 server and test the impact.
Then, though it's a far stretch, remove /etc/X11/xorg.conf and restart the server again
(it's an nvidia-settings generated one, full of cruft and references to dated and dead in the water input drivers - I do not hope this to be it, but the entire thing is strange AF)
/usr/bin/reflect from https://archlinux.org/packages/extra/x86_64/mesa-demos/ allows input and uses freeglut as well - might be an interesting cross-test…

Restarted X11, doesn't work.
Deleted /etc/X11/xorg.conf and restarted X11, doesn't work.

reflect works, including the keyboard controls.

Alexpin · 2023-01-12 10:24:10

Hey there, I have the same issue on one of my computers. Did you have any luck in solving it, or narrowing it down?

hongy19 · 2023-01-29 09:36:57

Alexpin wrote:

Hey there, I have the same issue on one of my computers. Did you have any luck in solving it, or narrowing it down?

I has same issue. mupdf-gl doesn't response to keyboard from WSL2 but mupdf could work.

Alexpin · 2023-01-29 11:50:07

Interestingly, a workaround is using mupdf-git from the AUR.

Arch Linux

#1 2022-11-30 23:18:19

mupdf-gl not responsive to keyboard anymore

#2 2022-11-30 23:31:39

Re: mupdf-gl not responsive to keyboard anymore

#3 2022-12-01 04:41:37

Re: mupdf-gl not responsive to keyboard anymore

#4 2022-12-01 08:08:34

Re: mupdf-gl not responsive to keyboard anymore

#5 2022-12-01 21:47:58

Re: mupdf-gl not responsive to keyboard anymore

#6 2022-12-01 22:01:31

Re: mupdf-gl not responsive to keyboard anymore

#7 2022-12-01 22:42:51

Re: mupdf-gl not responsive to keyboard anymore

#8 2022-12-02 08:24:02

Re: mupdf-gl not responsive to keyboard anymore

#9 2022-12-02 22:52:45

Re: mupdf-gl not responsive to keyboard anymore

#10 2022-12-03 08:27:04

Re: mupdf-gl not responsive to keyboard anymore

#11 2022-12-05 18:30:17

Re: mupdf-gl not responsive to keyboard anymore

#12 2022-12-05 19:08:03

Re: mupdf-gl not responsive to keyboard anymore

#13 2022-12-05 22:36:49

Re: mupdf-gl not responsive to keyboard anymore

#14 2022-12-06 07:13:41

Re: mupdf-gl not responsive to keyboard anymore

#15 2022-12-06 17:59:44

Re: mupdf-gl not responsive to keyboard anymore

#16 2022-12-06 20:48:35

Re: mupdf-gl not responsive to keyboard anymore

#17 2022-12-06 21:47:56

Re: mupdf-gl not responsive to keyboard anymore

#18 2022-12-12 17:49:25

Re: mupdf-gl not responsive to keyboard anymore

#19 2022-12-12 18:48:28

Re: mupdf-gl not responsive to keyboard anymore

#20 2022-12-12 20:19:03

Re: mupdf-gl not responsive to keyboard anymore

#21 2022-12-12 20:46:53

Re: mupdf-gl not responsive to keyboard anymore

#22 2022-12-12 22:32:09

Re: mupdf-gl not responsive to keyboard anymore

#23 2023-01-12 10:24:10

Re: mupdf-gl not responsive to keyboard anymore

#24 2023-01-29 09:36:57

Re: mupdf-gl not responsive to keyboard anymore

#25 2023-01-29 11:50:07

Re: mupdf-gl not responsive to keyboard anymore

Board footer