Just throwing this out there...

I am very new to Logos. I just downloaded A4 on Friday and I'm playing around with it as much as I can. I understand Logos 4 Mac is very unstable since it is just an Alpha test. I just want to give the developers a heads up that I had a severe software problem on my mac yesterday morning while trying to access my computer. I couldnt even load OSX. Thinking it was a hard drive problem, I took my computer in to the Apple store but they couldn't find the root of the issue. I have my computer back up and running but the only abnormal activity on my Macbook in recent days has been loading A4. In fact, everything else is very stable and I take great care of my machine. I am beginning to think A4 may have had something to do with the OS failure. I may be completely wrong and I'm not even upset, but I do want to make you guys aware as you continue developing the Alpha releases. If I'm right and A4 caused the issue, I know you would want to check it out. I know there is a long road ahead for you guys and I appreciate the hard work. I look forward to seeing the final product in the next few months. In the meantime, I'm having the previous version of Logos shipped!

In His Grip,
Matt

P.S - Other issues I'm seeing seem to be the same as others - perpetual indexing, can't search, locking up and shutting down when opening resources or accessing the library...

Find more posts tagged with

Comments

Matthew C Jones

I try to stay out of the Mac related posts since I have not attempted to run Logos on my Macs. (I got the initial release under Version 3. Just never tried it after hearing of limitations.) I'm very happy with how Versions 3 & 4 run on my PCs.

In His Grip,
Matt

I just had to comment on your byline. "In His Grip" is so short but packs a whale of a punch. It is a comforting reminder right when I needed one. Also, your post is refreshingly civil, understanding and helpful. Don't be a stranger.

Pat Soliday

https://community.logos.com/discussion/comment/43536#Comment_43536

Hi Matt,

Just to let you know, I experienced the same thing a few days ago (something I have not yet experienced on my Macbook Pro until I installed this Alpha version). I tried everything, resetting the PRAM, removing the battery, etc. The bootup was stuck on the grey screen with the Apple logo and revolving gear. I tried waiting about 20 minutes with the computer in this state with no progress. That's when I assumed it was hung. I was just about to make an appointment with the Apple store but I decided I would wait a little longer, about 30 minutes. Well, after about 30 minutes or more it finally booted up. The only thing I remember I did different was to shut down the computer while Logos4 was still indexing and I remember it took quite awhile to shut down. After hearing your story I'm now sure that Logos4 Alpha had something to do with this.

Pat.

Jonathan Griffiths

https://community.logos.com/discussion/comment/43545#Comment_43545

Oh look at that... me too. And here I was blaming my VMWare Fusion machine. I did permissions repair, and disk repair. Nothing would get it past the initial OS loading screen. Finally I restored from a Time Machine backup and I'm back in the game. So that's three people with the same symptoms - probably A4 at the root of it - do you guys @Logos need more data from us?

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/43552#Comment_43552

Guys,

Sorry to hear about your troubles with booting. This is the first we've heard of this, but we definitely want to see if this is A4 related.

How much free space do you have on your disks?

Can you post your Indexer.log? (See http://community.logos.com/forums/p/3311/27262.aspx for how to post logs).

Thanks,

Tom

Michael Kares

https://community.logos.com/discussion/comment/43561#Comment_43561

Happened to me twice. Never occurred to me it might be related to Logos. I thought it was a different app I was trying out.

Blessings,

Michael Kares

P.S. It was about a week and a half ago, my logs are probably long gone.

Jonathan Griffiths

https://community.logos.com/discussion/comment/43561#Comment_43561

Not sure indexer logs will be much use since I've had to rebuild my mac from a TimeMachine backup, but if you think you can mine data I'll do that tonight gladly. At the time I had about 60GB of free space on my HDD. I now have around 72GB free because I did not restore my VMWare XP box, thinking it may have been the cause of the issue (it was acting pretty weird then hung up entirely). But the symptoms I had are identical to the other posters.

Robin Lee

https://community.logos.com/discussion/comment/43565#Comment_43565

If this is the case, it also happened to me last week. I suffered a very long boot up time and I thought it was my OS problem.

Pat Soliday

https://community.logos.com/discussion/comment/43561#Comment_43561

I have 108 GB free.

Matt Morrison

https://community.logos.com/discussion/comment/43588#Comment_43588

Wow... Glad to know I'm not alone out there! I did not have my indexer set to log at that point. However, my experience was the same as Pat's. I do remember shutting down my computer Saturday night and seeing the Logos icon open and the indexer running. Mine worked out the same way. It took 20 minutes to boot up the next morning and eventually ran (unfortunately, after I had to teach my students without my notes :-/...fun experience there!) When I took it into the Apple store, they verified that my hard drive was running properly but told me that it could have something to do with the permissions. That's what led me to point the finger at A4. At the present moment, I have 24.14GB of free space on the hard drive. I hope that helps you guys somehow. Thanks for looking into it!

Jonathan Griffiths

https://community.logos.com/discussion/comment/43630#Comment_43630

Just a thought - does the indexer get entered into the startup items for Mac OSX? In my research on the problem, prior to the Time Machine restoration and prior to thinking A4 was the culprit, I found the same symptoms (long or failed boot process, spinning gear symbol) related to startup items. Unfortunately I couldn't get in in safe mode to verify and just presumed my OS was toast.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/43685#Comment_43685

Jonathan,

The indexer does get started when you log in, not when you start the computer. It's in your ~/Library/LaunchAgents/com.logos.LogosIndexer.plist

To test out if this is the problem, try the following. Change the value <true/> after <key>RunAtLoad</key> to <false/> and save the file. Then reboot the computer and see if that fixes your issue.

Tom

Before:

<key>RunAtLoad</key> <true/>

After:

<key>RunAtLoad</key> <false/>

Jonathan Griffiths

https://community.logos.com/discussion/comment/43689#Comment_43689

Thanks Tom - if it happens again I'll see what I can do, but since restoring to my TimeMachine backup I've not had it repeat the problem. And if the problem recurs I'm not sure I'll be able to get into my OS to make the change and see if it fixes the problem!

I got Logos 4 installed on a PC in the meantime and I'm so impressed with what your company has created. Can't wait for the bugs to ironed out of the Mac version!!

If the indexer is not designed to run until login, then it probably wasn't that (since I never made it to the login prompt).

David Oxtoby

https://community.logos.com/discussion/comment/43698#Comment_43698

Wow, wished i'd seen this thread, since i never gave A4 a second thought as been the cause for my Mac hanging with same symptoms as described here. Yep i also had to rebuild from TM backups, so a real problem with A4.

David O.

Jonathan Griffiths

https://community.logos.com/discussion/comment/43735#Comment_43735

Isn't that so sweet that none of us pointed the finger at A4? [:)]

I'll try to get my indexer logs posted tonight if they might be helpful. When the problem occurred I was running OSX 10.6.1 with Logos 4 (A4) and Logos 1.2.2 installed on my MacBook. I also had a VMWare Fusion 2.0.5 XP box running Logos 4, and that box was running super slow.

Now, post rebuild from backup, I've not got my XP box installed, and I've upgraded to 10.6.2 with Logos 4 (A4) and Logos 1.2.2 installed still.

MacBook 2.4GHz with 2GB RAM.

Maybe others that have experienced this could post their configs so we can either find correlation or rule out stuff.

Brian Fox

Got the exact same problem on my MacBook Pro 15" 2.53 with 115gb of available HD space. My machine took about 40 minutes to bootup the other day stuck on the Apple with spinning gear. For sure related to A4.

Donovan R. Palmer

https://community.logos.com/discussion/comment/43743#Comment_43743

I also had a VMWare Fusion 2.0.5 XP box running Logos 4, and that box was running super slow.

From what I understand, you really need to be able to allocate 2gb to your virtual machine to run L4 Windows in order to get good performance. So the only way to do this would be to increase your physical ram in your macbook to 4gb.

Adam Crafton

Same thing happened to me this morning. . .after 15 mins I booted from a backup drive, shut it down, and then booted normally and it came up in about 10 mins.

Bob

https://community.logos.com/discussion/comment/43898#Comment_43898

I also had a VMWare Fusion 2.0.5 XP box running Logos 4, and that box was running super slow.

From what I understand, you really need to be able to allocate 2gb to your virtual machine to run L4 Windows in order to get good performance. So the only way to do this would be to increase your physical ram in your macbook to 4gb.

Well I get pretty good response with 756Meg on my (very old) 17" MBP. I am using Parallels 3 (never updated since it works) and XP. Perhaps the requirements are different if you use Vista or 7. Using more virtual RAM is out of the question since this box only allows 2Gb of RAM. As I recall it took nearly 8 hours to index the first time (Gold(LE))

Jonathan Griffiths

https://community.logos.com/discussion/comment/43898#Comment_43898

Yeh, I'll upgrade RAM eventually. But last night I loaded Win7RC (yes, I still have access to it for a few more months) and the box was lightning fast with the adjustments made on the 3D acceleration etc., and I loaded Logos 4 Leaders Edition, with full download and indexing, within a few hours. Setting the VM to only 1GB of RAM (and I'm running the most basic install of 7), the system is usable. Sure, it's not rocket speed in Logos, but it is functional for now until a) I get more RAM or b) Logos 4 Mac gets further along.

No recurrence of the boot screen hang up in Mac OSX, but I've not been launching Logos 4 (a4) very much either.

David Oxtoby

https://community.logos.com/discussion/comment/43898#Comment_43898

I also had a VMWare Fusion 2.0.5 XP box running Logos 4, and that box was running super slow.

From what I understand, you really need to be able to allocate 2gb to your virtual machine to run L4 Windows in order to get good performance. So the only way to do this would be to increase your physical ram in your macbook to 4gb.

I have Fusion with XP, allocated only 1gb of ram, and L4 runs pretty well, the key is not to have it running in Unity mode, but fullscreen, this makes a big difference, as well as try and not have any AntiVirus running in the VM was well, so a good lean XP seems to help L4 run well.

Timothy J. Minter

https://community.logos.com/discussion/comment/43561#Comment_43561

Hm. Had the same thing happen to me. I also did a Time Machine restore, but now I'm wondering.