I got the A1 of L4Mac loaded, completed the lengthy indexing, but now everytime it launches I get two copies of the Logos Installer in my dock, and when I run the install and relaunch the same thing keeps happening. I've tried quitting one of the installers and runing the install and relaunch that way too, but all to no avail.
Anyone else experienced this? I'm running on a MacBook, Snow Leopard, and the original Logos for Mac is installed.
that is a new one to me... Someone on Tech will have to chime in on that one.
- my blog MoreThanCake.org
- my books EmergingLife.org
You replied when I posted, so I reply when you post. Yup. Same problem. I noticed I had two versions of Logos 4 installed "Logos 4" and "Logos 4 (32462)". Deleted the oldest one and it crashed. I think I may be starting over again...
all about Christ,
David Buckham
My indexing has said all day (0:01 remaining)
MacBook Pro 2.4 GHz Intel core 2 Duo4 GB SDRAMMac OS X 10.6.1
My indexing completed just fine - 15 hours later, and I only have the Leader's Library! But this loop problem is weird. Waiting to hear from people.
I heard from Tech. They are aware of the looping problem and hope to have it fixed in the next release due at the end of the week.
So presumably we just ignore the request to install and relaunch and get on with using Logos 4?
If your indexing is making progress, let it work. If you are stuck in the loop, I would think the only option is to ignore it until the next drop.
My indexing is all done. The looping issue began AFTER the indexing finished. I saw in a post re: L4win that some people have had many downloads in a row that turned out to be resources. I plan on trying again later with logging enabled and see if that sheds any light on this. I suspect it will just be a case of waiting for the next update end of this week.
Good to hear some feedback on this issue, I look forward to the update as well. I just started what seems to be a new round of indexing... 30hrs is the time listed. Guess I will leave it all night.
We've pushed out a new build which should fix the continuous updating problem. Thanks for the patience.
How do we force the update if we are in the indexing loop?
Okay, I stopped indexing, shut down and restarted L4mac. I waited about 5 minutes, shut down again. When I restarted, a message came up saying I had no downloads to install. This should be the next Alpha drop.
Little blue icon says I am in stage 2 of 3 for indexing. I tried to open the program but get the error message
"You can't open this application Logos Bible Software 4 because it may be damaged or incomplete"
I'm still stuck in the update loop. Will keep working on it and post if I get a solution.
Hold onto your hats ladies and gents... so keeping in mind my issues started AFTER indexing, so some of us may not be having the exact same issues...
1) Upon first, second and third launch, I experienced the same loop of updates/relaunch/updates
2) One of the sessions hung up and so I executed a "force quit" from the dock items (installer then Logos)
3) The next time I launched the task bar icon was back and hovering over I see a package downloading that is 48.6MB - just the right size to be the package promised earlier in the thread.
I'm about 1/3 done with the download, but things are looking up! And to the team working the Mac build - high fives all round. I know you're all under the gun here, and you're doing great work which we really appreciate!
Had the same problem described above by Jonathan, and just launched Logos 4 after giving up a few hours ago. The looping is in process as I saw earlier, but also see that a 48.6 MB file is downloading...
Yep, that did it! So, now I have an installed and indexed L4mac A1! Passage guide, and exegetical guide attempt to do something, but it looks like that functionality is not complete yet.
Glad that solved it for you guys. It seems to be working well for me too.
Dave Ketah: Passage guide, and exegetical guide attempt to do something, but it looks like that functionality is not complete yet.
Sounds about right. In other words, the functionality is there, it just doesn't function yet.
It sure does seem like this will be a quick alpha!