Apple Users - CAREFUL about installing El Capitan

El Capitan is the latest Mac OS. The public beta was released today. Yesterday the developer version was released, and prevented Logos from starting up.

I don't know if the public beta released today is the same as the developer beta released yesterday, but I don't want to find out. I spent several hours last night reloading my system.

So, for the time present, don't upgrade to the El Capitan public beta if you truly need Logos for your work (as I do).

Greg Lawhorn

Find more posts tagged with

Comments

FrMoses

Yes, same issue here, unfortunately.

_____

Process: Logos [685]

Path: /Applications/Logos.app/Contents/MacOS/Logos
Identifier: com.logos.Logos
Version: 6.4.0.65 (61640.0.65)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logos [685]
User ID: 502

Date/Time: 2015-07-09 13:40:31.119 -0700
OS Version: Mac OS X 10.11 (15A215h)
Report Version: 11
Anonymous UUID: B1C9DD2D-F8EF-5E26-6029-8E0D522AC999

Time Awake Since Boot: 240 seconds

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff85112076 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff88ea863d pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8c57e83b abort + 129
3 libmonosgen-2.0.1.dylib 0x00000001054a2968 monoeg_g_logv + 280
4 libmonosgen-2.0.1.dylib 0x00000001054a2ad9 monoeg_g_log + 361
5 libmonosgen-2.0.1.dylib 0x000000010549b823 mono_mach_init + 291
6 libmonosgen-2.0.1.dylib 0x0000000105499265 mono_threads_init + 373
7 libmonosgen-2.0.1.dylib 0x00000001053f76fc mono_gc_base_init + 444
8 libmonosgen-2.0.1.dylib 0x000000010534fbd1 mono_debug_init + 177
9 com.logos.MonoHost 0x0000000109bdf14b +[MonoHost initializeMonoRuntimeWithDirectoryPrefix:frameworkVersion:andAssembly:andArguments:] + 2015
10 com.logos.ApplicationBundle 0x0000000104022d2c -[OurAppController applicationDidFinishLaunching:] + 153
11 com.apple.CoreFoundation 0x00007fff81b9b64c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
12 com.apple.CoreFoundation 0x00007fff81b9b5bf ___CFXRegistrationPost_block_invoke + 63
13 com.apple.CoreFoundation 0x00007fff81b9ac87 _CFXRegistrationPost + 407
14 com.apple.CoreFoundation 0x00007fff81b9a9f2 ___CFXNotificationPost_block_invoke + 50
15 com.apple.CoreFoundation 0x00007fff81b96e92 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1938
16 com.apple.CoreFoundation 0x00007fff81a84293 _CFXNotificationPost + 675
17 com.apple.Foundation 0x00007fff84b28bdd -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
18 com.apple.AppKit 0x00007fff839bcdd5 -[NSApplication _postDidFinishNotification] + 297
19 com.apple.AppKit 0x00007fff839bcb47 -[NSApplication _sendFinishLaunchingNotification] + 203
20 com.apple.AppKit 0x00007fff839ba065 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 557
21 com.apple.AppKit 0x00007fff839b9b0f -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 250
22 com.apple.Foundation 0x00007fff84b5ab61 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 290
23 com.apple.Foundation 0x00007fff84b5a9db _NSAppleEventManagerGenericHandler + 102
24 com.apple.AE 0x00007fff81f17408 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 531
25 com.apple.AE 0x00007fff81f1718f dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 31
26 com.apple.AE 0x00007fff81f170ab aeProcessAppleEvent + 288
27 com.apple.HIToolbox 0x00007fff86772ea5 AEProcessAppleEvent + 55
28 com.apple.AppKit 0x00007fff839b3c4f _DPSNextEvent + 2148
29 com.apple.AppKit 0x00007fff83d815c9 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 343
30 com.apple.AppKit 0x00007fff839a96dc -[NSApplication run] + 682
31 com.logos.Logos 0x00000001010e7c42 DesktopApplicationMain + 518
32 com.logos.Logos 0x00000001010e7cb2 main + 9
33 libdyld.dylib 0x00007fff8aa005ad start + 1

Charles

So, for the time present, don't upgrade to the El Capitan public beta if you truly need Logos for your work (as I do).

Good advice. Some time ago I posted how I deal with beta versions of OS X, or as of late, the MS Office 2016 Preview. I clone my hard drive (using Carbon Copy Cloner) to an external USB 3 hard drive where I install the beta or Preview. I then boot from the external drive and do my testing that way. This keeps the beta and Preview off the main church computer (iMac). If it crashes, I can always erase the external hard drive, make another clone and start over.

In Christ,

Charles

Ed Stone

https://community.logos.com/discussion/comment/748088#Comment_748088

I am on Capitan as well and Logos is crashing for me too.

Cody Lekan

Has anyone herd of when support for El Captain will be up and running? I upgraded to El Captain and need Logos. I am traveling this summer and can't get back to my back up drive to undo the upgrade but still need access to Logos. Any ideas ???

JT (alabama24)

https://community.logos.com/discussion/comment/748447#Comment_748447

Has anyone herd of when support for El Captain will be up and running?

Sorry for your troubles Cody! [:s]

Faithlife doesn't support thier applications (desktop, mobile) on beta OS versions. In other words, users who experiment with beta are "on their own." The answer to your question is really, "we don't know." It is likely, but not guaranteed, that it will be ready by release date. Most of the time it is... but at least once I can remember FL recommended waiting a couple of days.

Your only options (neither good): 1) reinstall Yosemite or 2) wait for a compatible engine. If you choose the later, keep an eye on the beta forum.

Cody Lekan

https://community.logos.com/discussion/comment/748450#Comment_748450

Thank you for getting back to me so fast! Should I be looking for the update to fix the crash through apple or through faith life?

https://community.logos.com/discussion/comment/748461#Comment_748461

Apple released the update to resolve the 32 bit problems, but logos still crashes...seriously frustrating (especially since logos responses are 1. that it's apple's fault, and 2. that the crashes are due to the 32 bit apps not running in el capitan)...

JT (alabama24)

https://community.logos.com/discussion/comment/748461#Comment_748461

Thank you for getting back to me so fast! Should I be looking for the update to fix the crash through apple or through faith life?

You should occasionally peruse the BETA FORUM. Look for release notes for beta versions.

I would be remiss not to add: ALL beta software is intended for developers to get feedback on software. If you beta test long enough, you WILL have crashes. You WILL have to reinstall. You should NOT use any beta software on "production" computers (i.e. one you need for work).

JT (alabama24)

https://community.logos.com/discussion/comment/748467#Comment_748467

especially since logos responses are 1. that it's apple's fault, and 2. that the crashes are due to the 32 bit apps not running in el capitan

With all due respect: Beta software is not intended for "production" computers. I feel sorry for you and have compassion... I have been there... but it is your fault. Don't pass the blame to apple or logos. In both cases, warnings were provided, which you ignored. [;)]

https://community.logos.com/discussion/comment/748470#Comment_748470

The winky face does not make your comment more friendly. There were warnings from Apple, though not much from logos. I wasn't blaming Apple actually, though logos staff seems to be doing that on many threads. Perhaps warnings of some sort would be taken more seriously if logos hadn't formerly worked in the developer beta (note: a beta versio), which kind of negates your refrain that it doesn't run in beta. The frustration, which I think is legitimate, is that the developer beta was very shaky; yet, when Apple releases the public beta it is almost always stable but needs a few very minor tweaks. So, (a) it doesn't make sense that the logos policy to not run in beta would work in the unstable developer beta but not in the stable versio. (B) if, as other logos reps have been saying, it was a problem with the 32 bit apps, then it would mean that logos would work after the update released today. Lastly, many of your comments encourage returning to Yosemite, which is terrible advice in general, as the process would likely cost customers the data they thought was backed up but was actually wiped after their update. An unfortunate quirk of Time Machine for which there is also little to no warning

JT (alabama24)

https://community.logos.com/discussion/comment/748479#Comment_748479

I am sorry you are upset David, but you don't understand the purpose of beta testing. It isn't "hey I want to get the coolest thing first." Beta testing means "Oh no, my computer crashed and I have to wipe it clean." The purpose of beta testing is to find bugs. Bits and pieces get added along the way which WILL cause incompatibilities with other components and software. Beta 2 might cause more problems than Beta 1. Your claim of Apple public beta's being "almost always stable" is particularly interesting since the FIRST ever "public beta" of OS X was only last year.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/748479#Comment_748479

(B) if, as other logos reps have been saying, it was a problem with the 32 bit apps, then it would mean that logos would work after the update released today

I could be mistaken, but I don't think any Faithlife employees have been claiming this (because Logos has been a 64-bit application on Mac for some time).

Stewart Robertson

https://community.logos.com/discussion/comment/748506#Comment_748506

Hi Bradley,

Thanks for your input. Being that the Beta is in the wild and that testing at the Alpha level has been underway for some time, do you have any internal snapshot as to the reason that El Capitan has broken your application?

Dave Hooton

https://community.logos.com/discussion/comment/748479#Comment_748479

Perhaps warnings of some sort would be taken more seriously if logos hadn't formerly worked in the developer beta (note: a beta versio), which kind of negates your refrain that it doesn't run in beta.

You shouldn't assume that programs you rely upon will work in a beta OS, and you should heed the warnings from Apple about running a beta OS. It is not the responsibility of Faithlife, nor any other third-party software provider. Exactly the same applies to Windows users, but we have been fortunate that Logos works in Windows 10. Even so, I always run a beta/preview OS in the safety of a virtual machine.

Travis Marsh

I know this isn't what you might like as a beta tester but this is why there is beta testing in my opinion. This is great because now people can focus on this issue and get it resolved.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/748685#Comment_748685

do you have any internal snapshot as to the reason that El Capitan has broken your application?

No, sorry, I haven't heard yet from the developers who were looking into the problem.

https://community.logos.com/discussion/comment/748688#Comment_748688

All,

Thank you for your many efforts to point out something that I already - viz. the accepted risks that come with using a beta version that is still being developed. To the person who continues to troll me in multiple posts [not you, dave]- (1) I sincerely hope that you don't represent Faithlife/Logos, but are just someone with a superfluous amount of time spent correcting people in online forums. (2) If you do represent either, then I think you should adjust your tone - the condescension is off putting (it's in posts to others as well). (3) Thank you, however, for deigning to give me the wikipedia explanation of "beta" software as if I had been raised without electricity and just tried using OSX for the first time. Acting that way definitely enabled you to understand what I was saying...*shazam* issues resolved! (4) I have been enrolled in beta software on different platforms and know the potential risks/rewards, as well as some basics of coding/development - I posted my original frustration, not because I couldn't read the giant letters on the apple developer site and was naive enough to think, 'gee aint this swell' only to later complain that beta isn't polished/complete (stop correcting adjectival usage). But in response to your repeated claim that it has long been Logos policy to not run in a beta OSX. (5) someone from Faithlife actually cleared this up elsewhere...that's nonsense. But you may have misspoken. Perhaps, I should explain to you the purpose of a Q&A forum in a way that suggests you know nothing about the internet (it was invented by Al Gore, or was it GHW Bush? Ted Cruz? [before I wake any more trolls - I don't actually think any of that, and I'm not interested in any theories on the subject]). (6) Most importantly, in case this isn't clear for some reason - adding a cheery emoji to a condescending litany that insults someone's intelligence, does not change the comments from what they really are - presumptuous and, well, it might make more sense this way: 💩...a smily face added to a swirl of poo.

Lastly, though I should have seen it coming, this has been an utterly useless endeavor that has yielded no substantive responses. So, in an effort to keep my battles with trolls on matters political and theological...I'm extricating myself from under the bridge. It's funny how often it seems that people who develop software assume they have fully understood other people's intelligence. I really have neither the energy nor interest in defending mine and correcting a zillion posts that say i'm blaming apple (I'm not) or that I believe Faithlife screwed me somehow (they didn't). For the record, I'm a big fan of Faithlife software - and Logos is, in my opinion the most comprehensive and efficient program of its kind (I have accordance as well for syriac). My initial issue was based not upon a misunderstanding of apple, or beta software, but the assumption that a particular post was made on behalf of Faithlife. It wasn't - and an actual rep corrected it. So, I'm sending the e-mail notifications for this feed to junk...if you wish to keep correcting illusory issues that I supposedly think then feel free, I won't get them.

A parting thought about other attempts to inform me about the meaning of a "beta" version:

MJ. Smith

https://community.logos.com/discussion/comment/748709#Comment_748709

A parting thought about other attempts to inform me about the meaning of a "beta" version:

Frequently, individuals in the forums are not familiar with beta protocols. I am sorry that you felt the reminders were insulting but in the majority of cases they would have been appropriate. As you clearly know "it's silly, very silly indeed" to expect support when running a beta OS. As fellow Logos users we know Logos not Apple OS's.