Linux version of Logos Bible Software

1272830323362

Comments

  • Paul Unger
    Paul Unger Member Posts: 220

    So what would you recommend I do? Uninstall Wine and Logos 8 and reinstall them both? 32 or 64 bit? Other tips?

    Good news: The wine 5.1 is out and have fixed the Logos 8 bug (about the ReOpenFile implementation). Then you don't need the wine staging for this anymore (and the implementation of normal wine should be better than the wine staging).

    The vote is already producing results (I'm impressed).

  • So what would you recommend I do? Uninstall Wine and Logos 8 and reinstall them both? 32 or 64 bit? Other tips?

    It's hard to recommend something at this point. If you want the easy way, just use the script I have made, that will install the 32bits version using the AppImage. If you want use your native installation, you can use this script that I made for Gene-W (this install using your wine 32bits, but you need it well installed, and with the implementation of ReOpenFile). If you want to venture in unstable lands, just study how wine work on 64bits first, because that will help a lot (and search all bugs on googles too). The main question is "what you want?", the most working side, for wine, at this time, is the 32bits.

  • Jim Rutledge
    Jim Rutledge Member Posts: 7

    Is anyone else experiencing the same "fuzzy text" problem I'm experiencing with Logos on Linux? I'm attaching a screenshot so you can see what I'm talking about. The screenshot can't pick up everything I'm seeing on my screen, but it comes across well in the words "LORD" and "GOD."

    I don't know what is causing it. Is it the text renderer, or maybe the anti-aliasing being used? More importantly, is there a solution? The text was pretty crisp and clean on Windows, but this strains the eyes.

  • Dirk Kellner
    Dirk Kellner Member Posts: 101

    Hi Jim

    I have the same issue (mint 19-4 XFCE and mint 19-4 Cinnamon). I tried to change the resolution, the anti-aliasing an rendering, but this changed nothing. The appearance in Windows is really better for the eyes. I hope there'll be a solution.

    Dirk

  • Paul Unger
    Paul Unger Member Posts: 220

    @ Jim Rutledge: you might want to try a different font. Go Tools > Program Settings > Text Display > Default Resource Font, and select a different option from the drop-down list. My guess, though, is that with words like L[ORD] and G[OD], we're facing the issues inherent with fake / synthetic small caps; see https://practicaltypography.com/small-caps.html or https://designforhackers.com/blog/small-caps/ for discussion and examples. It would be nice to hear from someone at Logos how they render them!

    I agree with you, though--compared to other programs I use on Linux, Logos looks somewhat washed out... :-(

  • Jim Rutledge
    Jim Rutledge Member Posts: 7

    I appreciate the suggestion, but it isn't the font. I have tried different fonts, both OpenType (Arno Pro, Source Serif Pro, Minion Pro) and TrueType (Linux Libertine, Ubuntu, Gentium Basic, SBL Hebrew and Greek), and it's the same with all of them. The one in the screenshot is Source Serif Pro, so the small caps should be real.

    It's something to do with the program itself. I guess there's no telling what's going wrong, but I'm glad it isn't just me. The washed out look is definitely part of it the problem.

  • I'm sorry, but my eyesight is no longer good for this.
    This looks like a freetype2 kinda bug. There was some changes in the way it render fonts (Basically the freetype2 changes are speed over quality based - to provide subpixel hinting support). And now the Subpixel hinting mode can be chosen by setting the right TrueType interpreter (like it was in olds versions of freetype2):
    * truetype:interpreter-version=35 # Classic mode (default in 2.6)
    * truetype:interpreter-version=38 # Infinality mode
    * truetype:interpreter-version=40 # Minimal mode (default in 2.7)
    There is reports of good results using the "Classic mode". And you can test this by using the variable FREETYPE_PROPERTIES, like:
    FREETYPE_PROPERTIES="truetype:interpreter-version=35" wine Logos.exe

  • Bill Anderson
    Bill Anderson Member Posts: 506 ✭✭

    I’m running Logos in an Ubuntu 18.04 container on my Pixelbook and the fonts render fine. Perhaps ChromeOS have fonts figured out. 

  • Taylor
    Taylor Member Posts: 80 ✭✭

    While we're on the subject of text, any idea why the space/kerning between the letters F and r would be so drastic? The font is Times New Roman.

  • Paul Unger
    Paul Unger Member Posts: 220

    Yeah, weird... I've got a random thing where there's a space between an apostrophe and what follows, like this in Firefox > Preferences:

    [picture showing up when I edit, but not in preview or when I post...]

  • Meanwhile I tried to install Logos 8;11.0.0017 from source, but the program doesnt start. Maybe because there is no Logos in Home/.wine-logos/drive-c/users/[Name]/Application Data... I tried to install Logos from source...

    Something else, I have some free time to spare, and I would like to learn how to use LibreOffice.Is it a good idea that I clean up the ubuntu guide? Just for reading purposes, not for improving the code skills...

  • Meanwhile I tried to install Logos 8;11.0.0017 from source, but the program doesnt start. Maybe because there is no Logos in Home/.wine-logos/drive-c/users/[Name]/Application Data... I tried to install Logos from source...

    Something else, I have some free time to spare, and I would like to learn how to use LibreOffice.Is it a good idea that I clean up the ubuntu guide? Just for reading purposes, not for improving the code skills...

    * You can try to find the Logos executable using the command:

    find $HOME/.wine-logos -name Logos.exe |  grep "Logos\/Logos.exe"

    * About the LibreOffice is a good option. But for edit Microsoft files (like docx) the most compatible on linux, at this time, is the WPS Office. And the WPS Office have the same usage that the MS Office. Documentation update is always welcome :)

  • Frank Sauer
    Frank Sauer Member Posts: 1,824 ✭✭✭

    Have to say this project continues to get better! Thank you to all who are a part of it!

    Currently running:

    Kubuntu 20.04

    Logos 8.11 64 Bit

    Wine 5.3 64 Bit Prefix

    Windows 10 default

    The videos now appear to play fine

    No indexer issues

    Some black box graphical glitches

    Read Aloud still crashes

    Printing is still not working

    So overall - it is a daily driver. The glitches and Printing being fixed would make it perfect for me personally, as I do not use Read Aloud on my laptop.

    Great job All!

    Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14

  • Frank Sauer,

    Is good to know about this. The bug reports, together with the votes, is getting results fast (so, let's keep doing it).

    Workaround: On the "Print/Export" window, you can just use the "Export" option. Sometimes, I just Export to "Rich Text Format (Word, etc.)", but I like more the option "Copy to clipboard" then paste on the WPS Office (so, I can edit before print).

  • Paul Unger
    Paul Unger Member Posts: 220

    I have had persistent indexing issues. @Frank Sauer addressed this on page 42 (https://community.logos.com/forums/p/121/1081696.aspx#1081696), but his solution didn't work for me... What DID work was to copy the index information from a second, up-to-date, everything downloaded Win7 machine I have:

    C:\Users\username\AppData\Local\Logos\Data\randomID\BibleIndex, ~/LibraryIndex, and ~PersonalBookIndex

    and paste it into my corresponding wine-logos folders:

    /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/randomID/BibleIndex, ~/LibraryIndex, and ~PersonalBookIndex.

    Indexing now works! Takeaway: keep a copy of known-good indexing folders--you never know when you'll need them!

  • Frank Sauer
    Frank Sauer Member Posts: 1,824 ✭✭✭

    Paul,

    You may be experiencing an issue with the Library Catalog. I have noticed a few instances of this happening lately after any resource upgrades and/or new resources added to the library. It appears that this has caused the indexer to run continually without ever completing and was not fixed with the workaround that I posted earlier in your reference.

    When this was happening to me, I noticed that the Library Catalog folder appeared to be corrupted based upon number of files. I deleted everything in the Library Catalog folder and opened Logos, allowed it to refresh the Library Catalog, it then indexed with no issues. Library Catalof looks to be an 8 file folder when complete.

    I have had persistent indexing issues. @Frank Sauer addressed this on page 42 (https://community.logos.com/forums/p/121/1081696.aspx#1081696), but his solution didn't work for me... What DID work was to copy the index information from a second, up-to-date, everything downloaded Win7 machine I have:

    C:\Users\username\AppData\Local\Logos\Data\randomID\BibleIndex, ~/LibraryIndex, and ~PersonalBookIndex

    and paste it into my corresponding wine-logos folders:

    /home/user/.wine-logos/drive_c/users/username/Local Settings/Application Data/Logos/Data/randomID/BibleIndex, ~/LibraryIndex, and ~PersonalBookIndex.

    Indexing now works! Takeaway: keep a copy of known-good indexing folders--you never know when you'll need them!

    Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14

  • Paul Unger
    Paul Unger Member Posts: 220

    Hi Frank,

    My issue was with indexing right after installing--it never got past 7%... I tried clearing out the three ___Index folders, as you suggested in your post, but that didn't work for me. When I copied known-good index files into them, indexing proceeded as expected.

    I downloaded a new book this morning (after applying my fix), and indexing went ahead without a hitch. Here's hoping it continues!

  • Paul Unger
    Paul Unger Member Posts: 220

    "Software Updater" (Ubuntu) just informed me of a 182 MB update for "Logos Installer". Running "Update now" from within Logos tells me there is no update available... Do I need the update that "Software Installer" is offering? Is there any way to find out what the "Logos Installer" package contains?

  • "Software Updater" (Ubuntu) just informed me of a 182 MB update for "Logos Installer". Running "Update now" from within Logos tells me there is no update available... Do I need the update that "Software Installer" is offering? Is there any way to find out what the "Logos Installer" package contains?

    "Logos Installer" package, like the name, only have what's is necessary to install and run Logos.

    After Logos is installed, it can update itself. Then you don't need one new "Logos Installer", but is still a good ideai to update it (in case you need it again)

  • Paul Unger
    Paul Unger Member Posts: 220

    Thanks! I kind of thought that was the case, but just wanted to confirm it.

  • James Hudson
    James Hudson Member Posts: 337 ✭✭✭

    Hi Daniel,

    Amazing scripts - thank you!

    Have used the Installer to install!

    Can you let me know the purpose of the Indexer.sh script?

    Thanks.

    James

  • Rik Shaw
    Rik Shaw Member Posts: 77

    @Paul or others, to be clear, the update your system is notifying you of is the update to wasta-logos-installer, which I bumped to version 8.9.0.0030. So as Daniel or others have pointed out, this would only be used if you re-run wasta-logos-setup, which you can re-run if you want to "repair" your install.

    On this note, here is the best link for tracking what the newest version of logos is:

    https://wiki.logos.com/Logos_8_Release_Notes

    I note there that version 8.12 was just released, as a "RC". Is the most recent "stable" release 8.10.0.0034? If so, my Logos is NOT updating to 8.10, but is still at 8.9.x.

    Do others see this from their Logos Wine installs (that it won't update to newer feature releases?)

    Maybe there is a setting to indicate you want to move to newer feature releases not just bug releases for the current feature version?

  • Hi Daniel,

    Amazing scripts - thank you!

    Have used the Installer to install!

    Can you let me know the purpose of the Indexer.sh script?

    Thanks.

    James

    Well, the LogosIndexing.sh is just for when the Logos fail to do the indexing by itself (can happens).

    Glad to help :)

  • Paul Unger
    Paul Unger Member Posts: 220

    Rik Shaw said:

    I note there that version 8.12 was just released, as a "RC". Is the most recent "stable" release 8.10.0.0034? If so, my Logos is NOT updating to 8.10, but is still at 8.9.x.

    Do others see this from their Logos Wine installs (that it won't update to newer feature releases?)

    I'm at version 8.8 SR-1 | 8.8.0.0046 (32 bit) (from Help > About). I've run "Update now" a number of times over the past couple of weeks and I'm always told there are no updates available. Based on the "Release Notes" page, I'm stuck back in October 2019... Just looking at the details of the releases, though, it doesn't look like I'm missing much--a few bug fixes that haven't affected me. The 8.11 and 8.12 releases have a heap of new features and fixes, but it looks like those are just for "gold" package owners.
  • Rik Shaw
    Rik Shaw Member Posts: 77

    Paul,

    You can run wasta-logos-setup to apply the 8.9.x that is now part of wasta-logos-installer. It will do an inplace update to your Logos so that it won't lose your resources, indexes, etc. (but please make a backup copy of your ~/.wine-logos FIRST just to make sure you will be safe).

    Later I am happy to move the wasta-logos-installer to 8.10.x or up to 8.12.x if we feel that the "RC" ("gold") version is safe. Maybe to be safe we should wait for it to be out of "RC" ("release candidate") status.

    Rik

  • Paul Unger
    Paul Unger Member Posts: 220

    Rik Shaw said:

    You can run wasta-logos-setup to apply the 8.9.x that is now part of wasta-logos-installer. It will do an inplace update to your Logos so that it won't lose your resources, indexes, etc. (but please make a backup copy of your ~/.wine-logos FIRST just to make sure you will be safe).

    Is this the only way to update to a more recent version number? Download the installer package when prompted by Software Updater, and then run wasta-logos-setup in the Terminal? Logos won't do so on its own? Nor Software Updater, for that matter (i.e., I have to run wasta-logos-setup after Software Updater has downloaded the installer package)? If so, that's fine--I'm just curious. And a bit unsure of the steps...
  • Rik Shaw
    Rik Shaw Member Posts: 77

    Is this the only way to update to a more recent version number? Download the installer package when prompted by Software Updater, and then run wasta-logos-setup in the Terminal? Logos won't do so on its own? Nor Software Updater, for that matter (i.e., I have to run wasta-logos-setup after Software Updater has downloaded the installer package)? If so, that's fine--I'm just curious. And a bit unsure of the steps...

    Paul, It is *definitely* a workaround, I am not sure of other users if they are able to have Logos update itself or not, but this is again a *workaround* until we can sort out *why* Logos isn't updating itself (it used to, so I am not sure if it is a settings change or??)

    Do other users have any comments on if Logos is updating for them or not?

  • Rik Shaw said:

    Do other users have any comments on if Logos is updating for them or not?

    Yes, it is.

    But i'm not using wasta-wine, so maybe it isn't relevant.

  • Rik Shaw
    Rik Shaw Member Posts: 77

    Rik Shaw said:

    Do other users have any comments on if Logos is updating for them or not?

    Yes, it is.

    But i'm not using wasta-wine, so maybe it isn't relevant.

    Daniel, what version are you now on, compared to what version was originally installed? Just trying to figure if it is because it won't migrate "major" versions or?? And is there a setting you know of about enabling / disabling updates (distinct from the general "use internet" option)?