When Mac shuts down, Logos 5 refuse to quit and had to force closure.8080.LogosLogs.user.20140103-133107.zip
Welcome to the forums! [:)]
When Mac shuts down, Logos 5 refuse to quit and had to force closure.
This is a common complaint, but this is "by design." [:S]
When Mac shuts down, Logos 5 refuse to quit and had to force closure. This is a common complaint, but this is "by design."
This is a common complaint, but this is "by design."
Two comments
1. Do you allow your Mac to sleep with Logos running? There is a problem in the current stable release which is being addressed in the current beta (5.2a). Solution, do not allow your Mac to sleep with Logos running.
2. Prior to shutting down your Mac quit L5 and allow it to finish the synch cycle prior to shut down.
No... it's not.
I'm curious what made you think that?
No... it's not. I'm curious what made you think that?
Endless threads. I thought for sure that you (or another Logos employee) had said something along the lines: "A number of applications can cancel the shut down process..." with the implication that the sync process needed to happen first. The advice given was shut down logos first before you shut down the computer. I'll look and see if I can find it.
From a logos employee: http://community.logos.com/forums/p/51334/481671.aspx#481671
See also: http://community.logos.com/forums/p/59455/490833.aspx#490833
Is that information inaccurate?
That is not the same as this issue. Both of those threads are "Why does Logos cancel shutdown?" where as this is "Logos refused to quit and must be Force Quit."
Does that clarify the difference? The implication here is that by "refusing to quit" T H is saying the app is hanging and has to be forced. The other threads are asking that the app automatically close when shutting down, which (to the best of my knowledge) it is not intended to do.
Maybe I misunderstood the OP. I construed him to be saying he had to "Force Quit" Logos 5; this indicates a bug/hang and should never be by design.
my initial reply above was really only in response to the first part of the users complaint... And isn't that the heart of his issue? Is that not the same issue as the other threads?
I do understand the nuance that the user had to force quit, but was that his concern? FWIW - I have to force quit Logos almost every time I want to close it down now... But that is a "known issue," right?
Honestly, we need more info from T H to know exactly what the issue is - the one sentence we have is a little vague. [;)]
I construed him to be saying he had to "Force Quit" Logos 5; this indicates a bug/hang and should never be by design.
This is what I assumed as well, and with the thread title being "Hang" and mentioning force quit, I feel that's a reasonable conclusion.
This is a tricky question, since the OP of both threads you linked are referring to this:
If that is your "by design" then you are correct - and that's what Tommy was referring to. But the second thread you linked is almost immediately hijacked by Martin to be "L5 won't shut down without force quit", which is different than the above image. Bradley and I are focusing on the latter part of T H's comment:
[quote]When Mac shuts down, Logos 5 refuse to quit and had to force closure.
That is definitely not by design, and what I thought you meant by your comment. [:)]
Now! Looking at the Console Message log, it appears that T H is putting the computer to sleep with Logos running, which is a known issue that should be fixed once 5.2a is shipped to Stable users.
I've talked to a Mac expert and have some additional information about the problem.
When Mac OS X shuts down, it asks every application to close, and gives them a small amount of time to do so. Logos 5 syncs your data on exit, to make sure the latest documents and settings aren't only stored on the computer you're shutting down, potentially causing a sync conflict later. (And we have to sync if you want "At Startup Open to: Most recent layout - any" to work.)
Logos 5 doesn't explicitly cancel OS shutdown; instead, if it doesn't quit within a small (Apple-defined) period of time, the OS shows that dialog. You should be able to click Try Again after giving it a little more time.
So it's not "by design" that we cancel shutdown; it's "by design" that we sync on exit and this may conflict with Apple's time limits.
I have to say that Windows handles this much better. [:P] It also gives applications a few seconds to shut down. If they don't, it displays an overlay listing all the "slow" applications. As soon as an application exits, it's immediately removed from that list; if it was the last one, Windows proceeds with shutdown. So you can fix this problem by getting a more user-friendly OS. [;)]
Nuanced, but OK. [:)]
So you can fix this problem by getting a more user-friendly OS.
I have a better idea. Let's have the developers speed up the way-too-slow sync on closing. (Logos always takes forever* to close)
*where "forever" is subjectively determined by this forum user. [:P] Sometimes it is 10-15 seconds.
… (Logos always takes forever* to close) *where "forever" is subjectively determined by this forum user. Sometimes it is 10-15 seconds.
… (Logos always takes forever* to close)
*where "forever" is subjectively determined by this forum user. Sometimes it is 10-15 seconds.
Those of us who remember rejoicing upon acquiring an IBM Selectric II must smile at this hyperbole, although I agree that Logos developers need to speed up synchronizing.