I had Logos 6 Beta open earlier and saw there was an update. When I quit, I cannot get the program to reopen at all. I have rebooted my Mac three times, to no avail.
What is my next step?
Robert Dean
When I attempt to open, only Logos and Edit menus show in the menu bar. When I click on Logos, four drop down options appear, all are "Untitled." I am running a MacBook pro OSX 10.11.1
One suggestion is using Apple Store to update OS X since 10.11.4 includes graphic driver updates => https://support.apple.com/en-us/HT206167
Humanly would like to look at Logos diagnostic log files => https://www.logos.com/support/logos6/mac/report-problem (please use paper clip to attach log files)
Manual update of Logos 6 application could be done using Mac link in => *IMPORTANT* Beta Testing Information/Warnings
Keep Smiling [:)]
I hope this helps
8156.LogosLogs.rldeanjr.20160405-173216.zip
I haven't a clue what to do once I got to the Apple support page.
Suggest using Mac App Store to install OS X Updates => https://support.apple.com/en-us/HT201541
FYI: Apple Support has list of Security Updates => https://support.apple.com/en-us/HT201222 that shows OS X 10.11.4 was released on 21 Mar 2016
This sounds like an issue from half a year ago. I'm not near a computer to read your logs. What version were you using?
Any thoughts on reinstalling Logos would be greatly appreciated. I am leaving on a 3 day Bible conference this morning, and will need to reinstall when I arrive this afternoon.
I have the latest beta update before the one that messed up yesterday
did you simply delete the engine, download the newest one and reinstall? Everything else is left in place.
I had Logos 6 Beta open earlier and saw there was an update. When I quit, I cannot get the program to reopen at all. I have rebooted my Mac three times, to no avail. What is my next step?
I'm not a Mac person, but since it seems those were not able to help you immediately, I'll just share my thoughts:
What you describe sounds compatible with observing a security feature that prevents recently changed programs from running / accessing the internet in order to curb malicious software. It could be that you need to tell your Mac OS or another security software on your machine that the new version of Logos is "safe" (my PC is secured by McAfee and I have to grant internet access to each new Logos beta version anew).
Let's please make this simple. Please give me the link to reinstall. It's been a long time since I last did that so I don't remember off the top or bottom of my head what the steps are to reinstall.
Please give me the link to reinstall.
Links to reinstall the beta version are at https://community.logos.com/forums/t/52967.aspx
Links to install the stable version are at https://www.logos.com/install
Please note that if you have had the beta version installed you can't just install the stable version over it. You would need to remove the existing files from your disk first.
Thanks Graham. Do i need to uninstall anything before I reinstall the beta?
Do i need to uninstall anything before I reinstall the beta?
No - you should be fine.
EDIT: On second thoughts I don't use the Mac platform so may be best to wait till someone who does comments on whether anything needs to be done first.
Robert,
Can you upload your error database which can be found at "/Users/rldeanjr/Library/Application Support/Logos4/Data/f0lmhe5x.yrg/Errors/Application/ErrorReportManager.db"? You can then delete that file and it should allow the application to launch successfully.
You can then delete that file and it should allow the application to launch successfully.
I certainly hope this isn't a revisit to the problem from last year. [:S]
When I go to rldeanjr (home) there is no "Library" folder
6811.ErrorReportManager.db
Martin. That did not work. I leave on my next flight and will be online again around 2:45 pacific time
The Library folder is hidden by default in OS X. Hold down the Option key and select Go from the Menu Bar. The Library folder will then appear in the menu list.
Guys, I downloaded the beta version to reinstall. Still doesn't work. At this point, I don't know what I need to do, but apparently the website says I need to uninstall a bunch of files. How? Which ones?
I don't care about getting the beta working again, I need my Logos to work again. So what are the specific steps I need to follow to be able to reinstall a working, stable version of Logos?
Guys, I downloaded the beta version to reinstall. Still doesn't work.
We need updated logs to determine what the issue is.
ok, so tell me how to do updated logs, do not assume I automatically know what this means
Jack Caviness' post (3 up from yours) has links to instructions at the bottom.
The logs are the same as yesterday. why do I need to repeat the same thing. Insanity is doing the same thing over and over and expecting different results.
So what is wrong with the logs from yesterday when it is the same probelm
The only way you should still getting the exact same crash is if the file was not deleted, but without updated logs there is no way for us to confirm that it is the same error or a new one.
Can you please confirm that the file I asked you to delete was actually deleted? You can find the file in Finder by pressing Cmd+Shift+G, typing (or pasting) "/Users/rldeanjr/Library/Application Support/Logos4/Data/f0lmhe5x.yrg/Errors/Application/" into the box, then clicking the "Go" button.
Yes it is deleted
2577.LogosLogs.rldeanjr.20160406-170812.zip
Was the Beta Logos 6 application replaced with Stable ?
Console message shows folder access error:
2016-04-06 17:08:04 Macintosh Logos[974] <Warning>: System.UnauthorizedAccessException: Access to the path "/Users/rldeanjr/Library/Application Support/Logos4/Users" is denied.
Noticed many quarantine data messages for Logos 6 6.10.0.41 preceding access denied
To troubleshoot path access permissions, please open Terminal in the Applications / Utilities folder
cd ~/Library/App*t/Logos4
ls -la
Please copy list output and paste into thread reply. FYI: ls is the list command with -la parameter for long and all files. cd is change directory command using a wildcard for Application Support.
Yes. I tried to replace with stable but it didn't work
You can't do that. When you update the engine, changes are made "under the hood." When you install an old engine, it doesn't know what to do with the changed (newer) files. To install the new beta engine, as always is the case, you can look for a sticky thread at the top of the beta forum which will provide a link.
Here is the current thread: https://community.logos.com/forums/t/124827.aspx
If you open Terminal as Keep Smiling 4 Jesus said, you can type/paste (without the quotes) "sudo chown -R rldeanjr ~/Library/Application\ Support/Logos4" into Terminal, press enter and it will ask you for your password. This command will change the permissions on the Logos4 folder and all subfolders so that you are the owner. This should get you past the current error in your logs.
If Logos still fails to launch, can you please type/paste (without the quotes) "ls -la ~/Library/Application\ Support/Logos4" into Terminal, press enter and post the output along with updated logs?
If you open Terminal as Keep Smiling 4 Jesus said, you can type/paste (without the quotes) "sudo chown -R rldeanjr ~/Library/Application\ Support/Logos4" into Terminal, press enter and it will ask you for your password. This command will change the permissions on the Logos4 folder and all subfolders so that you are the owner. This should get you past the current error in your logs. If Logos still fails to launch, can you please type/paste (without the quotes) "ls -la ~/Library/Application\ Support/Logos4" into Terminal, press enter and post the output along with updated logs?
Thankful for Faithlife developer's guidance.
Also appreciate your high priority goal is a working Logos 6 installation. An option during conference may be:
https://biblia.com
https://app.logos.com
Thread => Updates to app.logos.com and app.verbum.com
To change from Beta to Stable requires more than replacing application plus takes many hour(s). Logos wiki has => https://wiki.logos.com/OS_X_Troubleshooting#Uninstalling_Logos_for_Mac
Personally puzzled by permission issue since the uninstall steps do not change folder permissions.
FYI: 6.11 stable release has target date of Mon 18 Apr.
Keep Smiling for Jesus, If I did this correctly, I pasted the two lines you had into my Terminal and this is what camp up
drwxr-xr-x 3 root 501 102 Apr 6 17:00 .drwx------ 104 rldeanjr 501 3536 Apr 6 17:00 ..drwxr--r-- 2 root 501 68 Apr 6 17:00 Logging
Martin, ok, the Terminal stated
Macintosh:Logos4 rldeanjr$ Macintosh:Logos4 rldeanjr$ sudo chown -R rldeanjr ~/Library/Application\ Support/Logos4WARNING: Improper use of the sudo command could lead to data lossor the deletion of important system files. Please double-check yourtyping when using sudo. Type "man sudo" for more information.To proceed, enter your password, or type Ctrl-C to abort.Password:
An icon which wouldn't copy, but looked like a gray box with a key in it was just after the colon following Password. The location would not accept a cursor to type in the Password (I also wasn't sure which password, but assumed it was my Logos password)
So where do I go from here?
Thank you so much for the help. Very much appreciated.
I attempted to put in my Logos password and my Mac password and neither worked.
Keep Smiling for Jesus, If I did this correctly, I pasted the two lines you had into my Terminal and this is what camp up drwxr-xr-x 3 root 501 102 Apr 6 17:00 .drwx------ 104 rldeanjr 501 3536 Apr 6 17:00 ..drwxr--r-- 2 root 501 68 Apr 6 17:00 Logging
Those permissions are incorrect as only the "root" user has access to write to your Logos4 folder, which is why you are getting the permissions error.
An icon which wouldn't copy, but looked like a gray box with a key in it was just after the colon following Password. The location would not accept a cursor to type in the Password (I also wasn't sure which password, but assumed it was my Logos password) So where do I go from here?
You will not get a normal cursor and you will not see any visible change as you type your password. The password you will need to enter is your Mac user account password so the OS can make the requested changes to the folder permissions.
Martin, I'm not sure this is getting us anywhere. I pasted the command from several posts back, the one beginning with "sudo" and when the Terminal asked for the password I typed it in and it did not accept it. Perhaps there is a way for you to take control of my computer and see for yourself what is going on? Maybe that will save time.
Here is a picture.
I do not have the setup to provide remote assistance, but let me get with someone in Tech support and see if we can't get something worked out this afternoon. Is there a time that would work best for you?
I'm on the West Coast, pacific time. I will be tied up from 1-2:30, but available the rest of the time until about 6 pm
Martin - For his sake, can you redact Robert's phone number after you have it down?
If 3:00pm Pacific time works for you, I will plan on having Tommy and myself call you at that time.
If you open Terminal as Keep Smiling 4 Jesus said, you can type/paste (without the quotes) "sudo chown -R rldeanjr ~/Library/Application\ Support/Logos4" into Terminal, press enter and it will ask you for your password.
[:$] Terminal command for root to change ownership and group of rldeanjr's Logos4 folder should be:
sudo chown -R rldeanjr:staff /Users/rldeanjr/Library/Application\ Support/Logos4
FYI: when sudo (super user do) command is used, current user becomes root so ~/Library resolves to /var/root/Library (since Logos4 should not exist in /var/root/Library/Application Support folder, no harm should have been done from previous command). List output shows 501 for group, which happens when group for number 501 does not exist. First user created on OS X has default number of 501 along with default group of staff (20).
After changing rldeanjr's Logos4 folder ownership and group, please run list command:
ls -la ~/Library/Application\ Support/Logos4
Suspect folder permissions modification would be appropriate (since Logging had 744 permissions)
chmod -R 755 /Users/rldeanjr/Library/Application\ Support/Logos4
FYI: when sudo (super user do) command is used, current user becomes root so ~/Library resolves to /var/root/Library (since Logos4 should not exist in /var/root/Library/Application Support folder, no harm should have been done from previous command).
The ~ should be resolved before elevation due to the sudo command (it does on 10.11 and prior) so the command given was correct. This can be trivially verified with sudo echo ~.
FYI: when sudo (super user do) command is used, current user becomes root so ~/Library resolves to /var/root/Library (since Logos4 should not exist in /var/root/Library/Application Support folder, no harm should have been done from previous command). The ~ should be resolved before elevation due to the sudo command (it does on 10.11 and prior) so the command given was correct. This can be trivially verified with sudo echo ~.
Thanks; using OS X 10.10.5 trivial elevation showed user path for ~ (along with sudo whoami showing root).
Sorry, I was at a lunch meeting that lasted much longer than I anticipated. I am now once again available until 6 pm
Thanks for all of your help Martin, and Keep Smiling 4 Jesus:)!!!!! All has been restored and seemed to be functional. Thank you so much!!!
