Posts

Post not yet marked as solved
4 Replies
0 Views
More info. FaceTime in Monterey (now Beta 4) is absolutely maddening. Not only does the Full Screen menu option not work, but now the maximize/minimize buttons don't work either. There is a right click Zoom option, which goes to "sorta full screen" but not true full screen. I don't know what they are doing with the application, but is simply is not working as expected and the usual options are there but non-functional. There is something weird going on. I thought it was something about the 2019 16" MBP, but I've replicated the problem on a second computer - a 2019 iMac 5K. This is definitely a bug.
Post marked as solved
4 Replies
0 Views
No problem with the upgrade, but Safari won’t run. Loads, but crashes upon entering anything (any keystroke) in the search bar. Latest Safari Dev Preview.
Post not yet marked as solved
2 Replies
0 Views
That's kind of a lame workaround. What regression did the October 16 beta introduce? I'm having the same problem across 9 different time zones.
Post not yet marked as solved
3 Replies
0 Views
They need to rethink this. For some of us with old eyes, the smaller icons are more densely packed on the screen and makes it hard to pick them out. Right now it isn't that big a problem because what filled an entire screen before, now fills only half the screen. They icons are still too small but they aren't as densely packed as with a full screen. Screen real estate is wasted this way, and there is no way to move icons from screen to screen without using a computer. This all seems self defeating. The icons should be resizeable, at least undervAccesdibility options.
Post not yet marked as solved
23 Replies
0 Views
I Finally gave up and wiped the drive, reinstalling Mojave. This is the first time in 10 years of testing Mac OS that I’ve had to **** away an early beta. The machine was so unstable that I could never predict when it would just freeze or when it might work. Everytime it froze, it was the Finder, even if I was inside another program. It will be awhile before I load another Catalna beta on my test machine. FWIW, it is a 2017 Retina MBP 15” with top specs.
Post not yet marked as solved
32 Replies
0 Views
And here I thought it was just me. Can't get past 10.14.3 despite all efforts.
Post marked as solved
6 Replies
0 Views
Thanks. I can wait until it gets rolled up into a later beta.Mrf
Post not yet marked as solved
2 Replies
0 Views
There isn’t a Mojave GM yet.
Post not yet marked as solved
34 Replies
0 Views
This link pretty well covers the problem and offers suggested ways Apple can fix the problem.https://www.felix-schwarz.org/blog/2018/06/apple-event-sandboxing-in-macos-mojave
Post not yet marked as solved
34 Replies
0 Views
Correct. All my scripts failed in the same way as in 6.
Post not yet marked as solved
33 Replies
0 Views
Printers are definitely fixed in Beta 7. Can print to my two Epson All-In-Ones, my Epson R-3000 photo printer, and my Dymo 4XL labelwriter.Beta 6 was definitely a bummer, but 7 seems better so far. I'm sure they've broken something else, but I'm hopeful it won't affect my work.mrf
Post not yet marked as solved
34 Replies
0 Views
It *might* be fixed in Beta 7. I'm testing with SuperDuper! right now. When it first ran, it asked for Copy Job.app to have permission to access Finder and SuperDuper!, which I granted. Since then, timed events have gone off as scheduled without requiring manual intervention. We'll see if this holds through all of the copy jobs.mrf
Post not yet marked as solved
34 Replies
0 Views
Has anyone tested with Beta 7. I’m installing right now.mrf
Post not yet marked as solved
34 Replies
0 Views
A good illustration of this problem is to run the scheduling module in SuperDuper! Prior to Beta 6, everything ran like clockwork. Beginning with DP6, it won’t run unattended because every time the Copy Job.app gets accessed inside of SD! It requires the user to explicitly grant permission for Apple Events to use Copy Job, Finder to use Copy Job, and SuperDuper! To use copy job. If you don’t respond, the event times out with three errors, all -1712, which relate to system events. There is no way to get around this because there is no way to issue a one-time “sticky” authorization for each job. I have 4 scheduled jobs that runeach night. Every morning I wake up to 12 errors that each have to be dismissed before I can regain control of my desktop. THIS IS TOTALLY UNACCEPTABLE (and I’ve reported it as a bug, which is marked DUPE and closed). All of the security changes may eventually work out, but boy are they a PITA is this release. Wonder what new surprises DP 7 will bring.