Linux based bug - Error: X11 error X11Error { error_kind: Drawable, error_code: 9, sequence: 13, bad_value: 0, minor_opcode: 0, major_opcode: 14, extension_name: None, request_name: Some("GetGeometry") }

[sapg]

Describe the bug
When I run t-rec I get this error:

Error: X11 error X11Error { error_kind: Drawable, error_code: 9, sequence: 13, bad_value: 0, minor_opcode: 0, major_opcode: 14, extension_name: None, request_name: Some("GetGeometry") }

To Reproduce
Steps to reproduce the behavior:

1. t-rec

Expected behavior
Whatever should happen when it runs normally.

Version Numbers of your System:
just run: inxi -SGxx and paste it below:

System:
  Host: laptop Kernel: 5.15.0-122-generic x86_64 bits: 64 compiler: gcc
    v: 11.4.0 Desktop: GNOME 42.9 tk: GTK 3.24.33 wm: gnome-shell dm: GDM3
    Distro: Ubuntu 22.04.5 LTS (Jammy Jellyfish)
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: Dell driver: i915
    v: kernel ports: active: LVDS-1
    empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0166
  Device-2: Microdia Integrated Webcam type: USB driver: uvcvideo
    bus-ID: 1-1.5:4 chip-ID: 0c45:648b
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 display-ID: 0
  Monitor-1: LVDS-1 model: LG res: 1600x900 dpi: 131 diag: 355mm (14")
  OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    v: 4.2 Mesa 23.2.1-1ubuntu3.1~22.04.2 direct render: Yes

Additional context

Please include the output of xwininfo -root -tree -int

xwininfo: Window id: 564 (the root window) (has no name)

Root window id: 564 (the root window) (has no name)
Parent window id: 0 (none)
34 children:
8388618 "gnome-shell": ("gnome-shell" "Gnome-shell") 1x1+-200+-200 +-200+-200
1 child:
8388619 (has no name): () 1x1+-1+-1 +-201+-201
16777242 "New Issue · sassman/t-rec-rs - Google Chrome": ("google-chrome" "Google-chrome") 1562x873+38+27 +38+27
27262981 "": ("" "") 880x525+393+167 +393+167
1 child:
27263695 (has no name): () 1x1+-1+-1 +392+166
8390670 "gnome-shell": () 10x10+-100+-100 +-100+-100
27262983 (has no name): () 1x1+0+0 +0+0
18874376 (has no name): () 1x1+-1+-1 +-1+-1
16777221 (has no name): () 1x1+0+0 +0+0
18874371 "google-chrome-stable": ("google-chrome-stable" "Google-chrome-stable") 200x200+0+0 +0+0
1 child:
18874372 (has no name): () 1x1+-1+-1 +-1+-1
18874369 "google-chrome-stable": ("google-chrome-stable" "Google-chrome-stable") 10x10+10+10 +10+10
16777216 "Chromium clipboard": () 10x10+-100+-100 +-100+-100
10486179 (has no name): () 1600x1+0+899 +0+899
10486178 (has no name): () 1600x1+0+0 +0+0
10486177 (has no name): () 1x900+1599+0 +1599+0
10486176 (has no name): () 1x900+0+0 +0+0
10486112 "": ("" "") 800x360+0+0 +0+0
10486107 "n": ("n" "") 800x360+0+0 +0+0
10485822 "N": ("n" "") 740x560+449+183 +449+183
10485773 "": ("n" "") 278x108+679+415 +679+415
10485767 (has no name): () 1x1+0+0 +0+0
8388634 (has no name): () 1x1+-1+-1 +-1+-1
8388630 (has no name): () 1x1+-100+-100 +-100+-100
8388625 (has no name): () 1x1+-1+-1 +-1+-1
8388624 (has no name): () 1x1+-1+-1 +-1+-1
8388623 (has no name): () 1x1+-100+-100 +-100+-100
8388622 (has no name): () 1x1+-1+-1 +-1+-1
8388616 (has no name): () 1x1+-100+-100 +-100+-100
8388615 (has no name): () 1x1+-100+-100 +-100+-100
8388614 "GNOME Shell": () 1x1+-100+-100 +-100+-100
8388609 "gnome-shell": ("gnome-shell" "Gnome-shell") 10x10+10+10 +10+10
6291459 "ibus-xim": () 1x1+0+0 +0+0
1 child:
6291460 (has no name): () 1x1+-1+-1 +-1+-1
6291457 "ibus-x11": ("ibus-x11" "Ibus-x11") 10x10+10+10 +10+10
2097154 (has no name): () 10x10+0+0 +0+0
2097153 "gsd-xsettings": ("gsd-xsettings" "Gsd-xsettings") 10x10+10+10 +10+10
8388629 "mutter guard window": () 1600x900+0+0 +0+0

[popey]

Looks like you're running a wayland session. t-rec doesn't support Wayland (or indeed XWayland on top of Wayland). Logout, and login again with an X session.

See #27

[sassman]

Interesting though is that it seems like Xwayland is already running.

  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.1

@sapg Could you please confirm that you are running on Xwayland?

[sapg]

Yes, I was running Wayland, that was the problem.

[westurner]

FWIW gpu_screen_recorder and OBS Studio do work with wayland:

• GPU Screen Recorder
  https://flathub.org/apps/com.dec05eba.gpu_screen_recorder
  https://git.dec05eba.com/gpu-screen-recorder/tree/src/window/window_wayland.c

• OBS Studio
  https://flathub.org/apps/com.obsproject.Studio
  https://github.com/obsproject/obs-studio/blob/master/plugins/linux-pipewire/portal.c

[sassman]

The wayland discussion is really helpful, but let's have it on the correct issue #27 then.
Thanks for sharing the osb-studio approach. Indeed I have seen others also using dbus to have RPC on the wayland compositor. So I'm very sure that's the way forward.