Linux version of Logos Bible Software
Comments
-
The installer script (i.e., LogosLinuxInstaller.sh) creates another script on install that is the launcher script (i.e., Logos.sh). You could read the launcher's template in the GitHub repo and that would let you see which files are deleted by the launcher's remove library catalog function and thus it would tell you how to remove the library catalog files.
To run the script is somewhat simple, but if you are new to Linux, which I presume based on your questions, you need to learn a few basic Linux commands and/or operations and procedures. Learning the command line interface (CLI) is a great way to learn Linux because most desktop actions are little more than fancy graphics laid on top of CLI commands.
First you need to download the script. You can do so either by downloading it from GitHub or by opening the raw file and copying and pasting it into your own file. If you open the file in GitHub, you can click the download button at the following link.
https://github.com/ferion11/LogosLinuxInstaller/blob/master/LogosLinuxInstaller.sh
Alternatively, you can run this in the CLI:
wget -O ~/Downloads/LogosLinuxInstaller.sh https://github.com/ferion11/LogosLinuxInstaller/blob/master/LogosLinuxInstaller.sh
This command, wget, does two things. First, it is going to download a file to your Downloads directory named LogosLinuxInstaller.sh. The ~ indicates you want it stored in your home directory. Making a guess here, your home directory is located at /home/douglas/. Your Downloads directory would be at /home/douglas/Downloads/. It is going to name the downloaded file LogosLinuxInstaller.sh. The file it is going to download is found at the given GitHub URL.
Once you download the file LogosLinuxInstaller.sh, then you must make it executable, whether by CLI or by using your mouse and DE's menu system. To use your mouse, you most likely need to right click the file in your file browser, open the settings menu for the file, and navigate to a permissions tab. You need to turn on executable or x mode bit in that menu system. To do so by CLI, you would run the following command:
chmod 700 ~/Downloads/LogosLinuxInstaller.sh
In Linux there are file owners and file groups and file permissions. This command changes (ch) a file's mode (mod) bits and it sets them to:
- file owner can read, write, and execute
- file group can neither read, write, nor execute
- everybody else can neither read, write, nor execute
Now that the file is downloaded to your computer and executable, you need to run it, but before you do so, you need one more program installed called a dialog program. Which dialog program you use depends on whether you want to install Logos through the CLI or through a GUI.
You need to install `dialog` or `whiptail` for a CLI install if your distro does not by default (and usually they install at least one), or you need to install `zenity` to get a GUI install.
If you are on Ubuntu, this would be done by running one of the following in the CLI:
- sudo apt install dialog
- sudo apt install whiptail
- sudo apt install zenity
Once the script is downloaded and made executable and you have a dialog program installed, you can now run the script. You run the script either by double clicking on it in your file browser if you installed zenity or by running it from the CLI. You can run it from the CLI by typing:
~/Downloads/LogosLinuxInstaller.sh
Once running, the script should be able to give you all the feedback you need to carry on. One of the first things you will encounter is that you need additional dependencies. In a future upgrade we plan to make the script install the dependencies for you, but for now, you must do so manually.
When you run the script, it will tell you what dependencies are missing if it can't find a particular command the script needs.
Once all dependencies are met, everything else you need should be given to you through the dialogs the script creates.
For more help, please join us either in Telegram or on Matrix.
0 -
Thank you for the detailed instructions. I hope they will benefit not only me, but others who need to install Logos on Linux. I also posted a question on Matrix (username dougmn) and got some good help from T.H. Wright.
I got it installed, and Logos opens. Now to get it working properly! I'll ask for help in Matrix.
0 -
Having a problem using the installer. I am only so versed in this. I ran the installer and it downloaded the msi file. But then it is saying that “installation failed. Not found.“ the file is definitely in both the downloads folder and then again in the LogosBible10 folder.
0 -
Hi Michael,
I feel your pain... Unfortunately, I don't know enough to help you. Those who do are usually pretty good at replying. Hang in there!
Paul
0 -
That’s why I use a Mac 😏
0 -
Have a new crash with latest update and Logos is no longer usable. See the issue below:
0 -
Perhaps best not to install the four WINE updates I was offered this morning...? From the 'Description' in Software Updater:JS said:Have a new crash with latest update and Logos is no longer usable. See the issue below:
Changes for wine-staging-amd64 versions:
Installed version: 8.15~focal-1
Available version: 8.16~focal-10 -
It doesn't work, I've tried a thousand times in every way and it's impossible.
And apologies, but statistics are always very biased, they don't say what it is.
I have been to hundreds of forums to install Logos on Linux, and I see that many people, not companies, are crying out for it.
I think Logos should divorce Microfoft, it's the only acceptable divorce in the canons.No funciona, lo he intentagdo mil veces de todas las maneras y es imposible.
Y disculpas, pero las estadisticas siempre son muy sesgadas, no dicen lo que es.
He estado en centenares de bolg para instalar Logos en Linux, y veo que muchas las personas, no empresas, que lo están pidiendo a gritos.
Pienso que Logos debería divorciarse de Microfoft, es el único divorcio aceptable en los cánones.0 -
NO FUNCIONA, SIMPLEMENTE NO FUNCIONA.
LOGOS DEBERIA DIVORCIARSE DE MICROFOST WINDOWS Y TENER A LINUX, AUNQUE FUERA A MODO DE AMANTE; PORQUE ES CIERTO QUE WINDOWS LE DA MUCHOS PERFUMES Y ANILLOS Y BANQUETES, PERO AL FINAL LE SUCEDERA LO DE ISAREL Y EL PROFETA OSEAS.
Saludos.
0 -
NO FUNCIONA, SIMPLEMENTE NO FUNCIONA.
LOGOS DEBERIA DIVORCIARSE DE MICROFOST WINDOWS Y TENER A LINUX, AUNQUE FUERA A MODO DE AMANTE; PORQUE ES CIERTO QUE WINDOWS LE DA MUCHOS PERFUMES Y ANILLOS Y BANQUETES, PERO AL FINAL LE SUCEDERA LO DE ISAREL Y EL PROFETA OSEAS.
Saludos.
Solo porque no tienes lo que tu quieres eso no te da derecho a usar la Palabra de Dios con semejante irreverencia. Y a GRITOS menos conseguirás lo que quieres. Ese comportamiento no es digno del evangelio.
DAL
0 -
Me disculpo por lo de los gritos.
No era mi intención, siempre olvido que escribir con mayúsculas se interpreta con estar gritando, y lo olvido, porque en mis 63 años es la tercera ocasión que escribo en un blog, no soy de invertir mi tiempo en ello, tampoco en las redes sociales.
Con relación a lo de La Palabra del Señor y El Evangelio, recomendaría hacer diferencia entre El Evangelio, las buenas nuevas de salvación, que es una gran parte de Las Sagradas Escrituras, del cual no hice uso ni mención en mi queja, y La Palabra Del Señor, de la cual si hice uso y no me disculpo, por qué?
Porque lo que expresé es una gran verdad y si usted no se ha dado cuenta o no quiere reconocerlo, Logos dejo de ser lo que se creía que era y lo que debería ser, un ministerio, sin avaricia, sin elitismo, sin comerciar con El Reino y todo lo concerniente a Él.
Y no estoy insinuando que todo lo ofrezcan gratis o sin rentabilidad, pero sí quiten un poco los ojos y el corazón en las cifras y los pongan en las necesidades de los hijos del Reino, eso sí Logos considera una institución cristiana.
Si gusta, podemos tener una conversación personal y le sustento lo que expreso.
Cristo está muy a las puertas, meditelo bien,
Un abrazo en el amor de Cristo.
Dr. Oscar Mauricio Escobar Porras.
0 -
Me disculpo por lo de los gritos.
No era mi intención, siempre olvido que escribir con mayúsculas se interpreta con estar gritando, y lo olvido, porque en mis 63 años es la tercera ocasión que escribo en un blog, no soy de invertir mi tiempo en ello, tampoco en las redes sociales.
Con relación a lo de La Palabra del Señor y El Evangelio, recomendaría hacer diferencia entre El Evangelio, las buenas nuevas de salvación, que es una gran parte de Las Sagradas Escrituras, del cual no hice uso ni mención en mi queja, y La Palabra Del Señor, de la cual si hice uso y no me disculpo, por qué?
Porque lo que expresé es una gran verdad y si usted no se ha dado cuenta o no quiere reconocerlo, Logos dejo de ser lo que se creía que era y lo que debería ser, un ministerio, sin avaricia, sin elitismo, sin comerciar con El Reino y todo lo concerniente a Él.
Y no estoy insinuando que todo lo ofrezcan gratis o sin rentabilidad, pero sí quiten un poco los ojos y el corazón en las cifras y los pongan en las necesidades de los hijos del Reino, eso sí Logos considera una institución cristiana.
Si gusta, podemos tener una conversación personal y le sustento lo que expreso.
Cristo está muy a las puertas, meditelo bien,
Un abrazo en el amor de Cristo.
Dr. Oscar Mauricio Escobar Porras.
0 -
Oscar Mauricio Escobar Porras Pongo primero traducción al inglés, y abajo lo que escribí en español:
It's too bad that there isn't a native version of Logos for Linux. In the mean time, in order to resolve your problem, I recommend that you join this conversation:
https://app.element.io/#/room/#logosbible:matrix.org
and explain to the brothers there what you have done, and the details of your computer system, and I think they can help you get Logos installed on your Linux system. That's the way it worked for me, and there was no other way. The resources that you can find on the internet are not up to date, but the brothers on element or matrix can help you.
Original en español:
Lástima que no hay versión de Logos nativo para Linux. Mientras, para resolver su problema, le recomiendo que acude a esta conversación:
https://app.element.io/#/room/#logosbible:matrix.org
Y explíqueles a los hermanos que están allí que ha hecho usted, y los detalles de su sistema de computación, y creo que le pueden ayudar a instalar Logos en su sistema Linux. Así fue para mí, y no hubo otra forma. Los recursos que se encuentran por internet no están actualizados, pero los hermanos en element o matrix le pueden ayudar.
0 -
I can no longer click a link to open it from the Logos Home page, Explore section. Is it just me, or are others facing this as well? Is there a work-around? I can right-click an item and see the link, but I can't find any way to copy it for pasting into a browser. I'm running Logos 10, ver. 25.2.56.
0 -
Paul Unger said:
I can no longer click a link to open it from the Logos Home page, Explore section. Is it just me, or are others facing this as well? Is there a work-around? I can right-click an item and see the link, but I can't find any way to copy it for pasting into a browser. I'm running Logos 10, ver. 25.2.56.
I think it is a regression yes, when I get a chance I'll look into it.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
I'm trying to install the latest Logos on an Ubuntu 23.10 system. The install seems to work. When I start Logos using the Logos.sh script, I get the initial splash window, and it seems to try to start a window for the program, and I hear the typical Logos start sound, but then the window where it seemed to try to start the program goes away. The indexer seems to work as well (the icon appears in the menubar at the top of the screen. There's a lot of output written to the terminal, so it's hard for me to discern what exactly is the problem.
I'm running Wine 8.18-staging.
What am I doing wrong, or need to do in order to get it to run properly?
Thank you for your help!
John
0 -
Try running:
./Logos.sh
--remove-library-catalog0 -
Thank you for the suggestion, Taylor. The same results were produced. I get the splash screen, the small preparing your library window, the small synchronizing window, then the logos program window which stays black, then goes away.
I'm guessing from the output that this could be the start of the crash:
011c:err:eventlog:ReportEventW L"Application: Logos.exe\n"
011c:err:eventlog:ReportEventW L"CoreCLR Version: 7.0.1023.36312\n"
011c:err:eventlog:ReportEventW L".NET Version: 7.0.10\n"
011c:err:eventlog:ReportEventW L"Description: The process was terminated due to an unhandled exception.\n"
011c:err:eventlog:ReportEventW L"Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.\n"Thank you,
John
0 -
I'm seeing this as well. After about a year of successfully running Logos on Fedora using https://github.com/ferion11/LogosLinuxInstaller the latest Logos software update has killed it. Even after a completely fresh reinstall, it throws the same error.
Prior to using Wine I was using Windows VM for nothing other than Logos, but after having to do two complete OS installs because the VMs got corrupted it was such a relief to finally get Logos running in Wine. I've been running Linux only for the last 15 years (software developer by trade), and every other software package I use has native Linux support. It's so frustrating that given there are so many open-source cross-platform options for developing good software Logos hasn't ported from a Windows-only .net solution.I've invested quite a bit of money into Logos resources because I found the original language study resources to be quite good... a bit better than the free alternatives like Bibletime and the other Sword library-based projects. But it's so frustrating to have to spend so much time and effort trying to get Logos to run... I'd rather be spending that time studying God's word and thinking on him, rather than getting frustrated with this kind of thing.
Is there really nothing that can be done about this?
There are lots of thriving open-source communities that are willingly spending their time developing bible software. If Logos really doesn't have the resources to provide a cross-platform offering. Then couldn't they let these open-source communities help?
If the backend engine can be compiled on other operating systems and released as a proprietary binary, maybe you could open-source the GUI? Developers in the community could then help port it over to a cross-platform GUI library.I realise there are licensing issues with the resources that are provided, and DRM concerns that need to be addressed. However wouldn't it be possible to provide some kind of API that gave access to the resources via Logos account login in a way that protected the DRM of the resources? In a similar way most open-source bible software is built on top of the sword library and the resources they provide... could Logos provide a library that would allow developers to create plugins to existing open-source projects that made use of Logos resources.
Just a thought.
Anyway, for the moment with great sadness, I think I'm going to have to go back to other bible software that works on Linux.0 -
I am curious David which VM you were running? I have been using Qemu/KVM for years with no issue at all, including passing thorough a GPU from a spare slot to get near native video performance using looking-glass. I would recommend you dig into it if you have not tried that rather than give up on Logos.
I would love to see a plugin system for Logos, or even open sourcing parts of the client with a sufficiently restrictive license, imagine the number of people that could considerably contribute to the software.
Welcome to the forum btw!
0 -
Hi Kevin, thanks for the reply.
To start with I used VirtualBox for a while and then there was some Windows/Linux/Logos update that killed it. I can't remember exactly what triggered it but come to think of it now I went through a couple of installs there. After that, I tried Gnome Boxes which is a GUI wrapper on top of QEMU which made the setup quite easy, although no as configurable as VirtualBox. Again I can't remember exactly what triggered the break, but seem to remember Windows 11 wouldn't boot and I ended up with a black screen of death.
I've not tried raw QEMU thanks for the suggestion. However it's not that I don't know how to get Logos software running under a VM, I'm sure I could get something running again with the VM route. It's just the hassle, it feels like a house of cards. I've got to go buy another Windows license which I don't need for anything other than Logos, download the Windows ISO, install Windows, Mess with the Windows registry and boot image because Windows 11 doesn't like running inside a VM, reset my Windows Live password because I've not used it in a few years and forgotten it, then finally install Logos. Doing all this knowing that at some point I've got to do it all again because a Linux kernel update will break something or Windows will get an update that breaks it.
By far the simplest solution I've found so far is the Wine solution provided by ferion11: https://github.com/ferion11/LogosLinuxInstaller which handles all the config for you. However, it's just not the same as being able to do a "sudo dnf install bibletime" and within a couple of minutes get a working install which covers all my basic day-to-day needs. Granted not quite as well as Logos, but if I need to dig into something a bit more I can pull the paper versions of my Lexicons/grammar off the bookshelf next to me, or still use the web version or the mobile version (if I've got 4G signal to keep the DRM checks happy, which I've often not).
I think what it comes down to is I don't have 2-3 days to work out how to get Logos working again right now. Just need some bible software that works on my desktop machine so I can do some study. At some point I might have those spare 2-3 days to get something up and running again, but just not now.
This thread has been running for 14 years now and as far as I can see we are still no further to an official solution.
It's a little disheartening.0 -
Just another thought. Maybe someone could put together a Docker image that provided a wine based containerised solution where the core Logos software and wine is baked into the image and the catalogue is on a docker volume. It wouldn't give the absolute latest version of the Logos software... but I'd take a stable setup over an almost daily churn of software updates for which there isn't much noticeable change.
0 -
I'm getting so tired of Bill Gates business Plan of updating my computer and making it do things I never asked it to do. And his love for the ways of the antichrist I do not care to subsidize.
0 -
Rick Ratzlaff said:
I'm getting so tired of Bill Gates business Plan of updating my computer and making it do things I never asked it to do. And his love for the ways of the antichrist I do not care to subsidize.
Come on ... I'm getting so tired of coming on the Logos forums and reading judgmental/slanderous comments like calling someone's way "antichrist."
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Rick Ratzlaff said:
I'm getting so tired of Bill Gates business Plan of updating my computer and making it do things I never asked it to do. And his love for the ways of the antichrist I do not care to subsidize.
That's why I switched to Mac. It runs Logos just fine.
0 -
I'm glad to see I'm not alone in trying to get Logos running on Linux.
I have been using Garuda Linux Dragonized Edition.
I couldn't get Logos to run in Bottles. I was able to install and set it up in WINE, but when I went to open the app, the windows wouldn't render and would just crash.
I tried adding it to Steam and using the Proton Experimental branch to see if that would work, nope.
I also tried Crossover to no avail
However!!! I got it to run through Lutris!
I had to create an instance for the program, and set it for windows 10. When I went to run the installer it didn't really work.
So the created instance didn't have an executable listed to run, and I went and selected my previous install of Logos, and its running. It is a bit laggy, but I'm hoping that is just because of the indexing.0 -
The problem in recent updates is that Logos checks to see if you're running a supported version of Windows, ie 10 or 11. That's what's crashing it.
I've got a working version using the snap here: https://snapcraft.io/logos10-unofficial
The snap currently keeps Logos from going to version 30 which is necessary for now.
Installation is easy. Just execute the snap command exactly as it appears. When doing this, Logos initially came up with a black window, which I realized was the login window, so if that happens, just start entering your email.
0 -
We are working on fixing the script because of the need to be on Windows 11. This is currently an upstream issue with Wine and we may need more development even after Windows 11 becomes available.
0 -
Thank you so much!
I'm planning on switching to Linux after the Christmas season is done. I didn't want to swap my main machine with all the church services coming up. I was wondering if I would get locked in to Garuda. I tried the distro, because I figured the group who would be most keen in getting windows programs to run on Linux is gamers.
Having this in snap opens up a lot of options.0 -
Wow. It looks like this is more important that I thot. My gut feeling (100) is that Windows is going to evolve even more to the World Order each day. We can count on it. An alternative is going to be more important. My bet is for every one on this form there are at least a hundred (100) who would agree, and hundreds like me that are too old to figure out how to switch. Opening the door to Linux would provide real security to the Word. Thank you all for your input.
0
