Prioritise the use of tools dedicated to Wayland in environments where a composer related to it operates

[Ricky-Tigg]

Hello. The GNOME Project has gone Wayland-protocol-only, removing the X11 back-end from Mutter, GNOME’s compositor and window manager. It still keeps alive the Xwayland support for those users that still nowadays wish to run X11 clients under Wayland.

On my system, 'rpm -qR fastfetch' allows me to deduce that fastfetch likely relies solely on X11 clients to fetch strings related to certain modules; for instance, Display and Monitor, via xdriinfo, xdpyinfo, xprop, and xrandr. However, an X11 client cannot compete with a dedicated Wayland tool, e.g. like wayland-info regarding the reliability of the information source on a system using a Wayland composer.

[CarterLi]

What are you talking about bro? Fastfetch never uses xdriinfo, xdpyinfo, xprop, xrandr, etc.

What distro are you using?

[Ricky-Tigg]

'rpm -qR fastfetch' allows me to deduce that fastfetch likely relies solely on X11 clients

Then it doesn't! I thought I could deduce it does as a sum on Fedora of those outputs:

$ wayland-info -i wl_output | sed -r "s/\t/ /g"
interface: 'wl_output',                                  version:  4, name:  3
 name: eDP-1
 description: Built-in display
 x: 0, y: 0, scale: 1,
 physical_width: 340 mm, physical_height: 190 mm,
 make: 'CMN', model: '0x15f5',
 subpixel_orientation: unknown, output_transform: normal,
 mode:
  width: 1600 px, height: 900 px, refresh: 59.946 Hz,
  flags: current

which if any tool must be able to fetch reliable values, then by comparing the output to

$ fastfetch -l none -s display
Display (CMN15F5): 1600x900 in 15", 60 Hz [Built-in]

which then is revealing that "15" especially and "60 Hz" are inaccurate since rounded, and finally with

$ inxi -G | sed 1d
  Device-1: Intel Kaby Lake-U GT2 [HD Graphics 620] driver: i915 v: kernel
  Display: wayland server: Xwayland v: 24.1.9 compositor: gnome-shell
    v: 50.0 driver: gpu: i915 resolution: 1600x900~60Hz
  Info: Tools: api: glxinfo wl: wayland-info x11: xdriinfo, xdpyinfo,
    xprop, xrandr

from which I concluded this tool too might use those X11 tools since fetching inaccurate values.

[CarterLi]

Bruh...

What on earch does rpm -qR fastfetch print?

which then is revealing that "15" especially and "60 Hz" are inaccurate since rounded, and finally with

There is an option to display the accurate/unrounded value:

    {
      "type": "display",
      "preciseRefreshRate": true,
    }

[Ricky-Tigg]

Let it be. Making values accurate one by one you are instructing.