Have never been able to get app to launch. Up to 23 bounces in the dock then, bye bye. I keep hoping the next release will be the one.
Here is the crash report:
[View:http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/75/8475.crash_5F00_log.txt:550:0]
Love to begin having the more normal problems.
I'm having the same problem, although I was able to get the program to launch with A1-3. For some reason from A4 it won't launch. I've deleted and reinstalled to no avail. Looking forward to a solution.
Brian, what are your system specs?
2 GHz Intel Core Duo
2 GB 667 MHz DDR2 SDRAM
OS X 10.5.8
Hard drive: Capacity: 297.77 GB
Available: 129.33 GB
Writable: Yes
File System: Case-sensitive Journaled HFS+
Ah. okay. At first I thought it might be something simple like you were using a Power PC (which is not supported), but I don't see any problems with your specs. Wish I could do more, but the techs will have to solve this one.
Terry Brown:I'm having the same problem, although I was able to get the program to launch with A1-3. For some reason from A4 it won't launch. I've deleted and reinstalled to no avail. Looking forward to a solution.
When you delete it, are you deleting just the application or are you also deleting all the supporting data? The Logos techies need to correct me here, but in addition to using a removal programme like AppZapper, you need to insure that under your home directory that the Library-->Application Support-->Logos4 directory is deleted. The reason for this is that if you just delete the Logos 4 application, all the data in this directory which is causing your problem will still exist when you do a reinstall.
Thank you, AppZapper was missing that file. However, after deleting it and emptying the trash, a new install has resulted in the same 23 bounces and no love.
Can you post your log?
Here's the crash report.
7206.crash_log.txt
The Logos techies are going to have to step in here and look at this. The big difference between your setup and mine is that you are running OSX 10.5.8, but that should not matter because that is a supported version for Logos for Mac.
Donovan R. Palmer: The Logos techies are going to have to step in here and look at this. The big difference between your setup and mine is that you are running OSX 10.5.8, but that should not matter because that is a supported version for Logos for Mac.
I am running 10.5.8 with limited problems. Occasionally L4 does dribble full court* before launch, but so far it has always opened.
*that means it bounces a lot before settling down to work.
Enable-and-Submit-Log-Files | Install
BrianKnapp: Here's the crash report. 7206.crash_log.txt
Can you please post your Logos4.log and Indexer.log files. Instructions can be found here: http://community.logos.com/forums/t/6731.aspx
Mac DeveloperFaithlife
Donovan R. Palmer:…in addition to using a removal programme like AppZapper…
There's no need to use AppZapper or anything like it. The application bundle and the contents of the folder in ~/Library/Application Support are the only files we create. If you find files from Logos 4 anywhere else, it's a bug and should be reported.
David Mitchell Development Lead Faithlife
David Mitchell: Donovan R. Palmer:…in addition to using a removal programme like AppZapper… There's no need to use AppZapper or anything like it. The application bundle and the contents of the folder in ~/Library/Application Support are the only files we create. If you find files from Logos 4 anywhere else, it's a bug and should be reported.
David
When I have installed each Alpha drop, AppTrap always requests permission to delete two files. If this happens with the next drop, I will let you know what they are.
I was trying to do this, but there is no logos4.log
Also when I tried to open nlog.config I got a message saying there was no default program to open it.
BrianKnapp:Also when I tried to open nlog.config I got a message saying there was no default program to open it.
In trying to follow the instructions, it was the only file in the logging folder and I thought maybe that was how to open the Console.
BrianKnapp: In trying to follow the instructions, it was the only file in the logging folder and I thought maybe that was how to open the Console.
There's actually an application called Console that is included in Mac OS X. Your Console messages are what will likely contain helpful info. The lack of a Logos4.log is a symptom of the issue -- it would be created by the application, but it isn't actually launching successfully.
Director of Engineering for Enterprise and Operations
Got a disk in the mail. Got this when I put it in.
I realize this is an older build, I just thought it was interesting it doesn't look like installing is even an option.