With Intuos4 not working with GNOME 45
I opened a bug on b.o.o (https://bugzilla.opensuse.org/show_bug.cgi? id=1215631) on this, but am struggling to provide more information that would help resolve the issue. I have been using an Intuos4 tablet for years with openSUSE, and the update to GNOME 45 has rendered it mostly inoperable, both with the mouse and the pen. I'm on Tumbleweed. As described in the bug, mouse clicks are occasionally recognized in the UI (enough that I can get a bluetooth mouse working), but in both GNOME and non-GNOME applications, I sometimes can get a mouse click to be recognized by hitting the super key a couple of times (to bring up 'activities' and then close it again). Testing with xev shows the mouse button events are not being received by the X server. This worked just fine in GNOME 44. I'm at a loss as to what to look at to provide information that would be useful for getting this fixed. Anyone have any ideas that I haven't already described in the bug? -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On Fri, Oct 13, 2023 at 1:01 PM Jim Henderson <hendersj@gmail.com> wrote:
I opened a bug on b.o.o (https://bugzilla.opensuse.org/show_bug.cgi? id=1215631) on this, but am struggling to provide more information that would help resolve the issue.
I have been using an Intuos4 tablet for years with openSUSE, and the update to GNOME 45 has rendered it mostly inoperable, both with the mouse and the pen. I'm on Tumbleweed.
As described in the bug, mouse clicks are occasionally recognized in the UI (enough that I can get a bluetooth mouse working), but in both GNOME and non-GNOME applications, I sometimes can get a mouse click to be recognized by hitting the super key a couple of times (to bring up 'activities' and then close it again).
Testing with xev shows the mouse button events are not being received by the X server.
This worked just fine in GNOME 44. I'm at a loss as to what to look at to provide information that would be useful for getting this fixed.
Anyone have any ideas that I haven't already described in the bug?
Since you appear to be using GNOME on Xorg, have you tried to see if it works in GNOME Wayland? -- 真実はいつも一つ！/ Always, there's only one truth!
On Fri, 13 Oct 2023 13:11:57 -0400, Neal Gompa wrote:
Since you appear to be using GNOME on Xorg, have you tried to see if it works in GNOME Wayland?
I have not - I attempted to try this earlier today, and discovered that because I use the nvidia proprietary drivers, the option is disabled in gdm as wayland + nvidia proprietary = unstable (apparently). -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On Fri, Oct 13, 2023 at 3:45 PM Jim Henderson <hendersj@gmail.com> wrote:
On Fri, 13 Oct 2023 13:11:57 -0400, Neal Gompa wrote:
Since you appear to be using GNOME on Xorg, have you tried to see if it works in GNOME Wayland?
I have not - I attempted to try this earlier today, and discovered that because I use the nvidia proprietary drivers, the option is disabled in gdm as wayland + nvidia proprietary = unstable (apparently).
That's very odd. I'm pretty sure upstream GNOME changed that with NVIDIA driver >= 510? Is your driver older than that? -- 真実はいつも一つ！/ Always, there's only one truth!
On Fri, 13 Oct 2023 17:54:55 -0400, Neal Gompa wrote:
On Fri, Oct 13, 2023 at 3:45 PM Jim Henderson <hendersj@gmail.com> wrote:
On Fri, 13 Oct 2023 13:11:57 -0400, Neal Gompa wrote:
Since you appear to be using GNOME on Xorg, have you tried to see if it works in GNOME Wayland?
I have not - I attempted to try this earlier today, and discovered that because I use the nvidia proprietary drivers, the option is disabled in gdm as wayland + nvidia proprietary = unstable (apparently).
That's very odd. I'm pretty sure upstream GNOME changed that with NVIDIA driver >= 510? Is your driver older than that?
Hmm, nope: $ rpm -qa | grep -i nvidia libnvidia-egl-wayland1-1.1.12-1.2.x86_64 nvidia-gl-G06-32bit-535.113.01-14.1.x86_64 nvidia-video-G06-535.113.01-14.1.x86_64 nvidia-utils-G06-535.113.01-14.1.x86_64 nvidia-compute-G06-32bit-535.113.01-14.1.x86_64 nvidia-gl-G06-535.113.01-14.1.x86_64 nvidia-compute-G06-535.113.01-14.1.x86_64 nvidia-driver-G06-kmp-default-535.113.01_k6.5.3_1-14.1.x86_64 nvidia-compute-utils-G06-535.113.01-14.1.x86_64 nvidia-video-G06-32bit-535.113.01-14.1.x86_64 kernel-firmware-nvidia-20230829-1.1.noarch Maybe I had old information. Either way, I don't see the option in gdm to select Wayland. Maybe I'm missing something? (The GNOME Wayland pattern is selected in YaST) $ rpm -qa | grep -i wayland libnvidia-egl-wayland1-1.1.12-1.2.x86_64 libwayland-cursor0-1.22.0-1.3.x86_64 libwayland-client0-1.22.0-1.3.x86_64 libwayland-egl1-1.22.0-1.3.x86_64 libQt6WaylandClient6-6.5.3-1.1.x86_64 wayland-devel-1.22.0-1.3.x86_64 libQt6WaylandEglClientHwIntegration6-6.5.3-1.1.x86_64 libwayland-server0-1.22.0-1.3.x86_64 libQt6WaylandEglCompositorHwIntegration6-6.5.3-1.1.x86_64 libQt6WaylandCompositor6-6.5.3-1.1.x86_64 qt6-wayland-6.5.3-1.1.x86_64 libva-wayland2-2.20.0-1.1.x86_64 libwayland-server0-32bit-1.22.0-1.3.x86_64 libQt5WaylandClient5-5.15.11+kde59-1.1.x86_64 gnome-session-wayland-45.0-1.1.x86_64 xwayland-23.2.1-1.1.x86_64 libgstwayland-1_0-0-1.22.6-1.1.x86_64 Thanks for the assist! -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On Fri, Oct 13, 2023 at 6:20 PM Jim Henderson <hendersj@gmail.com> wrote:
On Fri, 13 Oct 2023 17:54:55 -0400, Neal Gompa wrote:
On Fri, Oct 13, 2023 at 3:45 PM Jim Henderson <hendersj@gmail.com> wrote:
On Fri, 13 Oct 2023 13:11:57 -0400, Neal Gompa wrote:
Since you appear to be using GNOME on Xorg, have you tried to see if it works in GNOME Wayland?
I have not - I attempted to try this earlier today, and discovered that because I use the nvidia proprietary drivers, the option is disabled in gdm as wayland + nvidia proprietary = unstable (apparently).
That's very odd. I'm pretty sure upstream GNOME changed that with NVIDIA driver >= 510? Is your driver older than that?
Hmm, nope:
$ rpm -qa | grep -i nvidia libnvidia-egl-wayland1-1.1.12-1.2.x86_64 nvidia-gl-G06-32bit-535.113.01-14.1.x86_64 nvidia-video-G06-535.113.01-14.1.x86_64 nvidia-utils-G06-535.113.01-14.1.x86_64 nvidia-compute-G06-32bit-535.113.01-14.1.x86_64 nvidia-gl-G06-535.113.01-14.1.x86_64 nvidia-compute-G06-535.113.01-14.1.x86_64 nvidia-driver-G06-kmp-default-535.113.01_k6.5.3_1-14.1.x86_64 nvidia-compute-utils-G06-535.113.01-14.1.x86_64 nvidia-video-G06-32bit-535.113.01-14.1.x86_64 kernel-firmware-nvidia-20230829-1.1.noarch
Maybe I had old information. Either way, I don't see the option in gdm to select Wayland. Maybe I'm missing something? (The GNOME Wayland pattern is selected in YaST)
$ rpm -qa | grep -i wayland libnvidia-egl-wayland1-1.1.12-1.2.x86_64 libwayland-cursor0-1.22.0-1.3.x86_64 libwayland-client0-1.22.0-1.3.x86_64 libwayland-egl1-1.22.0-1.3.x86_64 libQt6WaylandClient6-6.5.3-1.1.x86_64 wayland-devel-1.22.0-1.3.x86_64 libQt6WaylandEglClientHwIntegration6-6.5.3-1.1.x86_64 libwayland-server0-1.22.0-1.3.x86_64 libQt6WaylandEglCompositorHwIntegration6-6.5.3-1.1.x86_64 libQt6WaylandCompositor6-6.5.3-1.1.x86_64 qt6-wayland-6.5.3-1.1.x86_64 libva-wayland2-2.20.0-1.1.x86_64 libwayland-server0-32bit-1.22.0-1.3.x86_64 libQt5WaylandClient5-5.15.11+kde59-1.1.x86_64 gnome-session-wayland-45.0-1.1.x86_64 xwayland-23.2.1-1.1.x86_64 libgstwayland-1_0-0-1.22.6-1.1.x86_64
Hmm, okay. Looking at the driver packaging sources, one difference I note from Fedora and openSUSE is that RPM Fusion's packaging includes a patch that turns on kernel modesetting by default. Since that patch (or equivalent) does not exist in openSUSE's NVIDIA driver packaging, can you check to see if you have "nvidia_drm.modeset=1" in your kernel boot arguments? You can check by reading /proc/cmdline. If it's not there, try modifying your kernel boot arguments in the grub configuration so that you have "nvidia_drm.modeset=1" in it. That may fix it for GNOME, since that will initialize NVIDIA's Direct Rendering Manager (DRM) support, which enables kernel modesetting. -- 真実はいつも一つ！/ Always, there's only one truth!
On Fri, 13 Oct 2023 18:36:07 -0400, Neal Gompa wrote:
Hmm, okay. Looking at the driver packaging sources, one difference I note from Fedora and openSUSE is that RPM Fusion's packaging includes a patch that turns on kernel modesetting by default. Since that patch (or equivalent) does not exist in openSUSE's NVIDIA driver packaging, can you check to see if you have "nvidia_drm.modeset=1" in your kernel boot arguments? You can check by reading /proc/cmdline. If it's not there, try modifying your kernel boot arguments in the grub configuration so that you have "nvidia_drm.modeset=1" in it. That may fix it for GNOME, since that will initialize NVIDIA's Direct Rendering Manager (DRM) support, which enables kernel modesetting.
That option wasn't enabled, so I enabled it and rebooted; still don't see the option in gdm to switch to Wayland. The output of cat /proc/cmdline is below: BOOT_IMAGE=/boot/vmlinuz-6.5.6-1-default root=UUID=a3a2a6c2-1701-406e- b823-6276b551890f splash=silent quiet security=apparmor nosimplefb=1 nvidia_drm.modeset=1 mitigations=auto -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
On Fri, Oct 13, 2023 at 6:52 PM Jim Henderson <hendersj@gmail.com> wrote:
On Fri, 13 Oct 2023 18:36:07 -0400, Neal Gompa wrote:
Hmm, okay. Looking at the driver packaging sources, one difference I note from Fedora and openSUSE is that RPM Fusion's packaging includes a patch that turns on kernel modesetting by default. Since that patch (or equivalent) does not exist in openSUSE's NVIDIA driver packaging, can you check to see if you have "nvidia_drm.modeset=1" in your kernel boot arguments? You can check by reading /proc/cmdline. If it's not there, try modifying your kernel boot arguments in the grub configuration so that you have "nvidia_drm.modeset=1" in it. That may fix it for GNOME, since that will initialize NVIDIA's Direct Rendering Manager (DRM) support, which enables kernel modesetting.
That option wasn't enabled, so I enabled it and rebooted; still don't see the option in gdm to switch to Wayland.
The output of cat /proc/cmdline is below:
BOOT_IMAGE=/boot/vmlinuz-6.5.6-1-default root=UUID=a3a2a6c2-1701-406e- b823-6276b551890f splash=silent quiet security=apparmor nosimplefb=1 nvidia_drm.modeset=1 mitigations=auto
So, these are the disabler rules: https://gitlab.gnome.org/GNOME/gdm/-/blob/gnome-45/data/61-gdm.rules.in?ref_... Can you give me a list of what's in /run/udev? -- 真実はいつも一つ！/ Always, there's only one truth!
On Fri, 13 Oct 2023 20:00:02 -0400, Neal Gompa wrote:
Can you give me a list of what's in /run/udev?
--- snip --- $ ls /run/udev/ control= data/ gdm-machine-has-hardware-gpu gdm-machine-has-vendor-nvidia-driver links/ static_node-tags/ tags/ watch/ --- snip --- With a little help from Malcolm, I was able to get into Wayland - I had to change /etc/gdm/custom.conf to comment out WaylandEnable=false. He'd suggested that I try using udevadm monitor while bringing up the environment to see what was happening in the udev rules; nothing at all seemed to happen with the nvidia device (this was before I made the change to /etc/gdm/custom.conf and got wayland running): --- snip --- monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[3555.550886] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256 (bluetooth) UDEV [3555.596343] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256 (bluetooth) KERNEL[3555.684341] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C (hid) KERNEL[3555.684631] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery/wakeup78 (wakeup) KERNEL[3555.684686] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery/hwmon5 (hwmon) KERNEL[3555.684784] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30 (input) KERNEL[3555.684941] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30/mouse1 (input) KERNEL[3555.684990] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30/event23 (input) KERNEL[3555.685048] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/hidraw/hidraw7 (hidraw) UDEV [3555.687520] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C (hid) UDEV [3555.697024] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30 (input) UDEV [3555.698118] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30/mouse1 (input) UDEV [3555.707033] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/hidraw/hidraw7 (hidraw) KERNEL[3555.723366] bind /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C (hid) UDEV [3555.753981] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/input/input30/event23 (input) UDEV [3555.767318] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery/wakeup78 (wakeup) UDEV [3555.787392] add /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery/hwmon5 (hwmon) UDEV [3555.788334] bind /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C (hid) KERNEL[3555.826827] change /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery (power_supply) KERNEL[3555.826897] change /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery (power_supply) UDEV [3555.828914] change /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery (power_supply) UDEV [3555.831174] change /devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/bluetooth/hci0/hci0:256/0005:004C:0269.000C/power_supply/hid-30:d9:d9:8a:ab:3a-battery (power_supply) KERNEL[3579.819210] add /devices/virtual/bdi/0:70 (bdi) UDEV [3579.865182] add /devices/virtual/bdi/0:70 (bdi) KERNEL[3580.812237] add /devices/virtual/bdi/0:120 (bdi) UDEV [3580.815281] add /devices/virtual/bdi/0:120 (bdi) KERNEL[3582.299835] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/usbmisc/hiddev2 (usbmisc) KERNEL[3582.299860] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A/hidraw/hidraw5 (hidraw) KERNEL[3582.299875] unbind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A (hid) KERNEL[3582.299885] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A (hid) KERNEL[3582.299901] unbind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1 (usb) UDEV [3582.301290] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/usbmisc/hiddev2 (usbmisc) UDEV [3582.303835] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A/hidraw/hidraw5 (hidraw) UDEV [3582.304865] unbind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A (hid) UDEV [3582.305706] remove /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000A (hid) UDEV [3582.306875] unbind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1 (usb) KERNEL[3582.309837] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D (hid) KERNEL[3582.309875] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/usbmisc/hiddev2 (usbmisc) KERNEL[3582.309944] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D/hidraw/hidraw5 (hidraw) KERNEL[3582.309989] bind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D (hid) KERNEL[3582.310012] bind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1 (usb) UDEV [3582.311011] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/usbmisc/hiddev2 (usbmisc) UDEV [3582.311709] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D (hid) UDEV [3582.321483] add /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D/hidraw/hidraw5 (hidraw) UDEV [3582.322091] bind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1/0003:3384:0007.000D (hid) UDEV [3582.322871] bind /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.2/1-6.2.2/1-6.2.2.4/1-6.2.2.4.6/1-6.2.2.4.6:1.1 (usb) --- snip --- Everything in 3555.x happened when I was connecting my bluetooth mouse. Running in Wayland, the Wacom tablet is completely disabled. GNOME settings says it's there, but I have no mouse pointer nor any indication it's affecting the environment at all. If it's useful, here's the output from inxi -Gaz --- snip --- $ inxi -Gaz Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3090 Ti] vendor: Gigabyte driver: nvidia v: 535.113.01 alternate: nouveau,nvidia_drm non-free: 530.xx+ status: current (as of 2023-05) arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 ports: active: none off: DP-1,DP-2,HDMI-A-1 empty: DP-3 bus-ID: c1:00.0 chip-ID: 10de:2203 class-ID: 0300 Display: wayland server: X.org v: 1.21.1.8 with: Xwayland v: 23.2.1 compositor: gnome-shell v: 45.0 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: 0 Monitor-1: DP-1 model: Dell P1914S serial: <filter> built: 2014 res: 1280x1024 dpi: 86 gamma: 1.2 size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4 modes: max: 1280x1024 min: 640x480 Monitor-2: DP-2 model: ViewSonic XG3220 SERIES serial: <filter> built: 2020 res: 3840x2160 dpi: 140 gamma: 1.2 size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes: max: 3840x2160 min: 640x480 Monitor-3: HDMI-A-1 model: Dell U3419W serial: <filter> built: 2018 res: 3440x1440 dpi: 109 gamma: 1.2 size: 800x335mm (31.5x13.19") diag: 867mm (34.1") modes: max: 3440x1440 min: 640x480 API: OpenGL v: 4.6.0 NVIDIA 535.113.01 renderer: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 direct-render: Yes --- snip --- -- Jim Henderson Please keep on-topic replies on the list so everyone benefits
participants (2)
-
Jim Henderson -
Neal Gompa