MeloNX/Ryujinx-ryubing
10
0
Fork 0
Code Issues 184 Pull Requests 15 Actions Packages Projects Releases 36 Wiki Activity

[Bug] X64 AppImage build fails to launch #325

New Issue
Closed
opened 2024-11-28 23:45:15 +00:00 by INS4NIt · 5 comments
INS4NIt commented 2024-11-28 23:45:15 +00:00 (Migrated from github.com)
Copy Link

Description of the issue

Attempting to launch either of the two existing X64 AppImage releases does not open the application. Attempting to run it via a program like AppImageLauncher produces the error message "Failed to register AppImage in system via libappimage"

The behavior is consistent with this: https://github.com/TheAssassin/AppImageLauncher/issues/410

Reproduction steps

Download any recent ryujinx-1.2.XX-x64 AppImage build and attempt to run it either directly or through AppImageLauncher

Log file

N/A (Ryujinx never launches)

OS

Fedora Linux 41

Ryujinx version

1.2.75, 1.2.76

Game version

No response

CPU

No response

GPU

No response

RAM

No response

List of applied mods

No response

Additional context?

No response

### Description of the issue Attempting to launch either of the two existing X64 AppImage releases does not open the application. Attempting to run it via a program like AppImageLauncher produces the error message "Failed to register AppImage in system via libappimage" The behavior is consistent with this: https://github.com/TheAssassin/AppImageLauncher/issues/410 ### Reproduction steps Download any recent ryujinx-1.2.XX-x64 AppImage build and attempt to run it either directly or through AppImageLauncher ### Log file N/A (Ryujinx never launches) ### OS Fedora Linux 41 ### Ryujinx version 1.2.75, 1.2.76 ### Game version _No response_ ### CPU _No response_ ### GPU _No response_ ### RAM _No response_ ### List of applied mods _No response_ ### Additional context? _No response_
piplup55 commented 2024-11-28 23:59:35 +00:00 (Migrated from github.com)
Copy Link

i can't promise this to get fixed but i will at least take a look, based on the info you have provided it makes me think it's a problem with the icon

i can't promise this to get fixed but i will at least take a look, based on the info you have provided it makes me think it's a problem with the icon
qurious-pixel commented 2024-11-29 00:53:41 +00:00 (Migrated from github.com)
Copy Link

@INS4NIt you cannot run an AppImage directly with AppImageLauncher installed. It creates hooks that intercepts all AppImages. You have to uninstall AppImageLauncher to test if the AppImage is broken or there is incomaptibility with the launcher.
There used to be some overrides, to NOT run the launcher on specific Appimages, but those do not seem to work anymore.

@INS4NIt you cannot run an AppImage directly with AppImageLauncher installed. It creates hooks that intercepts all AppImages. You have to uninstall AppImageLauncher to test if the AppImage is broken or there is incomaptibility with the launcher. There used to be some overrides, to NOT run the launcher on specific Appimages, but those do not seem to work anymore.
INS4NIt commented 2024-11-30 02:52:55 +00:00 (Migrated from github.com)
Copy Link

@qurious-pixel I was under the impression that selecting "Run once" in the initial integration popup would bypass the AppImageLauncher hooks... The program fails to launch whether attempting to run it after integrating, or opting to run it standalone.

If someone else can demonstrate that the AppImage build works on a clean system, I'll uninstall AppImageLauncher to help with troubleshooting. I'd rather not go the nuclear route and uninstall AppImageLauncher in the meantime, though.

@qurious-pixel I was under the impression that selecting "Run once" in the initial integration popup would bypass the AppImageLauncher hooks... The program fails to launch whether attempting to run it after integrating, or opting to run it standalone. If someone else can demonstrate that the AppImage build works on a clean system, I'll uninstall AppImageLauncher to help with troubleshooting. I'd rather not go the nuclear route and uninstall AppImageLauncher in the meantime, though.
GreemDev commented 2024-11-30 02:55:07 +00:00 (Migrated from github.com)
Copy Link

@qurious-pixel I was under the impression that selecting "Run once" in the initial integration popup would bypass the AppImageLauncher hooks... The program fails to launch whether attempting to run it after integrating, or opting to run it standalone.

If someone else can demonstrate that the AppImage build works on a clean system, I'll uninstall AppImageLauncher to help with troubleshooting. I'd rather not go the nuclear route and uninstall AppImageLauncher in the meantime, though.

This is the case, unfortunately. @piplup55 was in the Discord and had all of their app images break entirely which worked previously. After uninstalling AIL and rebooting, they worked again

> @qurious-pixel I was under the impression that selecting "Run once" in the initial integration popup would bypass the AppImageLauncher hooks... The program fails to launch whether attempting to run it after integrating, or opting to run it standalone. > > If someone else can demonstrate that the AppImage build works on a clean system, I'll uninstall AppImageLauncher to help with troubleshooting. I'd rather not go the nuclear route and uninstall AppImageLauncher in the meantime, though. This is the case, unfortunately. @piplup55 was in the Discord and had all of their app images break entirely which worked previously. After uninstalling AIL and rebooting, they worked again
INS4NIt commented 2024-11-30 03:20:08 +00:00 (Migrated from github.com)
Copy Link

Well huh, thanks for the confirmation. I uninstalled AppImageLauncher and rebooted, and Ryujinx launched just fine!

I installed Gear Lever and attempted to integrate Ryujinx with that instead, and it appears to play nicely so far. It seems AppImageLauncher is beginning to show it's age.

Well huh, thanks for the confirmation. I uninstalled AppImageLauncher and rebooted, and Ryujinx launched just fine! I installed Gear Lever and attempted to integrate Ryujinx with that instead, and it appears to play nicely so far. It seems AppImageLauncher is beginning to show it's age.
👍 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
audio
Affects Audio playback during emulation
blocked on external progress
This cannot move forward without work on an external project or service.
bug
Something isn't working
cpu
An issue with ARMeilleure, the JIT, or Hypervisor
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good first issues to work on for new contributors
gpu
Affects GPU emulation
graphics-backend:metal
Affects the Metal Graphics backend
graphics-backend:opengl
Affects the OpenGL Graphics backend
graphics-backend:vulkan
Affects the Vulkan Graphics backend
gui
Affects the Avalonia UI or translations.
help wanted
Extra attention is needed
horizon
Affects the Horizon OS HLE components.
infra
Updates to dependencies
invalid
This doesn't seem right
kernel
Affects the kernel HLE components.
ldn
Affects the LDN functionality
linux
Linux only issue
macOS
macOS only issue
not planned but open to a PR
I do not intend on working on this myself, but I would not be opposed to an implementation.
question
Further information is requested
windows
Windows only issue
wontfix
This will not be worked on
No Label
bug
good first issue
help wanted
wontfix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MeloNX/Ryujinx-ryubing#325
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?