Logos 30+ Support about logoslinuxinstaller HOT 3 OPEN

Is there anything I can do to help here? I'm completely new to Logos, and would like to get it running on my computer. I'm a seasoned C++ programmer and know a lot about Linux internals (linking, shared libraries etc.). I don't have a lot of free time, but am willing to investigate stuff or try things out if you point me to things which you feel might help.

from logoslinuxinstaller.

Is there anything I can do to help here? I'm completely new to Logos, and would like to get it running on my computer. I'm a seasoned C++ programmer and know a lot about Linux internals (linking, shared libraries etc.). I don't have a lot of free time, but am willing to investigate stuff or try things out if you point me to things which you feel might help.

Hello @tbleher!

For the past while we have been praying that God would help us to get this issue resolved. Perhaps you are an answer to our prayers! We need folks particularly skilled in languages like C++ due to our heavy reliance on Wine. I would like to at least point you in some of the right directions to get you caught up to speed.

You can find the AppDB for Logos on Wine here:

https://appdb.winehq.org/objectManager.php?sClass=application&iId=771

Here is the Wine Gitlab:

https://gitlab.winehq.org/explore/groups

We have outstanding issues that none of us have had time to git bisect or other issues related to upstream. The main issues for us from the Wine side can be found here: https://github.com/ferion11/LogosLinuxInstaller/wiki#known-issues

• No media playback. CrossOver and Steam Proton are working on these issues upstream
• An Async crash. Upstream is aware of this issue; it is primarily due to a lack of error catching. (See ferion11/LogosLinuxInstaller#205 (comment))
• Printing fails to work. This needs bisected by us.
• The big kahuna is the menu bug. @jg00dman had been working on this, but it requires some programming skills beyond where @n8marti and I are.

These matter for us as they also affect which settings we use in our install script, sort of a give and take between the two.

I bring all this up to say that there are other issues that can help you get acquainted with the problems we are facing.

While I don't know as much as John does after he spent time digging into this, all I can do is mention what he had shared and I posted above.

From John:

The issue has to do with the new dependency for Two system DLLs:

icuuc.dll (this is the ICU "common" library)
icuin.dll (this is the ICU "i18n" library)

You can install them, but you need to install both the 32bit and the 64 bit versions for the installer to work due to an oddity in the way the installer checks for the libraries.

The problem is that's only part of the battle. Once installed you have a version of Logos which will only crash. I need to get that crash fixed before we move forward.

If you want to get involved with what free time you can spare us, please reach out to me on Matrix if you want to communicate more easily with the developers.

from logoslinuxinstaller.

Thanks @thw26 for all the pointers! I'm currently looking into wine to understand how to debug it better (I've used wine in the past, but only once debugged a problem there, and that was more than ten years ago). I'll try to see what I can find, but it will probably take a while.

from logoslinuxinstaller.