Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can't run Trainers (Game Cheats)

Open
#492 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
linux
Domain
desktop

Research direction

The issue names no source file, test, or entry point. Start by reproducing the missing trainer GUI with Bottles 66.8 and soda-11.0-3 on Wayland, then identify the relevant project entry point; done means the trainer window renders and accepts interaction in the described setup.

Written by the indexing model from the issue text.

Description

Description

Games run perfectly smooth inside Bottles, but launching a game trainer (.exe) inside the same bottle fails to display its GUI. The trainer process starts and its icon appears on the taskbar/system tray, but no interactive window is rendered on screen.

Steps to Reproduce
  1. Launch a game inside a bottle (runs smoothly without issues).
  2. Run the game trainer executable (.exe) inside the same bottle (via "Run Executable" or as a shortcut).
  3. Observe the system taskbar/dock: The trainer process icon appears.
  4. Try clicking or switching to the window: The GUI fails to render on screen.
Expected Behavior

The trainer GUI should render normally over or alongside the game window, allowing key inputs and UI interaction.

Actual Behavior

The trainer process remains running in the background/taskbar, but the window interface never shows up.

System / Environment
  • OS / Kernel: CachyOS (7.2.0-1-cachyos)
  • Display Server: Wayland
  • GPU: NVIDIA GeForce RTX 5060 (Driver: nvidia)
  • Bottles Version: 66.8
  • Runner Used: soda-11.0-3
Dominant language
No language data
Stars
111
Forks
93
Avg merge
1d 1h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bottlesdevs/programs

All issues in bottlesdevs/programs

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.