Hidamari dosen't open

[Uzvengrir]

When I run flatpak run io.github.jeffshee.Hidamari in the terminal it returns:

X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 146 ()
Minor opcode of failed request: 5
Resource id in failed request: 0x3c00003
Serial number of failed request: 56
Current serial number in output stream: 57
Traceback (most recent call last):
File "/app/bin/hidamari", line 44, in
sys.exit(main.main(VERSION, pkgdatadir, localedir))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/share/hidamari/hidamari/main.py", line 43, in main
sys_info.append(f"is_nvidia_proprietary = {is_nvidia_proprietary()}")
^^^^^^^^^^^^^^^^^^^^^^^
File "/app/share/hidamari/hidamari/utils.py", line 44, in is_nvidia_proprietary
output = subprocess.check_output(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/subprocess.py", line 466, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'glxinfo -B' returned non-zero exit status 1.

What would be a correct course of actions in order to make Hidamari to work?

[gccpsben]

I have the same problem as well, setup: KDE + Wayland, Arch Linux + Proprietary NVIDIA Driver.
I am using a 4-monitors setup. More information.

> hidamari
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  146 ()
  Minor opcode of failed request:  5
  Resource id in failed request:  0x1c00003
  Serial number of failed request:  56
  Current serial number in output stream:  56
Traceback (most recent call last):
  File "/usr/bin/hidamari", line 44, in <module>
    sys.exit(main.main(VERSION, pkgdatadir, localedir))
             ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/hidamari/hidamari/__main__.py", line 43, in main
    sys_info.append(f"is_nvidia_proprietary = {is_nvidia_proprietary()}")
                                               ~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/share/hidamari/hidamari/utils.py", line 44, in is_nvidia_proprietary
    output = subprocess.check_output(
        "glxinfo -B", shell=True, encoding='UTF-8')
  File "/usr/lib/python3.14/subprocess.py", line 472, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
           ~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
               **kwargs).stdout
               ^^^^^^^^^
  File "/usr/lib/python3.14/subprocess.py", line 577, in run
    raise CalledProcessError(retcode, process.args,
                             output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'glxinfo -B' returned non-zero exit status 1.

Calling glxinfo -B:

> glxinfo -B
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12288 MB
    Total available memory: 12288 MB
    Currently available dedicated video memory: 10568 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 3060/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 590.48.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  146 ()
  Minor opcode of failed request:  5
  Resource id in failed request:  0x1200003
  Serial number of failed request:  56
  Current serial number in output stream:  56

[lelelelkorgpt]

try to reinstall

[QuasarG]

I’m on Ubuntu 24.04 (GNOME 46). After switching to a Wayland session, Hidamari fails to start with:

X Error of failed request: BadWindow (invalid Window parameter)
...
subprocess.CalledProcessError: Command 'glxinfo -B' returned non-zero exit status 1

Running Hidamari with this env var makes it start successfully:

flatpak run --env=__GLX_VENDOR_LIBRARY_NAME=mesa io.github.jeffshee.Hidamari

So it looks like the startup NVIDIA/GLX detection via glxinfo -B can fail under Wayland (Xwayland/GLX), and forcing Mesa’s GLX vendor avoids the crash. A possible fix could be to handle glxinfo failure gracefully (don’t crash if it exits non-zero) or use an alternative detection method on Wayland.