> For the complete documentation index, see [llms.txt](https://kaizo-1.gitbook.io/kaizo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kaizo-1.gitbook.io/kaizo-docs/common-issues.md).

# Common issues

Quick fixes for Kaizo. You only get the Kaizo binary. There is no `scripts` folder and no `./scripts/run.sh`.

If you installed with the app menu, you can still pass env vars in a terminal:

```bash
SOBER_OVERLAY_DISPLAY=:0 ~/.local/share/kaizo/kaizo
```

Or for a manual binary:

```bash
SOBER_OVERLAY_DISPLAY=:0 sudo -E ./Roblox_Cheat
```

## NixOS (`libEGL.so.1` missing)

On NixOS, file capabilities and nix-ld cannot be used together. `setcap` makes glibc drop `LD_*`, so Kaizo cannot find `libEGL.so.1`, and a raw root launch can change HWID.

Follow [NixOS](/kaizo-docs/common-issues/nixos.md) instead of the normal install path. That page is from **yori brah** (`@multihued`).

## Crashes when joining, leaving, or switching games

Sometimes crashes are caused by **Internal chams** or **Raycast aimbot** being left on.

Turn those off in the menu, then try again:

1. Open the Kaizo menu with Insert or Home.
2. Turn off Internal chams.
3. Turn off Raycast aimbot (or Raycast silent).
4. Rejoin the game or restart Kaizo if it already crashed.

If it still crashes with both off, ask in Discord with what you had enabled.

## Waiting for Sober

Sober is not running yet. Open Roblox with Sober and wait. The cheat will keep trying.

## Permission denied on /proc mem

The cheat cannot read the game. Run it once with sudo so caps can stamp:

```bash
sudo -E ./Roblox_Cheat
```

Or if you use the installed app path:

```bash
sudo -E ~/.local/share/kaizo/kaizo
```

Then start it again from the app menu if it asks you to.

## Login window fails or Authorization required

Do not run it as plain root. Use sudo from your own user:

```bash
sudo -E ./Roblox_Cheat
```

The `-E` keeps your display env so the login window can open.

## No display / DISPLAY not found

Your display env got lost under sudo. Always use:

```bash
sudo -E ./Roblox_Cheat
```

### Pick which display to use

If you have more than one screen setup, or the overlay opens on the wrong display, force it.

1. In a normal terminal (not sudo), check your display:

```bash
echo $DISPLAY
```

You will usually see `:0` or `:1`.

2. Start Kaizo with that value:

```bash
SOBER_OVERLAY_DISPLAY=:0 sudo -E ./Roblox_Cheat
```

Or:

```bash
SOBER_OVERLAY_DISPLAY=:1 sudo -E ./Roblox_Cheat
```

Use the same number your `echo $DISPLAY` showed. If the overlay is still wrong, try the other one.

## Overlay does not show

First put Sober on XWayland, then restart Sober. See Desktops and window managers.

```bash
flatpak override --user --socket=x11 --nosocket=wayland org.vinegarhq.Sober
```

Quit Sober completely and open it again.

Every window manager is supported (GNOME, KDE, Hyprland, niri, Sway, and the rest). The overlay follows the Sober window after that.

If you are on a normal desktop and it still does not show, try forcing X11:

```bash
ROBLOX_CHEAT_OVERLAY_BACKEND=x11 sudo -E ./Roblox_Cheat
```

Also check you picked the right display with `SOBER_OVERLAY_DISPLAY` above.

## Overlay is all black (KDE)

On KDE Plasma, Sober can ask KWin to turn the compositor off. That makes the Kaizo overlay a black screen.

Turn this setting **off**:

1. Open **System Settings**.
2. Go to **Display & Monitor → Compositor** (or search for `Compositor`).
3. Uncheck **Allow applications to block compositing**.
4. Click Apply, then restart Sober and Kaizo.

{% hint style="warning" %}
The setting name is **Allow applications to block compositing**. Leave it off. If a game is allowed to block compositing, the overlay goes black.
{% endhint %}

## Overlay does not line up

The overlay follows the Sober window. If it is stuck fullscreen or on the wrong screen:

1. Make sure Sober is on XWayland (command above) and you restarted it.
2. In the Kaizo menu, set **Settings → Displays → Overlay Monitor** to **Auto (follow game)**.
3. A named monitor fills that whole display on purpose.

See Desktops and window managers.

## Overlay eats clicks / no click-through

Sober is probably still on native Wayland. Run the XWayland override, restart Sober, then start Kaizo again.

When the menu is closed, clicks should go through to the game. When the menu is open, only the menu is clickable.

## NVIDIA GLX errors

Try:

```bash
ROBLOX_CHEAT_GLX_VENDOR=nvidia sudo -E ./Roblox_Cheat
```

## Insert does nothing / menu will not open

Global input may have failed. Run with sudo so it can open `/dev/input`.

Mouse aim also needs `/dev/uinput`. Camera aim can still work without that.

If the menu still will not open, check your system tray. Kaizo has a tray icon there. You can open the menu from the tray as a backup.

{% hint style="warning" %}
**Insert still dead?** Some users have reported that updating their kernel fixed Insert. Reboot after the update, or use **Home** / the tray icon until then.
{% endhint %}

## License key errors

Enter a valid key and check your internet. If login was cancelled, just start the cheat again.

## Related

* NixOS
* How to run
* Desktops and window managers
* Requirements
* Installation


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kaizo-1.gitbook.io/kaizo-docs/common-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.