Logos loads, but never shows a screen. I can't even tell you what version I'm running, because of this.
I've force-quit, I've rebooted, all to no avail. Suggestions?
I'm on a 2010 imac with 100Gb free on my SSD, 16Gb RAM, latest build of Sierra.
When this has popped up in the past, one potential solution was to try opening the app from the application folder (rather than the dock). If that doesn't work, tryi downloading and installing the engine again manually.
I did that. I've also deleted Logos, redownloaded (just the DMG) and reinstalled, and get the same thing. I guess my option now is a full delete of all settings and files and reinstall...
Has Mac been restarted ?
Any Log files ? => https://www.logos.com/support/mac/report-problem
Keep Smiling [:)]
Here's a log.7220.LogosLogs.BenSpackman.20170911-201746.zip
FL has not been forthcoming about this problem and it is irritating. [:@]
Does Activity Monitor show LogosSplashScreen or Logos Indexer running ? If so, suggest force quit followed by launching Logos.
Console Messages has many warnings about LogosSplashScreen already running:
LogosSplashScreen[5594] <Warning>: LogosSplashScreen.app is already running (5593), exiting splash screen now.
No, only Logos.
Has Logos application been dragged from DMG to a folder: e.g. Applications followed by launching from that folder ?
FYI: Logos application cannot run from downloaded DMG. Logos 6 support for Mac shows dragging => https://www.logos.com/support/install_logos_6
Yes, I try running it from the Applications folder.
Puzzling so suggest contacting Faithlife technical support => https://www.logos.com/contact
I'm having the same problem - please post if you find a fix - thanks.
Welcome to the forums! Sorry you are having troubles. [:s]
Your problem may or may not have anything to do with the issue of the OP. Please create a new thread, provide appropriate details and post logs. See my signature line for instructions.
I'm having similar problems. It was running fine on my Mac Air, from 2012. Bought an iMac last month and imported everything from time machine and Logos is acting up. Much slower than the Air and this processor is so much faster, with more memory and disk space!
It's slow but also freezes usually when I get back from sleep mode, I think.
imported everything from time machine
That may be the problem, but as I recommended before, please create a new thread, explain your issue clearly, provide appropriate details including logs.
As it turns out, I had overzealously deleted some key files which inexplicably reside in a "Logos 4" folder. Reinstall fixed this, obviously.
I followed the instructions for the full removal (remove all traces of the program) from https://www.logos.com/support/mac/L3/reinstall , then reinstalled and it corrected the issue. Thanks
which inexplicably reside in a "Logos 4" folder.
FL made a poor design choice MANY years ago, which impacts installations in the present. Because of this, even brand new installations must go into a folder named "Logos 4."
I Have same problem too!
When I try to launch directly from the inside package of the logos app I receive this in Terminal:
Last login: Tue Sep 26 16:37:31 on ttys000
Frederics-MacBook-Pro:~ frederic$ /Applications/Logos.app/Contents/MacOS/Logos ; exit;
2017-09-26 16:38:42.651 Logos[2094:114631] *** WARNING: Textured window <NSPanel: 0x7fe354dac590> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.
Where can I send my logs (I used the log utility for logos software) ?? Full of errors in these logs...
Two options:
Thanks I did it. Now I wait for the technical support about it.
I found the solution !!!
Go to this link: https://www.logos.com/support/logos6/mac/crash and then apply the solution 2. It was a access rights on my account problem.
Ouf! (as we say in French). But as a Christian I prefer to say "Thanks God!".
The lesson: to be patient :-)
Alabama, it would really be nice if Logos / FL would think about correcting issue connected with having the "Logos 4" folder
Based on my impression from a post MANY years ago, it won't ever happen unless/until FL moves away from the current base code. If a new release is SO different that users can't simply "update" the engine, but have to perform a clean install... then it might happen.
