-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add Logos 30.0+ Support #219
Comments
How do we download v29 exactly? |
At this point the easiest way will be to use the Python rewrite: https://github.com/FaithLife-Community/LogosLinuxInstaller The best would be to wait for us to release alpha3 due to issues in alpha2, but you can run from source (requires Python 3.12; instructions in README) and it should be fairly easy to do so. |
Cool, sounds good. If the recommendation is to use said installer, should this repo be archived or at least the readme updated to reflect? |
It will be archived in the near future once we are satisfied with the state of the new Python app. Since it is still alpha, I can't yet archive this. Please see the write up I made for the workaround here: |
Thank you! That is a very helpful write-up! Do you also have a URL to install the previous version of Verbum? |
For Verbum, it should be a small modification. Here is the one-liner with no Zenity pop-ups:
|
I'm sure this won't necessarily be helpful, but I just got the update to Wine 9.2 and the update still errors out. Thanks! |
I am still getting the same error as well. I know I set the variable
however it is still using the newer MSI
|
Is that Can you try running this instead before installing?
|
that is what I did. The echo command validates that the variable has been set that is all. |
Besides saying you can use the new Python program as it should be able to handle this, I took a look through the code. I'm not seeing why this would happen on an initial survey. What you can do is change this line: To instead say:
And that should disable the script's pinging the RSS feed for the latest version of Logos and instead just use the latest. The reason I haven't recommended this before is that it requires editing the file, but it is a simple change. |
We have started discussing that error here: FaithLife-Community/LogosLinuxInstaller#74 I think it is the lack of support for Logos 30+ that you're seeing here. Best bet is to disable automatic updates. |
Be careful about upgrading Wine. I updated to wine 9.3. My logos installation wouldn't run after the upgrade. Thankfully, I was able to downgrade back to 9.2-1 and it ran perfectly |
That's the first I've heard that a 9.x binary will work. Perhaps we can get an AppImage of it still. |
Oh yeah, I've been using 9.2 for over two weeks and it works great. It won't upgrade to 30, but it runs excellent otherwise. That being said, I'm not using an appimage. I don't know if that is relevant for your decisions. |
We have released a new alpha version in the Python script that enables Logos 30+ access. It requires somewhere around at least Wine 9.10+ to run. Closing this issue. |
FaithLife released an update in Logos 30.0 that requires new DLLs.
STATUS
We are working on sorting this one out. We have an initial set of fixes but bumped into a secondary set of problems after the initial fix.
WORKAROUND
Install the last version of 29 and disable auto-updates.
The text was updated successfully, but these errors were encountered: