Linux version of Logos Bible Software

Once again, I am pushing foward for a Linux version of Logos, a lot of user are using Linux, and we have been struggling to break away from Windows, but Logos has always been the single software that require us to either dual boot or run a virtual machine with Linux OS.

Anyone share the same view?

Find more posts tagged with

Comments

https://community.logos.com/discussion/comment/1073189#Comment_1073189

I think that looks normal.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073182#Comment_1073182

My workaround is that I copied all files in the directory "/opt/wasta-wine/lib/wine/" with the extension "*.so-wasta" into the same directory with the new extension "*.so".

Dominik, so the files still had the .so-wasta extension name after the install of wasta-wine finished? The postinst "should have renamed them" so I will have to see if others have that issue.

Everyone, to re-run the postinst script to see if it would automatically rename the files, I think the easiest thing to do is this:

sudo dpkg-reconfigure wasta-wine

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073181#Comment_1073181

BUT: It doesn't start. Wasta-Wine is set to xp.

Dirk, please try to start Logos from the terminal and see if it gives more clues:

WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073212#Comment_1073212

Hi Rik

I tried that too. Logos started and told me .net 4.7.2 is required. "Do you want to install it now..."?

I have reset my system with rsync now and will retry it in the evening. While installing .net there were some irritating messages like "failed to parse...". I could upload the whole terminal output next time, if you want. Maybe you can see the problem.

Greetings

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073238#Comment_1073238

I tried that too. Logos started and told me .net 4.7.2 is required. "Do you want to install it now..."?

I have reset my system with rsync now and will retry it in the evening. While installing .net there were some irritating messages like "failed to parse...". I could upload the whole terminal output next time, if you want. Maybe you can see the problem.

You may want to first save your Logos/Data, Logos/Documents, and Logos/Users from your current ~/.wine-logos install. Then when running wasta-logos-setup choose to delete and re-install the wine prefix (this ~/.wine-logos folder). That way you would have a clean attempt that may show the errors more clearly, or may even get you all the way to a working install.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073211#Comment_1073211

... Dominik, so the files still had the .so-wasta extension name after the install of wasta-wine finished? The postinst "should have renamed them" so I will have to see if others have that issue....

Yes, the files still had the "*.so-wasta" extension after installation.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073260#Comment_1073260

Rik:

Attached is the terminal output of Logos with recent changes installed.

Wine gives Program Error soon after Logos is launched.

Thanks for all you are doing to get Logos to run on Linux.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073238#Comment_1073238

Do you have cabextract installed? If not, that will be one of the reasons it fails. Winetricks needs cabextract in order to install .Net. However, you're trying to run it on Arch right? It was added as a dependency in the Wasta installer, but as a dependency for Ubuntu. if you're trying to get this working on Arch, then you would need to install it on your own.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073368#Comment_1073368

Yeah, it's working now. And it's relatively fast on my old 4GBRAM-Machine. Thank you so much. The only thing is, that I must launch it in the terminal mith:

WINEPREFIX=$HOME/.wine-logos/ /opt/wasta-wine/bin/wine $HOME/.wine-logos/drive_c/users/$USER/Local\ Settings/Application\ Data/Logos/Logos.exe LC_ALL=C

After clicking on the official starter nothing happens.Even if I copy this command and overwrite the command of the starter nothing happens.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073391#Comment_1073391

Dirk, glad you got it working! You could run wasta-logos-setup again (do NOT create a new prefix) and it should repair your launcher. Alternatively, you can manually adjust it. Here is what my launcher has:

Exec=env WINEPREFIX="/home/rik/.wine-logos" /opt/wasta-wine/bin/wine C:\\\\windows\\\\command\\\\start.exe /Unix /home/rik/.wine-logos/dosdevices/c:/users/rik/Start\\ Menu/Programs/Logos\\ Bible\\ Software.lnk LC_ALL=C

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073346#Comment_1073346

      Attached is the terminal output of Logos with recent changes installed.

      Wine gives Program Error soon after Logos is launched.

      Thanks for all you are doing to get Logos to run on Linux.

Al, sorry I don't see anything apparent there. There are a LOT of messages that fly by and I am not good enough to know which may be the problem you are facing.

Can you possibly try re-creating the ~/.wine-logos prefix by re-running wasta-logos-setup? This would require a full re-download of your Data, however. You could save your Logos/Data, Logos/Documents, and Logos/Users from your existing ~/.wine-logos first and then restore them after the install finishes, but if you have decent internet maybe you want to fetch it cleanly from the internet again? I think that would give the best chance to make sure it isn't anything in the local ~/.wine-logos that is causing the issues.

Rik

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073397#Comment_1073397

Rik:

Somehow got it working. Reran wasta-logos-setup, did not setup new .wine-logos directory.

Did a uninstall of Logos software in the Logos installer, which did not uninstall Logos.

I do not know why but it is working now.

Thank you again for all of your efforts.

Logos runs very well on an old Compaq 6710b with a Intel Celeron processor.

I am running Lubuntu 18.04

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073408#Comment_1073408

Hi Rik

I replaced the starter command by what you wrote me and adopted it. No success: "directory or file not found". Now I created my own shell-script logos.sh and a launcher to run it. That's not the direct and simple way, but it works. Thank you for the support.

Dirk

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073413#Comment_1073413

I replaced the starter command by what you wrote me and adopted it. No success: "directory or file not found". Now I created my own shell-script logos.sh and a launcher to run it. That's not the direct and simple way, but it works. Thank you for the support.

Dirk, I am glad after a LOOOONG process that you finally have it running. I can't exactly say why your launcher isn't working, but if you want to post the contents of it, maybe something would be apparent. Again it seems "possible" that by re-running wasta-logos-setup and choosing "repair" that it should repair your launcher, but maybe you don't want to mess around too much if it is working now via a script to launch it.

Rik

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073572#Comment_1073572

Hi Rik

I deleted the old launcher. And you are right: Ich don't want to mess around. I'm fine with my own little script (my first linux-script, lol). I'll test the other issue I wrote in the google doc. Maybe it works now.

Greetings, Dirk

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1074050#Comment_1074050

I updated wasta-wine to version 0.1.8 that adds "rename" as a dependency. I am hoping this will take care of the issue of some users getting errors from the .so-wasta files not getting renamed to .so on install.

So if anyone else has an error where something like ntdll.dll.so is not found, but the files are still named .so-wasta (so ntdll.dll.so-wasta for example) in the /opt/wasta-wine/lib/wine folder then please let me know.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1074391#Comment_1074391

I have completely reinstalled logos with the new packages on Kubuntu 19.10.

Everything works great now. Thank you [:)]

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1068120#Comment_1068120

I hadn't read this thread since August or early September, so imagine my surprise when I stumbled upon this post last night! As a sysadmin, this made it very difficult to sleep: to finally be rid of Windows.[^0] As with many others, I no longer need Windows at all. As a student at RTS, this is great news for my research! When BibleWorks went down, I bought the crossover package and setup my virtual machine. (Here's that caveat: unfortunately the seminary requires use of the Lockdown Browser for exams so the drive will be dual booted until graduation, but the VBox machine can be destroyed!)

Seeing that Logos was more than willing to let their installer be included in a repo was also wonderful news full of brotherly love. [:)]

Thank you so much for everyone's hard work! Louis Lenders, our Wine dev, @Rik, @John, and all other contributors. Surely there must be treasures stored up in heaven for this!

My main workstation's setup is i7-4790k, 32 GB[^1], on SSD; Kubuntu 18.04, using KDE Plasma w/ GTX 970.

The install through wasta took me 15 minutes. Now its downloading the rest of my library and indexing.

I will have to checkout an rsync of the data over to my laptop!

[^0]: One caveat.

[^1]: Because VirtualBox Logos had to be a thing.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075323#Comment_1075323

So, I am back trying to get this to work on my chromebook. Long story short, I am dual-booting into GalliumOS, which is a build of Xubuntu 18.04. Here is my terminal output when I try to run wasta-logos-setup:

chrx@chrx:~$ sudo apt install wasta-logos-setup
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
wasta-logos-setup : Depends: wasta-wine but it is not going to be installed
E: Unable to correct problems, you have held broken packages

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075353#Comment_1075353

The following packages have unmet dependencies:
wasta-logos-setup : Depends: wasta-wine but it is not going to be installed
E: Unable to correct problems, you have held broken packages

Bill, can you try to install wasta-wine directly so we can see what (sub) dependency has issues?

sudo apt install wasta-wine

Then keep manually trying each package that gives an error saying it is not going to be installed so we can build a list of packages that are not able to be installed, thus leading to wasta-logos-setup not being able to be installed.

Rik

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075356#Comment_1075356

Here's the terminal output. There are a lot of dependencies.

chrx@chrx:~$ sudo apt install wasta-wine
[sudo] password for chrx:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
wasta-wine : Depends: libasound2:i386 (>= 1.0.16) but it is not installable
Depends: libc6:i386 (>= 2.27) but it is not installable
Depends: libglib2.0-0:i386 (>= 2.12.0) but it is not installable
Depends: libgphoto2-6:i386 (>= 2.5.10) but it is not installable
Depends: libgphoto2-port12:i386 (>= 2.5.10) but it is not installable
Depends: libgstreamer-plugins-base1.0-0:i386 (>= 1.0.0) but it is not installable
Depends: libgstreamer1.0-0:i386 (>= 1.4.0) but it is not installable
Depends: liblcms2-2:i386 (>= 2.2+git20110628) but it is not installable
Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not installable
Depends: libmpg123-0:i386 (>= 1.13.7) but it is not installable
Depends: libopenal1:i386 (>= 1.14) but it is not installable
Depends: libpcap0.8:i386 (>= 0.9.8) but it is not installable
Depends: libpulse0:i386 (>= 0.99.1) but it is not installable
Depends: libudev1:i386 (>= 183) but it is not installable
Depends: libx11-6:i386 but it is not installable
Depends: libxext6:i386 but it is not installable
Depends: libxml2:i386 (>= 2.9.0) but it is not installable
Depends: ocl-icd-libopencl1:i386 but it is not installable or
libopencl1:i386 but it is not installable
Depends: ocl-icd-libopencl1:i386 (>= 1.0) but it is not installable or
libopencl-1.1-1:i386 but it is not installable
Depends: zlib1g:i386 (>= 1:1.1.4) but it is not installable
Depends: libasound2-plugins:i386 but it is not installable
Depends: libncurses6:i386 but it is not installable or
libncurses5:i386 but it is not installable or
libncurses:i386 but it is not installable
Recommends: libcapi20-3:i386 but it is not installable
Recommends: libcups2:i386 but it is not installable
Recommends: libdbus-1-3:i386 but it is not installable
Recommends: libfaudio0:i386 but it is not installable
Recommends: libfontconfig1:i386 but it is not installable
Recommends: libfreetype6:i386 but it is not installable
Recommends: libglu1-mesa:i386 but it is not installable or
libglu1:i386 but it is not installable
Recommends: libgnutls30:i386 but it is not installable or
libgnutls28:i386 but it is not installable or
libgnutls26:i386 but it is not installable
Recommends: libgsm1:i386 but it is not installable
Recommends: libgssapi-krb5-2:i386 but it is not installable
Recommends: libjpeg62-turbo:i386 but it is not installable or
libjpeg8:i386 but it is not installable
Recommends: libkrb5-3:i386 but it is not installable
Recommends: libodbc1:i386 but it is not installable
Recommends: libosmesa6:i386 but it is not installable
Recommends: libpng16-16:i386 but it is not installable or
libpng12-0:i386 but it is not installable
Recommends: libsane:i386 but it is not installable or
libsane1:i386 but it is not installable
Recommends: libsdl2-2.0-0:i386 but it is not installable
Recommends: libtiff5:i386 but it is not installable
Recommends: libv4l-0:i386 but it is not installable
Recommends: libxcomposite1:i386 but it is not installable
Recommends: libxcursor1:i386 but it is not installable
Recommends: libxfixes3:i386 but it is not installable
Recommends: libxi6:i386 but it is not installable
Recommends: libxinerama1:i386 but it is not installable
Recommends: libxrandr2:i386 but it is not installable
Recommends: libxrender1:i386 but it is not installable
Recommends: libxslt1.1:i386 but it is not installable
Recommends: libxxf86vm1:i386 but it is not installable
Recommends: rename but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075356#Comment_1075356

The following packages have unmet dependencies:
wasta-logos-setup : Depends: wasta-wine but it is not going to be installed
E: Unable to correct problems, you have held broken packages

Bill, can you try to install wasta-wine directly so we can see what (sub) dependency has issues?

sudo apt install wasta-wine

Then keep manually trying each package that gives an error saying it is not going to be installed so we can build a list of packages that are not able to be installed, thus leading to wasta-logos-setup not being able to be installed.

Rik

Attached are all the dependencies. I'm not all that knowledgeable in this, but it looks like it wants a lot of i386 packages. Is there a way to get them in one fell swoop?4454.Dependencies.docx

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075356#Comment_1075356

I'm hitting the same issue on both my workstation and my laptop after following the Google Doc install instructions. When using the Library tool to open a new resource, I am getting the following issues.

Both when the indexer is running and when it has completed, if I attempt to open a new resource—not one of my bookmarks—through the library tool, Logos immediately crashes. I don't see this issue in the Google Doc. Others have found their indexing to work fine. Should I delete something? Add specific flags? Should I install the 64bit version? Or is this something presently unknown?

I am rebuilding the index now.

What other information can I provide?

3515.backtrace.txt

5165.cli-output.txt

System information:

Wine build: wine-4.18

Platform: i386

Version: Windows 5.1 (0), or XP

Host system: Linux, Kubuntu 18.04

Host version: 4.15.0-66-generic

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075431#Comment_1075431

Attached are all the dependencies. I'm not all that knowledgeable in this, but it looks like it wants a lot of i386 packages. Is there a way to get them in one fell swoop?4454.Dependencies.docx

Bill, I think the best way to proceed is to find out which one (or more than 1) are not available for you. Please try to do sudo apt install <package name> one by one with the below list. Patience will give us more information!

libasound2:i386
libc6:i386
libglib2.0-0:i386
libgphoto2-6:i386
libgphoto2-port12:i386
libgstreamer-plugins-base1.0-0:i386
libgstreamer1.0-0:i386
liblcms2-2:i386 (>= 2.2+git20110628)
libldap-2.4-2:i386
libmpg123-0:i386
libopenal1:i386
libpcap0.8:i386
libpulse0:i386
libudev1:i386
libx11-6:i386
libxext6:i386
libxml2:i386
ocl-icd-libopencl1:i386 | libopencl1:i386
ocl-icd-libopencl1:i386 | libopencl-1.1-1:i386
zlib1g:i386
libasound2-plugins:i386
libncurses6:i386 | libncurses5:i386 | libncurses:i386
rename

Where the "|" is you only need one of them to work, so try each of them to see if it is able to install... it is only a problem if NONE of them in the same line don't install.

Please keep track of which ones do NOT install, then we will work on that list to track down why they are not available to you. I think the problem is you may have an Ubuntu repository NOT enabled, which is where these packages come from. So you can use "Software Sources" to make sure that all the repositories are enabled.

Rik

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075437#Comment_1075437

Might be better to delete the library db in case that was corrupted somehow. That happened to someone else... Others are reporting success on the same configuration so you have a good chance!

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075500#Comment_1075500

So, I did sudo dpkg --add architecture i386 before re-running sudo apt install wasta-wine and it installed wasta-wine. Logos is installing within a Ubuntu 18.04 LXC container on my Pixelbook right now. The installation isn't finished yet (preparing library step), but if all goes well I will redo everything and document my steps for other users.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075504#Comment_1075504

I ran the following two commands and so far so good.

find /home/$USER/.wine-logos/drive_c/users/$USER/Local Settings/Application Data/Logos/Data -iname libraryindex.db -delete
find /home/$USER/.wine-logos/drive_c/users/$USER/Local Settings/Application Data/Logos/Data -iname libraryindex-journal.db -delete

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075507#Comment_1075507

So, I did sudo dpkg --add architecture i386 before re-running sudo apt install wasta-wine and it installed wasta-wine. Logos is installing within a Ubuntu 18.04 LXC container on my Pixelbook right now. The installation isn't finished yet (preparing library step), but if all goes well I will redo everything and document my steps for other users.

Bill, good work! I didn't realize it was possible to *not* have the i386 architecture automatically available. We are certainly wanting to document that step for others, especially if everything else works for you. Note that I think the command should have an extra "-" between add and architecture, like this:

sudo dpkg --add-architecture i386

Keep us updated

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075507#Comment_1075507

Very interesting Bill. I was running into a similar problem when trying to install Logos in a LXC container in Ubuntu. I'm going to run "sudo dpkg --add architecture i386" and see what happens. Please keep reporting back. I'd really like to know if it is possible to run Logos on a Chromebook.

Soon I will be purchasing a new laptop. My three main requirements are that it 1.) Be able to run Linux (ChromeOS actually qualifies for me) and 2.) that it be relative lightweight and easy to carry, and 3.) that it have really good battery life. Reviews are in for the Pixel Book Go and they are pretty good, so it is a candidate. The one concern I have for Chromebooks is that they typically don't have very large hard drives. Last time I checked my WINE folder for Logos was at least 32 gigs. Something to think about. Still, I would like to know if this is possible. If I get the LXC container working on Ubuntu, I wonder if I could transfer it to a Chromebook. Keep the reports coming.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075536#Comment_1075536

So, I did sudo dpkg --add architecture i386 before re-running sudo apt install wasta-wine and it installed wasta-wine. Logos is installing within a Ubuntu 18.04 LXC container on my Pixelbook right now. The installation isn't finished yet (preparing library step), but if all goes well I will redo everything and document my steps for other users.

Bill, good work! I didn't realize it was possible to *not* have the i386 architecture automatically available. We are certainly wanting to document that step for others, especially if everything else works for you. Note that I think the command should have an extra "-" between add and architecture, like this:

sudo dpkg --add-architecture i386

Keep us updated

Thanks, Rik. You are right about the command and what I left out. I know just enough about Linux to be dangerous.

My problem now is twofold: I have the problem of the launcher not working and I have to start Logos from the command line. I have looked at the launcher and it appears to be correct, but it's not working. I have rerun wasta-wine and repaired the installation, with no effect.

The second problem is not anything anyone here can help with but is a limitation with running a Linux container on a Chromebook right now. Currently, Google only allocates half of your RAM to the container. I have 16gb of RAM, which gives me 8gb in the container. Things run a little slowly. If someone had a Chromebook with 4gb of RAM, I can't see Logos running well at all in a container. But, evidently, in the future, you'll be able to allocate more RAM to the Linux container.

Once I get the steps for installation within a Linux container nailed down, I will set up a chroot with Ubuntu 18.04 on my Pixelbook and try installing Logos in that. The performance may be better. I will even try a third method which is a dual-boot set up with Ubuntu 18.04 and ChromeOS. Lots to tinker with.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075541#Comment_1075541

Soon I will be purchasing a new laptop. My three main requirements are that it 1.) Be able to run Linux (ChromeOS actually qualifies for me) and 2.) that it be relative lightweight and easy to carry, and 3.) that it have really good battery life. Reviews are in for the Pixel Book Go and they are pretty good, so it is a candidate. The one concern I have for Chromebooks is that they typically don't have very large hard drives. Last time I checked my WINE folder for Logos was at least 32 gigs. Something to think about. Still, I would like to know if this is possible. If I get the LXC container working on Ubuntu, I wonder if I could transfer it to a Chromebook. Keep the reports coming.

Logos is definitely running in the container on my Pixelbook. For your purchase decision, get as much RAM and storage as you can afford. If money isn't an issue, you can look at the Dell Inspiron 5300. You can configure this through the roof!

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075561#Comment_1075561

I replicated the installation of Logos on my 2017 Pixelbook and have written up the steps in this Logos Installation on Chromebooks (Google Doc).

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075561#Comment_1075561

Bill, I am indebted to you. Thanks to your "sudo dpkg --add-architecture i386" I have successfully installed Logos in a LXD container on Ubuntu. Right now it is downloading and indexing. I was never able to get it to work before this. The beauty of this is that once this is done I should truly have a truly portable version of Logos that I can quickly setup on any computer with LXD (well, probably any system that can run LXC containers, but LXD on Ubuntu is so very helpful).

Also, thank you so very much for the information about Chromebooks. I knew about the hard disk limitations (namely that Chromebooks are usually limited in disk space), but I did not know about the ram restrictions. As you say, this may be configurable in the future, but it gives me pause. Makes me think that I may try and hold out for a beefier machine that I can just run Linux on - like one of the Dell XPS 13s which comes loaded with Ubuntu.

Bill, again thanks very much. I will be putting your tip into the Google Docs page.

Blessings,

Adam

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075589#Comment_1075589

Adam, that's great! You know, I stumbled across this solution when Rik told me to try to run wasta-wine directly so that we could see the dependencies. Virtually every one of them had i386 after it and I thought that was weird because my Pixelbook is amd64. That got me searching for a way to install the dependencies with one fell swoop because I didn't have enough patience to try installing them one by one. I came across the solution searching for the answer. It was a shot in the dark as far as I was concerned, but I was really excited when I saw that wasta-wine ran and started downloading megabytes of packages. I knew I had turned the corner.

I think the Dell XPS is a fantastic choice. I have thought about getting one myself, but I really like ChromeOS.

Can you start Logos in your container from the launcher? If you had issues with that and found a solution, please report back.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075597#Comment_1075597

I haven't tried to set up a launcher yet, but I think that could be done.

I'm going to try to write up a full how to for the Google Doc next week.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075607#Comment_1075607

Downloading all of my 7,000 resources into my LXC container took 24 hours (way longer than my other installations) and indexing is proceeding really, really slowly. Is this an issue others have encountered with their Linux installations, or might it be unique to the fact that I installed mine in a Linux container?

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075951#Comment_1075951

I can't think of any reason why downloading would take longer than on any other system. A container could take longer to index if the host system limited the container resources, but otherwise it shouldn't take any longer.

I know that downloading didn't take any longer for me in the container that I set up. I am unsure if indexing took any longer or not. I let it run overnight, when I came back it was done.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1075956#Comment_1075956

Hi

I asked Alistair (maintainer of Wine-staging) to include the patch from https://bugs.winehq.org/show_bug.cgi?id=47668 in Staging, and it`s now in.

So you can use upcoming wine-staging (4.21 i guess) released in 1.5 week to work around the issue reported in that bug. Guess more issues to solve, but hey, it`s linux

Regards

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076098#Comment_1076098

Louis,

THANK YOU! We are indebted to you for your contributions.

Rik

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076195#Comment_1076195

Yes thanks so much! I noted one of the other devs said it was looking good and could be included in dev? What do you think?

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076202#Comment_1076202

I'm still having problems with my Logos installation in a container finishing indexing. It gets stuck at 5% even after several hours. I can tell indexing is not finished because I can't do searches and the performance is really slow. Does anyone have suggestions for how I can address this?

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076209#Comment_1076209

Did you set your wine version to win xp? That seems to fix some indexing issues? I have found that indexing can finish but it only reports a small percentage done. The evidence it is done is that the process is idle and when quitting it doesn't continue like it would if it had work to do... but then all my searches work. Is there a limitation on the container? Is chrome os throttling it for some reason?

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1073395#Comment_1073395

Dirk, glad you got it working! You could run wasta-logos-setup again (do NOT create a new prefix) and it should repair your launcher. Alternatively, you can manually adjust it. Here is what my launcher has:

Exec=env WINEPREFIX="/home/rik/.wine-logos" /opt/wasta-wine/bin/wine C:\\\\windows\\\\command\\\\start.exe /Unix /home/rik/.wine-logos/dosdevices/c:/users/rik/Start\\ Menu/Programs/Logos\\ Bible\\ Software.lnk LC_ALL=C

For some reason my launcher had Exec=env WINEPREFIX="/home/wmadan/.wine-logos" /opt/wasta-wine/bin/wine C:\\\\\\\\windows\\\\\\\\command\\\\\\\\start.exe /Unix /home/wmadan/.wine-logos/dosdevices/c:/users/wmadan/Start\\\\ Menu/Programs/Logos\\\\ Bible\\\\ Software.lnk LC_ALL=C

I underlined the extra / characters.

I had to remove the extra / characters from the launcher. Then it worked.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076367#Comment_1076367

The second way to install Logos on a Chromebook is to run "crouton" -- essentially, a desktop Linux within a chroot within ChromeOS. Why would you want to do this as opposed to installing Logos within Crostini on a Chromebook (as an earlier post of mine documented)?

You have full access to all of your hardware. In my case, I have the full 16gb of RAM that is installed on my Pixelbook.
Logos appears to run much better in crouton than in Crostini.
You can use crouton to run all of your Linux programs rather than Crostini. Some apps may not run in Crostini, I am told.
I experienced some nagging issues running Logos in Crostini (launcher icon wouldn't work, indexing wouldn't finish, graphic tearing and artifact issues.)

The drawback of running a chrooted Linux environment on a Chromebook is that it requires you to run in developer mode, which disables ChromeOS's security protections. You can read about this particular issue on the crouton Github page. That, and when you reboot, you have to make sure you hold down the ctrl and D keys or else your whole setup could be wiped out.

That said, Logos runs really well in crouton. If you want to know how I installed Logos in crouton on my 2017 Pixelbook, here are the steps: How to Install Logos in Crouton on a Chromebook (Google Doc).

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1076467#Comment_1076467

If you are not familiar with the company, Pine64 has a slew of quality and cheap Linux products. The newest is the Pinebook Pro and soon to be are the PinePhone, PineTab, and PineTime.

Any thoughts on how Logos would run on the Pinebook Pro (arm64, RK3399 4GB RAM) or similar hardware?

Logos lists 2GB of RAM as recommended and only OS, storage, and screensize.

The PineTab would have less hardware (and the PinePhone would hopefully be able to run Android apps sometime, that or the Logos web app) but if you think it'd run on the PBP, the PBP would be a $200 Logos on Linux machine.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1077149#Comment_1077149

Taylor, the Pinebook Pro looks like an excellent little device, but I do not believe that Windows apps compiled for x86 will work on ARM chips via WINE. Don't think that problem can be overcome.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1077149#Comment_1077149

Is it normal behavior for Logos on startup to open with a blank screen and no layouts? If I go to settings and tell Logos to open the last layout, it doesn't work.

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1077277#Comment_1077277

Unfortunately, that is normal for me under Linux. It is not normal under Windows. It is a minor annoyance. I'm not sure what the issue is here, but hopefully it will work itself out eventually. Is anyone NOT having that problem?

Adam

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1077149#Comment_1077149

Taylor,

The Pinebook Pro sounds great. However, since WINE cannot run x86 programs on ARM, this will be a no go. To bad though. These look like nice machines.

Adam

LogosTerminal.rtf

https://community.logos.com/discussion/comment/1077435#Comment_1077435

Unfortunately, that is normal for me under Linux. It is not normal under Windows. It is a minor annoyance. I'm not sure what the issue is here, but hopefully it will work itself out eventually. Is anyone NOT having that problem?

John reported on the Google Doc the following:

"I have set to another layout without a problem... I would suggest they try to remake the layout. I've had similar happen on Mac, so it may not be a platform specific problem."

So if people can try remaking custom layouts and see if they "stick". Sorry I am not enough of a Logos user to know much about this, but if anyone has tips / tricks to make it "remember" please post back.

LogosTerminal.rtf

Quick Links