Linux version of Logos Bible Software

Page 44 of 49 (964 items) « First ... < Previous 42 43 44 45 46 Next > ... Last »
This post has 963 Replies | 52 Followers

Posts 1041
John Goodman | Forum Activity | Replied: Tue, Jan 28 2020 3:25 PM

Marc Zoellner:

John Goodman:
I want us to be in the top 25, ideally ahead of the watchtower library app;)

*Done* Geeked

Many greetings
Marc

Awesome! This is not just very helpful but also great witness! Well done folks.

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

Posts 122
Paul Unger | Forum Activity | Replied: Sat, Feb 1 2020 7:19 AM

I'm having issues with indexing, as in, it churns away for a couple of hours and then throws an error. I found this post, which looks promising. Unfortunately, I don't understand how to do this step:

Frank Sauer:
After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.

Could someone break that down for a new linux user? Much appreciated,

Paul

[later...] I found a little snippet on the Logos 8 WineHQ page:

If indexing fails:
Set windows version for indexing
WINEPREFIX=$HOME/.wine-logos/winetricks winxp

This returned the error: "winxp: command not found"...

Frank Sauer:

Hopefully this is some good news....

I am running:

Kubuntu 19.10

Wine Staging 5.0 RC2 64 Bit

Logos 64 Bit

The indexer as has been noted was almost instantly crashing and changing the winecfg to Win XP as default nor as Win XP just for LogosIndexer.exe changed nothing - consistent crashes.

I decided to dig into the file system of Logos to see if I noticed any of the funky file issues we had way back in the beginning of the Beta testing days, when the indexer was first being introduced and quite volatile in behavior.

The Bible Index and Library index folders looked fine - the Personal Book index folder has a mess in it - a sign that there was possibly some corrupt files in there.

So I decided to clean out those directories after making sure that Logos.exe and Logoeindexer.exe were not running.

After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.

The indexer immediately started, the laptop went into full overdrive as the indexer is known to do and some time later - no crashes and a completed index running Logos 64 bit under Wine 64 bit. (this is Wine Staging 5.0 RC2 64 Bit)

The three folders should have 9 files in them - any more or any less and something is incomplete or corrupt.

The folders are located in:

/home/username/wineprefixfolder/drive_c/users/username/Local Settings/Application Data/Logos/Data/randomLogosnamedfolder

Replace the italicized portions of the path with you personal setup to get to the correct folder.

In the folder the three folders you want to check are:

BibleIndex

LibraryIndex

PersonalBookIndex

Each should have 9 files and the size all depends on the number of resources you have in your library (it can be many Gigs) - again any more or any less than 9 and that could be the issue. **(The 9 files is based upon my experience with successful installs and from my fully indexed Windows and Linux installs - Logos developers may know otherwise - purely a user experience observance)

To try out what worked for me you can delete the contents of each of those three folders or mock delete them by creating a folder in each and moving each folder's contents to the new folder.

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Sat, Feb 1 2020 4:18 PM

Paul Unger:

I'm having issues with indexing, as in, it churns away for a couple of hours and then throws an error. I found this post, which looks promising. Unfortunately, I don't understand how to do this step:

...

Download and use this script: https://github.com/ferion11/LogosLinuxInstaller/releases/download/v1.3/LogosIndexing.sh

Any issue with this, you can post here: https://github.com/ferion11/LogosLinuxInstaller/issues

:)

Posts 122
Paul Unger | Forum Activity | Replied: Sat, Feb 1 2020 6:35 PM

Hi Daniel,

Thanks for offering to help. I don't know if you saw all of my post, but I'm a new Linux user, so: a) I don't know what you mean when you say to "use this script"--how?; and b) I wouldn't mind learning what's going on in your script. Maybe b) is asking too much...; but be that as it may, I definitely need help with a)!

Thanks,

Paul

Daniel Ribeiro da Silva:

Posts 76
David J. Ring, Jr. | Forum Activity | Replied: Sat, Feb 1 2020 7:30 PM
Download the script that is here. https://github.com/ferion11/LogosLinuxInstaller/releases/download/v1.3/LogosIndexing.sh It's easiest to use wget.  If wget isn't installed, install it. Open a terminal in your graphic user interface (GUI) then open a terminal, like mate-terminal or other terminal. Type this: cd Downloads wget https://github.com/ferion11/LogosLinuxInstaller/releases/download/v1.3/LogosIndexing.sh You will have LogosIndexing.sh in the Downloads folder. Become root.  Use su to do that and give the root password. su Your terminal turns from a $ prompt to a # prompt showing you are root. Now you have to chmod the script to make it executable. In terminal type: chmod +x LogosIndexing.sh Now LogosIndexing.sh can be executed. In the same terminal, exit from root and you will be regular user. The prompt will change to $. Type this: ./LogosIndexing.sh When there some file that you want to run and it's not in a regular place that programs are kept (called the "path") you need to put ./ in front of the name of the file.  If the file that you need to run is not in the directory that your prompt is, you need the full path. You can find out where your terminal is open by typing "pwd" which is short for print working directory. If you have any errors, you will be able to read them in your terminal. Just let the script work and work - it takes a long time. Best wishes, David
Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Sat, Feb 1 2020 11:03 PM

Paul Unger:

Hi Daniel,

Thanks for offering to help. I don't know if you saw all of my post, but I'm a new Linux user, so: a) I don't know what you mean when you say to "use this script"--how?; and b) I wouldn't mind learning what's going on in your script. Maybe b) is asking too much...; but be that as it may, I definitely need help with a)!

Thanks,

Paul

Sorry. I always try to be concise here, as most of my comments are moderated by the forum (and take a while to appear).

My scripts don't need "root", so you just need "download" and "execute" ("run"). The "download" part should be just click on the link and the browser (like google-chrome) should download it. The "execute" part can be made by 2 steps:

1- Make it executable (because linux, for security reasons, don't use defaults executables, you have to explicitly said what you want to be one executable). And

1a- Right click on your .sh file and select "Properties".

1b- Click Permissions tab. And Select Allow executing file as a program.

2- Execute it by double-click (or single click, depending on your "File Management Preferences" preferences, because you can change this Behavior on linux).

Something like this: https://www.youtube.com/watch?v=RvKIN_z5QXQ

Posts 122
Paul Unger | Forum Activity | Replied: Sun, Feb 2 2020 7:44 AM

Thanks for the instructions--I appreciate that. Here's how it went: When I ran your script, I got the message, "The /home/username/.wine32 don't exists on your filesystem. Do you want to do Logosindex in another installation?" [No] [Yes]

I clicked [Yes]; selected my Wine Logos installation from the list that appeared; it downloaded something and churned away for about three seconds and then returned this message: "rndll32.exe This application could not be started. Do you want to view information about this issue?" [Yes] [No]

When I selected [Yes] a Windows Troubleshooting page opened in my browser, but the terminal then continued running some "winetricks" operations. After about 30 seconds of various winetricks windows popping up, it said Logos was indexing, and about 20 seconds later I was told it was finished and I was free to open Logos. That seemed incredibly quick, but I went to start Logos, and was told (via a Wine window) that the configuration had changed, and then the same "rundll32.exe This application could not be started. Do you want to view information about this issue?" [Yes] [No] error... When I clicked [Yes] another Windows Troubleshooting page opened in my browser, but Logos went ahead and started and my processor went to work. Opening System Monitor shows that Lgosindexer.ex is using 23% of my CPU (as it was earlier), but there isn't any indication in Logos that indexing is happening (i.e., the notification beside the Sync arrows).

In short, I'm afraid the script didn't work--this is exactly what was happening earlier. And I'm also afraid that my configuration in knackered... :-( Thoughts?

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Sun, Feb 2 2020 3:36 PM

Paul Unger:

...

In short, I'm afraid the script didn't work--this is exactly what was happening earlier. And I'm also afraid that my configuration in knackered... :-( Thoughts?

The Frank Sauer have reported one bug of LogosBible 64bits on linux about this issue: https://community.logos.com/forums/p/121/1081685.aspx#1081685

You could try the same solution. Or just install LogosBible 32bits too.

I know that LogosBible itself have better support on windows 64bits. But the wine 64bits (that run LogosBible on linux) is very new and have a lot of bugs. If you want avoid bugs, you should try the 32bits version.

Posts 122
Paul Unger | Forum Activity | Replied: Mon, Feb 3 2020 8:51 AM

Well, that's where I started, Daniel. :-P Asking how to perform an instruction from Frank Sauer's post:

Frank Sauer:
After this, I double-checked that Logos.exe was set to Win10 and Logosindexer.exe was set to WinXP in winecfg and launched Logos.

Which is when you suggested your script. ;-) Do you know how to do what Frank suggested? Thanks for any instructions, if you do!

Paul

Daniel Ribeiro da Silva:

The Frank Sauer have reported one bug of LogosBible 64bits on linux about this issue: https://community.logos.com/forums/p/121/1081685.aspx#1081685

You could try the same solution. Or just install LogosBible 32bits too.

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Tue, Feb 4 2020 10:25 AM

Paul Unger:

Which is when you suggested your script. ;-) Do you know how to do what Frank suggested? Thanks for any instructions, if you do!

Paul

No. Each Linux distribution has its own compilations for many versions of WINE, and the problem is even worse if we talk about the 64-bit version. I prefer stability. And the 32-bit version works better.

Because of this, my installer uses the 32bits version (inside one AppImage) with all dependencies, in order to ensure that the operation will be the same in all linux distributions. Outside of this, each case is unique.

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Tue, Feb 4 2020 10:35 AM

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).

Posts 122
Paul Unger | Forum Activity | Replied: Tue, Feb 4 2020 10:44 AM

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

Daniel Ribeiro da Silva:

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).

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Tue, Feb 4 2020 11:00 AM

Paul Unger:

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.

Posts 7
Jim Rutledge | Forum Activity | Replied: Sat, Feb 8 2020 10:23 PM

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.

Posts 95
Dirk Kellner | Forum Activity | Replied: Mon, Feb 10 2020 12:06 AM

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

Posts 122
Paul Unger | Forum Activity | Replied: Mon, Feb 10 2020 2:23 PM

@ 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... :-(

Posts 7
Jim Rutledge | Forum Activity | Replied: Mon, Feb 10 2020 10:03 PM

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.

Posts 35
Daniel Ribeiro da Silva | Forum Activity | Replied: Tue, Feb 11 2020 4:27 AM

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

Posts 843
Bill Anderson | Forum Activity | Replied: Tue, Feb 11 2020 6:56 AM

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

Posts 11
Taylor | Forum Activity | Replied: Tue, Feb 11 2020 9:56 AM

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.

Page 44 of 49 (964 items) « First ... < Previous 42 43 44 45 46 Next > ... Last » | RSS