MAC OS 12 Monterey

This is just a head's up I know there is no support for Beta OS software and I am not asking for any.

I have the developer's copy of MAC OS 12 on one of my Macs. Everything works fine except when I type an f in notes it will either minimize or maximize my screen. It can be a lower or uppercase f. I can shut logos down and re launch and it will stop for a while and then it starts back again.

Don't know if your working with Monterey yet, but wanted to let you know.

Find more posts tagged with

Comments

mab

I consider that a very good sign that it is mostly stable. I think we are getting closer to not having the rug being pulled out from under us with every new release. Considering how beta that OS is, I don't expect it to go south in the future.

Rob Bruce

https://community.logos.com/discussion/comment/1171056#Comment_1171056

Yes! There were times when Logos wouldn’t even launch.

Gregory Lawhorn

Not typing "f"s might hinder things a bit, but you could always get creative:

Your eye shall not pity. It shall be liphe phor liphe, eye phor eye, tooth phor tooth, hand phor hand, phoot phor phoot. (Deuteronomy 19:21)

I usually wait until the 2nd developer release before installing Apple's latest. I need Proclaim to work as well, so I'll install it on an external SSD and see how it goes.

Thanks for the inpho!

Rob Bruce

https://community.logos.com/discussion/comment/1171074#Comment_1171074

Love the work around. I only have it on one machine. I know better.

Myke Harbuck

Just an FYI....Logos mobile is working well on iOS 15. Haven't noticed any issues yet.

Wes Keene

Is that the only issue you've observed in Logos with Monterey? I'm strongly considering putting it on my M1, but it would be annoying if Logos couldn't do at least basic things (open resource, multiple resource view, etc).

mab

https://community.logos.com/discussion/comment/1171146#Comment_1171146

I'm much too lazy and white knuckle. The only thing I use nowadays is a release candidate of LibreOffice. Those work well enough.

JT (alabama24)

https://community.logos.com/discussion/comment/1171146#Comment_1171146

it would be annoying if Logos couldn't do at least basic things

If you need the installation or if losing it would be more than a minor inconvenience, you should never install a beta. Things can and will go wrong. Just because beta 1 has no significant issues doesn’t mean that beta 2 won’t break the bank. I know from personal experience, but thankfully I did not need Logos for work at the time.

Rob Bruce

https://community.logos.com/discussion/comment/1171146#Comment_1171146

If you only have 1 Mac for your work, do not do it. I have 3 Macs. Beta 2 could be worse or better who knows? It's a beta.If you are going to do it wait till the public beta, but if you only have one machine do not do it.

Mike Binks

https://community.logos.com/discussion/comment/1171146#Comment_1171146

Is that the only issue you've observed in Logos with Monterey? I'm strongly considering putting it on my M1, but it would be annoying if Logos couldn't do at least basic things (open resource, multiple resource view, etc).

If app.logos.com would meet your everyday needs then you should be able to install the beta and ride out the storm.

Gregory Lawhorn

I've installed the second beta of Monterey on an external SSD. It appears that the 'f' issue reported has been resolved.

It also appears that Proclaim and Logos both function properly, although I haven't done any detailed work yet. I'll be continuing sermon prep tomorrow, and I'll use Monterey, and report on how it goes.

Rob Bruce

https://community.logos.com/discussion/comment/1172422#Comment_1172422

I still have the "f" issue but only lower case

Rob Bruce

https://community.logos.com/discussion/comment/1172422#Comment_1172422

I still have the "f" issue, but only lower case.

Gregory Lawhorn

https://community.logos.com/discussion/comment/1172446#Comment_1172446

I still have the "f" issue, but only lower case.

It just happened to me as well. Phortunately I do my text editing elsewhere.

Gregory Lawhorn

https://community.logos.com/discussion/comment/1172422#Comment_1172422

Sermon prep went fine last week using Monterey. I prepared a Bible study this week, and have been preparing Sunday's message as well. I went ahead and installed Monterey Beta 2 on my MacBook Air and MacBook Pro. The Pro is in my office, connected to a large monitor. The Air goes with me. Both have functioned without a hitch.

As always, beta software can be problematic, but frankly, this is the smoothest beta OS I've ever used.

I did decide to use the Logos default update channel, rather than the beta, for the time being; no point pushing it too far.

Unsichtbar

https://community.logos.com/discussion/comment/1173459#Comment_1173459

I'm using a workaround: using (macOS) system settings and overriding the "fullscreen" or "back to normal" shortcut from the logos window-menu. Then you can use 'f' again as usual without restarting every couple of minutes.

Rob Bruce

https://community.logos.com/discussion/comment/1173678#Comment_1173678

Great work around, thanks!

Kevin A. Purcell

https://community.logos.com/discussion/comment/1173704#Comment_1173704

Either this is not a universal problem or I'm just very lucky but I'm not seeing this issue on Monterey on my MBPM1.

EDIT.

Running 9.6.0.0020

Richard Bickings

https://community.logos.com/discussion/comment/1173678#Comment_1173678

I am using MAC OS 12 (Montery), and just encountered this problem. I used it last week but without the problem (f-key full screen toggle). I tried to locate the logos window-menu you were wrote about but there was no "fullscreen" or "back to normal" setting...could you please help?

Thanks, Dick Bickings

Levi Durfey

https://community.logos.com/discussion/comment/1183519#Comment_1183519

Thanks, Dick Bickings

Does this post help? https://community.logos.com/forums/p/201886/1174085.aspx#1174085

Jeff

https://community.logos.com/discussion/comment/1183519#Comment_1183519

I am having the same issue with the lowercase "f" key. It worked fine until I upgraded to macOS Monterey 12.0.1. Now, every time I type the lowercase "f" key in the sermon editor it goes to full screen.

Levi Durfey

https://community.logos.com/discussion/comment/1183545#Comment_1183545

I am having the same issue with the lowercase "f" key. It worked fine until I upgraded to macOS Monterey 12.0.1. Now, every time I type the lowercase "f" key in the sermon editor it goes to full screen.

See Gregory's post for a workaround to this issue: https://community.logos.com/forums/p/201886/1174085.aspx#1174085

Philana R. Crouch

Everything works fine except when I type an f in notes it will either minimize or maximize my screen. It can be a lower or uppercase f. I can shut logos down and re launch and it will stop for a while and then it starts back again.

Thanks for reporting this. We do have a case to work on fixing this.

Jack

https://community.logos.com/discussion/comment/1183623#Comment_1183623

Hi,

I have Logos 9 on my M1 Mac MIni and upgraded to Monterey (12.0.1) two days ago.

When typing in any note now, if I hit the "f" key, my screen corrupts (jiggles and blurs) for 1-2 seconds and character entry in my note is temporarily stopped. The "f" enters but no other letters after that. After a couple of seconds, I can go back and complete the word that was supposed to start with "f" and continue typing normally until I hit another "f". This occurs 100% of the time when I hit an "f" when typing in Notes.

Help or Thoughts?

Graham Criddle

https://community.logos.com/discussion/comment/1183798#Comment_1183798

Hi Jack - and welcome to the forums

Does the workround suggested above - at https://community.logos.com/forums/p/201886/1174085.aspx#1174085 - help in what you are seeing?

Graham

Jack

https://community.logos.com/discussion/comment/1183801#Comment_1183801

Yes. Thank you so much!

Philana R. Crouch

Everything works fine except when I type an f in notes it will either minimize or maximize my screen. It can be a lower or uppercase f.

This has been fixed in 9.8 SR-2.

mab

https://community.logos.com/discussion/comment/1184188#Comment_1184188

This has been fixed in 9.8 SR-1.

Great news