Linux Mint installation failed with Proton and v30 also fails with appimage about logoslinuxinstaller HOT 31 CLOSED

You're welcome. We hope to have backup and restore options built in by beta. That would presumably be how you could upgrade in the future without having to redownload all your resources (or you could always manually copy the relevant folders elsewhere before upgrading, then move them back afterwards, if you're industrious to find out or ask where they are). And at that point it will install proper .desktop files, as well, and you'll be able to delete the workaround.

from logoslinuxinstaller.

The scaling issue i could resolve. Logos offers to set the scaling over the three dots menu on bottom left.

But performance is not the best. I guess proton would be better, due i can game also with it so i would love to get it working wiht proton.

from logoslinuxinstaller.

I tried to install Logos with the older Skript from the old repo which failed completely. The Logos installer says windows needs to be updated. I then tried tmanuall ylink the prodon dir but it then only found win64 and not winserver.

This is #22, which is why you could install Logos 29.

You should be able to get a desktop shortcut by running the app and either selecting the shortcut creation button or running the binary with the -s option.

@n8marti, any thoughts on the other issue?

from logoslinuxinstaller.

A couple of thoughts:

• I wish I knew why, but somehow the terminal wrapping goes haywire if there's an exception while running the terminal-based script.
• The script is written in Python 3.12, and that byteorder parameter was given a default setting as 'big' in 3.11. So you're using a python version <3.11, which is probably why you got the TypeError in the first run you show.
• Regarding the NoneType error for release = release.lstrip(), it's hard to sort out because you're running the script from our main branch, which is changing frequently right now. But I think it's failing on the wine.get_mscoree_winebranch function. If you have it, can you upload the log file at ~/.local/state/Logos_on_Linux/install.log? That might give us some more useful debugging details.
• Is it possible that your Proton installation is only 32-bit? The function mentioned above looks specifically for the 64-bit mscoree.dll file among the wine libraries.
• Lastly, you're probably better off downloading and running binary on the Releases page, because it includes all the dependencies already. Or, if you really want to run the script, switch to the v4.0.0-alpha.1 tag in the "branches" menu so that we know for certain which version of the script you're running.
• If you do run the script, you would be better off creating a virtual environment, ensuring that Python 3.12 is installed in it, then running pip install -r requirements.txt to ensure the best outcome. I have a lightly-tested explanation of this in the scripts folder of the branch altdev, which is not yet merged in.

from logoslinuxinstaller.

By "explanation" in the last bullet point above, I mean "two scripts that install Python 3.12 and set up the virtual environment on an Ubuntu-based system". I think your Mint installation should be compatible...

from logoslinuxinstaller.

Here is the log. Its pretty long. I guessing some log entries where from the bash skript.
install.log

I was using python 3.10 and not 3.12 which was preinstalled from the distro. I already created the venv and did it with the main branch but there wasn't mentioned the version.

But i rather try the binary first if it works. This is the output of the ls -a command. So proton is surely installed with 64-bit:

ls -la ~/.steam/debian-installation/steamapps/common/Proton*/dist/bin
insgesamt 768
drwxr-xr-x 2 joshua joshua   4096 Okt 19 12:46 .
drwxr-xr-x 6 joshua joshua   4096 Dez 27 01:23 ..
-rwxr-xr-x 1 joshua joshua   2101 Okt 19 12:46 msidb
-rwxr-xr-x 1 joshua joshua  15560 Okt 19 12:46 wine
-rwxr-xr-x 1 joshua joshua  16712 Okt 19 12:46 wine64
-rwxr-xr-x 1 joshua joshua  18488 Okt 19 12:46 wine64-preloader
-rwxr-xr-x 1 joshua joshua  17664 Okt 19 12:46 wine-preloader
-rwxr-xr-x 1 joshua joshua 695040 Okt 19 12:46 wineserver

from logoslinuxinstaller.

Hmm the binary seems not to find the wine binary if i passing the custom folder to the script:

It provides only the option using the AppImage and not my Proton installation by passing the custom path.

The binary provides me with an better error message in the logs:

2024-01-08 15:23:16 INFO: Removing binary: /home/joshua/.steam/debian-installation/steamapps/common/Proton 8.0/dist/bin/wine64 because: Can't use Stable release
2024-01-08 15:23:21 DEBUG: config.FLPRODUCT: Logos
2024-01-08 15:23:21 DEBUG: config.FLPRODUCTi: logos4
2024-01-08 15:23:21 DEBUG: config.LOGOS_VERSION: 29.1.0.0022
2024-01-08 15:23:21 DEBUG: config.INSTALLDIR: /home/joshua/LogosBible10
2024-01-08 15:23:21 DEBUG: config.APPDIR: /home/joshua/LogosBible10/data
2024-01-08 15:23:21 DEBUG: config.APPDIR_BINDIR: /home/joshua/LogosBible10/data/bin
2024-01-08 15:23:21 INFO: Removing binary: /home/joshua/.steam/debian-installation/steamapps/common/Proton 8.0/dist/bin/wine64 because: Can't use Stable release

Would be nice to show such error in the GUI.

So is only proton experminental supported yet?

I will try to change the steam settings to use experimental version instead of 8.0 and try again.

But congratulation, the binary is much more convient.

from logoslinuxinstaller.

Proton 7.0 is supported. Wine 8.0 is broken, and thus Proton 8.0 is broken.

Wine 8.1+ fixed whatever the issue in 8.0 was. You might be able to use GE.

For that matter, Wine 9.0 RCs have been broken last we checked, so at this rate, so will Proton 9.0.

from logoslinuxinstaller.

Yeah Proton Experimental seemed also not to work...

Says also Can't use Stable release. Will you fix it at a lather date? So it rather recommended to stay with the Appimage Version? Proton 7 is pretty old. Or is the Performance better with Proton 7?

from logoslinuxinstaller.

Says also Can't use Stable release. Will you fix it at a lather date?

This is an issue with Wine. With Wine 8.16+, we can use devel instead of staging. With time we will be able to use stable.

So it rather recommended to stay with the Appimage Version?

This is our method for a stable(ish) install across all distros.

Proton 7 is pretty old. Or is the Performance better with Proton 7?

I agree. I've wanted to test Proton GE builds but haven't had time. If you have time to test, I encourage you to do so! I'd love to be able to test the latest Valve improvements for our use case.

from logoslinuxinstaller.

How to i get Proton GE? Steam itselfs does not have that option.

I think i leave it with the current installation which seems have work also with 3.10 python and appimage.

But creation of the shortcut seems not working. I ran the python script with the option --shortcut in the terminal but it opens the script with the pages to choose run logos, run indexing, etc. And does not create anything. This is really a hussle to always need to change to the folder, launch the virtual env and then start the app. Due the binary i downloaded does not provide an option at all to launch it due it seems not to reconise the existing installation.

from logoslinuxinstaller.

Also i had a strange error: I tried to ran the binary in GUI mode (double clicking) and then install. In the log it has correctly an critical error that the Installation already exists. But i got logged out entireley as the whole login broke. Maybe another issue that need to be checked.

from logoslinuxinstaller.

I think in the next few days we'll be releasing v4.0.0-alpha.2 (right, @thw26?), which brings in a lot of fixes. I would suggest waiting for that before doing any testing. Otherwise, using the alpha.1 release and the AppImage with Logos v29 should work best if you have to reinstall again right away.

from logoslinuxinstaller.

Currently i have a working installation i only want to have a shortcut to simplyfiy opening the App ;) - i did it with checkout of the main branch last night as descriped and v29 using appimage. Just wanted first proton as you wrote in the doku (which may be outdated, that proton offes better performance).

Do not want to reinstall everything and redownload my libary which is about 5GB. But can't wait for upcoming fixes, especially version 30. Hopefully it will be possible to upgrade instead of reinstall. Or at least be a way to transfer the library over to the new installation.

from logoslinuxinstaller.

Hmm it seems to have created a shortcut without any icon in .local/share/applications/Logos with command wine C:/users/joshua/AppData/Local/Logos/System/Logos.exe but that seems not been working. Timing is last night when app was installed last night.

from logoslinuxinstaller.

The easiest solution is probably to edit that file so that it has the correct info for your working installation. Can you upload it?

from logoslinuxinstaller.

You'll probably have the icon file in your Downloads folder as logos4-128-icon.png. And you'll want to make sure the Exec line is correct

from logoslinuxinstaller.

Yes what would be the correct exec line. As reverse engineering it seems to run following two commands if i choose Run Logos:

/home/joshua/LogosBible10/data/bin/wineserver None -w
/home/joshua/LogosBible10/data/bin/wine64 /home/joshua/LogosBible10/data/wine64_bottle/drive_c/users/joshua/AppData/Local/Logos/Logos.exe

If i try to chain it in the exec as following i see the startup sceen but not the app itself. What does the python script do differently?:

/home/joshua/LogosBible10/data/bin/wineserver None -w  & /home/joshua/LogosBible10/data/bin/wine64 /home/joshua/LogosBible10/data/wine64_bottle/drive_c/users/joshua/AppData/Local/Logos/Logos.exe

from logoslinuxinstaller.

Logos.cinnamon-generated.desktop.tar.gz

from logoslinuxinstaller.

The packaged binary, which includes the script and all its dependencies, sets the correct environment variables before launching the app. So your Exec line needs to reference the script or binary. So we first need to determine which one of those to use and where it is. Can you tell me what's in $HOME/LogosBible10 with:

$ find ~/LogosBible10 -maxdepth 3

from logoslinuxinstaller.

/home/joshua/LogosBible10
/home/joshua/LogosBible10/data
/home/joshua/LogosBible10/data/Logos_v29.1.0.0022-x64.msi
/home/joshua/LogosBible10/data/bin
/home/joshua/LogosBible10/data/bin/wine64
/home/joshua/LogosBible10/data/bin/selected_wine.AppImage
/home/joshua/LogosBible10/data/bin/wineserver
/home/joshua/LogosBible10/data/bin/wine
/home/joshua/LogosBible10/data/bin/winetricks
/home/joshua/LogosBible10/data/bin/wine-devel_8.19-x86_64.AppImage
/home/joshua/LogosBible10/data/wine64_bottle
/home/joshua/LogosBible10/data/wine64_bottle/user.reg
/home/joshua/LogosBible10/data/wine64_bottle/userdef.reg
/home/joshua/LogosBible10/data/wine64_bottle/system.reg
/home/joshua/LogosBible10/data/wine64_bottle/dosdevices
/home/joshua/LogosBible10/data/wine64_bottle/.update-timestamp
/home/joshua/LogosBible10/data/wine64_bottle/drive_c
/home/joshua/LogosBible10/data/wine64_bottle/winetricks.log

Here the output. This is the installation i did with the python script directly and not the packaged binary.

from logoslinuxinstaller.

Thanks. And can you tell me if your working installation was done with the binary or with the script? If you're not sure, you could try to find both with:

$ find ~ -name 'LogosLinuxInstaller*'

Edit: Now I see that you used the script. So we need to know where it is located. Using that find command will work fine.

from logoslinuxinstaller.

I downloaded the repo there:

/home/joshua/Dokumente/git/LogosLinuxInstaller
/home/joshua/Dokumente/git/LogosLinuxInstaller/LogosLinuxInstaller.spec
/home/joshua/Dokumente/git/LogosLinuxInstaller/LogosLinuxInstaller.py

I did following to install logos:

$ python3 -m venv env # create a virtual env folder called "env"
$ . env/bin/activate # activates the env
(env) $ pip3 install -r requirements.txt
(env) $ ./LogosLinuxInstaller.py # run the script

(As descibed above needed to install python3-tk and the distro package which was missing in requirements.txt) (Dependencies i installed with the command from the older script already)

Currently i need to do following to launch logos:

cd ~/Dokumente/git/LogosLinuxInstaller/
. env/bin/activate
./LogosLinuxInstaller.py

There it opens a menu with 15 entries where i can choose "Run Logos" and then the App starts.

from logoslinuxinstaller.

try this desktop file by putting it in ~/.local/share/applications and removing the '.txt' from the end of the name.
Logos-v4.0.0-alpha.1-joshua.desktop.txt

from logoslinuxinstaller.

If "Logos" shows up twice in your app menu, this will has the Comment line "Logos (4.0.0-alpha.1 hack)".

from logoslinuxinstaller.

Thank you for the updated file. it seems not working properly, I tnot open anything and if i runn the command in terminal i get followign error:

/home/joshua/LogosBible10/data/wine64_bottle/drive_c/users/joshua/AppData/Local/Logos/Logos.exe: 1: MZ����@���: not found
/home/joshua/LogosBible10/data/wine64_bottle/drive_c/users/joshua/AppData/Local/Logos/Logos.exe: 1: Syntax error: Unterminated quoted string

For debugging purpose. Here my config file which i can open with edit config:

{
    "APPDIR": "/home/joshua/LogosBible10/data",
    "APPDIR_BINDIR": "/home/joshua/LogosBible10/data/bin",
    "APPIMAGE_LINK_SELECTION_NAME": "selected_wine.AppImage",
    "BACKUPDIR": null,
    "FLPRODUCT": "Logos",
    "FLPRODUCTi": "logos4",
    "INSTALLDIR": "/home/joshua/LogosBible10",
    "LOGOS_DIR": null,
    "LOGOS_EXE": "/home/joshua/LogosBible10/data/wine64_bottle/drive_c/users/joshua/AppData/Local/Logos/Logos.exe",
    "LOGOS_EXECUTABLE": "Logos_v29.1.0.0022-x64.msi",
    "LOGS": null,
    "TARGETVERSION": "10",
    "WINE64_APPIMAGE_FULL_FILENAME": "wine-devel_8.19-x86_64.AppImage",
    "WINE64_APPIMAGE_FULL_URL": "https://github.com/FaithLife-Community/LogosLinuxInstaller/releases/download/wine-devel-8.19/wine-devel_8.19-x86_64.AppImage",
    "WINEBIN_CODE": "AppImage",
    "WINECMD_ENCODING": "850",
    "WINEPREFIX": "/home/joshua/LogosBible10/data/wine64_bottle",
    "WINESERVER_EXE": "/home/joshua/LogosBible10/data/bin/wineserver",
    "WINETRICKSBIN": "/home/joshua/LogosBible10/data/bin/winetricks",
    "WINE_EXE": "/home/joshua/LogosBible10/data/bin/wine64"
}

from logoslinuxinstaller.

sorry, I had missed part of the Exec line. Try this version:
Logos-v4.0.0-alpha.1-joshua.desktop.txt
It works for me (except the icon) when I substitute my own username in place of yours.

from logoslinuxinstaller.

Thanks i did found out too that the wine64 part was missing.
This start now Logos sucessfully.

Last question. Somethimes it opens a pop up that the update failed. I guess this is due it want to update to V30 and that won't work. Is it possible to disable the update check in logos. Where i can do that? Did not find the option:

from logoslinuxinstaller.

https://matrix-client.matrix.org/_matrix/media/v3/download/t2bot.io/f21a1ecf8da08c60a15e67923dda742a1a55729d1742123923635437568

In Logos' settings there's an option to turn off "Automatically start downloads" (yours might be in German?). This will prevent automatic app updates from downloading, as well as resource updates. But I think you can go to individual resources in the Library and download them one at a time. I'm not so sure about resource updates, though.

from logoslinuxinstaller.

You should be able to get a desktop shortcut by running the app and either selecting the shortcut creation button or running the binary with the -s option.

@thw26 The --shortcut option exists in v4.0.0-alpha.1, but I don't think it was actually implemented yet. It will be when #40 is merged, though, so I assume that it will be included in v4.0.0-alpha.2

from logoslinuxinstaller.

Thank you found the option. Yeah the tooltip mentions that also resources won't be updated. But there is another option download new books which says it will download new books automatically. So i will see.

Thank you again for your time and support. Glad i have now a working Logos installation on my Linux client. Feel free to close this issue and open seperate ones for keep track of other things. And if you need to test further things, don^t hesitate to write. I am open to test again later maybe the upgrade from v29 to v30 if you have fixed it. God bless you!

from logoslinuxinstaller.