Linux version of Logos Bible Software
Comments
-
Just completed the upgrade to Kubuntu 20.04 - everything is running the same in regard to Logos. No issues found with the OS upgrade thus far. Seems the one drawback may be not having access to upgrading Wine, until they add a Focal repository
Logos 10 - OpenSuse Tumbleweed, Windows 11, Android 16 & Android 14
0 -
Hi Daniel, thank you for your work on this. I followed the steps and everything looks like it installed correctly, but when I try to launch Logos I get target not found: /home/u/Desktop/Logos.sh.
I do see the Logos.sh in Desktop. Is there a different way I should launch this that I'm missing?
Running Manjaro Gnome
Husband, Dad, Expat to Northern Europe. I serve people, share hope, & write about simple theology for a messy life at genewhitehead.com.
0 -
Gene,
From a command prompt in a terminal, run ./Logos.sh
That's what I have to do in Ubuntu because the launch icon doesn't work.
0 -
Hi Gene,
I don't know if you've checked these things.
Your user name must be "u" so check permissions.Open terminal, and list the Desktop folder.ls /home/u/Desktop/Is Logos.sh there?If it is, check permissions using terminal.ls -l /home/u/Desktop/Logos.shYou should get back something similar to this. Ignore the numbers as I made those up:-rwxrwxrwx 2 u u 652 Jan 12 2020 Logos.shJust look at the -rwxrwxrwx and the ownership names "u u" as the file name, the rest I just made up.The parts that important are that there are x's in the first part and that your user name owns the file.Become root and chmod if you don't see rwxrwxrwx and chown if you don't own the file. Either condition will cause that error.Regards,David0 -
Gene W. said:
Hi Daniel, thank you for your work on this. I followed the steps and everything looks like it installed correctly, but when I try to launch Logos I get target not found: /home/u/Desktop/Logos.sh.
I do see the Logos.sh in Desktop. Is there a different way I should launch this that I'm missing?
Running Manjaro Gnome
You can use the same that the script at the end of installation run:
$HOME/Desktop/Logos.sh
But you should be able to run it from your Desktop with a double click (or using right click and on the "Run" option). If you have some bug/suggestion/comment... you can post a issue HERE too.
0 -
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
0 -
Ollie Pindakaas said:
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
I will wait for the release of "wine staging x86 v5.0" from playonlinux. They were able to compile only the "wine upstream x86 v5.0" version, but the "wine staging x86 v5.0" got an error. And I feel that the wine developers don't consider this v5.0 stable, but that they want to forget about supporting previous versions (because it hasn't had many tests yet).
0 -
John Goodman said:
I want us to be in the top 25, ideally ahead of the watchtower library app;)
*Done* [8-|]
Many greetings
Marc0 -
Ollie Pindakaas said:
It seems that there is a new wine-stable: wine 5.0-stable, which works only with FAudio. I didnt have the time to check it out...
Maybe are these three videos on YouTube helpful:
- Wine 5.0 on Ubuntu 19.10 > [View:
https://www.youtube.com/watch?v=uE-73Hjfy7s:550:0]- Wine 5.0 on ubuntu 18.04 > [View:
https://www.youtube.com/watch?v=sj08gKkHDpY:550:0]- Wine 5.0 on Mint 19.3 > [View:
https://www.youtube.com/watch?v=T6epKRoHpRw:550:0]0 -
Marc Zoellner said:John Goodman said:
I want us to be in the top 25, ideally ahead of the watchtower library app;)
*Done*
Many greetings
MarcAwesome! This is not just very helpful but also great witness! Well done folks.
גַּם־חֹשֶׁךְ֮ לֹֽא־יַחְשִׁ֪יךְ מִ֫מֶּ֥ךָ וְ֭לַיְלָה כַּיּ֣וֹם יָאִ֑יר כַּ֝חֲשֵׁיכָ֗ה כָּאוֹרָֽה
0 -
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 said: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 winxpThis returned the error: "winxp: command not found"...
Frank Sauer said: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.
0 -
Paul Unger said:
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
0 -
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 said: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
0 -
Download the script that is here.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 DownloadsYou will have LogosIndexing.sh in the Downloads folder.Become root. Use su to do that and give the root password.suYour 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.shNow 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.shWhen 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
0 -
Paul Unger said:
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
0 -
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?
0 -
Paul Unger said:
...
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.
0 -
Well, that's where I started, Daniel. :-P Asking how to perform an instruction from Frank Sauer's post:
Frank Sauer said: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 said: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.
0 -
Paul Unger said:
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.
0 -
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).
0 -
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 said: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).
0 -
Paul Unger said:
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.
0 -
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.
0 -
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
0 -
@ 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... :-(
0 -
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.
0 -
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.exe0 -
I’m running Logos in an Ubuntu 18.04 container on my Pixelbook and the fonts render fine. Perhaps ChromeOS have fonts figured out.
0 -
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.
0 -
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...]
0 -
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...
0 -
Ollie Pindakaas said:
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
0 -
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
0 -
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).
0 -
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!
0 -
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.
Paul Unger said: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
0 -
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!
0 -
https://askzorin.com/c/logos-bible-software-linux/13 Discussion form for Linux
0 -
"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?
0 -
Paul Unger said:
"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)
0 -
Thanks! I kind of thought that was the case, but just wanted to confirm it.
0 -
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
0 -
@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?
0 -
James Hudson said:
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
0 -
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 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?)
0 -
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
0 -
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 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).
0 -
Paul Unger said:
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?
0 -
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.
0 -
Daniel Ribeiro da Silva said: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)?
0
