Linux version of Logos Bible Software

Page 47 of 49 (963 items) « First ... < Previous 45 46 47 48 49 Next >
This post has 962 Replies | 52 Followers

Posts 18
Scott Warner | Forum Activity | Replied: Sun, May 10 2020 2:00 PM

I tried, but with no success.

Posts 1041
John Goodman | Forum Activity | Replied: Sun, May 10 2020 3:29 PM

While a few people, generally with smaller libraries, are succeeding with 64bit. Please use the 32 bit version if you want reliability. 32bit wine apps run fine on 64bit linux. We are working on getting 64bit stable asap. Wasta packages or the appimage are both easier than rolling your own wine setup.

גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה

Posts 18
Scott Warner | Forum Activity | Replied: Mon, May 11 2020 5:45 AM

I had Logos working on my setup, but then I had to reinstall my OS.  I noticed the installer is not 8.13 (a newer version).  I could install with the older version.  Could it be that the changed version doesn't work together?  Once again, I was able to install and use Logos a month ago (still on LM 19.3), but now I can't install.  Any help would be welcome.

Thanks,

Scott

Posts 58
Rik Shaw | Forum Activity | Replied: Mon, May 11 2020 5:55 AM

Scott,

Sorry for the problems. If you are using the wasta-logos-setup process then yes there may be a problem with new installs. I thought I had everything working, but possibly the newer version of wine (5.7), the newer version of logos (8.13), the newer version of winetricks (20200420), or a missing dependency problem between them is causing some issue. I have been working on it over the weekend but haven't solved it yet.

If you have adequate bandwidth, the AppImage version from Daniel may be your best option if you need a solution. I am evaluating using that process as part of wasta-logos-setup, but the AppImage has a bit older version of wine (4.21) and I understand there to be some optimizations in newer versions that may help with performance a bit.

Here is Daniel's process: https://github.com/ferion11/LogosLinuxInstaller

Rik

Posts 34
Daniel Ribeiro da Silva | Forum Activity | Replied: Mon, May 11 2020 9:38 AM

Rik Shaw:

Scott,

Sorry for the problems. If you are using the wasta-logos-setup process then yes there may be a problem with new installs. I thought I had everything working, but possibly the newer version of wine (5.7), the newer version of logos (8.13), the newer version of winetricks (20200420), or a missing dependency problem between them is causing some issue. I have been working on it over the weekend but haven't solved it yet.

If you have adequate bandwidth, the AppImage version from Daniel may be your best option if you need a solution. I am evaluating using that process as part of wasta-logos-setup, but the AppImage has a bit older version of wine (4.21) and I understand there to be some optimizations in newer versions that may help with performance a bit.

Here is Daniel's process: https://github.com/ferion11/LogosLinuxInstaller

Rik

I have one updated AppImages here if you want to test (now is using wine v5.7 on the Wine_Appimage_dev repo): https://github.com/ferion11/Wine_Appimage_dev/releases/tag/continuous

But there is wine v5.x bugs with the LogosBible like the black boxes (this is the worst issue today, because it can hide text). Then i will hold the wine version update (on the main repo Wine_Appimage) to when this get one bugfix (and security issues, related to this, are "workarounded" by using the container, so don't need worry here).

Posts 18
Scott Warner | Forum Activity | Replied: Mon, May 11 2020 1:14 PM

Thanks for all your efforts, Rik.  I just wanted to be sure that I wasn't doing something wrong.

Thanks also to Daniel and John for all your work (and anyone else I might have missed).

Be God's,

Scott

Posts 58
Rik Shaw | Forum Activity | Replied: Tue, May 12 2020 8:09 AM

Daniel Ribeiro da Silva:

I have one updated AppImages here if you want to test (now is using wine v5.7 on the Wine_Appimage_dev repo): https://github.com/ferion11/Wine_Appimage_dev/releases/tag/continuous

But there is wine v5.x bugs with the LogosBible like the black boxes (this is the worst issue today, because it can hide text). Then i will hold the wine version update (on the main repo Wine_Appimage) to when this get one bugfix (and security issues, related to this, are "workarounded" by using the container, so don't need worry here).

Daniel, thanks for updating to Wine 5.7. I tested the AppImage process and it works pretty well.... a few comments / ideas / questions below: (I will also leave these as "issues" at the site, but will put them here so other casual readers can see them):

  • Execute winetricks with "-q" so it is non-interactive (like this: winetricks -q dotnet48)
  • You can combine winetricks installs, like this: "winetricks arial andale calibri cambria candara"
  • The flashing black boxes are because the "ddr=gdi" winetrick is "broken" in newer winetricks. It is a simple fix, you can either sed edit the winetricks script before running it to change "DirectDrawRenderer" to "renderer" for the key, or use regedit after winetricks to change the item. Reference: https://bugs.winehq.org/show_bug.cgi?id=47837
  • Note that ddr=gdi makes videos NOT play in Logos (I have never seen them play anyway..... still a bug we hope to solve)
  • Note that appending "LC_ALL=C" to the launcher may PREVENT saved layouts from loading on start, and makes Logos always open to the home screen. So we REMOVED that and I don't think there is any negative side-effect. You may want to test in your case, however before removing it.
  • Question: you put a pile of fonts in, does Logos use those, or are you just being thorough?
  • Question: The PowerPoint Viewer, again does that only give more fonts, or is that to help making a PDF or something else? Someone commented on PDF creation not working and I don't recall what we need to do to make it work?
  • Question: does the "disable-winemenubuilder" reg key just make wine not create launchers?

Posts 58
Rik Shaw | Forum Activity | Replied: Tue, May 12 2020 8:12 AM

Scott Warner:

Thanks for all your efforts, Rik.  I just wanted to be sure that I wasn't doing something wrong.

Thanks also to Daniel and John for all your work (and anyone else I might have missed).

Scott, I reverted "wasta-wine" to version 4.21 for 18.04 / LM 19 just to be conservative and since there are several using it and I don't want to cause issues. For 20.04 I have just been testing wine 5.8 for wasta-wine, and I think it is working well. Again if you have good internet, Daniel's script to download all this from scratch works quite well.

Anyway, I hope / assume this will work well for you to get re-installed but please keep us posted.

Posts 34
Daniel Ribeiro da Silva | Forum Activity | Replied: Tue, May 12 2020 10:07 AM

Rik Shaw:
Daniel, thanks for updating to Wine 5.7. I tested the AppImage process and it works pretty well.... a few comments / ideas / questions below: (I will also leave these as "issues" at the site, but will put them here so other casual readers can see them):

Well, I'm keeping always one "dev" more updated version and the "proton wine version" that maybe be another alternative on the future.

Rik Shaw:

  • Execute winetricks with "-q" so it is non-interactive (like this: winetricks -q dotnet48)

I had thought about it, but the lack of feedback bothered me. I'm thinking of adding this option to the main script, leaving everything optional.

Rik Shaw:

  • You can combine winetricks installs, like this: "winetricks arial andale calibri cambria candara"

Yes (there is the "allfonts" too). But in this part, the user have to wait a good time, then to get more feedback, I have divided it in smaller steps (later I will create a bash function to let the code more clean, and give one better feedback to the user). I have to improve the quality of the code too.

Rik Shaw:

  • The flashing black boxes are because the "ddr=gdi" winetrick is "broken" in newer winetricks. It is a simple fix, you can either sed edit the winetricks script before running it to change "DirectDrawRenderer" to "renderer" for the key, or use regedit after winetricks to change the item. Reference: https://bugs.winehq.org/show_bug.cgi?id=47837

Thanks. I have tested the "opengl" too, because on the documentation today there is only "gdi" and "opengl". But that's is the first time that I remember seen the "renderer" option, so I will have to test it and understand what it's doing first.

Rik Shaw:

  • Note that ddr=gdi makes videos NOT play in Logos (I have never seen them play anyway..... still a bug we hope to solve)

Yes. This is an old wine's bug, not only with LogosBible but in others applications too (and as far as I know, it happens in opengl rendering too).

Rik Shaw:

  • Note that appending "LC_ALL=C" to the launcher may PREVENT saved layouts from loading on start, and makes Logos always open to the home screen. So we REMOVED that and I don't think there is any negative side-effect. You may want to test in your case, however before removing it.

Indeed. The last wine 5.x have a better Unicode support, then I had planned to drop it after the next big update of the Wine_Appimage repo version.

Rik Shaw:

  • Question: you put a pile of fonts in, does Logos use those, or are you just being thorough?

Well, it's more to make sure that the dotnet works better because of the Windows fallback font system (with possible others languages issues too), and allow the user to have more options, with cost of size less than 40MB. But after reading the "Why Logos’ Typography Matters", and review/rebuild many of my font system and uses, I'm re-thinking about this.

Rik Shaw:

  • Question: The PowerPoint Viewer, again does that only give more fonts, or is that to help making a PDF or something else? Someone commented on PDF creation not working and I don't recall what we need to do to make it work?

No, on the current script is just to get the fonts. But the extra fonts can help the PDF system too. Maybe the PDF system is using the cups-pdf to work. I would need to see more details about the issue.

Rik Shaw:

  • Question: does the "disable-winemenubuilder" reg key just make wine not create launchers?

I would like to disable any wine auto-creating, non controlled, system. Because it can make a mess on your user configuration, like making all text files associations with notepad.exe (and many others, without asking). But the main motivation is to not conflict with the local wine installation of your system, which can be used at the same time. The idea original was to leave everything in the same directory, separated into sub-directories (one for AppImage, another to LogosBible wine bottle, ...), like one big portable app. Perhaps on the future.

Posts 1
aaylnx | Forum Activity | Replied: Tue, May 12 2020 2:47 PM

Daniel (and anyone else for that matter),

Rik recently joined in the Telegram channel.  I believe we would all welcome you in there as well.  I have been using your AppImage for some time now and quite like it.  I think it would be good to have you involved in all discussions so as to compare notes.  Who knows, perhaps everyone could end up joining forces on the same approach.  I think there is value in the AppImage approach since it is works across Linux distros.

The Telegram channel is here - https://t.me/linux_logos

Adam

Posts 46
Mirko D. Walter | Forum Activity | Replied: Fri, May 29 2020 5:52 AM

Daniel Ribeiro da Silva:

You, Sir, are officially my hero of the day Wink

Working really fine. The indexing will take a couple of hours (no wonder, way to much books...)... 

Robert Warren wrote 2015 how to get the personal books from a working windows-installation to linux: just copy the lsbpp-files from the application folder over to the linux-one... doesn't matter, if you had the 64-bit version working on windows and now the 32bit- version on linux (but DON'T copy the complete library, this will not work, you have to download your whole library from the faithlife-server - that's why my indexing is cooking my cpus).

Posts 12
Kevin Moore | Forum Activity | Replied: Thu, Jun 4 2020 11:35 AM

Many thanks to all who have been working on this! [8-| ]I installed wast-logos-setup some months ago (Linux Mint 19.2 xfce) It worked very well and was steadily improving until very recently. Now Logos will load as before, but it crashes as soon as I try to interact with any of the windows. Not sure exactly when it stopped working - my guess would be after May 20, 2020. My system update regularly from the Wasta Logos PPA, so is it likely this is related to an update in the wasta distribution? Indexing problem? Any suggestions? Would really like to solve this without having to reinstall all my books!

Tried installing the V1.3 appimage version here: https://github.com/ferion11/LogosLinuxInstaller/releases/tag/v1.3  but I could not get it to install -- so far.

Posts 122
Paul Unger | Forum Activity | Replied: Thu, Jun 4 2020 12:04 PM

I don't have a solution to your immediate problem, but I would recommend keeping a copy of your "index" and "resource" folders so that if something does go wrong, you can get back on your feet with relative ease. The index folders on my machine are:

  • /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/random.id/BibleIndex
  • /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/random.id/LibraryIndex
  • /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/random.id/PersonalBookIndex

and the resources are in:

  • /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/random.id/ResourceManager/Resources

Your "user", "username", and "random.id" will be different, of course.

I use scripts in FreeFileSync to update the backups any time I add / update a resource. If your Logos install goes down and you have to start over, at least you can copy these files over and save yourself a lot of time (and bandwidth...).

Posts 58
Rik Shaw | Forum Activity | Replied: Thu, Jun 4 2020 12:18 PM

Kevin, sorry there is some problem for you. Can you please report your specific version of wasta-wine, wasta-winetricks, wasta-logos-setup, and wasta-logos-installer? (if you use "synaptic package manager" you can find them there).

As noted, keep backups of your resources and index files, etc. but then you should be able to re-run wasta-logos-setup at anytime with an existing Logos install (do NOT remove your existing .wine-logos install, and later choose to "repair" in the Logos installer). This will upgrade your Logos to the newest 8.13 version, plus possibly fix any issues.

Let us know any update.

Posts 12
Kevin Moore | Forum Activity | Replied: Thu, Jun 4 2020 12:49 PM

Thanks. Yes, I'll do that.

Posts 12
Kevin Moore | Forum Activity | Replied: Thu, Jun 4 2020 12:57 PM

Thanks for the quick replies! Wasta-logos-installer - 8.13.0.0008~ubuntu2;   wasta-logos-setup 1.1.2~ubuntu18.04.1;   wasta-wine 5.7.0~ubuntu18.04.1;   wasta-winetricks  20200412.3~ubuntu18.04.1

Posts 58
Rik Shaw | Forum Activity | Replied: Thu, Jun 4 2020 1:01 PM

Kevin Moore:

Thanks for the quick replies! Wasta-logos-installer - 8.13.0.0008~ubuntu2;   wasta-logos-setup 1.1.2~ubuntu18.04.1;   wasta-wine 5.7.0~ubuntu18.04.1;   wasta-winetricks  20200412.3~ubuntu18.04.1

Kevin, as I suspected, since you were a regular updater, you got a version of wasta-wine that I intended for testing but accidtenally / prematurely pushed to the main Wasta Logos PPA. I have since reverted it to wasta-wine 4.18.x (what was there since last fall) as getting all the dependencies for Bionic 18.04 (and derivatives such as Mint) proved to be a bit tricky.

So, can you please uninstall wasta-wine. Then, if you install again it will re-install wasta-wine 4.18. Hopefully that is all you need. But in case it is not running correctly, please re-run wasta-logos-setup.

Again please keep us updated. Sorry again for the problem!

Posts 12
Kevin Moore | Forum Activity | Replied: Thu, Jun 4 2020 1:08 PM

Will do that and let you know. Thought it might be something like that. Again, thanks for the help.

Posts 12
Kevin Moore | Forum Activity | Replied: Sat, Jun 6 2020 11:37 AM

Rik Shaw:

Kevin, as I suspected, since you were a regular updater, you got a version of wasta-wine that I intended for testing but accidtenally / prematurely pushed to the main Wasta Logos PPA. I have since reverted it to wasta-wine 4.18.x (what was there since last fall) as getting all the dependencies for Bionic 18.04 (and derivatives such as Mint) proved to be a bit tricky.

So, can you please uninstall wasta-wine. Then, if you install again it will re-install wasta-wine 4.18. Hopefully that is all you need. But in case it is not running correctly, please re-run wasta-logos-setup.

Again please keep us updated. Sorry again for the problem!

Was able to work with this again today... As suggested, tried uninstalling wasta-wine and reinstalling that with no success. Re-ran wasta-logos-setup and that, too fails.  Then uninstalled completely all wasta items in Synaptic and re-installed using the steps at:

https://docs.google.com/document/d/1Gms_Bc2Q_OOH3G5lmP6twXnqiSWxrFFT7lCN3nRyymw/edit#

Installed:

wasta-logos-installer: 8.13.0.00008.0~ubuntu18.04.1

wasta-logos-setup: 1.1.2~ubuntu18.04.1

wasta-wine 4.18.-~ubuntu18.04.1

wasta-winetricks  20200412.3~ubuntu18.04.1

This failed while running the logos installer on indexing. It fails to load. I saved the backtrace and attached the resulting text file.

Thanks again for your help!

0028.Logos - 2020-06-06 - backtrace.txt

Posts 58
Rik Shaw | Forum Activity | Replied: Sat, Jun 6 2020 12:01 PM

If you have adequate internet can you try a clean install of Logos?

You could save your ~/.wine-logos first, then after it is running again you may be able to replace your resources folder.

Anyway, again I am sorry but I think a clean install of Logos may be needed. :-(

Page 47 of 49 (963 items) « First ... < Previous 45 46 47 48 49 Next > | RSS