Hybrid mode bug black screen with blinking underscore

System info:

Manjaro (5.15.85-1)
HP Pavilion Laptop 15-cs1xxx
Nvidia 1050 GTX mobile
Intel® Core™ i7-8565U × 8
NVIDIA Proprietary Drivers
Gnome (43.2) X11 + gdm

Steps to reproduce

Change from any other mode to hybrid
Reboot

Temporary "fix"
Execute sudo envycontrol --reset.
After reboot, command envycontrol -q returns hybrid mode but if I execute sudo envycontrol -s hybrid the bug triggers again

Can you get into GDM or is it straight not giving video output?

Straight not giving video output

Straight not giving video output

Did you enable the RTD3 option?

Straight not giving video output

Did you enable the RTD3 option?

I tried with that option enabled and disabled. Getting the same result in both scenarios

Straight not giving video output

Did you enable the RTD3 option?

I tried with that option enabled and disabled. Getting the same result in both scenarios

Try downgrading your Nvidia drivers, on my setup I'm experiencing black screens and freezes since 525.78 on hybrid mode after their failed attempt to fix the high CPU usage problem.
Maybe your issue is also related to new Nvidia drivers.
PD: The only thing envycontrol touches on hybrid mode is enabling modeset and NVreg_PreserveVideoMemoryAllocations (required for Wayland under Gnome).

Straight not giving video output

Did you enable the RTD3 option?

I tried with that option enabled and disabled. Getting the same result in both scenarios

Try downgrading your Nvidia drivers, on my setup I'm experiencing black screens and freezes since 525.78 on hybrid mode after their failed attempt to fix the high CPU usage problem.
Maybe your issue is also related to new Nvidia drivers.
PD: The only thing envycontrol touches on hybrid mode is enabling modeset and NVreg_PreserveVideoMemoryAllocations (required for Wayland under Gnome).

I have installed the version 525.60.11 which isn't the newest.

@Carlos-SE are you still experiencing this problem?

Yes. Just upgraded envycontrol and still getting the same problem

Yes. Just upgraded envycontrol and still getting the same problem

Please attach the lspci output

Please attach the lspci output

00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620]
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0b)
00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30)
00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30)
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)
00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 30)
00:19.0 Serial bus controller: Intel Corporation Cannon Point-LP Serial IO I2C Host Controller (rev 30)
00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0)
00:1d.1 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #10 (rev f0)
00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller: Intel Corporation Cannon Point-LP SPI Controller (rev 30)
02:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)
02:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
05:00.0 Non-Volatile memory controller: Toshiba Corporation BG3 NVMe SSD Controller (rev 01)

@Carlos-SE when the black screen problem happens can you access a TTY?
If so please check the output of sudo dmesg | grep nvidia, looks like a driver related problem to me

Here it is:
[    5.330073] nvidia: module license 'NVIDIA' taints kernel.
[    5.358197] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[    5.359293] nvidia 0000:02:00.0: enabling device (0106 -> 0107)
[    5.359461] nvidia 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
[    5.870608] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  525.89.02  Wed Feb  1 23:09:40 UTC 2023
[    6.101842] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver
[    6.965839] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:02:00.0 on minor 1
[    7.539941] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
[    7.553030] nvidia-uvm: Loaded the UVM driver, major device number 507.

@Carlos-SE also journalctl -u gdm.service -b

@Carlos-SE also journalctl -u gdm.service -b
While blackscreen?

@Carlos-SE also journalctl -u gdm.service -b

While blackscreen?

Yes, also the X.org logs from /var/log/Xorg.0.log

journalctl -u gdm.service -b  output:
Mar 14 19:11:51 manjaro systemd[1]: Starting GNOME Display Manager...
Mar 14 19:11:51 manjaro systemd[1]: Started GNOME Display Manager.
Mar 14 19:11:53 manjaro gdm[654]: Gdm: GdmDisplay: Session never registered, failing
Mar 14 19:11:53 manjaro gdm[654]: Gdm: Child process -689 was already dead.

/var/log/Xorg.0.log:
[     7.499] (--) Log file renamed from "/var/log/Xorg.pid-733.log" to "/var/log/Xorg.0.log"
[     7.502]
X.Org X Server <IP_ADDRESS>
X Protocol Version 11, Revision 0
[     7.502] Current Operating System: Linux manjaro 5.15.94-1-MANJARO #1 SMP PREEMPT Tue Feb 14 19:45:58 UTC 2023 x86_64
[     7.502] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64 root=UUID=24b118f2-d157-44f3-b63b-65fbfd7a4494 rw quiet udev.log_priority=3
[     7.502]
[     7.502] Current version of pixman: 0.42.2
[     7.502] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     7.502] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     7.502] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 14 18:51:08 2023
[     7.504] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     7.506] (==) ServerLayout "layout"
[     7.506] (==) No screen section available. Using defaults.
[     7.506] (**) |-->Screen "Default Screen Section" (0)
[     7.506] (**) |   |-->Monitor "<default monitor>"
[     7.506] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     7.506] (==) Automatically adding devices
[     7.506] (==) Automatically enabling devices
[     7.506] (==) Automatically adding GPU devices
[     7.506] (==) Automatically binding GPU devices
[     7.506] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     7.506] (WW) The directory "/usr/share/fonts/misc" does not exist.
[     7.506] 	Entry deleted from font path.
[     7.507] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[     7.507] 	Entry deleted from font path.
[     7.507] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[     7.507] 	Entry deleted from font path.
[     7.507] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[     7.507] 	Entry deleted from font path.
[     7.507] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[     7.507] 	Entry deleted from font path.
[     7.507] (==) FontPath set to:
	/usr/share/fonts/TTF
[     7.507] (==) ModulePath set to "/usr/lib/xorg/modules"
[     7.507] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     7.507] (II) Module ABI versions:
[     7.507] 	X.Org ANSI C Emulation: 0.4
[     7.507] 	X.Org Video Driver: 25.2
[     7.507] 	X.Org XInput driver : 24.4
[     7.507] 	X.Org Server Extension : 10.0
[     7.508] (++) using VT number 1

[     7.511] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[     7.513] (II) xfree86: Adding drm device (/dev/dri/card0)
[     7.513] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[     7.514] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0
[     7.514] (II) xfree86: Adding drm device (/dev/dri/card1)
[     7.514] (II) Platform probe for /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/drm/card1
[     7.515] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 15 paused 0
[     7.518] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[     7.518] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[     7.878] (--) PCI:*(0@0:2:0) 8086:3ea0:103c:856a rev 0, Mem @ 0xa2000000/16777216, 0xb0000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[     7.878] (--) PCI: (2@0:0:0) 10de:1c8d:103c:856a rev 161, Mem @ 0xa3000000/16777216, 0x90000000/268435456, 0xa0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[     7.879] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     7.879] (II) LoadModule: "glx"
[     7.884] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     7.906] (II) Module glx: vendor="X.Org Foundation"
[     7.906] 	compiled for <IP_ADDRESS>, module version = 1.0.0
[     7.906] 	ABI class: X.Org Server Extension, version 10.0
[     7.906] (II) Applying OutputClass "intel" to /dev/dri/card0
[     7.906] 	loading driver: modesetting
[     7.906] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[     7.906] 	loading driver: nvidia
[     7.906] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[     7.906] 	loading driver: nvidia
[     7.909] (==) Matched modesetting as autoconfigured driver 0
[     7.909] (==) Matched nvidia as autoconfigured driver 1
[     7.909] (==) Matched nouveau as autoconfigured driver 2
[     7.909] (==) Matched nv as autoconfigured driver 3
[     7.909] (==) Matched fbdev as autoconfigured driver 4
[     7.909] (==) Matched vesa as autoconfigured driver 5
[     7.909] (==) Assigned the driver to the xf86ConfigLayout
[     7.909] (II) LoadModule: "modesetting"
[     7.911] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     7.916] (II) Module modesetting: vendor="X.Org Foundation"
[     7.916] 	compiled for <IP_ADDRESS>, module version = 1.21.1
[     7.916] 	Module class: X.Org Video Driver
[     7.916] 	ABI class: X.Org Video Driver, version 25.2
[     7.916] (II) LoadModule: "nvidia"
[     7.917] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     7.947] (II) Module nvidia: vendor="NVIDIA Corporation"
[     7.947] 	compiled for <IP_ADDRESS>1, module version = 1.0.0
[     7.947] 	Module class: X.Org Video Driver
[     7.947] (II) LoadModule: "nouveau"
[     7.948] (WW) Warning, couldn't open module nouveau
[     7.948] (EE) Failed to load module "nouveau" (module does not exist, 0)
[     7.948] (II) LoadModule: "nv"
[     7.949] (WW) Warning, couldn't open module nv
[     7.949] (EE) Failed to load module "nv" (module does not exist, 0)
[     7.949] (II) LoadModule: "fbdev"
[     7.950] (WW) Warning, couldn't open module fbdev
[     7.950] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     7.950] (II) LoadModule: "vesa"
[     7.952] (WW) Warning, couldn't open module vesa
[     7.952] (EE) Failed to load module "vesa" (module does not exist, 0)
[     7.952] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     7.952] (II) NVIDIA dlloader X Driver  525.89.02  Wed Feb  1 23:14:37 UTC 2023
[     7.952] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     7.952] (II) modeset(0): using drv /dev/dri/card0
[     7.952] (II) systemd-logind: releasing fd for 226:1
[     7.954] (II) Loading sub module "fb"
[     7.954] (II) LoadModule: "fb"
[     7.954] (II) Module "fb" already built-in
[     7.954] (II) Loading sub module "wfb"
[     7.954] (II) LoadModule: "wfb"
[     7.954] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     7.957] (II) Module wfb: vendor="X.Org Foundation"
[     7.957] 	compiled for <IP_ADDRESS>, module version = 1.0.0
[     7.957] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     7.957] (II) Loading sub module "ramdac"
[     7.957] (II) LoadModule: "ramdac"
[     7.957] (II) Module "ramdac" already built-in
[     7.958] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     7.958] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[     7.958] (==) modeset(0): RGB weight 888
[     7.958] (==) modeset(0): Default visual is TrueColor
[     7.958] (II) Loading sub module "glamoregl"
[     7.958] (II) LoadModule: "glamoregl"
[     7.958] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[     7.977] (II) Module glamoregl: vendor="X.Org Foundation"
[     7.977] 	compiled for <IP_ADDRESS>, module version = 1.0.1
[     7.977] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    10.081] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics 620 (WHL GT2)
[    10.081] (II) modeset(0): glamor initialized
[    10.081] (==) modeset(0): VariableRefresh: disabled
[    10.081] (==) modeset(0): AsyncFlipSecondaries: disabled
[    10.083] (II) modeset(0): Output eDP-1 has no monitor section
[    10.107] (II) modeset(0): Output HDMI-1 has no monitor section
[    10.109] (II) modeset(0): EDID for output eDP-1
[    10.109] (II) modeset(0): Manufacturer: AUO  Model: 23ed  Serial#: 0
[    10.109] (II) modeset(0): Year: 2016  Week: 0
[    10.109] (II) modeset(0): EDID Version: 1.4
[    10.109] (II) modeset(0): Digital Display Input
[    10.109] (II) modeset(0): 6 bits per channel
[    10.109] (II) modeset(0): Digital interface is DisplayPort
[    10.109] (II) modeset(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[    10.109] (II) modeset(0): Gamma: 2.20
[    10.109] (II) modeset(0): No DPMS capabilities specified
[    10.109] (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:2:2
[    10.109] (II) modeset(0): First detailed timing is preferred mode
[    10.109] (II) modeset(0): Preferred mode is native pixel format and refresh rate
[    10.109] (II) modeset(0): Display is continuous-frequency
[    10.109] (II) modeset(0): redX: 0.575 redY: 0.346   greenX: 0.347 greenY: 0.572
[    10.109] (II) modeset(0): blueX: 0.158 blueY: 0.117   whiteX: 0.313 whiteY: 0.329
[    10.109] (II) modeset(0): Manufacturer's mask: 0
[    10.109] (II) modeset(0): Supported detailed timing:
[    10.109] (II) modeset(0): clock: 141.0 MHz   Image Size:  344 x 193 mm
[    10.109] (II) modeset(0): h_active: 1920  h_sync: 2028  h_sync_end 2076 h_blank_end 2086 h_border: 0
[    10.109] (II) modeset(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1126 v_border: 0
[    10.109] (II) modeset(0): Supported detailed timing:
[    10.109] (II) modeset(0): clock: 94.0 MHz   Image Size:  344 x 193 mm
[    10.109] (II) modeset(0): h_active: 1920  h_sync: 2028  h_sync_end 2076 h_blank_end 2086 h_border: 0
[    10.109] (II) modeset(0): v_active: 1080  v_sync: 1090  v_sync_end 1100 v_blanking: 1126 v_border: 0
[    10.109] (II) modeset(0): Unknown vendor-specific block 2
[    10.109] (II) modeset(0): EDID (in hex):
[    10.109] (II) modeset(0): 	00ffffffffffff0006afed2300000000
[    10.109] (II) modeset(0): 	001a010495221378116e859358589228
[    10.109] (II) modeset(0): 	1e505400000001010101010101010101
[    10.109] (II) modeset(0):<PHONE_NUMBER>01143780a670382e406c30
[    10.109] (II) modeset(0): 	aa0058c110000018b82480a670382e40
[    10.109] (II) modeset(0): 	6c30aa0058c110000018000000000000
[    10.109] (II) modeset(0):<PHONE_NUMBER>0000000000000000000002
[    10.109] (II) modeset(0): 	001048ff0f3c6e0f16286e2020200033
[    10.109] (II) modeset(0): Printing probed modes for output eDP-1
[    10.109] (II) modeset(0): Modeline "1920x1080"x60.0  141.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[    10.109] (II) modeset(0): Modeline "1920x1080"x120.0  356.38  1920 2080 2288 2656  1080 1081 1084 1118 doublescan -hsync +vsync (134.2 kHz d)
[    10.109] (II) modeset(0): Modeline "1920x1080"x119.9  266.50  1920 1944 1960 2000  1080 1081 1084 1111 doublescan +hsync -vsync (133.2 kHz d)
[    10.109] (II) modeset(0): Modeline "1920x1080"x60.0  173.00  1920 2048 2248 2576  1080 1083 1088 1120 -hsync +vsync (67.2 kHz d)
[    10.109] (II) modeset(0): Modeline "1920x1080"x59.9  138.50  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.6 kHz d)
[    10.109] (II) modeset(0): Modeline "1920x1080"x40.0   94.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (45.1 kHz e)
[    10.109] (II) modeset(0): Modeline "1680x1050"x60.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 -hsync +vsync (65.3 kHz d)
[    10.109] (II) modeset(0): Modeline "1680x1050"x59.9  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz d)
[    10.109] (II) modeset(0): Modeline "1400x1050"x60.0  122.00  1400 1488 1640 1880  1050 1052 1064 1082 +hsync +vsync (64.9 kHz d)
[    10.109] (II) modeset(0): Modeline "1600x900"x120.0  246.00  1600 1728 1900 2200  900 901 904 932 doublescan -hsync +vsync (111.8 kHz d)
[    10.109] (II) modeset(0): Modeline "1600x900"x119.9  186.50  1600 1624 1640 1680  900 901 904 926 doublescan +hsync -vsync (111.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1600x900"x59.9  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync (56.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1600x900"x59.8   97.50  1600 1648 1680 1760  900 903 908 926 +hsync -vsync (55.4 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x1024"x60.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1400x900"x60.0  103.50  1400 1480 1624 1848  900 903 913 934 -hsync +vsync (56.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1400x900"x59.9   86.50  1400 1448 1480 1560  900 903 913 926 +hsync -vsync (55.4 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x960"x60.0  108.00  1280 1376 1488 1800  960<PHONE_NUMBER> +hsync +vsync (60.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1440x810"x120.0  198.12  1440 1548 1704 1968  810 811 814 839 doublescan -hsync +vsync (100.7 kHz d)
[    10.109] (II) modeset(0): Modeline "1440x810"x119.9  151.88  1440 1464 1480 1520  810 811 814 833 doublescan +hsync -vsync (99.9 kHz d)
[    10.109] (II) modeset(0): Modeline "1368x768"x59.9   85.25  1368 1440 1576 1784  768 771 781 798 -hsync +vsync (47.8 kHz d)
[    10.109] (II) modeset(0): Modeline "1368x768"x59.9   72.25  1368 1416 1448 1528  768 771 781 790 +hsync -vsync (47.3 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x800"x120.0  174.25  1280 1380 1516 1752  800 801 804 829 doublescan -hsync +vsync (99.5 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x800"x119.9  134.25  1280 1304 1320 1360  800 801 804 823 doublescan +hsync -vsync (98.7 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x800"x59.8   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x800"x59.9   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x720"x120.0  156.12  1280 1376 1512 1744  720 721 724 746 doublescan -hsync +vsync (89.5 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x720"x120.0  120.75  1280 1304 1320 1360  720 721 724 740 doublescan +hsync -vsync (88.8 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x720"x59.9   74.50  1280 1344 1472 1664  720 723 728 748 -hsync +vsync (44.8 kHz d)
[    10.109] (II) modeset(0): Modeline "1280x720"x59.7   63.75  1280 1328 1360 1440  720 723 728 741 +hsync -vsync (44.3 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x768"x120.1  133.47  1024 1100 1212 1400  768 768 770 794 doublescan -hsync +vsync (95.3 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz d)
[    10.109] (II) modeset(0): Modeline "960x720"x120.0  117.00  960 1024 1128 1300  720 720 722 750 doublescan -hsync +vsync (90.0 kHz d)
[    10.109] (II) modeset(0): Modeline "928x696"x120.1  109.15<PHONE_NUMBER> 1264  696 696 698 719 doublescan -hsync +vsync (86.4 kHz d)
[    10.109] (II) modeset(0): Modeline "896x672"x120.0  102.40<PHONE_NUMBER> 1224  672 672 674 697 doublescan -hsync +vsync (83.7 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x576"x119.9   98.50  1024 1092 1200 1376  576 577 580 597 doublescan -hsync +vsync (71.6 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x576"x119.9   78.38  1024 1048 1064 1104  576 577 580 592 doublescan +hsync -vsync (71.0 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x576"x59.9   46.50  1024 1064 1160 1296  576 579 584 599 -hsync +vsync (35.9 kHz d)
[    10.109] (II) modeset(0): Modeline "1024x576"x59.8   42.00  1024 1072 1104 1184  576 579 584 593 +hsync -vsync (35.5 kHz d)
[    10.109] (II) modeset(0): Modeline "960x600"x119.9   96.62  960 1028 1128 1296  600 601 604 622 doublescan -hsync +vsync (74.6 kHz d)
[    10.110] (II) modeset(0): Modeline "960x600"x120.0   77.00<PHONE_NUMBER> 1040  600 601 604 617 doublescan +hsync -vsync (74.0 kHz d)
[    10.110] (II) modeset(0): Modeline "960x540"x119.9   86.50  960 1024 1124 1288  540 541 544 560 doublescan -hsync +vsync (67.2 kHz d)
[    10.110] (II) modeset(0): Modeline "960x540"x120.0   69.25<PHONE_NUMBER> 1040  540 541 544 555 doublescan +hsync -vsync (66.6 kHz d)
[    10.110] (II) modeset(0): Modeline "960x540"x59.6   40.75<PHONE_NUMBER> 1216  540 543 548 562 -hsync +vsync (33.5 kHz d)
[    10.110] (II) modeset(0): Modeline "960x540"x59.8   37.25  960 1008 1040 1120  540 543 548 556 +hsync -vsync (33.3 kHz d)
[    10.110] (II) modeset(0): Modeline "800x600"x120.0   81.00  800<PHONE_NUMBER>  600 600 602 625 doublescan +hsync +vsync (75.0 kHz d)
[    10.110] (II) modeset(0): Modeline "800x600"x60.3   40.00  800<PHONE_NUMBER>  600 601 605 628 +hsync +vsync (37.9 kHz d)
[    10.110] (II) modeset(0): Modeline "800x600"x56.2   36.00  800<PHONE_NUMBER>  600 601 603 625 +hsync +vsync (35.2 kHz d)
[    10.110] (II) modeset(0): Modeline "840x525"x120.0   73.12  840<PHONE_NUMBER>  525 526 529 544 doublescan -hsync +vsync (65.3 kHz d)
[    10.110] (II) modeset(0): Modeline "840x525"x119.8   59.50  840 864 880 920  525 526 529 540 doublescan +hsync -vsync (64.7 kHz d)
[    10.110] (II) modeset(0): Modeline "864x486"x59.9   32.50  864<PHONE_NUMBER>  486 489 494 506 -hsync +vsync (30.3 kHz d)
[    10.110] (II) modeset(0): Modeline "864x486"x59.6   30.50  864<PHONE_NUMBER>  486 489 494 500 +hsync -vsync (29.8 kHz d)
[    10.110] (II) modeset(0): Modeline "700x525"x120.0   61.00  700 744 820 940  525 526 532 541 doublescan +hsync +vsync (64.9 kHz d)
[    10.110] (II) modeset(0): Modeline "800x450"x119.9   59.12  800<PHONE_NUMBER>  450 451 454 467 doublescan -hsync +vsync (56.0 kHz d)
[    10.110] (II) modeset(0): Modeline "800x450"x119.6   48.75  800 824 840 880  450 451 454 463 doublescan +hsync -vsync (55.4 kHz d)
[    10.110] (II) modeset(0): Modeline "640x512"x120.0   54.00  640 664 720 844  512 512 514 533 doublescan +hsync +vsync (64.0 kHz d)
[    10.110] (II) modeset(0): Modeline "700x450"x119.9   51.75  700 740 812 924  450 451 456 467 doublescan -hsync +vsync (56.0 kHz d)
[    10.110] (II) modeset(0): Modeline "700x450"x119.8   43.25  700 724 740 780  450 451 456 463 doublescan +hsync -vsync (55.4 kHz d)
[    10.110] (II) modeset(0): Modeline "640x480"x120.0   54.00  640 688 744 900  480 480 482 500 doublescan +hsync +vsync (60.0 kHz d)
[    10.110] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz d)
[    10.110] (II) modeset(0): Modeline "720x405"x59.5   22.50  720 744 808 896  405 408 413 422 -hsync +vsync (25.1 kHz d)
[    10.110] (II) modeset(0): Modeline "720x405"x59.0   21.75  720 768 800 880  405 408 413 419 +hsync -vsync (24.7 kHz d)
[    10.110] (II) modeset(0): Modeline "684x384"x119.8   42.62  684 720 788 892  384 385 390 399 doublescan -hsync +vsync (47.8 kHz d)
[    10.110] (II) modeset(0): Modeline "684x384"x119.7   36.12  684 708 724 764  384 385 390 395 doublescan +hsync -vsync (47.3 kHz d)
[    10.110] (II) modeset(0): Modeline "640x400"x119.8   41.75  640 676 740 840  400 401 404 415 doublescan -hsync +vsync (49.7 kHz d)
[    10.110] (II) modeset(0): Modeline "640x400"x120.0   35.50  640 664 680 720  400 401 404 411 doublescan +hsync -vsync (49.3 kHz d)
[    10.110] (II) modeset(0): Modeline "640x360"x119.7   37.25  640 672 736 832  360 361 364 374 doublescan -hsync +vsync (44.8 kHz d)
[    10.110] (II) modeset(0): Modeline "640x360"x119.7   31.88  640 664 680 720  360 361 364 370 doublescan +hsync -vsync (44.3 kHz d)
[    10.110] (II) modeset(0): Modeline "640x360"x59.8   18.00  640 664 720 800  360 363 368 376 -hsync +vsync (22.5 kHz d)
[    10.110] (II) modeset(0): Modeline "640x360"x59.3   17.75  640 688 720 800  360 363 368 374 +hsync -vsync (22.2 kHz d)
[    10.110] (II) modeset(0): Modeline "512x384"x120.0   32.50  512 524 592 672  384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[    10.110] (II) modeset(0): Modeline "512x288"x120.0   23.25  512 532 580 648  288 289 292 299 doublescan -hsync +vsync (35.9 kHz d)
[    10.110] (II) modeset(0): Modeline "512x288"x119.8   21.00  512 536 552 592  288 289 292 296 doublescan +hsync -vsync (35.5 kHz d)
[    10.110] (II) modeset(0): Modeline "480x270"x119.3   20.38  480 496 544 608  270 271 274 281 doublescan -hsync +vsync (33.5 kHz d)
[    10.110] (II) modeset(0): Modeline "480x270"x119.6   18.62  480 504 520 560  270 271 274 278 doublescan +hsync -vsync (33.3 kHz d)
[    10.110] (II) modeset(0): Modeline "400x300"x120.6   20.00  400 420 484 528  300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[    10.110] (II) modeset(0): Modeline "400x300"x112.7   18.00  400 412 448 512  300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[    10.110] (II) modeset(0): Modeline "432x243"x119.8   16.25  432 444 484 536  243 244 247 253 doublescan -hsync +vsync (30.3 kHz d)
[    10.110] (II) modeset(0): Modeline "432x243"x119.1   15.25  432 456 472 512  243 244 247 250 doublescan +hsync -vsync (29.8 kHz d)
[    10.110] (II) modeset(0): Modeline "320x240"x120.1   12.59  320 328 376 400  240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[    10.110] (II) modeset(0): Modeline "360x202"x119.0   11.25  360 372 404 448  202 204 206 211 doublescan -hsync +vsync (25.1 kHz d)
[    10.110] (II) modeset(0): Modeline "360x202"x118.3   10.88  360 384 400 440  202 204 206 209 doublescan +hsync -vsync (24.7 kHz d)
[    10.110] (II) modeset(0): Modeline "320x180"x119.7    9.00  320 332 360 400  180 181 184 188 doublescan -hsync +vsync (22.5 kHz d)
[    10.110] (II) modeset(0): Modeline "320x180"x118.6    8.88  320 344 360 400  180 181 184 187 doublescan +hsync -vsync (22.2 kHz d)
[    10.135] (II) modeset(0): EDID for output HDMI-1
[    10.135] (II) modeset(0): Output eDP-1 connected
[    10.135] (II) modeset(0): Output HDMI-1 disconnected
[    10.135] (II) modeset(0): Using exact sizes for initial modes
[    10.135] (II) modeset(0): Output eDP-1 using initial mode 1920x1080 +0+0
[    10.135] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    10.135] (==) modeset(0): DPI set to (96, 96)
[    10.135] (II) Loading sub module "fb"
[    10.135] (II) LoadModule: "fb"
[    10.135] (II) Module "fb" already built-in
[    10.135] (==) NVIDIA(G0): Depth 24, (==) framebuffer bpp 32
[    10.135] (==) NVIDIA(G0): RGB weight 888
[    10.135] (==) NVIDIA(G0): Default visual is TrueColor
[    10.135] (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0)
[    10.135] (**) Option "AllowNVIDIAGpuScreens"
[    10.135] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[    10.135] (II) Applying OutputClass "nvidia" options to /dev/dri/card1
[    10.135] (**) NVIDIA(G0): Option "AllowEmptyInitialConfiguration"
[    10.135] (**) NVIDIA(G0): Enabling 2D acceleration
[    10.135] (II) Loading sub module "glxserver_nvidia"
[    10.135] (II) LoadModule: "glxserver_nvidia"
[    10.135] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    10.374] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    10.374] 	compiled for <IP_ADDRESS>1, module version = 1.0.0
[    10.375] 	Module class: X.Org Server Extension
[    10.375] (II) NVIDIA GLX Module  525.89.02  Wed Feb  1 23:13:01 UTC 2023
[    10.375] (II) NVIDIA: The X server supports PRIME Render Offload.
[    10.384] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:2:0:0
[    10.384] (--) NVIDIA(0):     DFP-0 (boot)
[    10.386] (II) NVIDIA(G0): NVIDIA GPU NVIDIA GeForce GTX 1050 with Max-Q Design (GP107-A)
[    10.386] (II) NVIDIA(G0):     at PCI:2:0:0 (GPU-0)
[    10.386] (--) NVIDIA(G0): Memory: 4194304 kBytes
[    10.386] (--) NVIDIA(G0): VideoBIOS: 86.07.5f.00.2c
[    10.386] (II) NVIDIA(G0): Detected PCI Express Link width: 16X
[    10.430] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    10.430] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    10.430] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    10.430] (--) NVIDIA(GPU-0):
[    10.434] (II) NVIDIA(G0): Validated MetaModes:
[    10.434] (II) NVIDIA(G0):     "NULL"
[    10.434] (II) NVIDIA(G0): Virtual screen size determined to be 640 x 480
[    10.439] (WW) NVIDIA(G0): Cannot find size of first mode for Acer K242HQL (DFP-0);
[    10.439] (WW) NVIDIA(G0):     cannot compute DPI from Acer K242HQL (DFP-0)'s EDID.
[    10.439] (==) NVIDIA(G0): DPI set to (75, 75); computed from built-in default
[    10.490] (==) modeset(0): Backing store enabled
[    10.490] (==) modeset(0): Silken mouse enabled
[    10.568] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    10.568] (==) modeset(0): DPMS enabled
[    10.569] (II) modeset(0): [DRI2] Setup complete
[    10.569] (II) modeset(0): [DRI2]   DRI driver: iris
[    10.569] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[    10.569] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    10.569] (II) NVIDIA:     access.
[    10.573] (II) NVIDIA(G0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    10.573] (II) NVIDIA(G0):     may not be running or the "AcpidSocketPath" X
[    10.573] (II) NVIDIA(G0):     configuration option may not be set correctly.  When the
[    10.573] (II) NVIDIA(G0):     ACPI event daemon is available, the NVIDIA X driver will
[    10.573] (II) NVIDIA(G0):     try to use it to receive ACPI event notifications.  For
[    10.573] (II) NVIDIA(G0):     details, please see the "ConnectToAcpid" and
[    10.573] (II) NVIDIA(G0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    10.573] (II) NVIDIA(G0):     Config Options in the README.
[    10.597] (II) NVIDIA(G0): Setting mode "NULL"
[    10.602] (==) NVIDIA(G0): Disabling shared memory pixmaps
[    10.603] (==) NVIDIA(G0): Backing store enabled
[    10.603] (==) NVIDIA(G0): Silken mouse enabled
[    10.603] (==) NVIDIA(G0): DPMS enabled
[    10.603] (II) Loading sub module "dri2"
[    10.603] (II) LoadModule: "dri2"
[    10.603] (II) Module "dri2" already built-in
[    10.603] (II) NVIDIA(G0): [DRI2] Setup complete
[    10.603] (II) NVIDIA(G0): [DRI2]   VDPAU driver: nvidia
[    10.603] (II) Initializing extension Generic Event Extension
[    10.603] (II) Initializing extension SHAPE
[    10.603] (II) Initializing extension MIT-SHM
[    10.603] (II) Initializing extension XInputExtension
[    10.603] (II) Initializing extension XTEST
[    10.603] (II) Initializing extension BIG-REQUESTS
[    10.603] (II) Initializing extension SYNC
[    10.604] (II) Initializing extension XKEYBOARD
[    10.604] (II) Initializing extension XC-MISC
[    10.604] (II) Initializing extension SECURITY
[    10.604] (II) Initializing extension XFIXES
[    10.604] (II) Initializing extension RENDER
[    10.604] (II) Initializing extension RANDR
[    10.604] (II) Initializing extension COMPOSITE
[    10.604] (II) Initializing extension DAMAGE
[    10.604] (II) Initializing extension MIT-SCREEN-SAVER
[    10.605] (II) Initializing extension DOUBLE-BUFFER
[    10.605] (II) Initializing extension RECORD
[    10.605] (II) Initializing extension DPMS
[    10.605] (II) Initializing extension Present
[    10.605] (II) Initializing extension DRI3
[    10.605] (II) Initializing extension X-Resource
[    10.605] (II) Initializing extension XVideo
[    10.605] (II) Initializing extension XVideo-MotionCompensation
[    10.605] (II) Initializing extension GLX
[    10.605] (II) Initializing extension GLX
[    10.605] (II) Indirect GLX disabled.
[    10.610] (II) AIGLX: Loaded and initialized iris
[    10.610] (II) GLX: Initialized DRI2 GL provider for screen 0
[    10.610] (II) Initializing extension XFree86-VidModeExtension
[    10.610] (II) Initializing extension XFree86-DGA
[    10.610] (II) Initializing extension XFree86-DRI
[    10.610] (II) Initializing extension DRI2
[    10.611] (II) Initializing extension NV-GLX
[    10.611] (II) Initializing extension NV-CONTROL
[    10.611] (II) modeset(0): Damage tracking initialized
[    10.611] (II) modeset(0): Setting screen physical size to 508 x 285
[    10.665] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    10.665] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    10.665] (II) LoadModule: "libinput"
[    10.665] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    10.671] (II) Module libinput: vendor="X.Org Foundation"
[    10.671] 	compiled for <IP_ADDRESS>, module version = 1.2.1
[    10.671] 	Module class: X.Org XInput Driver
[    10.671] 	ABI class: X.Org XInput driver, version 24.4
[    10.671] (II) Using input driver 'libinput' for 'Power Button'
[    10.671] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 48 paused 0
[    10.671] (**) Power Button: always reports core events
[    10.671] (**) Option "Device" "/dev/input/event2"
[    10.687] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    10.688] (II) event2  - Power Button: device is a keyboard
[    10.688] (II) event2  - Power Button: device removed
[    10.688] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[    10.688] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    10.688] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    10.688] (II) event2  - Power Button: device is a keyboard
[    10.689] (II) config/udev: Adding input device Video Bus (/dev/input/event11)
[    10.689] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[    10.689] (II) Using input driver 'libinput' for 'Video Bus'
[    10.689] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 51 paused 0
[    10.689] (**) Video Bus: always reports core events
[    10.689] (**) Option "Device" "/dev/input/event11"
[    10.690] (II) event11 - Video Bus: is tagged by udev as: Keyboard
[    10.690] (II) event11 - Video Bus: device is a keyboard
[    10.690] (II) event11 - Video Bus: device removed
[    10.690] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input14/event11"
[    10.690] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[    10.691] (II) event11 - Video Bus: is tagged by udev as: Keyboard
[    10.691] (II) event11 - Video Bus: device is a keyboard
[    10.691] (II) config/udev: Adding input device Video Bus (/dev/input/event12)
[    10.691] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[    10.691] (II) Using input driver 'libinput' for 'Video Bus'
[    10.692] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 52 paused 0
[    10.692] (**) Video Bus: always reports core events
[    10.692] (**) Option "Device" "/dev/input/event12"
[    10.693] (II) event12 - Video Bus: is tagged by udev as: Keyboard
[    10.693] (II) event12 - Video Bus: device is a keyboard
[    10.693] (II) event12 - Video Bus: device removed
[    10.693] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:49/LNXVIDEO:01/input/input15/event12"
[    10.693] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
[    10.693] (II) event12 - Video Bus: is tagged by udev as: Keyboard
[    10.694] (II) event12 - Video Bus: device is a keyboard
[    10.694] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    10.694] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    10.694] (II) Using input driver 'libinput' for 'Power Button'
[    10.694] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 53 paused 0
[    10.695] (**) Power Button: always reports core events
[    10.695] (**) Option "Device" "/dev/input/event1"
[    10.695] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    10.695] (II) event1  - Power Button: device is a keyboard
[    10.695] (II) event1  - Power Button: device removed
[    10.695] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[    10.695] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 9)
[    10.696] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    10.696] (II) event1  - Power Button: device is a keyboard
[    10.696] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[    10.696] (II) No input driver specified, ignoring this device.
[    10.696] (II) This device may have been added with another device file.
[    10.697] (II) config/udev: Adding input device Compx 2.4G Receiver (/dev/input/event4)
[    10.697] (**) Compx 2.4G Receiver: Applying InputClass "libinput keyboard catchall"
[    10.697] (II) Using input driver 'libinput' for 'Compx 2.4G Receiver'
[    10.697] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 54 paused 0
[    10.697] (**) Compx 2.4G Receiver: always reports core events
[    10.698] (**) Option "Device" "/dev/input/event4"
[    10.698] (II) event4  - Compx 2.4G Receiver: is tagged by udev as: Keyboard
[    10.698] (II) event4  - Compx 2.4G Receiver: device is a keyboard
[    10.699] (II) event4  - Compx 2.4G Receiver: device removed
[    10.699] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:25A7:FA23.0001/input/input5/event4"
[    10.699] (II) XINPUT: Adding extended input device "Compx 2.4G Receiver" (type: KEYBOARD, id 10)
[    10.700] (II) event4  - Compx 2.4G Receiver: is tagged by udev as: Keyboard
[    10.700] (II) event4  - Compx 2.4G Receiver: device is a keyboard
[    10.700] (II) config/udev: Adding input device Compx 2.4G Receiver Mouse (/dev/input/event5)
[    10.700] (**) Compx 2.4G Receiver Mouse: Applying InputClass "libinput pointer catchall"
[    10.700] (II) Using input driver 'libinput' for 'Compx 2.4G Receiver Mouse'
[    10.701] (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 55 paused 0
[    10.701] (**) Compx 2.4G Receiver Mouse: always reports core events
[    10.701] (**) Option "Device" "/dev/input/event5"
[    10.702] (II) event5  - Compx 2.4G Receiver Mouse: is tagged by udev as: Mouse
[    10.702] (II) event5  - Compx 2.4G Receiver Mouse: device is a pointer
[    10.702] (II) event5  - Compx 2.4G Receiver Mouse: device removed
[    10.702] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0002/input/input6/event5"
[    10.702] (II) XINPUT: Adding extended input device "Compx 2.4G Receiver Mouse" (type: MOUSE, id 11)
[    10.702] (**) Option "AccelerationScheme" "none"
[    10.702] (**) Compx 2.4G Receiver Mouse: (accel) selected scheme none/0
[    10.702] (**) Compx 2.4G Receiver Mouse: (accel) acceleration factor: 2.000
[    10.702] (**) Compx 2.4G Receiver Mouse: (accel) acceleration threshold: 4
[    10.703] (II) event5  - Compx 2.4G Receiver Mouse: is tagged by udev as: Mouse
[    10.703] (II) event5  - Compx 2.4G Receiver Mouse: device is a pointer
[    10.704] (II) config/udev: Adding input device Compx 2.4G Receiver Mouse (/dev/input/mouse0)
[    10.704] (II) No input driver specified, ignoring this device.
[    10.704] (II) This device may have been added with another device file.
[    10.704] (II) config/udev: Adding input device Compx 2.4G Receiver (/dev/input/event6)
[    10.704] (II) No input driver specified, ignoring this device.
[    10.704] (II) This device may have been added with another device file.
[    10.705] (II) config/udev: Adding input device Compx 2.4G Receiver Consumer Control (/dev/input/event7)
[    10.705] (**) Compx 2.4G Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[    10.705] (II) Using input driver 'libinput' for 'Compx 2.4G Receiver Consumer Control'
[    10.705] (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 56 paused 0
[    10.705] (**) Compx 2.4G Receiver Consumer Control: always reports core events
[    10.705] (**) Option "Device" "/dev/input/event7"
[    10.706] (II) event7  - Compx 2.4G Receiver Consumer Control: is tagged by udev as: Keyboard
[    10.706] (II) event7  - Compx 2.4G Receiver Consumer Control: device is a keyboard
[    10.706] (II) event7  - Compx 2.4G Receiver Consumer Control: device removed
[    10.706] (II) libinput: Compx 2.4G Receiver Consumer Control: needs a virtual subdevice
[    10.706] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0002/input/input8/event7"
[    10.706] (II) XINPUT: Adding extended input device "Compx 2.4G Receiver Consumer Control" (type: MOUSE, id 12)
[    10.706] (**) Option "AccelerationScheme" "none"
[    10.706] (**) Compx 2.4G Receiver Consumer Control: (accel) selected scheme none/0
[    10.706] (**) Compx 2.4G Receiver Consumer Control: (accel) acceleration factor: 2.000
[    10.706] (**) Compx 2.4G Receiver Consumer Control: (accel) acceleration threshold: 4
[    10.707] (II) event7  - Compx 2.4G Receiver Consumer Control: is tagged by udev as: Keyboard
[    10.707] (II) event7  - Compx 2.4G Receiver Consumer Control: device is a keyboard
[    10.708] (II) config/udev: Adding input device Compx 2.4G Receiver System Control (/dev/input/event8)
[    10.708] (**) Compx 2.4G Receiver System Control: Applying InputClass "libinput keyboard catchall"
[    10.708] (II) Using input driver 'libinput' for 'Compx 2.4G Receiver System Control'
[    10.708] (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 57 paused 0
[    10.708] (**) Compx 2.4G Receiver System Control: always reports core events
[    10.708] (**) Option "Device" "/dev/input/event8"
[    10.709] (II) event8  - Compx 2.4G Receiver System Control: is tagged by udev as: Keyboard
[    10.709] (II) event8  - Compx 2.4G Receiver System Control: device is a keyboard
[    10.710] (II) event8  - Compx 2.4G Receiver System Control: device removed
[    10.710] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0002/input/input9/event8"
[    10.710] (II) XINPUT: Adding extended input device "Compx 2.4G Receiver System Control" (type: KEYBOARD, id 13)
[    10.710] (II) event8  - Compx 2.4G Receiver System Control: is tagged by udev as: Keyboard
[    10.711] (II) event8  - Compx 2.4G Receiver System Control: device is a keyboard
[    10.711] (II) config/udev: Adding input device HP Wide Vision HD Camera: HP Wi (/dev/input/event13)
[    10.711] (**) HP Wide Vision HD Camera: HP Wi: Applying InputClass "libinput keyboard catchall"
[    10.711] (II) Using input driver 'libinput' for 'HP Wide Vision HD Camera: HP Wi'
[    10.712] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 58 paused 0
[    10.712] (**) HP Wide Vision HD Camera: HP Wi: always reports core events
[    10.712] (**) Option "Device" "/dev/input/event13"
[    10.713] (II) event13 - HP Wide Vision HD Camera: HP Wi: is tagged by udev as: Keyboard
[    10.713] (II) event13 - HP Wide Vision HD Camera: HP Wi: device is a keyboard
[    10.713] (II) event13 - HP Wide Vision HD Camera: HP Wi: device removed
[    10.713] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/input/input16/event13"
[    10.713] (II) XINPUT: Adding extended input device "HP Wide Vision HD Camera: HP Wi" (type: KEYBOARD, id 14)
[    10.714] (II) event13 - HP Wide Vision HD Camera: HP Wi: is tagged by udev as: Keyboard
[    10.714] (II) event13 - HP Wide Vision HD Camera: HP Wi: device is a keyboard
[    10.714] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event15)
[    10.714] (II) No input driver specified, ignoring this device.
[    10.714] (II) This device may have been added with another device file.
[    10.714] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
[    10.714] (II) No input driver specified, ignoring this device.
[    10.714] (II) This device may have been added with another device file.
[    10.715] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event17)
[    10.715] (II) No input driver specified, ignoring this device.
[    10.715] (II) This device may have been added with another device file.
[    10.715] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event18)
[    10.715] (II) No input driver specified, ignoring this device.
[    10.715] (II) This device may have been added with another device file.
[    10.715] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event20)
[    10.715] (II) No input driver specified, ignoring this device.
[    10.715] (II) This device may have been added with another device file.
[    10.715] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event21)
[    10.715] (II) No input driver specified, ignoring this device.
[    10.715] (II) This device may have been added with another device file.
[    10.716] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event22)
[    10.716] (II) No input driver specified, ignoring this device.
[    10.716] (II) This device may have been added with another device file.
[    10.716] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event23)
[    10.716] (II) No input driver specified, ignoring this device.
[    10.716] (II) This device may have been added with another device file.
[    10.716] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event24)
[    10.716] (II) No input driver specified, ignoring this device.
[    10.716] (II) This device may have been added with another device file.
[    10.716] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event25)
[    10.716] (II) No input driver specified, ignoring this device.
[    10.716] (II) This device may have been added with another device file.
[    10.717] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event26)
[    10.717] (II) No input driver specified, ignoring this device.
[    10.717] (II) This device may have been added with another device file.
[    10.717] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event3)
[    10.717] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[    10.717] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    10.718] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 59 paused 0
[    10.718] (**) AT Translated Set 2 keyboard: always reports core events
[    10.718] (**) Option "Device" "/dev/input/event3"
[    10.718] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    10.718] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[    10.719] (II) event3  - AT Translated Set 2 keyboard: device removed
[    10.719] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input3/event3"
[    10.719] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 15)
[    10.720] (II) event3  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[    10.720] (II) event3  - AT Translated Set 2 keyboard: device is a keyboard
[    10.721] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event14)
[    10.721] (**) ETPS/2 Elantech Touchpad: Applying InputClass "libinput touchpad catchall"
[    10.721] (II) Using input driver 'libinput' for 'ETPS/2 Elantech Touchpad'
[    10.721] (II) systemd-logind: got fd for /dev/input/event14 13:78 fd 60 paused 0
[    10.721] (**) ETPS/2 Elantech Touchpad: always reports core events
[    10.721] (**) Option "Device" "/dev/input/event14"
[    10.722] (II) event14 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad
[    10.723] (II) event14 - ETPS/2 Elantech Touchpad: device is a touchpad
[    10.723] (II) event14 - ETPS/2 Elantech Touchpad: device removed
[    10.723] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input13/event14"
[    10.723] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 16)
[    10.724] (**) Option "AccelerationScheme" "none"
[    10.724] (**) ETPS/2 Elantech Touchpad: (accel) selected scheme none/0
[    10.724] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[    10.724] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[    10.724] (II) event14 - ETPS/2 Elantech Touchpad: is tagged by udev as: Touchpad
[    10.725] (II) event14 - ETPS/2 Elantech Touchpad: device is a touchpad
[    10.726] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1)
[    10.726] (II) No input driver specified, ignoring this device.
[    10.726] (II) This device may have been added with another device file.
[    10.726] (II) config/udev: Adding input device PC Speaker (/dev/input/event10)
[    10.726] (II) No input driver specified, ignoring this device.
[    10.726] (II) This device may have been added with another device file.
[    10.728] (II) config/udev: Adding input device Wireless hotkeys (/dev/input/event9)
[    10.728] (**) Wireless hotkeys: Applying InputClass "libinput keyboard catchall"
[    10.728] (II) Using input driver 'libinput' for 'Wireless hotkeys'
[    10.728] (II) systemd-logind: got fd for /dev/input/event9 13:73 fd 61 paused 0
[    10.728] (**) Wireless hotkeys: always reports core events
[    10.728] (**) Option "Device" "/dev/input/event9"
[    10.729] (II) event9  - Wireless hotkeys: is tagged by udev as: Keyboard
[    10.729] (II) event9  - Wireless hotkeys: device is a keyboard
[    10.729] (II) event9  - Wireless hotkeys: device removed
[    10.729] (**) Option "config_info" "udev:/sys/devices/virtual/input/input11/event9"
[    10.729] (II) XINPUT: Adding extended input device "Wireless hotkeys" (type: KEYBOARD, id 17)
[    10.729] (II) event9  - Wireless hotkeys: is tagged by udev as: Keyboard
[    10.729] (II) event9  - Wireless hotkeys: device is a keyboard
[    10.730] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event19)
[    10.730] (**) HP WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    10.730] (II) Using input driver 'libinput' for 'HP WMI hotkeys'
[    10.730] (II) systemd-logind: got fd for /dev/input/event19 13:83 fd 62 paused 0
[    10.730] (**) HP WMI hotkeys: always reports core events
[    10.730] (**) Option "Device" "/dev/input/event19"
[    10.731] (II) event19 - HP WMI hotkeys: is tagged by udev as: Keyboard Switch
[    10.731] (II) event19 - HP WMI hotkeys: device is a keyboard
[    10.731] (II) event19 - HP WMI hotkeys: device removed
[    10.731] (**) Option "config_info" "udev:/sys/devices/virtual/input/input21/event19"
[    10.731] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 18)
[    10.731] (II) event19 - HP WMI hotkeys: is tagged by udev as: Keyboard Switch
[    10.731] (II) event19 - HP WMI hotkeys: device is a keyboard
[    10.742] (**) Compx 2.4G Receiver Consumer Control: Applying InputClass "libinput keyboard catchall"
[    10.742] (II) Using input driver 'libinput' for 'Compx 2.4G Receiver Consumer Control'
[    10.742] (II) systemd-logind: returning pre-existing fd for /dev/input/event7 13:71
[    10.742] (**) Compx 2.4G Receiver Consumer Control: always reports core events
[    10.742] (**) Option "Device" "/dev/input/event7"
[    10.742] (II) libinput: Compx 2.4G Receiver Consumer Control: is a virtual subdevice
[    10.742] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:25A7:FA23.0002/input/input8/event7"
[    10.742] (II) XINPUT: Adding extended input device "Compx 2.4G Receiver Consumer Control" (type: KEYBOARD, id 19)
[    11.568] (II) modeset(0): EDID vendor "AUO", prod id 9197
[    11.568] (II) modeset(0): Printing DDC gathered Modelines:
[    11.568] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[    11.568] (II) modeset(0): Modeline "1920x1080"x0.0   94.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (45.1 kHz e)
[    11.601] (II) modeset(0): EDID vendor "AUO", prod id 9197
[    11.601] (II) modeset(0): Printing DDC gathered Modelines:
[    11.601] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[    11.601] (II) modeset(0): Modeline "1920x1080"x0.0   94.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (45.1 kHz e)
[    11.670] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    11.670] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    11.670] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    11.670] (--) NVIDIA(GPU-0):
[    11.869] (II) modeset(0): Allocate new frame buffer 3840x1080 stride
[    11.980] (II) NVIDIA(G0): Setting mode "HDMI-1-0: nvidia-auto-select @1920x1080 +1920+0 {AllowGSYNC=Off, ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    12.896] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    12.896] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    12.896] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    12.896] (--) NVIDIA(GPU-0):
[    12.985] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    12.985] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    12.985] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    12.985] (--) NVIDIA(GPU-0):
[    13.000] (II) modeset(0): EDID vendor "AUO", prod id 9197
[    13.000] (II) modeset(0): Printing DDC gathered Modelines:
[    13.000] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[    13.000] (II) modeset(0): Modeline "1920x1080"x0.0   94.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (45.1 kHz e)
[    13.033] (II) modeset(0): EDID vendor "AUO", prod id 9197
[    13.034] (II) modeset(0): Printing DDC gathered Modelines:
[    13.034] (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (67.6 kHz eP)
[    13.034] (II) modeset(0): Modeline "1920x1080"x0.0   94.00  1920 2028 2076 2086  1080 1090 1100 1126 -hsync -vsync (45.1 kHz e)
[    13.099] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    13.099] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    13.099] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    13.099] (--) NVIDIA(GPU-0):
[    13.398] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    13.398] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    13.398] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    13.398] (--) NVIDIA(GPU-0):
[    13.443] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): connected
[    13.443] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): Internal TMDS
[    13.443] (--) NVIDIA(GPU-0): Acer K242HQL (DFP-0): 600.0 MHz maximum pixel clock
[    13.443] (--) NVIDIA(GPU-0):
[    19.312] (II) config/udev: Adding input device Keychron K8 (/dev/input/event27)
[    19.312] (**) Keychron K8: Applying InputClass "libinput keyboard catchall"
[    19.312] (II) Using input driver 'libinput' for 'Keychron K8'
[    19.315] (II) systemd-logind: got fd for /dev/input/event27 13:91 fd 80 paused 0
[    19.315] (**) Keychron K8: always reports core events
[    19.315] (**) Option "Device" "/dev/input/event27"
[    19.321] (II) event27 - Keychron K8: is tagged by udev as: Keyboard
[    19.322] (II) event27 - Keychron K8: device is a keyboard
[    19.323] (II) event27 - Keychron K8: device removed
[    19.323] (II) libinput: Keychron K8: needs a virtual subdevice
[    19.323] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:05AC:024F.0003/input/input31/event27"
[    19.323] (II) XINPUT: Adding extended input device "Keychron K8" (type: MOUSE, id 20)
[    19.324] (**) Option "AccelerationScheme" "none"
[    19.325] (**) Keychron K8: (accel) selected scheme none/0
[    19.325] (**) Keychron K8: (accel) acceleration factor: 2.000
[    19.326] (**) Keychron K8: (accel) acceleration threshold: 4
[    19.331] (II) event27 - Keychron K8: is tagged by udev as: Keyboard
[    19.332] (II) event27 - Keychron K8: device is a keyboard
[    19.334] (**) Keychron K8: Applying InputClass "libinput keyboard catchall"
[    19.334] (II) Using input driver 'libinput' for 'Keychron K8'
[    19.334] (II) systemd-logind: returning pre-existing fd for /dev/input/event27 13:91
[    19.334] (**) Keychron K8: always reports core events
[    19.334] (**) Option "Device" "/dev/input/event27"
[    19.334] (II) libinput: Keychron K8: is a virtual subdevice
[    19.334] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/bluetooth/hci0/hci0:256/0005:05AC:024F.0003/input/input31/event27"
[    19.334] (II) XINPUT: Adding extended input device "Keychron K8" (type: KEYBOARD, id 21)
[    22.646] (**) Option "fd" "48"
[    22.646] (II) event2  - Power Button: device removed
[    22.647] (**) Option "fd" "51"
[    22.647] (II) event11 - Video Bus: device removed
[    22.647] (**) Option "fd" "52"
[    22.647] (II) event12 - Video Bus: device removed
[    22.648] (**) Option "fd" "53"
[    22.648] (II) event1  - Power Button: device removed
[    22.648] (**) Option "fd" "54"
[    22.648] (II) event4  - Compx 2.4G Receiver: device removed
[    22.649] (**) Option "fd" "55"
[    22.649] (II) event5  - Compx 2.4G Receiver Mouse: device removed
[    22.649] (**) Option "fd" "56"
[    22.650] (**) Option "fd" "57"
[    22.650] (II) event8  - Compx 2.4G Receiver System Control: device removed
[    22.650] (**) Option "fd" "58"
[    22.650] (II) event13 - HP Wide Vision HD Camera: HP Wi: device removed
[    22.651] (**) Option "fd" "59"
[    22.651] (II) event3  - AT Translated Set 2 keyboard: device removed
[    22.651] (**) Option "fd" "60"
[    22.651] (II) event14 - ETPS/2 Elantech Touchpad: device removed
[    22.652] (**) Option "fd" "61"
[    22.652] (II) event9  - Wireless hotkeys: device removed
[    22.652] (**) Option "fd" "62"
[    22.652] (II) event19 - HP WMI hotkeys: device removed
[    22.653] (**) Option "fd" "56"
[    22.653] (II) event7  - Compx 2.4G Receiver Consumer Control: device removed
[    22.653] (**) Option "fd" "80"
[    22.653] (**) Option "fd" "80"
[    22.654] (II) event27 - Keychron K8: device removed
[    22.654] (II) AIGLX: Suspending AIGLX clients for VT switch
[    24.761] (EE) modeset(0): Failed to set CTM property: -13
[    24.761] (EE) modeset(0): failed to set mode: No such file or directory
[    24.761] (II) systemd-logind: got pause for 13:69
[    24.761] (II) systemd-logind: got pause for 13:83
[    24.761] (II) systemd-logind: got pause for 13:72
[    24.761] (II) systemd-logind: got pause for 13:65
[    24.761] (II) systemd-logind: got pause for 13:91
[    24.761] (II) systemd-logind: got pause for 13:68
[    24.761] (II) systemd-logind: got pause for 13:78
[    24.761] (II) systemd-logind: got pause for 13:67
[    24.761] (II) systemd-logind: got pause for 13:77
[    24.761] (II) systemd-logind: got pause for 13:73
[    24.761] (II) systemd-logind: got pause for 13:76
[    24.761] (II) systemd-logind: got pause for 13:75
[    24.761] (II) systemd-logind: got pause for 13:71
[    24.761] (II) systemd-logind: got pause for 13:66
[    30.722] (II) UnloadModule: "libinput"
[    30.723] (II) systemd-logind: not releasing fd for 13:91, still in use
[    30.723] (II) UnloadModule: "libinput"
[    30.723] (II) systemd-logind: releasing fd for 13:91
[    30.748] (II) UnloadModule: "libinput"
[    30.748] (II) systemd-logind: not releasing fd for 13:71, still in use
[    30.748] (II) UnloadModule: "libinput"
[    30.748] (II) systemd-logind: releasing fd for 13:83
[    30.771] (II) UnloadModule: "libinput"
[    30.771] (II) systemd-logind: releasing fd for 13:73
[    30.807] (II) UnloadModule: "libinput"
[    30.807] (II) systemd-logind: releasing fd for 13:78
[    30.868] (II) UnloadModule: "libinput"
[    30.868] (II) systemd-logind: releasing fd for 13:67
[    30.908] (II) UnloadModule: "libinput"
[    30.908] (II) systemd-logind: releasing fd for 13:77
[    30.936] (II) UnloadModule: "libinput"
[    30.936] (II) systemd-logind: releasing fd for 13:72
[    30.969] (II) UnloadModule: "libinput"
[    30.969] (II) systemd-logind: releasing fd for 13:71
[    30.980] (II) UnloadModule: "libinput"
[    30.980] (II) systemd-logind: releasing fd for 13:69
[    31.001] (II) UnloadModule: "libinput"
[    31.001] (II) systemd-logind: releasing fd for 13:68
[    31.034] (II) UnloadModule: "libinput"
[    31.034] (II) systemd-logind: releasing fd for 13:65
[    31.060] (II) UnloadModule: "libinput"
[    31.060] (II) systemd-logind: releasing fd for 13:76
[    31.080] (II) UnloadModule: "libinput"
[    31.080] (II) systemd-logind: releasing fd for 13:75
[    31.098] (II) UnloadModule: "libinput"
[    31.098] (II) systemd-logind: releasing fd for 13:66
[    31.128] (WW) NVIDIA(G0): Failed to set the display configuration
[    31.128] (WW) NVIDIA(G0):  - Setting a mode on head 0 failed: Insufficient permissions
[    31.128] (WW) NVIDIA(G0):  - Setting a mode on head 1 failed: Insufficient permissions
[    31.128] (WW) NVIDIA(G0):  - Setting a mode on head 2 failed: Insufficient permissions
[    31.128] (WW) NVIDIA(G0):  - Setting a mode on head 3 failed: Insufficient permissions
[    31.147] (II) NVIDIA(GPU-0): Deleting GPU-0
[    31.150] (II) Server terminated successfully (0). Closing log file.

@Carlos-SE do you have an external screen connected?
Also try reinstalling Nvidia drivers and upgrading to a newer kernel

@Carlos-SE do you have an external screen connected?
Also try reinstalling Nvidia drivers and upgrading to a newer kernel

Yes I do have an external screen

@Carlos-SE do you have an external screen connected?
Also try reinstalling Nvidia drivers and upgrading to a newer kernel

Yes I do have an external screen

If you disconnect the external screen does HDMI start?

It doesn't

It doesn't

Upgrade your kernel and reinstall the Nvidia drivers

I have GTX 1060 and disabled wayland in gdm config.
here is what I get in Xorg logs:
[    22.051] (II) Initializing extension DRI2
[    22.052] (EE) modeset(G0): Failed to create pixmap
[    22.052] (EE)
Fatal server error:
[    22.052] (EE) failed to create screen resources(EE)
[    22.052] (EE)
Please consult the The X.Org Foundation support
	 at http://wiki.x.org
 for help.
[    22.052] (EE) Please also check the log file at "/var/lib/gdm/.local/share/xorg/Xorg.0.log" for additional information.
[    22.052] (EE)
[    22.052] (II) AIGLX: Suspending AIGLX clients for VT switch
[    22.085] (EE) Server terminated with error (1). Closing log file.

That's for wayland isn't it?


--clean removes input file

Hi, decompile.sh help states that
--cleanup    Removes temporary files created during the decompilation.

I use it with --mode raw,  --select-ranges  however it also removes input file which is a bit annoying if I want to select different range I need to copy the input file again. Solution is not to use --clean option but it is nice to remove the temporary files automatically.

Hi. Thank you for the report! You are totally right. Steps to reproduce with the current master:
$ wget https://github.com/avast-tl/retdec-regression-tests/raw/master/features/raw/binaries/raw.raw
$ retdec-decompiler.sh --mode raw --arch arm --endian big --raw-entry-point 0x0 --raw-section-vma 0 --cleanup raw.raw
$ ls raw*
raw.raw.c  raw.raw.c.frontend.dsm

cool, thx ! BTW. when you're at it you could remove *.frontend.dsm since it's created during the decompilation and not removed.

In #309, I have proposed a fix (commit b94efd20374ce2b4873ba49bae72a89bc8ca8b27). After my colleague reviews the changes and accepts them, they will be merged and this issue will be fixed.


Add "Running" conversions category

Problem Statement
Distance running is a constant interplay between space, time, and pain. Eavesdrop into any discussion between runners, and you’ll be constantly hearing about paces, race times, interval splits, and hitting the wall. Athletes and coaches need to convert between different speed, pace, and race time measures when they are planning their training or races. These conversions are mentally difficult to perform, and even to think of an algorithm for, if the runner is not mathematically inclined.
Evidence or User Insights
A web search can get us a lot of charts and online calculators that try to address this problem, but they usually provide conversions for a small set of data points, and only for a few measurements (usually between minutes per mile and minutes per kilometer paces).
Yet, distance running is an extremely popular sport, and very available to everyone. In 2018, more than 18 million people registered for road races just in the USA (reference). Helping this broad user base around the world easily solve their conversion problems would bring them one step closer to achieving their goals.
Proposal
We propose to introduce a new conversion mode into Windows Calculator that would make these conversions easy for everyone interested in or practicing running.
A typical list of measures would include:

Speed: Miles per hour
Speed: Kilometers per hour
Pace: Minutes per mile
Pace: Minutes per kilometer
Race time: 5K
Race time: 10K
Race time: Half marathon
Race time: Marathon
Intervals: 200m time
Intervals: 400m time
Intervals: 600m time
Intervals: 800m time

Goals
With this mode, a user would be able to solve real world problems such as:

What pace do I need to run to achieve my goal 42:00 time in a 10K race?
My training plan shows paces in minutes per kilometer, but I am using minutes per mile, how can I change them using Windows Calculator?
What speed do I set the treadmill to for my interval workout? The plan specifies paces.
What’s the target pace for 1’15” 400m intervals?
If I could run as fast as Eliud Kipchoge when he achieved his latest Marathon world record, what would my 5K time be? (The right answer is “you probably can’t” but the calculator would show 14:24. Wow. I can't think that fast, let alone run.)

Non-Goals
Calculating race times and paces for non-standard race distances, including ultras.
Low-Fidelity Concept

That would be super cool. Running community will highly appreciate this!!!

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Thanks for the feature suggestion! This is really well thought-out, and we really appreciate it. Let's keep this idea open for discussion so the community has the chance to provide feedback. Check out our New Feedback Process for more info on the user-centered process we follow for new feature development.

This is a nice idea! It will require to modify how UnitConverter works and manage units with sub-units. Take a look at this proposal, it covers these 2 prerequisites:
https://github.com/Microsoft/calculator/issues/379

We reviewed the pitch and would love to move forward with it! I think this pitch is a great start, but there are still some open questions. Moving this into pre-production to iron out some of the details.
A particularly noteworthy question that was raised was whether this can be made even more generic to encompass all “pace” conversions (i.e., not just running, but other activities as well, like hiking, biking, etc.), but as @rudyhuyn points out, this does behave a bit different from existing converters, so that is something to think through as well.
I created calculator-specs/runningConversions to track progress. For more information on next steps, check out our spec workflow.

@grochocki can you make suggestions on user research? I was considering enlisting like-minded colleagues from my org to review the specs before a PR, but if there is a better option please share.

Hello ima new bee to OS


EGM pose controller

I was wondering if there was any example available for a EGM pose controller?
I have been able to follow example 2 and use the joint_group_velocity_controller and joint_group_position_controller. However I called the /egm/controller_manager/list_controller_types service and these does not seem to be a pose controller in the list.

If by "pose controller" you mean a Cartesian controller, then you are right, there is no example for those.
But that's more because there is no standard/default Cartesian controller in ros_controllers than anything else.
Controllers which require special "Cartesian resources" will not be supported out-of-the-box, but you could perhaps see whether fzi-forschungszentrum-informatik/cartesian_ros_control covers your use-case.
Finally, just to clarify: abb_robot_driver is a ros_control based ROS driver for ABB robots. It's not an EGM application or library, nor necessarily an EGM-only ROS component.

However I called the /egm/controller_manager/list_controller_types service and these does not seem to be a pose controller in the list.

The output of that service is the list of controllers configured in the ros_control configuration loaded by the respective .launch files in the bringup package. It does not list whatever control interfaces EGM supports.

If by "pose controller" you mean a Cartesian controller, then you are right, there is no example for those.
But that's more because there is no standard/default Cartesian controller in ros_controllers than anything else.
Controllers which require special "Cartesian resources" will not be supported out-of-the-box, but you could perhaps see whether fzi-forschungszentrum-informatik/cartesian_ros_control covers your use-case.
Finally, just to clarify: abb_robot_driver is a ros_control based ROS driver for ABB robots. It's not an EGM application or library, nor necessarily an EGM-only ROS component.

However I called the /egm/controller_manager/list_controller_types service and these does not seem to be a pose controller in the list.

The output of that service is the list of controllers configured in the ros_control configuration loaded by the respective .launch files in the bringup package. It does not list whatever control interfaces EGM supports.

@gavanderhoorn - Thanks for the clarification on the ros_controllers.
It seems the best approach for my application is to use abb_libegm directly.

@gavanderhoorn - Thanks for the clarification on the ros_controllers.
It seems the best approach for my application is to use abb_libegm directly.

Adding a Cartesian resource and then using a forwarding Twist controller on-top of that for instance should really not be that much work.
Probably less work than using EGM directly.

Adding a Cartesian resource and then using a forwarding Twist controller on-top of that for instance should really not be that much work.
Probably less work than using EGM directly.

And I forgot to mention fzi-forschungszentrum-informatik/cartesian_controllers.
Those should work with the joint space interfaces already supported by abb_robot_driver.

And I forgot to mention fzi-forschungszentrum-informatik/cartesian_controllers.
Those should work with the joint space interfaces already supported by abb_robot_driver.

I already had a working code based on abb_libegm before starting using abb_robot_driver so in my case it was easy but I will definitely consider your recommendation as an improvement.

I already had a working code based on abb_libegm before starting using abb_robot_driver so in my case it was easy but I will definitely consider your recommendation as an improvement.

If you do, we'd be interested in potentially integrating something like that here.
Adding Cartesian support is on the TODO list, so you'd help a lot of other users.

If you do, we'd be interested in potentially integrating something like that here.
Adding Cartesian support is on the TODO list, so you'd help a lot of other users.

Of course! I will share if I come up with anything useful.

Of course! I will share if I come up with anything useful.

As it seems we've answered the initial question, I'm going to close the issue.
Feel free to keep commenting on it of course.

As it seems we've answered the initial question, I'm going to close the issue.
Feel free to keep commenting on it of course.

Hi, from what I understood here, if I have a cartesian pose that I want my robot end-effector to move to, I cannot send this pose via the abb_robot_driver to RobotStudio? I would have to use another package with the abb_robot_driver to get this to work?

If you're not interested in getting to that pose while actively trying to avoid collisions -- so just use pure Cartesian interpolation from start to end -- then, yes, you'll have to configure your driver to load a Cartesian controller.
abb_robot_driver currently does not support Cartesian resources, as until very recently, there was no support for that in ros_control.

If you're not interested in getting to that pose while actively trying to avoid collisions
Did you mean "If I AM interested" ?

What exactly does the service /rws/sm_addin/start_egm_pose do ? And how can I use it?
If I wanted to let RobotStudio handle the Inverse Kinematics and somehow send it a pose, how can I achieve this using this package? Would the service /rws/sm_addin/start_egm_pose help?

If you're not interested in getting to that pose while actively trying to avoid collisions

Did you mean "If I AM interested" ?

No, I meant to ask what I wrote.
The IRC5 will use straightforward linear interpolation between poses. There is no collision detection nor avoidance, except for the robot with itself and -- depending on whether you have that option -- what SafeMove can do for you.
So using EGM in pose mode will also just linearly interpolate between poses.
This in contrast to something like MoveIt, which will try to plan a collision free path for you between your starting and destination pose. MoveIt can directly use the driver as-is, as it uses JointTrajectory goals, which are fully supported.

What exactly does the service /rws/sm_addin/start_egm_pose do ?

It starts an EGM motion which accepts Cartesian poses as targets.

And how can I use it?

By sending Cartesian poses to the controller.
But not with abb_robot_driver, because, as I wrote before:

abb_robot_driver currently does not support Cartesian resources, as until very recently, there was no support for that in ros_control.

that comment probably also answers your next question:

If I wanted to let RobotStudio handle the Inverse Kinematics and somehow send it a pose, how can I achieve this using this package? Would the service /rws/sm_addin/start_egm_pose help?

As some general advice: if you aren't already, it would be good to familiarise yourself with the basic workings of EGM.
EGM is not something we invented here, or for this driver, but a regular software option developed and supported by ABB Robotics. We merely use it to "talk" to the IRC5.
Most of the functionality offered by the driver is a thin wrapper around EGM and RWS. If you don't have any experience with either of these two technologies, nor with ABB robots in general, making sense of the services, topics and terminology is going to be difficult.
<my_personal_opinion>

This driver (ie: abb_robot_driver) should not be your first experience with ABB robots. Industrial robots can be dangerous and their correct functioning depends on how you use them. Additionally, there are many aspects in the configuration which will influence the way they behave, which, when adding ROS to the mix, can make things quite complex.
If you have the option, I would recommend to first get your bearings with plain RobotStudio and the operation of ABB robots, before adding ROS and this driver. Most likely you'll find many things much clearer and easier to use.

</my_personal_opinion>

Thanks for the detailed response.
I need some advice as to how I can proceed: As it turns out, I need straightforward linear interpolation between poses without collision detection and other planning (the most rudimentary form of cartesian control). What is the best way to accomplish this using ROS and RobotStudio (without using rapid)?
So far I've understood from what you've said that this is not possible using the abb_robot_driver?
But this would be simpler if I were to use abb_libegm ?

Didn't you already find fzi-forschungszentrum-informatik/cartesian_controllers?
That's a collection of ros_control controllers which accept Cartesian inputs.

So far I've understood from what you've said that this is not possible using the abb_robot_driver?

ros_control doesn't / didn't support Cartesian interfaces, so abb_robot_driver doesn't either.
fzi-forschungszentrum-informatik/cartesian_ros_control adds Cartesian support to ros_control, but that would need to be added to abb_robot_driver to support it.

But this would be simpler if I were to use abb_libegm ?

Well, that would no longer be "using ROS". abb_libegm is a stand-alone library for interfacing with EGM capable ABB robot controllers. Nothing more.

If you have any further questions about this, please open a new issue. We should try to avoid commenting on an already closed issue.


Add the implementation of exposing promethues metrics via HTTP

the rust client library doesn't provide the implementation of exposing promethues metrics.

Maybe the intent is to use separate http framework to serve metrics data? There is an example using tide(https://github.com/search?q=tide&ref=opensearch) at the examples directory(https://github.com/prometheus/client_rust/blob/master/examples/tide.rs).

There is not one canonical way to do http in Rust. Thus, I would rather showcase many different use-cases in /examples rather than offering a single within the library.


Use Crate ordered_float instead of naive float types

https://github.com/Rust-Data-Science/ulist/issues/134


Feature: show releases

In a similar app (OctoDroid) you can see releases and downloads. This would be useful in ForkHub.

:+1:

I agree.
I am not asking for an ETA, however is this still on the priority list?

@moriel5 it is, and I hope to have basic support in the next release.

Thanks, I had just been wondering since this issue was opened over a year ago.


[CPPAPI] Provide access to TSRemapRequestInfo in RemapPlugins.

While plugins can modify a remap behavior by overloading the doRemap method, they cannot modify the origin URL directly, they have to change the client URL using transaction.getClientRequest().getUrl(), which is not very intuitive.
This change adds a new public method to the CPP API that gives plugins access to the original TSRemapRequestInfo structure. This new method doesn't change any current behavior, and all existent plugins work as expected. If you look at the diff, you can see that I only moved 4 lines of private code to this new virtual method.
I sent a message to the dev mailing list to discuss this change, but I didn't get any response. I'm guessing not many people use these APIs, which is understandable if you have more experience with the low level API.
Signed-off-by: David Calavera<EMAIL_ADDRESS>

[approve ci]

The current CPPAPI seems to be targeted at applications where optimizing performance is not a big issue.  There seem to be many cases where it makes it hard to use capabilities of the C plugin API.  I wrote this PR as a first step to an alternative approach.  Minimizing additional overhead, and easy mixing with direct C API cals.
https://github.com/apache/trafficserver/pull/5812

I read your PR some time ago @ywkaras and I think there is a lot of value there.
I'd like to make sure that people understand that that change is orthogonal to what I'm proposing here because the impact is much different.
I think there is a lot of value for the project to invest time in the CPP API. The way I see it is that the C API and the CPP API are two different layers, much like Git has the concepts of plumbing and porcelain. The C API is the core, it gives you a lot of power, but you also need a much higher level of understanding to work with it. The CPP API encapsulates the C API in a much more familiar interface, specially for people that don't have a background in C and CPP. Seeing concepts like Request, Response, Headers and Transaction makes it much more easy to work for newcomers to the project and the language than concepts like TSMLoc, TSMBuffer and others. People with more experience in the project will be ok using the C API, but people less experienced with it will have a better experience by starting to use the CPP API and reaching the C API when is necessary.
My change here gives you a glimpse of that. Working with the current virtual doRemap method is very easy, but it has some limitations. This change removes some of those limitations without forcing people to go full on to the C API.

Cherry-picked to v9.0.x branch.


Add benchmark for TRSM

Adds a benchmark for the level 3 BLAS function TRSM with a basic csv of square inputs. Also includes a minor change to the benchmark random data generation to use a static random device (in line with recent changes to the generation used in unit tests).

@mehdi-goli For some reason I can't request a review from you through Github so I'll ping you here instead!

@mehdi-goli For some reason I can't request a review from you through Github so I'll ping you here instead!


Structure Issue In Json Object

Can we get some solid structure for parameters in results section?
For example for unit currency type when we give $50 we get currency type divided to amount and currency but when we give 50 it gives only unit currency and its value as 50 and now there is no sections like amount and currency.
Is there a way to get to know if inner parameter is null?
For example when we give 50 then can it give unit currency entity as amount=50 and currency=null?

Hello!
Sorry for long answer. The given issue is reported to server-side team.


我的别一个表可以的。。。

ID column doesn't exist?


merge benchmark results and upload to GitHub Pages

relates to #13
Merge benchmarks, generate graphs and upload to GitHub Pages.
TODO:

Needs to review testconfig for metrics value based on its unit to make graphs relevant
~Move ref_timestamp out of benchmark metrics (this is just used for sorting refs in graphs)~
testutil.MergeBenchmarks should return an object that can be ingested directly by format output of merge command.

See https://moby.github.io/buildkit-bench/

Reverted on master branch and opened https://github.com/moby/buildkit-bench/pull/29


i can't run MHDDoS

Command: python3 start.py udp <IP_ADDRESS>:53 10 10000

This issue appeared after git pull repository.

Solution: https://bit.ly/3hEbSpG

workaround to run old version
git checkout fc9fc0bad7be5daaec7d852b96e1f69016018f73
pip3 install -r requirements.txt
then it works

fixed ❤

can i get older version please


bug in eval-correlation.py

I want to ask if the field indicated in the graph at line 39 of the eval-correlation.py file is written incorrectly. The original text says that there is no such field as factual_consistency when running, and I changed it to the one shown in the next graph to run normally. Does this affect the results of the operation?

sorry for the late response. i guess you are right. i believe the results should still be the same with those changes, but please note that the gpt-4 model, which we used in our experiments, is quite expensive compared to the current sota models like gpt4o or o1. i believe gpt4o-mini might show better results and >100x cheaper than the original gpt4, so you can consider using it instead if you want to apply our method to your application :)

你好，我正忙中，无法亲自回复你的邮件。我将在忙完结束后，尽快给你回复。

理解 😃


Random-image-slider added

Title and Issue number

Close #3357

I have added the project . Can it be merged now?
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

@MohitGupta121 Can it be merged now?


where is the solution

Hi, I just upload our slides and presentation.
We will provide code and well-trained models later.


flat_params hotfix respect to empty models

#177 missed the capability to get the tuple representation from an empty struct property. This PR solves that specific problem by adding a race condition.

Codecov Report

Merging #179 (c97630d) into dev (fc6323b) will increase coverage by 0.05%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##              dev     #179      +/-   ##
==========================================
+ Coverage   89.21%   89.26%   +0.05%
==========================================
  Files           8        8
  Lines         380      382       +2
==========================================
+ Hits          339      341       +2
  Misses         41       41

Files Changed
Coverage Δ

src/parameter_inspection.jl
100.00% <100.00%> (ø)

By discussed with @ablaom, we can simplify the race condition approach by just doing the verification in the trait.


Update templates to Azle 0.18.0

Azle 0.18.0 is a major change in syntax, and we would like to have the templates updated to Azle 0.18.0, as the frontend templates are very valuable.
Would you accept a PR with these changes?

Sure thing, will accept.


CRAYSAT-1399: Scan images using Snyk when building

Add code to release.sh that calls updated release library functions,
and creates separate artifacts for snyk scan archive and excel
spreadsheet.
For convenience, move function that renders templated files into a
separate script.
Modify Jenkinsfile to include SNYK_TOKEN, and to publish snyk
artifacts.

Test Description: I created a temporary branch with updated
hpc-shastarelm-release library code venored in, then built the product
stream.
Summary and Scope
Summarize what has changed. Explain why this PR is necessary. What is impacted? Is this a new feature, critical bug fix, etc?
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix?
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CRAYSAT-1399

Testing
See commit message
Risks and Mitigations
Are there known issues with these changes? Any other special considerations?
Pull Request Checklist

[X] Version number(s) incremented, if applicable
[X] Copyrights updated
[X] License file intact
[X] Target branch correct
[X] CHANGELOG.md updated
[X] Testing is appropriate and complete, if applicable
[X] HPC Product Announcement prepared, if applicable

I see the Jenkins builds are failing, it looks like that is because the vendored hpc-shastarelm-release library needs to be updated for this to work?

I see the Jenkins builds are failing, it looks like that is because the vendored hpc-shastarelm-release library needs to be updated for this to work?

Correct, I'll have to add that when the hpc-shastarelm-release PR is merged.

I rebased this to pull in the license check workflow as well as to squash the current fixup commit. I also updated the vendor library now that the change to hpc-shastarelm-release has been merged. At this point the build should be succeeding.


Backup-restore-operator (Rancher Backups) chart should only be available in local cluster

Rancher Backups (backup-restore-operator) chart for 2.5 should only be available in local cluster. The chart should have catalog.cattle.io/scope: management annotation so UI can show it only in local cluster

The chart now has this annotation

On master-head - commit id: 27000be7e
Rancher-Backup is NOT available in downstream cluster (backup-restore-operator in the snapshot should be removed as its the older chart, have an issue to track it)


feat: add raw response mode to process_query

Add raw_response option to return tuple instead of template
Update extract_content endpoint for plain text output

Example usage:
http://localhost:8000/extract/cyclotruc/gitingest?max_file_size=243&pattern_type=include&pattern=*.py

@cevatkerim Very good!
I tested with localhost:8000/extract/cyclotruc/gitingest and it seemed alright!
In order to reach the MVP state for an API we would probably need:

Read request headers in dynamic.py  to choose which response to send (html or raw)
Remove the /extract/ route
Make it possible to force raw response via url query args, idk if there's a convention but maybe a field like?format=txt ?
Add a few lines in /api docs to explain the usage

I would be very happy to help you work on this branch if you invited me as contributer to your repo
Let me know if you have any ideas to add or if you see anything I'm missing

@cevatkerim Very good! I tested with localhost:8000/extract/cyclotruc/gitingest and it seemed alright!
In order to reach the MVP state for an API we would probably need:

Read request headers in dynamic.py  to choose which response to send (html or raw)
Remove the /extract/ route
Make it possible to force raw response via url query args, idk if there's a convention but maybe a field like?format=txt ?
Add a few lines in /api docs to explain the usage

I would be very happy to help you work on this branch if you invited me as contributer to your repo Let me know if you have any ideas to add or if you see anything I'm missing

Sounds good I already added you as a collaborator. You should have access.


changing permissions issue

Hello. I use windows and smb for synced folders, and I can't change permissions on vagrant machine and it cause errors during work of Drupal 8 . It always throws errors that some operations are not permitted. Just FYI - I have 775 permissions for dir and 664 for files. But I can't change them under vagrant user or even root. Is there a way how to fix it? Thanks.

I am having the same exact issue. When I try to to chown or chmod nothing happens. I don't even get any errors in the terminal.

Have you got a sample of the console output, and have you also tried chgrp to the 'vagrant' group?

@fubarhouse
Here is my console output:

@jesrig Everything should be working, have you got a copy of the error message from the watchdog?
Also, could you check/submit the file system form to make sure everything is as expected?

@fubarhouse The issue I had was this: I loaded my site and found that all styling etc was broken. I looked at the javascript console and found the error 'Drupal is not defined'. I figured this might have to do with file permissions, tried to set them and ran into this issue. The watchdog log is full of file permissions errors:

I tried resubmitting the file system form (admin/config/media/file-system) and still nothing.

I might try to replicate this tonight, are you using a stock standard instance of Drupal VM?

@fubarhouse I did make some changes to the config.yml (which I store in config/config.yml) See attached (changed to txt so I could upload)
Vagrantfile.txt
. The changes made here worked fine with other sites.
config.txt

@jesrig I'll use these files when testing.
You've said this is only a problem on one site, is there anything of note on that site which could help diagnose it?

So I'm having no luck getting this replicated on Windows.
I have seen the problem before, but usually resubmitting the form, clearing caches, rebuilding registry and running a cron are among the tasks which fix it.
I in fact had a situation where I couldn't fix this but my database import script linked to my organisations Acquia account fixed it at the very end before taking me back to the menu.
One of the last commands to run are drush rr.
drush dl registry_rebuild
drush @site rr

Because I can't properly replicate it I can't offer any additional help, but I feel strongly that the above advice should fit it up as I have experienced this before.

Going to close this for now, as much time has passed—one solution could also just be to run drush @site cc all (D7) or drush @site cr to rebuild caches. Sometimes that's all that's needed.
Otherwise, maybe try using a different synced folder type (try '' (empty string), 'smb' (Samba), or 'rsync'), and see if that makes a difference.

@geerlingguy I gave up and did a vagrant destroy, and of course that did work.

@jesrig - Great!

My comment here may also be of help to folks if unsuccessful with the above: https://github.com/drupal-composer/drupal-project/issues/199#issuecomment-423741155


Could not set mesh1d in meshkernel correctly

Describe the bug
When creating 1d2d links, it is required to load 1d and 2d mesh in meshkernel. When using the following line to load mesh1d:
network._mesh1d._set_mesh1d(), mesh1d cannot be set correctly. Calling network.meshkernel.mesh1d_get() returns an Empty Mesh1d object.
However, the mesh1d in the network object is not empty: network._mesh1d.is_empty() returns False.
To Reproduce
Steps to reproduce the behavior:

assign mesh1d to the network, make sure network._mesh1d.is_empty() returns False.
set mesh1d to meshkernel using network._mesh1d._set_mesh1d()
check the mesh1d in meshkernal using network.meshkernel.mesh1d_get()
See the error: an empty Mesh1d object.

Expected behavior
After setting mesh1d using network._mesh1d._set_mesh1d(), network.meshkernel.mesh1d_get() should return the correct Mesh1d object.
Screenshots

Version info (please complete the following information):

OS: [e.g. Windows]
Version [e.g. 0.3.1]

Additional context
Note that it is possible to use network.meshkernel.mesh1d_set(network._mesh1d.meshkernel.mesh1d_get()). After this step, network.meshkernel.mesh1d_get() returns the correct Mesh1d object. See the above screenshot.

Not a bug in hydrolib-core, but a bug in hydrolib/hydromt_delft3dfm.
In the function to set up mesh1d, hydromt-delft3dfm adapted an iterative approach, which initializes a Mesh1d object at every iterative. The bug was that at every iteration, a new Mesh1d object initialized. Instead, the same meshkernal object should be passed so that the _meshkernelid is identical. '''self.dfmmodel.geometry.netfile.network._mesh1d = Mesh1d(meshkernel = self.dfmmodel.geometry.netfile.network.meshkernel)'''


Gems cleanup

This removes a few gems that aren't needed and applies a consistent approach to the Gemfile.
Since all the gems for this repo are at the latest version I thought we could apply an approach of specifying no gem versions which makes this file a lot cleaner. I'm pondering this as a convention that could be applied across GOV.UK where we only specify a pinned version where we've got a reason to do so. It's early days on that idea though.

Nice one - do we even need startup.sh anymore?

I still use it/them, I could live without but they are convenient. Could be a question for the dev tools survey?

@kevindew ah, fair enough. I think it's fine to leave them in - as long as they're adding some kind of value.


add favicons

resolve https://github.com/karmada-io/website/issues/22

https://realfavicongenerator.net/favicon_checker?protocol=https&site=deploy-preview-23--karmada.netlify.app%2F#.YjhIf-rP23A

/assign @RainbowMango

cc @rgrupesh
Can you help to take a look?

LGTM! @RainbowMango
@Arhell One feedback: always make the issue thorough. Add the details in the issue itself. I mean which specific icons are added or to be added and such. The link was helpful though. It would help to review effectively.


Typo: directory-assign-admin-roles.md

@evilensky : Thanks for your contribution! The author, @curtand, has been notified to review your proposed change.

Merging the typo fix.
@evilensky Thanks!


[travis-ci] merge pretty check

This PR merges the pretty checks into one to reduce the jobs and save time.
Besides, as many jobs were added, .travis/before_script.sh becomes very big. This PR removes pretty check and size report's dependency on that script. Since many job now differs much, it will be easier to maintain and use if each job itself manages its own prerequisites.

@bukepo, thanks for this contribution. For everyone's benefit, can you update the commit message with the purpose/benefits of this commit?

@jwhui added description.


Illegal layout on Ubuntu

Ubuntu 14.04.3
Electron 0.35.4

Layout breaks after lost focus on the window.

Chromium on Linux doesn't work well with certain virtual machines, and unfortunately Electron inherited this bug.
I'm closing this as won't fix.


Updated iOS Image Classifier Async Callbacks to Use Delegates

Updated iOS image classifier asynchronous callbacks to use delegates instead of completion blocks.
Added validation of packet type in MPPClassificationResult+Helpers

Raised a PR for changing pattern of iOS image classifier async callbacks. Please see my comment here.


Can't load SD card after CTR Transfer

So I completed part 2 successfully, backed out after the ctrtransfer and hit select to unmount my SD card. Now when I plug it back into my computer it's telling me I need to reformat it, am I missing something?
Edit: I've come to the conclusion that the card is defected and decided to shit out halfway through tyring to do this, in no way shape or form am I able to format the drive at all. So next comes a new question, is there anyway to continue the process with a new SD card? I currently have the 3DS running 2.1.0-4u but now I don't have any of the files on that I was using to do the hack. Do I just format everything and start from scratch? Thanks.

Just recopy all the files to it that you were told to, don't format the device.


Not required for nullable foreign key field

required param was hardcoded for fk fields, however that field may be null

Thanks!