Closed lfom closed 2 years ago
Thanks for reporting, do you have any links from others who have had such problems with other applications?
@mirkobrombin Sorry, I think I wasn't clear: I meant I have seen other Bottle issues related to ld-linux.so.2, not any other apps. All other AppImages I run here do not have this problem.
Ah ok I got it. I was able to replicate the bug but I think it will take me some time to investigate.
I have updated the text to make it clear. It is a minor issue, just a bit annoying. I just felt I should report it anyway, specially after I found other issues related told-linux.so.2
while trying to see if the same issue was reported already. Thanks again.
Regards
I have updated the text to make it clear. It is a minor issue, just a bit annoying. I just felt I should report it anyway, specially after I found other issues related to
ld-linux.so.2
while trying to see if the same issue was reported already. Thanks again. Regards
I have an idea about the possible cause and will do some experiments in the day
I ran into the same error when downloading through my Firefox web browser on Fedora 34. I then used wget
when I wanted to open an issue, but this time got different results. I was able to load the AppImage, but then when I tried to create my Software Bottle, it hung on downloading DXVK for a long while (30min) where the Flatpak did it in about 20sec. Below I have the terminal output of what I was doing.
Hopefully this output helps.
I ran into the same error when downloading through my Firefox web browser on Fedora 34. I then used
wget
when I wanted to open an issue, but this time got different results. I was able to load the AppImage, but then when I tried to create my Software Bottle, it hung on downloading DXVK for a long while (30min) where the Flatpak did it in about 20sec. Below I have the terminal output of what I was doing.Hopefully this output helps.
This is a different issue. I just launched an update that fixes it, it will be available soon, thanks for the report.
I can confirm this has happened for me too, on Ubuntu 18.04. Launching it a second time works.
Sooner or later I will understand what causes it
Confirming that this happened to me on Ubuntu 20.04 as well. Also launching it a second time is a work around like everyone else.
I'm happy to try any fixes if it would be of assistance!
At the moment I still have no idea, I just know that the old method we used to build the Appimage did not cause this problem, I have to investigate the new one
@mirkobrombin I have found it today, it seems to be the same issue: https://github.com/AppImageCrafters/appimage-builder/issues/93#issuecomment-781729104
Bootles uses appimage-builder
? Is it the latest version? If it is, I can make some tests here and try to find a fix...
@mirkobrombin I have found it today, it seems to be the same issue: AppImageCrafters/appimage-builder#93 (comment)
Bootles uses
appimage-builder
? Is it the latest version? If it is, I can make some tests here and try to find a fix...
If you do that it would be very much appreciated 🙏
@mirkobrombin OK, I think I have found a way to fix the problem, but now Bottles does not run properly my installed applications anymore. I think something changed in the database of apps/bottles: after running the new version, the previous version does not open the WINE bottle anymore, and the new version cannot find the executables, both the AUR package and the official AppImage, so I think the problem is something added in the last two versions...
Anyway, building the AppImage using the shell script in the repo results in a much smaller AppImage and it runs just fine, while the AppImage built using the GitHub workflow commands result in the behavior reported in this issue (I guess this is what is used for releases).
The problem is that the AppImage should be actually multiarch, since it has binaries for both amd64 and i386. With the current AppImageBuilder.yml, there is no AppDir/opt/libc/lib/ld-linux.so.2. Changing it to an actual multiarch fixes the issue (I got tips from here, using the exclude rules - execept etc - also reduced 5MB from the size of the final file):
apt:
arch: [amd64, i386]
sources:
- sourceline: 'deb http://archive.ubuntu.com/ubuntu/ hirsute main restricted universe multiverse'
key_url: 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x871920D1991BC93C'
#- sourceline: 'deb [arch=i386] http://archive.ubuntu.com/ubuntu/ hirsute main restricted universe multiverse'
# key_url: 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x871920D1991BC93C'
@mirkobrombin OK, I think I have found a way to fix the problem, but now Bottles does not run properly my installed applications anymore. I think something changed in the database of apps/bottles: after running the new version, the previous version does not open the WINE bottle anymore, and the new version cannot find the executables, both the AUR package and the official AppImage, so I think the problem is something added in the last two versions...
Anyway, building the AppImage using the shell script in the repo results in a much smaller AppImage and it runs just fine, while the AppImage built using the GitHub workflow commands result in the behavior reported in this issue (I guess this is what is used for releases).
The problem is that the AppImage should be actually multiarch, since it has binaries for both amd64 and i386. With the current AppImageBuilder.yml, there is no AppDir/opt/libc/lib/ld-linux.so.2. Changing it to an actual multiarch fixes the issue (I got tips from here, using the exclude rules - execept etc - also reduced 5MB from the size of the final file):
apt: arch: [amd64, i386] sources: - sourceline: 'deb http://archive.ubuntu.com/ubuntu/ hirsute main restricted universe multiverse' key_url: 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x871920D1991BC93C' #- sourceline: 'deb [arch=i386] http://archive.ubuntu.com/ubuntu/ hirsute main restricted universe multiverse' # key_url: 'http://keyserver.ubuntu.com/pks/lookup?op=get&search=0x871920D1991BC93C'
Ya the script in the repository root is the old build system but il lack all the necessary dependencies, it is not for standalone appimages. The new one use the AppImage recipe.
So just need to set the multiarch to fix the problem? If so, I can make the fix and build the latest release asap
So just need to set the multiarch to fix the problem? If so, I can make the fix and build the latest release asap
It did here (tested on two machines).
Nice I’m launching a new build 😎
Seems to work but
/bin/sh: line 1: cabextract: command not found
Yaa another bug, also p7zip is missing, despite it is inside the Appimage
I commented on the commit, you do not need: https://github.com/bottlesdevs/Bottles/blob/1162aecf3f1923b3f5f2cffe7fba69a72d390315/AppImageBuilder.yml#L60-L61 maybe it is related. I built the AppImage on focal, and using hirsute repos.
I think not, the problem should be related to the bin
path pointing to the wrong directory
Testing the official app I also noticed that it seems that $PATH is not properly set.
(15:42:29) INFO Opening the file manager in the path …
Traceback (most recent call last):
File "/usr/share/bottles/bottles/widgets/program.py", line 159, in browse_program_folder
ManagerUtils.open_filemanager(
File "/usr/share/bottles/bottles/backend/manager_utils.py", line 52, in open_filemanager
command = f"xdg-open '{path}'"
UnboundLocalError: local variable 'path' referenced before assignment
Testing the official app I also noticed that it seems that $PATH is not properly set.
(15:42:29) INFO Opening the file manager in the path … Traceback (most recent call last): File "/usr/share/bottles/bottles/widgets/program.py", line 159, in browse_program_folder ManagerUtils.open_filemanager( File "/usr/share/bottles/bottles/backend/manager_utils.py", line 52, in open_filemanager command = f"xdg-open '{path}'" UnboundLocalError: local variable 'path' referenced before assignment
But this should be related to another problem
It looks like, just the problem related to the bottle.yml. I have checkout 2021.12.14-treviso-3, added the changes in AppImageBuilder.yml to fix Wayland and ld-linux.so.2 errors and it is working fine after I reverted bottle.yml to a backup copy. If you wanna check it, it can be downloaded here.
Keep giving me errors due to missing p7zip and cabextract. Seems to be working in Wayland but doesn't find the necessary binaries (that are just in the same dir :| )
Weird, no problems here installing dxvk-1.9.1, for instance (no p7zip installed in the machine):
(16:50:17) INFO Opening the file manager in the path …
(16:50:22) INFO Installing component: [dxvk-1.9.1].
(16:50:22) WARNING File [dxvk-1.9.1.tar.gz] already exists in temp, skipping.
(16:50:23) INFO DXVKs found:
- dxvk-1.9.2
- dxvk-1.9.1
(16:50:30) INFO Opening the file manager in the path …
I’m using Fedora, you?
@mirkobrombin Arch (Gnome 41 + Wayland) and Pop!_OS 21.10 (Gnome 40 + Wayland), no problems with either using my 2021-12-14-treviso-3 AppImage build with the two fixes.
@mirkobrombin Arch (Gnome 41 + Wayland) and Pop!_OS 21.10 (Gnome 40 + Wayland), no problems with either using my 2021-12-14-treviso-3 AppImage build with the two fixes.
Nice! Can you open a PR with these fixes?
@mirkobrombin You have added them to master already:
The only difference is that I removed those two lines from AppImageBuilder.yml: https://github.com/bottlesdevs/Bottles/issues/481#issuecomment-1002726641
I applied the changes to 2021-12-14-treviso3 because the newer versions broke the bottle I use.
Done, I'll release the next build so we can test it and see if it is actually fixed
Release updated: https://github.com/bottlesdevs/Bottles/releases/tag/2021.12.28-treviso
The silent crash on cold start seems to be solved, thanks! I'm going to close this to focus on the "missing cabextract
" problem https://github.com/bottlesdevs/Bottles/issues/833
Thanks @lfom for your contribution :smile:
@mirkobrombin You are more than welcome. I am glad I could help at least a little with the project. Regards
Describe the bug After Bottles hasn't been run for a while, it silently fails to launch. Starting it a second time works fine.
Installation
To Reproduce The problem happens if a new version is installed, after the computer is restarted or simply when Bottles hasn't been run for a long time (maybe the issue is related to disk cache/speed somehow?).
Expected behavior Bottles should launch every time it is started.
Screenshots N/A
Desktop (please complete the following information):
Additional context In the first launch from terminal, it shows:
Unable to read file: /tmp/.mount_bottleylJovr//opt/libc/lib/ld-linux.so.2
I have seen other Bottles issues related to
ld-linux.so.2
, using both AppImage and Flatpak, so maybe something needs to be fixed in the way app loads.Thanks for maintaining Bottles!