-
Notifications
You must be signed in to change notification settings - Fork 69
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
bauh crashes with empty appimage url #207
Comments
Hi @Flash1232 , that's a bug for sure. What application were you trying to install ? |
It is a Joplin AppImage (v2.4.12 installed, should be upgraded to v2.5.12) |
@Flash1232 it is a bug associated with the backend script responsible for mapping the AppImage database (it is not checking if the release URL is none). The fix has been applied and in a few hours the AppImage database should be updated. I've also provided added some handling on the client side (bauh) to avoid this sort of issues: You can install the staging branch through AUR (bauh-staging) for testing. I suggest to reinstall this AppImage in 3 or 4 hours and use the staging branch to see if the issue has been fixed. |
Thanks for the feedback and quick fix! |
EDIT: After trying again with the OLD image this happened: Traceback (most recent call last):
File "/usr/lib/python3.9/site-packages/bauh/view/qt/thread.py", line 523, in run
success = bool(self.manager.upgrade(requirements, root_password, self))
File "/usr/lib/python3.9/site-packages/bauh/view/core/controller.py", line 288, in upgrade
res = man.upgrade(man_reqs, root_password, handler)
File "/usr/lib/python3.9/site-packages/bauh/gems/appimage/controller.py", line 366, in upgrade
if not self.install(req.pkg, root_password, None, watcher).success:
File "/usr/lib/python3.9/site-packages/bauh/gems/appimage/controller.py", line 509, in install
downloaded, file_name = True, pkg.local_file_path.split('/')[-1]
AttributeError: 'NoneType' object has no attribute 'split'
Fatal Python error: Aborted
Current thread 0x00007f47beffd640 (most recent call first):
<no Python frame>
Thread 0x00007f47dde7c640 (most recent call first):
File "/usr/lib/python3.9/site-packages/bauh/view/qt/thread.py", line 822 in run
Thread 0x00007f47f5f4d640 (most recent call first):
File "/usr/lib/python3.9/site-packages/bauh/view/qt/thread.py", line 822 in run
Thread 0x00007f4805596640 (most recent call first):
File "/usr/lib/python3.9/site-packages/bauh/view/util/cache.py", line 96 in run
File "/usr/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/usr/lib/python3.9/threading.py", line 930 in _bootstrap
Thread 0x00007f480fd40740 (most recent call first):
File "/usr/lib/python3.9/site-packages/bauh/app.py", line 54 in main
File "/usr/bin/bauh", line 33 in <module>
[1] 555760 abort (core dumped) bauh --logs |
It seems the first issue you have pointed allowed the second to happen. In other words: bauh failed to download the image, and it seems the previous installed file was erased (then the second issue happened). I'm going to debug this scenario. About your question related to selecting packages to upgrade: there is no button to "select/unselect all", but bauh just upgrades what's been currently displayed on the table (WYSWYG). So just filter the package you want to upgrade by its name. |
@Flash1232 , last bug discussed is fixed on the staging branch: 65df765 (already available in AUR) I suggest disabling multi-threaded download for now since it is failing to download some AppImages from GitHub. |
Sorry for the delayed answer, I appreciate your thorough explanations and quick response! :)
That's great to know! I was unable to reproduce any bugs with the current staging branch so I think the issue is well resolved. Thank you again! |
Before opening a new issue
Install the staging branch and check if the unexpected behavior is happening there as well.
If you are on ArchLinux-based distro, you can install it through AUR (bauh-staging). Otherwise, you have
to clone the repository and install it with pip:
Describe the bug
App crashes when AppImage url is suddenly empty (no idea how that could happen).
Software Environment
bauh version: 0.9.21-staging
O.S: 5.10.70-1-MANJARO
Python version: v3.9.7
Installation method: pacman
P.S: these instructions and the template must be respected, otherwise your issue will be closed.
I've opened a PR with a workaround that solves the issue for me, although it is not clear to me how the underlying issue came to be in the first place. Maybe there is a better solution for this...
The text was updated successfully, but these errors were encountered: