Mavs 10.9.2 released

[Craig Seeman]

I’ve had odd issues that I don’t think are QMaster related. One system displayed a blank window. I tossed all support items and it rebuilt. I have another system which works unless I try to create a new custom setting. It crashes. Crash log seems to point to ProApps so I have to dig through that and start tossing stuff as well.

[Mathieu Ghekiere]

Craig,

when Compressor 4.1 was released, we had a lot of problems.

We had Matrox Utilities installed (for using a Matrox MXO2 with MAX technology for making H.264’s quickly) and with that installed the new Compressor would just crash.

Since 4.1.1 we haven’t had any problems anymore (maybe doing a Compressor Repair with the Digital Rebellion Tools once), and the new interface really is much better. I really like it. We even got it to work with the Matrox.

The only problem is that if we want to add a new Destination in the FCPX Share Menu, adding a Compressor setting, we get an FCPX crash. I guess it’s maybe related to the Matrox as well, I’m not sure.

[Charlie Austin]

[Jeremy Garchow] “Perfect, now I get to blame you when it goes down in a fiery ball of silicon!”

I accept full responsibility. Mwahahahah!!!

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Mathieu Ghekiere] “The only problem is that if we want to add a new Destination in the FCPX Share Menu, adding a Compressor setting, we get an FCPX crash. I guess it’s maybe related to the Matrox as well, I’m not sure.”

Guess I’ve been lucky, it’s been OK for me… Do have the Digital rebellion crash analyzer? maybe that could point you in a directs as to the cause…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[John Pale]

Hey all,

If you hadn’t heard, there is an important security fix in this update. Mavericks introduced a serious SSL vulnerability (bug was also in iOS7 and was patched last week). Apple has been pretty tight lipped about how serious it was, but many folks went to DEFCON 1 over it. Apparently it was a Pretty bad and embarrassing bug that opened a huge security hole.

https://www.macrumors.com/2014/02/25/osx-update-ssl-facetime-audio/

[Dave Gage]

If this thread at Slashdot is correct, the bug not affect users of 10.6.8 (but I would assume most of you are on 10.9 by now-
https://apple.slashdot.org/story/14/02/22/2143224/apple-ssl-bug-in-ios-also-affects-os-x

A lot of it is above my head, but it seems to make sense. A couple of quotes:

“Snow Leopard (10.6) is not vulnerable to this bug, since Apple did not switch from OpenSSL to their own SSL/TLS library back then yet. Just verified on my 10.6 box (to verify visit https://www.imperialviolet.org:1266/ )”

“10.8.5 isn’t even effected, why would any previous version be? This is strictly an iOS 6.x, iOS 7.x and Mac OS X 10.9.x bug.”
—

I tried Firefox, Chrome, and Safari 5.1.9 in 10.6.8 and the page wouldn’t load. How this is or isn’t connected with the “Man In The Middle” (MITM), I have no idea.

[Craig Seeman]

Sounds much like my Create New Settings crash.
Crash log though isn’t pointing to Matrox device (which I do have installed, MXO2 and MAX as well) though.
It’s not a user preferences issue since the crash still happens when creating a New User Admin account.
Compressor Repair and FCS Remover (removing Compressor 4) and reinstall didn’t fix it either.
It looks system OS level. Crash log points to ProKit or CoreFoundation.

[Charlie Austin]

[Craig Seeman] “It looks system OS level. Crash log points to ProKit or CoreFoundation.”

Realizing it’s a giant PITA, have you tried an OS reinstall?

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Craig Seeman]

[Charlie Austin] “Realizing it’s a giant PITA, have you tried an OS reinstall?”

Just finished and…. boom crash same as it ever was.

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_pthread.dylib 0x99810643 __mtx_droplock + 488
1 libsystem_pthread.dylib 0x99810af9 pthread_mutex_unlock + 83
2 com.apple.Foundation 0x93288ed3 -[NSLock unlock] + 262
3 com.apple.Foundation 0x9328f6d1 +[NSBundle bundleForClass:] + 779
4 com.apple.prokit 0x47795c67 +[NSObject(ProAdditions) isDefinedInBundleForClass:] + 150
5 com.apple.prokit 0x47795cbd +[NSObject(ProAdditions) isProSubclass] + 62
6 com.apple.prokit 0x4781aea7 -[NSCell(ProAppearanceExtensions) proSetFont:] + 54
7 com.apple.prokit 0x4781af46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213

[Charlie Austin]

[Craig Seeman] “Just finished and…. boom crash same as it ever was.
“

Bummer. Do you have the Digital Rebellion crash analyzer? Be interesting to see what it says if you haven’t looked…

Since fonts often blow things up, this:

[Craig Seeman] “6 com.apple.prokit 0x4781aea7 -[NSCell(ProAppearanceExtensions) proSetFont:] + 54
7 com.apple.prokit 0x4781af46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213
“

Might mean something. Or not…

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~