-
Notifications
You must be signed in to change notification settings - Fork 265
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
Installation options not working on Ubuntu (23.10) Mantic #632
Comments
Confirmed. Same behavior. I was able to install the Lite app, but I do like the full app. I have been using it for years. |
Can confirm, Kubuntu (Ubuntu) 23.10. |
Can confirm the issue with the PPA on a fresh install of Ubuntu 23.10. I was able to install the .deb. Initially, installation failed. However, after running |
FWIW the deb worked for me today, so maybe I had some prereqs installed that others don't have. I did try the PPA first which didn't work, and that was a few weeks ago, so I don't remember what I tried in between then and now that might have affected whether it works. |
Same on 24.04. |
I'm seeing the same error on 23.10. I uninstalled appimagelauncher two days ago for unrelated reasons, and today I tried to reinstall it, unsuccessfully. |
Same issue on my newly installed Ubuntu. System Details ReportReport details
Hardware Information:
Software Information:
|
There are no installation packages for 24.04, 23.10, or 23.04 in the stable PPA, since the last package build was about 2 years ago. The most recent Ubuntu version supported is 22.10. Presumably if a new release was to be declared, then suitable packages could be compiled. |
Confirm same issue exists on Linux Mint 22 Cinnamon. Oddly enough, AppImageLauncher used to work. I don't know exactly where it broke, but it it was when I updated to Mint 22 from Mint 21. I think during that update it removed the version of AppImageLauncher that was installed previously (from the PPA). Maybe libcurl3 was removed between 21 and 22? I don't know how I could find out if that is the case. In any case, AppImageLauncher disppeared from my system, and now neither the PPA installation nor the .deb installation work. PPA for known reasons, .deb returns the error about libcurl3 not being available. If I can provide any logs or if anyone wants me to try something to diagnose let me know. |
Pre-submit checks
Describe the bug
I did not manage to install the AppImageLauncher. Not via PPA, nor via .deb file.
PPA
Installing via PPA, according to the instructions on the wiki here:
https://github.com/TheAssassin/AppImageLauncher/wiki/Install-on-Ubuntu-or-Debian#use-the-ppas
Leads to this result:
Deb
Installing following instructions here:
https://github.com/TheAssassin/AppImageLauncher/wiki/Install-on-Ubuntu-or-Debian#installing-directly-from-github
Trying to install the missing dependencies I see:
Expected behavior
I have installed the AppImageLauncher previously, on a different system. For this I followed the steps for installation via PPA on the wiki and it "just worked".
Now it does not install.
Steps to reproduce the issue
See the commands I input previously.
Screenshots
Distribution and desktop environment
Installed AppImageLauncher version
I tried to install via the PPA.
Also tried to install this one:
appimagelauncher_2.2.0-travis995.0f91801.xenial_amd64.deb
List of AppImages you tried
Additional context
I suspect this is the result of me being on Ubuntu Mantic, and the AppImageLauncher not being ready for this yet.
I think this is the cause of the issue because of this line in the output for the PPA attempt:
E: The repository 'https://ppa.launchpadcontent.net/appimagelauncher-team/stable/ubuntu mantic Release' does not have a Release file.
And this is confirmed by "Mantic" missing from the list here:
https://launchpad.net/~appimagelauncher-team/+archive/ubuntu/stable
The installation via .deb suggests that libcurl3 has been replaced with libcurl4. I suspect that you should update AppImageLauncher to use libcurl4 instead.
I see the PPA problem was already flagged months ago, albeit in a rude manner:
#616
I understand you do not want to work with issues like that, but the problem they point out does exist. For me, this application is now unusable.
I hope this issue is formatted well enough that you will take it into consideration. I really like the appimage workflow you offer. But for now I will have to live without it.
The text was updated successfully, but these errors were encountered: