To install Ryujinx on Linux now, use the Flathub package named Ryujinx (Ryubing). Its application ID is io.github.ryubing.Ryujinx, which replaces the retired org.ryujinx.Ryujinx ID used by older commands. Flathub labels this package as community-provided and unverified, so treat its issue tracker and the Ryubing project as separate support paths.
Install the current Flatpak package
When flatpak is missing or Flathub has not been added, first set up Flatpak and Flathub on your distribution, then return to this command.
flatpak install flathub io.github.ryubing.Ryujinx
Confirm the application ID before accepting the transaction because old tutorials point to an ID that no longer identifies the current Flathub listing.
Launch Ryujinx after installation
Your desktop environment should add Ryujinx to its application launcher, but you can also use the command below to confirm that Flatpak can start the installed application without relying on a menu entry.
flatpak run io.github.ryubing.Ryujinx
If Flatpak reports that the application is not installed, repeat the install command and check the ID character for character, then use the project and Flathub issue links from the package page if the launcher opens but the program does not.
Know which package you installed
The current Flathub listing calls the application Ryujinx (Ryubing) and labels it as a community package that is not officially supported by Ryubing. Send packaging bugs to the Flathub package tracker and emulator behavior to the project.
| What you are checking | What to use |
|---|---|
| Current Flathub application ID | io.github.ryubing.Ryujinx |
| Install and updates | Flatpak and Flathub |
| Packaging-specific problems | Flathub package issue tracker |
| Game content | Only content and system materials you are entitled to use |
A current package does not make every game compatible or every controller setup automatic, so start with the emulator window and configure only your own hardware and content within the laws and rights that apply to you.
Set up the rest of your Linux gaming desktop
Ryujinx is one part of a gaming setup. If you use Steam, configure your controller in Steam on Linux before chasing emulator input issues, and use the Steam Deck Gaming Mode shortcut workflow when you need a non-Steam launcher to behave well on a handheld.
For other systems, the Dolphin Linux install and mGBA guide cover separate consoles and workflows. The current Yuzu status guide explains why an old emulator tutorial can become a poor starting point after a project stops shipping updates.
Troubleshoot the install in the right order
- Run flatpak –version to confirm Flatpak is installed.
- Open the current Ryujinx (Ryubing) Flathub listing and compare the application ID with your command.
- Run the install command again and read the transaction prompt before approving it.
- Use flatpak run with the same application ID when the desktop launcher is missing.
- Report a Flatpak-specific fault to the package tracker, with the command output and your distribution details.
This order separates a missing Flatpak runtime, a wrong application ID, and a launcher integration issue. It also keeps a package-maintenance problem from being mistaken for an emulator problem.
Ryujinx on Linux FAQ
These answers focus on the current Flatpak package and its support boundary.
What is the current Ryujinx Flatpak application ID?
The current Flathub listing uses io.github.ryubing.Ryujinx. Do not use the retired org.ryujinx.Ryujinx ID from older tutorials.
Is the Ryujinx Flatpak officially supported by Ryubing?
No. Flathub labels it as a community package and says it is not officially supported by Ryubing. Use the Flathub package tracker for packaging-specific issues.
What should I do if Ryujinx is missing from my application menu?
Start it with flatpak run io.github.ryubing.Ryujinx. If that works, the install succeeded and the remaining problem is launcher integration.
Keep the Flathub listing open while you install. It is the quickest way to verify the package ID and find the right support route when the transaction or launcher behaves differently from the steps above.