-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Problem] Launching an AppImage using the AppImageLauncher by TheAssassin #331
Comments
The AppImage was built using the Is AppImageLauncher still developed and supported? The most recent release is from 2020. |
I don't know if it's being kept up to date, I tried running the AppImage using Gear Lever and it seems to work fine. All I know is the previous AppImages of FreeCAD until the weekly build worked with the AppImageLauncher. |
Right, we updated the images last week to use |
I would report this to appimagelauncher, beyond that I would recommend using appimagelauncher only for the desktop integration functionality and launch appimages directly the rest of the time |
I confirm this behavior with recent FreeCAD weeklies and AppImageLauncher (on Arm Debian Linux (bookworm) as a VM for me). It looks like AppImageLauncher does support https://github.com/AppImage/AppImageKit/releases |
AppImageLauncher actually replaces the launching functionality and you have to delete it to be able to launch AppImages without using it. As shown in the bug even attempting to run the AppImage from a terminal, it would still launch it using AppImageLauncher.
I can confirm the continuous build release of AppImageLauncher cannot launch the AppImage on Mint. |
even the continuous build of appimagelauncher is form 2022 so maybe this was abandoned, I'm not sure how wise it is to keep using it. The problem has been reported to them since at least oct 2023 TheAssassin/AppImageLauncher#602 |
Something has changed. This latest weekly is failing to launch. |
I am using this AppImageLauncher since forrever, this issue started to happen with the latest weekly build of Freecad. |
The issue is that AppImageLauncher is no longer maintained and does not support images built by recent versions of the |
Hello, i made a post on the freecad forum, then i saw this issue, i posted some info there, if it happen to be relevant here is the post: but same story, tried the aur package, then i downloaded it straight from this repo, thinking it might be a bad aur build and faced the same errors |
@Thiago-Assis-T Your issue is different from this one and is related to #332 . There appears to be an issue with either |
ooh, i see, thanks! |
so it doesn't sounds like there's much for us to do about this issue, I guess people should stop using appimage launcher... To replace it's functionality maybe we could include a script in the appimage that copies over the desktop file and icons? I'll see what I can come up with next week |
It doesn't for me:
|
have you restarted after removing appimagelauncher? do you have fuse3 installed? |
I can confirm that removing AppImageLauncher from my Linux Mint and chmod +x the RC4 app image the RC4 loads and runs. Bummer about AppImageLauncher, but good for RC4? Its hard to to tell how actively https://github.com/TheAssassin/AppImageLauncher is being maintained... |
Although you can see some relatively recent commits there's been no actual code changes for over a year. The author claims it is not abandoned though |
Yes fuse3 is installed. I've finally rebooted the computer and was able to launch the appimage. I don't know why the AppImageLauncher was still interfering with the launch while it was clearly removed. |
That would be great, @adrianinsaval. The main issue that AppImageLauncher solves for me is not being able to pin FreeCAD to my dock in Ubuntu or have it show up in the list of applications, due to lack of a desktop file. If the AppImage can solve that natively, then the launcher is not needed. |
Yes that sounds like the case. FYI, Gear Lever seems to do that same
thing as AppLauncher.
…On Sun, Nov 17, 2024 at 8:02 AM Ephi Blanshey ***@***.***> wrote:
so it doesn't sounds like there's much for us to do about this issue, I
guess people should stop using appimage launcher... To replace it's
functionality maybe we could include a script in the appimage that copies
over the desktop file and icons? I'll see what I can come up with next week
That would be great, @adrianinsaval <https://github.com/adrianinsaval>.
The main issue that AppImageLauncher solves for me is not being able to pin
FreeCAD to my dock in Ubuntu or have it show up in the list of
applications, due to lack of a desktop file. If the AppImage can solve that
natively, then the launcher is not needed.
—
Reply to this email directly, view it on GitHub
<#331 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI67KSMR756TKSIY6F7HOL2BC42VAVCNFSM6AAAAABRG43HQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBRGMZTAOBXHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Confirmed that Gear Level works as intended. |
Describe the bug
AppImages of the weekly build for x86_64 launched by the AppImageLauncher can't be launched and simply do not open.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Additional context
Error produced by attempting to run the AppImage from the terminal which opens the menu to click "Run Once".
OS: Linux Mint 22 (Cinnamon)
The text was updated successfully, but these errors were encountered: