Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases OS X 10.9.2 With Fix for Major SSL Vulnerability, FaceTime Audio
- Thread starter MacRumors
- Start date
- Sort by reaction score
how do i get facetime audio
do i need to buy the 99cent app from the appstore?
i have a mac mini with mavericks and i downloaded the new update
do i need to buy the 99cent app from the appstore?
i have a mac mini with mavericks and i downloaded the new update
Hmmm. After the update Spotify just closes on me... I uninstalled and and reinstalled it again but nothing =( oh well. I'll see what their support say about this. Thanks again.
While it does not work as you want it seems to me it works the way they want. To start with different window size go to "Settings|Settings|Windows" and change the "Windows size" rows and/or columns. A bit awkward, yes, but don't expect any fix for it.
Froze on the "Installing Software Update" page for me too (mid-2011 MBA), but just held standby button to power off in the end and as JonLa earlier had with his MBA it powered back up still as 10.9.1 but successfully updated to 10.9.2 the second time around.
I just find it extremely odd that the only difference between the two versions I referenced was reporting the SSL bug fix and that they'd have different versions of a change log for a published update for different locales.
Just noticed that Apple finally fixed the issue of optimizing mirrored displays by choosing the one with the greater resolution if you're only using one physical display and connecting to an audio receiver via HDMI.
Before, OS X would think that my audio receiver was actually a second 1080p display, which it's not, and so a non-existent secondary display existed and your arrow cursor could actually go off-screen to that imaginary display. And since my only physical display is a 27-inch iMac which runs in 1440p, mirroring in OS X always used the display with the lowest common denominator resolution, forcing my iMac to downscale to 1080p.
Now after 10.9.2, it seems they've added a drop down menu labeled "Optimize for:" in the Display preferences allowing you to choose which monitor's native resolution to use for while mirroring and at the same time, eliminating the non-existent display (because of mirroring). Very awesome. Thanks Apple!
Except now however, my FaceTime App is broke lol.
Before, OS X would think that my audio receiver was actually a second 1080p display, which it's not, and so a non-existent secondary display existed and your arrow cursor could actually go off-screen to that imaginary display. And since my only physical display is a 27-inch iMac which runs in 1440p, mirroring in OS X always used the display with the lowest common denominator resolution, forcing my iMac to downscale to 1080p.
Now after 10.9.2, it seems they've added a drop down menu labeled "Optimize for:" in the Display preferences allowing you to choose which monitor's native resolution to use for while mirroring and at the same time, eliminating the non-existent display (because of mirroring). Very awesome. Thanks Apple!
Except now however, my FaceTime App is broke lol.
I have a similar problem, already made a post about it in a current (pretty slow) thread:
http://community.spotify.com/t5/Hel...ate-0-9-7-16/m-p/660054/highlight/true#M72918
I have NOT done the update so still on 10.9.1, build 13B42.
same, just spend an hour with Apple support over the phone and they were unable to help. I made an appointment at the local apple store for Thursday, if i can't download it by then, i'll go to them and have them clean install and make me a usb installer (not sure they'd do it for the usb installer, but worth asking, i figure...)
Let me know if you are able to download it at any time in the mean time. i'd really appreciate it.
Cheers,
M,
You know what I'm happy not to see?
Those special builds for the late 2013 mbp and mp.
The ones for 10.9.1 made it really hard to make a bootable usb installer for those machines.
So it looks like the full installer on the mac app store for 10.9.2 will be good for this. Can't verify this though because I don't have one of those machines.
Has anyone tried this yet on those machines? I'd be interested to know if it works.
Those special builds for the late 2013 mbp and mp.
The ones for 10.9.1 made it really hard to make a bootable usb installer for those machines.
So it looks like the full installer on the mac app store for 10.9.2 will be good for this. Can't verify this though because I don't have one of those machines.
Has anyone tried this yet on those machines? I'd be interested to know if it works.
I would agree. Many customers from various ISPs are having issues with their Netflix traffic. The peering connections are fully saturated and ISPs basically refuse to upgrade or add equipment because they'd rather sell their ondemand movie services.
Are you referring to the non-functioning command-space number (even when System Preferences SAYS it is set to work)? Only the command-arrow (left or right) moves between spaces / desktops now.
Because of the time required to download the update (seems like the original Mavs update took about 5 hours with a 'faster' cable modem), I plan on waiting till the flurry of activity has subsided.
Huh? You aren't making any sense.
a) There is no "Settings|Settings" in the menu at all in Console.app. There only is Preferences, and nowhere does it say anything about window arrangements/settings.
b) You may have misunderstood my post. The point I was trying to raise is that when I go to Console.app, the window opens in the default 'small' size, and when I resize the window to make it bigger, then quit the app with the whole window resized to a bigger size, then... when I open the app again, the window has defaulted back to its original size. It does not remember or retain the window size. The expected behavior should be that when you resize a window, then quit the app, upon relaunch, the app should remember the new window size. This behavior applies to Safari, iMessage, Notes, TextEdit, and pretty much all the built-in apps that are resizable.
To test this behavior on 10.9.2, open Console, widen the window (or make it taller, doesn't matter), quit, then reopen Console. You should see that the window does not retain your resized parameters.
Make sense?
a) There is no "Settings|Settings" in the menu at all in Console.app. There only is Preferences, and nowhere does it say anything about window arrangements/settings.
b) You may have misunderstood my post. The point I was trying to raise is that when I go to Console.app, the window opens in the default 'small' size, and when I resize the window to make it bigger, then quit the app with the whole window resized to a bigger size, then... when I open the app again, the window has defaulted back to its original size. It does not remember or retain the window size. The expected behavior should be that when you resize a window, then quit the app, upon relaunch, the app should remember the new window size. This behavior applies to Safari, iMessage, Notes, TextEdit, and pretty much all the built-in apps that are resizable.
To test this behavior on 10.9.2, open Console, widen the window (or make it taller, doesn't matter), quit, then reopen Console. You should see that the window does not retain your resized parameters.
Make sense?
I'm stuck on the Installing Software Update screen. It's been 15 minutes in the same spot. It's about 95% done, but it hasn't moved any. What should I do?
swingerofbirch
macrumors 68040
iCloud, Set up computer screens - normal?
Did it ask anyone else to set up iCloud again and then say the computer was set up as if it had done a reinstall?
For me it went to a grey screen with the App Store icon where it installed, then restarted and continued installing, and then asked me to log into iCloud and something else I forget. All my data is on the computer still, at least from what I can tell, but it seems like a few settings may have changed.
I can't remember a .1 update saying your computer has now been set up, as if I had done a reinstall, before.
Did it ask anyone else to set up iCloud again and then say the computer was set up as if it had done a reinstall?
For me it went to a grey screen with the App Store icon where it installed, then restarted and continued installing, and then asked me to log into iCloud and something else I forget. All my data is on the computer still, at least from what I can tell, but it seems like a few settings may have changed.
I can't remember a .1 update saying your computer has now been set up, as if I had done a reinstall, before.
I saw the same thing (MBP mid-2009). I didn't enter my iCloud stuff but everything worked as expected.
You are talking about Terminal. Console in OS X is entirely different: it is the application where you can go through all the logfiles. Quite different than "console" in Linux
(which btw is incorrect usage of the word; the console is the physical device you're sitting at which runs a terminal which uses a shell so you can interact with the system).
I have trust me I even called my ISP they tell me there is nothing wrong I complained to Netflix and tell me it is my ISP I tell my ISP they say it is Netflix and keep on going around in circles
SO ONE IS BEING A DICK AND NEED S TO ADMIT WHO IS AT FAULT!
Your ISP isn't going to be able to tell you if your connection is randomly dropping without sending a technician to test the lines. It could also be an older/faulty modem not keeping up/restarting/timing out your connection.
Hung with Installing Software Update
My Mac Mini updated fine but my Macbook Air is just Hung with Installing Software Update at the same location. About 90% complete. Not sure what to do. If I power off/on I might loose my OS.
Any suggestions?
My Mac Mini updated fine but my Macbook Air is just Hung with Installing Software Update at the same location. About 90% complete. Not sure what to do. If I power off/on I might loose my OS.
Any suggestions?
Same thing happened to me. I shut it down via holding down the power button, and nothing bad happened. Then I tried to install the update again, and it worked.
gotofail.com apparently says it is fixed.
Without delving further into the code, that's about as much information as we have.