Soundflower For Os X 10.10.4
- Soundflower For Os X 10.10.4 Pro
- Soundflower For Os X 10.10.4 Server
- Soundflower For Os X 10.10.4 Version
- Os X 10.11.4
- Os X 10.12
- Os X Download
Jul 21, 2015 OS X Yosemite (10.10) MacRumors attracts a broad audience of both consumers and professionals interested in the latest technologies and products. We also boast an active community focused on purchasing decisions and technical aspects of the iPhone, iPod, iPad, and Mac platforms. OBS Studio for Mac is a free and open source software for video recording and live streaming.Download and start streaming quickly and easily on Windows, Mac or Linux. Control your stream from your Mac desktop with OBS Studio for macOS! OBS Classic and OBS Studio are both equipped with a powerful API, enabling plugin development to provide further customization and functionality specific to.
- Latest Version:
- OBS Studio 25.0.8 LATEST
- Requirements:
- macOS X 10.13 Sierra or later
- Author / Product:
- OBS Team / OBS Studio for Mac
- Old Versions:
- Filename:
- macos-25.0.8.dmg
- Details:
- OBS Studio for Mac 2020 full offline installer setup for Mac
OBS Studio for Mac is a free and open source software for video recording and live streaming. Download and start streaming quickly and easily on Windows, Mac or Linux. Control your stream from your Mac desktop with OBS Studio for macOS!
OBS Classic and OBS Studio are both equipped with a powerful API, enabling plugin development to provide further customization and functionality specific to your needs. Work with developers in the streaming community to get the features you need. OBS has been rebuilt from the ground up to be even more lightweight and high performance than before.
Hide your real IP address and protect your privacy while online! Check out HMA! Pro VPN for Mac!
Features and Highlights
High performance
Real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions.
Filters
For video sources such as image masking, color correction, chroma/color keying, and more.
Intuitive audio mixer
With filter functionality such as noise gate, noise suppression and gain.
Powerful and easy to use configuration options
Add new Sources, duplicate existing ones, and adjust their properties effortlessly.
Improved and streamlined Settings panel
For quickly configuring your broadcasts and recordings.
Both light and dark themes
Available to fit your preference.
Also Available: Download OBS Studio for Windows
Older entries..
Apr. 24, 2015
Apr. 25, 2015
Apr. 27, 2015
Apr. 28, 2015
Apr. 30, 2015
May. 1, 2015
May. 4, 2015
May. 5, 2015
May. 6, 2015
May. 7, 2015
May. 9, 2015
May. 11, 2015
May. 12, 2015
May. 14, 2015
Newer entries..
item.209681
Bob Jansen
After upgrading to Yosemite 10.10.3 using Software Update, I am finding the computer less stable with regular crashes and,more often preceding a crash, external screen display corruption.
I am not sure this is related to the Preview problem, discussed earlier on MacInTouch.
The screen corruption issue is primarily on a screen connected via the Thunderbolt port (or is it Lightning, I can never remember which) using an Apple Thunderbolt — DVI connector.
My other external monitor is connected via a USB dongle and basically works a treat,
Anyone else seen any behaviour like this?
Macbook Pro mid 2010
8GB RAM
NVIDIA graphics 330M 256MB
Apr. 25, 2015
item.209732
Peter Lovell
Bob Jansen wrote:
After upgrading to Yosemite 10.10.3 using Software Update, I am finding the computer less stable with regular crashes and, more often preceding a crash, external screen display corruption.
I am also having a display problem after the 10.10.3 update, but the details are different and I wonder if anyone else has seen them.
Occasionally there is a small flashing rectangle on screen, about an inch wide and 3/16 high. In many cases it seems that there are five tiny images side-by-side. The flashing rate varies, and in at least one instance it was just ‘on’ with no flashing. I have not been able to associate it with any particular process. It is transient so if you move a window over it, it goes away. Closing apps does not make it go away (unless you close the app whose window it happens to be in). Sometimes it appears on the open desktop, sometimes within an app window, sometimes crossing window boundaries.
I suspect some kind of memory-blasting but that’s just a guess. I have had two unexplained kernel panics since installing 10.10.3, so there might be some correlation.
Some background on the setup: it’s a 2012 Mini (quad i7) with 16 GB memory. Problems such as this never happened with earlier OS versions (10.9.x or 10.10.x). The 10.10.3 update was applied using the Combo updater. There are two Apple displays, and the problem can occur on either one.
Apr. 27, 2015
item.209767
John Leiher
Absolutely all the same problems here after the Yosemite 10.10.3 update. Small flashing rectangles on one or the other monitors that I’m using (not on both at the same time)..
I’ve also had frequent (5) unexplained kernel panics since that update.
I initially did the update via the App Store, and, once the problems began, I reinstalled it using the stand-alone combo updater.
Most disconcerting for me are the kernel panics — 10.10.2 offered none of the grief of the 10.10.3 update; I’m actually seriously thinking of reverting back. My machine, coincidentally, is also the 2012 i7 2.3 quad Mini with 16 GB ram — a beautiful wee thing until 10.10.3 bit it.
item.209776
Bruce Klutchko
This is a followup and correction to my post Saturday in response to Peter Lovell and Bob Jansen, who noticed video artifacts and kernel panics in 10.10.3. I wrote that I had removed all kexts except for Soundflower and Little Snitch and was still experiencing these symptoms.
Removing Little Snitch (latest version, 3.5.2) ended all the video artifacts and kernel panics.
I’ve sent the crash report, which includes ‘BSD process name corresponding to current thread: Little Snitch Ag’ to Objective Development. I noticed there are a number of similar reports on their forum.
There is a possibility that Little Snitch only gives trouble on a Mac Mini with 10.10.3, so it may be rare. Or it may have been installed incorrectly due to some system incompatibility during the period of time before Apple released the supplemental update to 10.10.3. This timing would also make it a rare problem. I haven’t tried reinstalling Little Snitch to find out if the latter possibility is true, because I hate seeing my Mac panic and restart.
I love Little Snitch and held off on writing this, hoping that it was not to blame. But it’s already been about 20 hours without any trouble. Before removing it, I couldn’t go 2 hours without a crash. I’ve also noticed that Safari now manages its memory better, frequently reducing the memory usage of web content processes and compressing memory successfully. That wasn’t working before, either.
item.209764
Bruce Klutchko
Peter Lovell wrote:
Bob Jansen wrote:
After upgrading to Yosemite 10.10.3 using Software Update, I am finding the computer less stable with regular crashes and, more often preceding a crash, external screen display corruption.
I am also having a display problem after the 10.10.3 update, but the details are different and I wonder if anyone else has seen them.
Occasionally there is a small flashing rectangle on screen, about an inch wide and 3/16 high. In many cases it seems that there are five tiny images side-by-side.
I had the flashing rectangles and also panic attacks. I reapplied a combo updater without effect and reinstalled the entire OS without help (but I was shocked how fast it installed on my Mini — under 30 minutes)/
Today I removed all non-Apple input managers, Internet plugins, kexts, etc. except Soundflower. I just removed Little Snitch and am waiting to see if there’s another crash. I’m certain this had to do with the 10.10.3 update, but, so far, I don’t know what the problem is. Maybe it’s the video cards on our Minis? The last crash report fingered Little Snitch, but it has been a different app each time.
item.209754
Mark Thomas
Peter Lovell wrote:
‘I have had two unexplained kernel panics since installing 10.10.3?’
I have had three. I wasted many hours troubleshooting in order to figure out what I’d done wrong.
Turns out what I’d done wrong was I’d installed Apple’s ‘update’.
item.209804
Bill Martin
Mark Thomas wrote re:
Peter Lovell wrote:
‘I have had two unexplained kernel panics since installing 10.10.3?’
I have had three. I wasted many hours troubleshooting in order to figure out what I’d done wrong..
.. Have you tried booting into Safe mode or a test account to see if the problem exists there? Have you disabled extensions and plug-ins? ..
item.209762
Bob Jansen
More on my screen corruption issue: Looking into things a bit closer, now that I’ve got some more time, the corruption shows up as tiles of other parts of the total displayed information, so maybe tiles of Finder info or parts of one of the other screens, sometimes with black or grey reaction goes to corrupt the actual display. Other times, on the menu bar, there are black flashing areas, usually on the right hand side of the menu bar.
I also notice that screen updates slow down noticeably, mouse movements are not real time, they lag the actual mouse. Typing is also slowed down with typed characters appearing some time after pressing the key character.
All in all, it looks like a screen memory issue. Rebooting solves the problem, as does removing the Thunderbolt dongle, thus removing the Thunderbolt-driven display. Removing the USB display makes no difference.
item.209763
Bob Jansen
More detective work: The problem might be related to App for Trello, an app that I recently installed to make access to Trello simpler. It is a menubar item and appears to do a background refresh. Removing this app seems to make things more stable but not completely.
Also, I mostly display Safari on this monitor and just now, the Safari window got scrambled, but OpenOffice windows also on the monitor didn’t. So, maybe also a Safari problem.
item.209823
MacInTouch Reader
The description Peter Lovell gives is 100% dead on for the flashing rectangle. I have seen it on both my Mac Minis — 2012 — one i5, one i7, both with hand-built fusion drives and 16 GB of RAM. It goes away easy enough, but it is really annoying and was not there prior to 10.10.3. My setup, the i7, has two 23' Cinema displays; the i5 has two 22' Dell displays. I have had 1 kernel panic on the i7 since updating.
item.209845
MacInTouch Reader
Hi,
I recently switched from Chrome to Safari on my MacBook Air running 10.10.3 to test a theory that Chrome was eating up my battery life. I think it is, but that’s not the subject of my question.
In Chrome, I can make a new Incognito Window and it is blank. In Safari, I seemingly can only make a new Private Window that automatically contains exactly the same thing a regular new Window contains. In my case, that’s a set of four tabs I use a lot.
This seems silly to me. Ideally, I would have some more options under General preferences, such as ‘New Private Windows open with’. Additionally, ‘Safari opens with’ should have the option to open a tab folder.
Does anyone have a workaround for this? What am I missing? Is there a plugin that can provide this behavior?
Thanks!
-Jonathan
p.s. I installed the SIMBL SafariStand just to get Safari tabs to have icons on them. Apple makes some weird choices IMHO.
Apr. 28, 2015
item.209827
Doug Unruh
I, too, am having the problem of a portion of my screen scrambling looking like little tiles. I’m not sure what the issue is; however, previously, I had a similar problem in the Finder window area. This problem was related to using TotalFinder. I don’t know if this issue might also be related to this app. Do any of the users reporting this problem use TotalFinder?
item.209849
Peter Lovell
Many thanks to all who took the time and effort to respond to my question about the funny flashing rectangles. So we can better integrate the available data on this, here are a few of my own data points ..
- I have been running Little Snitch, but it has been so trouble-free that I hadn’t suspected it. That’s actually a ‘bad’ on my part, as I used to build stuff that was similar, and kernel crashes were part of my daily routine
Soundflower For Os X 10.10.4 Pro
- Little Snitch is in a position to cause the problems that I’ve seen reported. Part of it runs in kernel-mode and therefore has privileged access to lots of system resources, such as memory. Putting stuff where it’s not supposed to go will sometimes cause video artifacts, other times it will cause the system to panic or crash
- kernel processes don’t normally address memory assigned to user-space (they can, but typically don’t), so it’s unlikely that memory corruption would crash an app directly. The corruption is more likely in memory assigned to the kernel. Of course, this can cause the app to crash, but indirectly
For the time being, I have turned off the filter and monitor functions [in Little Snitch], and I’ll wait to see how things unfold.
item.209814
Ed Graf
With the 10.10.3 ‘update’ I started experiencing problems with the bluetooth mouse as well as connectivity problems. Switched my AirPort Extreme from 2.400 to 5.000 GHz, which locked out my iPhone 4. Even a crash when the GPU switched from Intel to NVIDIA.
Reading the MacInTouch site, I forgot about using the ‘full’ updater, which I quickly downloaded and applied last week. Fingers crossed, but was able to switch the Extreme back, no crashes and mouse works fine.
Once again, thanks to you all for your input.
Apr. 30, 2015
item.209851
Bob Jansen
Many thanks to all who took the time and effort to respond to my question about the funny flashing rectangles. So we can better integrate the available data on this, here are a few of my own data points ..
- I have been running Little Snitch, but it has been so trouble-free that I hadn’t suspected it. That’s actually a ‘bad’ on my part, as I used to build stuff that was similar, and kernel crashes were part of my daily routine
- Little Snitch is in a position to cause the problems that I’ve seen reported. Part of it runs in kernel-mode and therefore has privileged access to lots of system resources, such as memory. Putting stuff where it’s not supposed to go will sometimes cause video artifacts, other times it will cause the system to panic or crash
- kernel processes don’t normally address memory assigned to user-space (they can, but typically don’t), so it’s unlikely that memory corruption would crash an app directly. The corruption is more likely in memory assigned to the kernel. Of course, this can cause the app to crash, but indirectly
For the time being, I have turned off the filter and monitor functions [in Little Snitch], and I’ll wait to see how things unfold.
Peter,
Further to my problems, I found that TrimEnabler was not up to date and appeared not to be running. It used to run but somehow got turned off. Updating to the latest version and setting it running seems to have stabilised my environment.
I also run Little Snitch, version 3.5.2. Will try turning that off next if the problem returns.
Have not reinstalled App for Trello though and will not at this stage, although it was a useful shortcut.
item.209880
MacInTouch Reader
Wow, I thought I was the only one experiencing the weird graphics block glitches since updating Yosemite.
Thanks to Peter Lovell for pointing out the potential that Little Snitch might be involved. I, too, run Little Snitch (which is awesome and I consider essential). Hope this is resolved soon.
item.209881
Bruce Klutchko
Thanks to Peter Lovell for bringing up an important issue about kernel extensions. I would like to reiterate and emphasize something he wrote: Kernel extensions have a tremendous capacity to interfere with System functioning without our realizing it.
After installing 10.10.3+, despite removing a number of kernel extensions, my Mac Mini was crashing a number of times a day and showing those rectangular video artifacts. I removed Little Snitch and didn’t experience any panics for almost a day. Then I noticed that the version of Soundflower that was still installed was from 2011. There is, however, a ‘new’ version from 2012. I removed Soundflower, as I’ve only used it a handful of times over the years.
More importantly, I realized that there is no organized way of notifying users that an extension is out of date. When Apple updated its OS to 10.3.3+, I think more extensions became incompatible. Apple really provides no utility to say ‘Delete these guys — they’ll cause a kernel panic.’
So once we install a system level extension, it can be a major challenge tracking down the causes of a crash. Over on the Apple boards, there are a lot of discussions about panics in Yosemite 10.3.3. Maybe these panics are really from extensions that were once compatible, but now aren’t.
It has now been 36 hours without a kernel panic. I’m still keeping my fingers crossed.
item.209973
Bruce Klutchko
Peter Lovell wrote:
Many thanks to all who took the time and effort to respond to my question about the funny flashing rectangles. ..
I have been running Little Snitch, but it has been so trouble-free that I hadn’t suspected it. That’s actually a ‘bad’ on my part..
I wrote Objective Development tech support about Little Snitch, and they very kindly wrote back. They said that Little Snitch is not the cause of instability, but instead said an outdated versions of Soundflower was doing this on my machine. They pointed me to Rogue Amoeba, which is currently hosting an updated version of Soundflower [here].
I plan to re-install Little Snitch and see what happens.
item.209891
Paul Ukena
Back in Mavericks, many users reported computer slowdowns, to the extent of non-usability.
I reached this point myself, where frustration with general slowdowns and Mail in particular finally made me put on my old troubleshooting hat and try to find out if any third-party app was the culprit. After some hours of turning things off and on, I found that deleting Little Snitch returned my computer to its zippy state. Not turning it off; deleting it and then zapping the PRAM. I reinstalled Little Snitch, and the slowdowns returned immediately. Uninstalled it and zapped PRAM; slowdowns gone. I reported my experience here and on some other forums, and no one commented at all.
I suspected (and still have not ruled out) that it might be some other 3rd-party thing that conflicted with LS, but I was glad enough to have zippiness back, I did no more research. Incidentally, this only happened on my 2012 MacBook Pro Retina; my 2012 11' Air had no problems with slowdowns with LS installed.
A couple of weeks after I installed Yosemite, I installed LS again, and experienced no slowdowns. I chalked it up to something changing in the underlying structure of the OS, or something changing in one of the other updated 3rd-party apps.
item.209924
Jim Steckel
Doug Unruh wrote:
I, too, am having the problem of a portion of my screen scrambling looking like little tiles. I’m not sure what the issue is; however, previously, I had a similar problem in the Finder window area. This problem was related to using TotalFinder. I don’t know if this issue might also be related to this app. Do any of the users reporting this problem use TotalFinder?
For what it’s worth: I run TotalFinder 1.6.17 on a 2014 iMac and a 2012 MacBook Pro, both using Yosemite OS X 10.10.3, and have no screen problems.
Sorry, I hate messages like this that don’t help me solve my problem [laughing].
item.209971
Bill Gallagher
I have been trying to find the source of a similar experience with those little squares popping up every so often. I thought my monitor was starting to go. Mine has been occurring for months, and I haven’t installed. 10.10.3 yet.. and I am no longer running Little Snitch (did at one time).
I was never able to find a source for the problem or what might have caused the onset. I do know that it seems to be exacerbated when switching desktops with a three-fingered swipe on my wireless Trackpad. Every so often the checkerboard pattern will go really nuts and start blinking during a swipe, and the screen will freeze halfway between one desktop and another.
item.209958
Bob Jansen
Peter,
I seem to have found my problem: TrimEnabler. I had the older version. Updating to the latest seems to have got rid of all instability.
So, maybe the comment about KEXT’s is on the mark.
item.209943
Gary Kellogg
Under Yosemite 10.10.3 I have noticed that Screen Sharing’s full screen mode seems very badly behaved: When viewing the screen of a shared computer in full screen mode on my wireless network, I find that when I need to use an application on the shared machine it works fine until I need to select a command from the app’s menu. When I attempt to do so, Screen Sharing switches almost immediately from Full Screen mode to Windowed mode and may very likely register a click on a somewhat random menu item on my local machine, or, more likely, none at all. On rare occasions I can register the click as I wish; however the screen still jumps into Window mode.
I am looking for a way to make Full Screen mode stay that way long enough for me to use menu items on the shared machine (i.e., not be so enthusiastic to get out of Full Screen mode). In Windowed mode, everything works predictably. Could there be a hidden preference? Is there a workaround? Or is this just another bug to report? Thanks.
item.209969
Keith Nichols
Neither Dashboard nor Launchpad could be summoned today using the icons in the dock, although Dashboard could be summoned via the Applications list. Then that failed to summon Dashboard. Is there a way to return Dashboard? I don’t really need Launchpad.
May. 1, 2015
item.210002
MacInTouch Reader
Re. KEXTs — Kernel Extensions:
My first ‘personal experience’ with kexts arose when Apple started allowing only signed kexts in Yosemite.
Before that, I had used both Chameleon and Trim Enabler on different Macs to install third party SSDs, without a thought for kexts.
Oh, I’d heard dire warnings about kexts for years. Never had a problem. Don’t even know if I ever had a program that utilized a ‘custom kext’ — until I wanted to enable TRIM.
In researching kexts I found Apple’s related developer pages.
In the ‘Overview’ section there’s a list of problems a bad kext can cause, and suggested alternatives to using a kext at all.
There’s also a list of reasons a developer might need a kext, much of which seems to be accessing hardware directly.
Sticking to the ‘executive summary level,’ I get that directly accessing hardware could enable a bad program to do bad things (as well as get in the way of others with different expectations).
Apple, however, in its developer site, and I presume more fully elsewhere, provides instructions and tutorials how to write ‘good kexts.’
Aggressive Googling turned up only a pointer to ‘forms’ behind Apple’s developer pay wall to ‘apply’ for a kext certificate. I found no external indications how (or if) Apple is approving ‘kext requests.’
Last, a question: Is Apple’s ‘switch’ that disables third-party SSD TRIM itself a kext?
Clearly, it’s an ‘Apple policy.’ So I’d presume an application for a signed kext to unlock Apple’s lock wouldn’t be approved.
These posts will take you deeper than you probably want to go:
Can’t sign kext in Mavericks/Yosemite? [Stack Overflow]
Gatebreak: Signed Kexts for Everyone [tonymacx86]
item.210013
Harold Zeh
Gary Kellogg asked how to keep Screen Sharing from exiting Full Screen Mode when attempting to drop a menu from the menu bar on the shared computer. You have to approach the menu bar slowly and not bang the pointer to the top of the display. Come close to the top, and into the menu bar area, but not hit it.
The behavior (like what Gary described) of Apple’s Screen Sharing client app is too odd for my tastes, so I use JollysFastVNC Home client (now on the App Store.) There is also a beefier version, but I do not share too many screens, nor access them from outside my local network — and the price is very right.
You still have to approach the menu bar with caution (not bang the display top) in a full screen view or the underlying machine’s menu bar drops — but the shared full screen machine stays without going into a sort of Exposé mode. I have also used (tried-out) Remotix and liked it also (more than I needed.) But not sure how it works these days.
I wish Apple would optimize the VNC server for Retina Displays. Long enough, already!
item.210026
Sterett Prevost
New 2015 Retina 12' MacBook (1.3 GHz, 512GB SSD) that came with 10.10.2. Due to lack of appropriate cables, had to migrate over wi-fi from 17' MacBook Pro running 10.9.5. It took 18 hours with the time remaining counter info increasing, stalling & decreasing from time to time. Just left it alone until it ‘said’ finished.
Both accounts got transferred OK (one regular, one admin). Did all the App Store updates to include the delta 10.10.3. Followed up by doing the combo 10.10.3 update, repair permissions, and FSCK on a single user restart.
Only glitch so far is that none of the menu extras, such as sound, wi-fi, and clock, appear when asked to do so in the appropriate System Preferences panels. Does anyone know how to get them to appear, or will we have to wait for 10.10.4?
May. 4, 2015
item.210086
David Charlap
An anonymous MacInTouch reader asked:
Last, a question: Is Apple’s ‘switch’ that disables third-party SSD TRIM itself a kext?
Not quite.
As I understand it, TRIM support itself is implemented via a kext. It checks the model of SSD and refuses to run if it doesn’t describe itself as a model that Apple [built into the computer and] supports.
Products like TRIM Enabler work by modifying the Apple-provided kext so that it no longer performs the check but blindly approves every SSD it finds. The reason this doesn’t work on Yosemite is because that kext’s signature (from Apple) no longer validates the kext, because the kext has been modified. Which is 100% correct — the signature should not be valid anymore.
There are several possible solutions to this problem.
1: Disable the OS’s support for kext signatures. This works, but it also opens the door to allow any other non-signed or invalid-signature kexts to run. In other words, any user or app (or malware) with permission to add or modify a kext file can do so.
2: Apple modifies their TRIM kext to support third-party SSDs, or provide a configuration option to do this. I wouldn’t hold my breath waiting for this solution.
3: Someone hacks Apple’s certificate and its private key so they can re-sign the modified kext and make it look like the change came from Apple. This shouldn’t be possible without someone stealing (hopefully restricted) data from Apple. And if it is done, you can bet that Apple will revoke their certificates, generate new ones, and issue critical system updates to push the changes to all customers. So this approach really isn’t viable either.
4: Someone who has a developer certificate that’s valid for kexts releases a modified TRIM kext signed with their own cert. But I think it’s reasonable to assume that Apple would not approve of this and would revoke that developer’s certificate in response.
5: Someone who has a developer certificate develops a completely new TRIM kext (not based on any Apple code) and releases it signed with his own certificate. Apple might not object to this, but it would be a massive engineering effort, and the developer would have to keep the code compatible with newer versions of Mac OS X. I wouldn’t expect such a solution to be a free product.
item.210109
Simon Wagstaff
In Item 210002, a MacInTouch reader wrote, re. KEXTs — Kernel Extensions:
.. Don’t even know if I ever had a program that utilized a ‘custom kext’ — until I wanted to enable TRIM..
Enabling TRIM isn’t really a ‘custom kext,’ it’s a hack that removes a string from an Apple kext, which has the effect of enabling TRIM for SSDs. Making this change to the Apple kext will cause the signature check to fail (which is what it’s supposed to do: identify that signed system software is changed, perhaps without the user’s knowledge).
The reader also wrote,
.. I found no external indications how (or if) Apple is approving ‘kext requests.’ ..
Little Snitch is a well-known utility that includes a signed kernel extension.
item.210115
Velvet Jones
Re:
Last, a question: Is Apple’s ‘switch’ that disables third-party SSD TRIM itself a kext?
I believe [the kext code-signing requirement] is an NVRAM flag, or possibly in the com.apple.boot.plist file.
Specifically,
nvram boot-args=kext-dev-mode=1
is the command that’s needed to allow unsigned kexts to load.
item.210219
Shirley Sanderson
Just upgraded my MacBook Pro to Yosemite a couple of days ago. I have experienced few problems, but after reading today’s Yosemite discussion here, decided to try to delete Photos. I was an Aperture user and then moved to Lightroom after Aperture was neglected and finally abandoned.
When I try to delete Photos, I get a message saying it can’t be done because it is required by the OS. Really, Apple? I never want to use Photos, and can’t imagine why it would be required by the OS. Does anyone know how I can get rid of Photos and reclaim some disk space?
[While Apple completely prevents deletion of its own, unwanted apps on iOS, at least OS X still lets the owner have a bit more control over their computer. Others have suggested booting from a different drive to enable deletion of the unwanted Apple Photos app. If that doesn’t work, let us know, and we’ll come up with another workaround. -Ric Ford]
May. 5, 2015
item.210194
MacInTouch Reader
As I understand it, TRIM support itself is implemented via a kext. It checks the model of SSD and refuses to run if it doesn’t describe itself as a model that Apple [built into the computer and] supports.
Products like TRIM Enabler work by modifying the Apple-provided kext so that it no longer performs the check but blindly approves every SSD it finds. The reason this doesn’t work on Yosemite is because that kext’s signature (from Apple) no longer validates the kext, because the kext has been modified. Which is 100% correct — the signature should not be valid anymore.
There are several possible solutions to this problem. [..]
I think it would be easier to get a dump of Apple SSD firmware, find the hex for the ID, then put that ID on the other manufacturer’s SSD. Then TRIM should work. Maybe.
Problem is:
- tool to access Apple’s firwmare
- tool to access 3rd party SSD
- ability to restore in case it goes wrong.
[Angelbird’s SSD wrk for Mac apparently mimics Apple’s own SSD identification, so ‘SSD wrk for Mac is the only 3rd party SSD that supports TRIM for Mac straight from the box. No driver, software or TRIM Enabler is needed!’ -Ric Ford.]
item.210197
MacInTouch Reader
Re:
.. I found no external indications how (or if) Apple is approving ‘kext requests.’ ..
Little Snitch is a well-known utility that includes a signed kernel extension.
Thanks. It was an eye-opening experience to open
/Library/Extensions where I found the LittleSnitch.kext identified to Objective Development November 14, 2014 (among others) and /System/Library/Extensions where I found many more. Right-clicking on them to ‘Get Info’ provides some insight into their source.
The Mac I’m using was given a clean Mavericks install and later updated in place to Yosemite 10.10.3
item.210207
Michael Fussell
Re:
1: Disable the OS’s support for kext signatures. This works, but it also opens the door to allow any other non-signed or invalid-signature kexts to run. In other words, any user or app (or malware) with permission to add or modify a kext file can do so.
But all OS X versions before Yosemite ran this way, did they not? So disabling kext signatures causes this part of Yosemite to run just like Mavericks.
There is another solution. Buy an SSD that announces that it is an Apple SSD and thus fools the Apple trim kext into running.
item.210224
G.J. Parker
To delete any file.. in an Admin account, open Terminal (usually sits in Utilities under Applications). You should get a window. in that window type
sudo rm -rf
and make sure you have a space at the end — do not hit Return now..
In the Finder, navigate to what you want to delete (e.g. Photos, which probably sits in Applications). Drag-and-drop the icon onto the Terminal window. It should have added the full path in the Terminal, e.g.:
sudo rm -rf /Applications/Photos.app
Now click on Terminal and press the Return key. It will ask you for your password in Terminal. Type it in. It will then delete whatever you drag-and-dropped. It will *not* show up in the Trash. It’s gone. For good. Forever.
One should be careful with Terminal. You should be especially careful with the command we typed in, sudo rm -rf, since it’s telling the system you’re going to something w/ root privileges (the ‘sudo’- i.e. you can do anything), it’s going to remove something (the ‘rm’) by doing a recursive delete (the ‘r’- it’s required to delete apps on Mac). and it will force the delete (the ‘f’- no questions asked).
(If this doesn’t work, then Apple actually broke Unix. If Apple breaks Unix, then it’s not Unix any more, and I won’t be an Apple customer any more, either.)
item.210227
MacInTouch Reader
Apple appears to be using a Deny everyone delete ACL (Access Control List, a modern permission implementation) on its own applications in /Applications, just like they do on some (or all) of the top-level home directory folders and System folders.
As a system administrator who finds himself supporting friends a lot, I appreciate this — it eliminates the ‘I deleted [insert this important application]’ calls. I assume this is why Apple choose to do this.
Not even root can delete a file or folder with an Everyone Deny delete ACL. I’ve seen this offend some long time system admins who expect root to be able to do anything.
The ACL can be removed by root or a superuser using the terminal using the command:
chmod -N path to the file or folder
Once removed, the file or folder can be deleted by a user with privileges to do so.
item.210228
MacInTouch Reader
[While Apple completely prevents deletion of its own, unwanted apps on iOS, at least OS X still lets the owner have a bit more control over their computer. Others have suggested booting from a different drive to enable deletion of the unwanted Apple Photos app. If that doesn’t work, let us know, and we’ll come up with another workaround. -Ric Ford]
Reggie Ashworth’s AppDelete (free trial) will do the job and offers an archive option if a re-install might be desired. The archive offers additional utility, as it facilitates moving some individual applications from one Mac to another.
In my experience the free similar AppCleaner didn’t remove Apple’s applications.
item.210269
Peter Lovell
[Re: screen corruption problems and kernel extensions..]
‘For the time being, I have turned off the filter and monitor functions [in Little Snitch], and I’ll wait to see how things unfold.’
Well, even without Little Snitch, it still happens. There are no kexts other than ones from Apple, so I’m at a loss to know what might be the cause. It wasn’t happening before the 10.10.3 update, so I think there’s some relation there, but I don’t know just what.
May. 6, 2015
item.210318
MacInTouch Reader
Re: Disabling kernel extensions signature, Michael Fussell writes:
‘But all OS X versions before Yosemite ran this way, did they not? So disabling kext signatures causes this part of Yosemite to run just like Mavericks.’
I completely agree. IMHO the risks of doing this are vastly overblown. Besides, if you have a hackintosh, you must disable kext signature anyway.
item.210289
David Taylor
rm -rf is juggling chainsaws unless you really know what you are doing and even sometimes at other times.
A number of years ago the IT guy was updating the Unix on a large (> 50 programmers + testers) in the middle of the night. In the clean up of an area he did rm -rf and wondered why it took so long, until he realized he was at root. He had complete backups, but it still shut things down for most of a day.
item.210291
David Charlap
G.J. Parker wrote..
sudo rm -rf /Applications/Photos.app
Yes, this will delete the app package, but it may not completely solve the problem.
There may be other installed files (e.g. stuff in various Application Support folders, maybe Launcher items, etc.) which should also be deleted. And there will be a ‘BOM’ (bill of materials) file in a ‘receipts’ folder.
Also note that if there are any periodic background tasks (e.g. Launcher items) that access files within the Photos.app package, they will start failing until you disable/remove them. Hopefully, the failures will just spew error messages into your system log and not cause other problems.
In other words, yes, you can always forcibly delete an application package, but that is not necessarily all you need to do in order to properly uninstall it.
item.210337
Arthur Van Der Harg
G.J. Parker writes
You should be especially careful with the command we typed in, sudo rm -rf, since it’s telling the system you’re going to something w/ root privileges (the ‘sudo’- i.e. you can do anything), it’s going to remove something (the ‘rm’) by doing a recursive delete (the ‘r’- it’s required to delete apps on Mac). and it will force the delete (the ‘f’- no questions asked).
One of the most breathtaking mistakes I ever made was typing sudo rm -rf . /*
while working late at night on the HP/UX computer that our entire group used. By the time I realised ‘hey, this is taking too long’, noticed the superfluous space and hit ctrl-C, the command was halfway through /bin. Luckily I don’t panic easily and knew not to reboot. With what was left of HP/UX I was able to reinstall the OS.
So Mr. or Mrs. Parker is right: do be careful when using sudo rm -rf.
But s/he’s wrong about one other thing: ACLs can override file permissions and they’re part of modern Unices.
So it is possible to prevent root from removing a file without having ‘broken’ Unix.
item.210313
Robert Bradford
I am running Yosemite 10.10.3, Server 4.1 on a 2014 Mac Mini (2.6GHz Core i5, 8 GB RAM). I can connect to it via VPN PPTP but not L2TP. Java se runtime environment 6. A Mac client running Yosemite 10.10.3 gives an error message ‘The L2TP-VPN server did not respond..’ Any suggestions?
May. 7, 2015
item.210384
Soundflower For Os X 10.10.4 Server
Motti Shneor
Regarding strange rectangles, duplicates or not, and other transient artifacts onscreen, there are usually two possible causes for this. (I’ve experienced, and still experiencing this on an old iMac i’m using).
1. GPU (the graphic processor on the display card) malfunction.
2. Mac OS integration with the specific GPU is broken. One of the low-level operating-system components, either the hardware driver, ‘Quartz’ Implementation or the Core-Graphics implementation suffers a serious bug.
You should register a bug at Apple, and maybe even go to an Apple Store to ask for resolve.
If #2 is the cause, no hardware fix can remove the problem (hmmm, unless you install a new type of GPU?), but if #1 is the cause, Apple should replace your GPU or the whole main board if necessary.
On my old 24' white iMac bought in 2006, the switch to OS X 10.7 started the problem (the problem would go away if I boot into 10.6.x). But the GPU overheated regularly, and eventually failed. I then replaced it (hard to do, and expensive too!) and then I had a year of normal function.
Now it fails again.. so you can see this is a tricky problem. Of course my Mac is not covered in any way, and Apple doesn’t seem to test its new software seriously on old hardware anymore.
Times have changed — for worse.
item.210372
Manny Veloso
I am running Yosemite 10.10.3, Server 4.1 on a 2014 Mac Mini (2.6GHz Core i5, 8 GB RAM). I can connect to it via VPN PPTP but not L2TP. A Mac client running Yosemite 10.10.3 gives an error message ‘The L2TP-VPN server did not respond..’ Any suggestions?
Make sure that the interface the L2TP/IPsec VPN is listening on is the primary (first in the list) interface. It won’t work if it isn’t.
item.210373
Nate Goldshlag
Yosemite doesn’t even multitask properly anymore. If I export a large calendar and then switch to the Finder, I can open a Finder window but I cannot delete any files using Command-delete. Nothing happens. After the export is done, I can once again delete files. Grrr…
item.210346 Best vpn for mac pro.
Antony Gravett
On an otherwise fully functioning install of 10.10.3 on a mid-2012 MacBook Air, I am getting a strange ‘phantom’ display of only the outline of the Maps main window (see screenshot at maps-mystery.jpg). This screenshot is on a bare desktop with only a dark gray desktop chosen; a similar ‘phantom’ shadow appears over the top of other apps’ windows, when they are displayed. This happens on both the MBA’s own screen and on an attached monitor.
It’s not possible to send a problem report, because its window is only displayed as a minimal top shadow (as also shown in the screenshot), and even the ‘About Maps’ dialog box is missing some interface elements. The app will start up and quit normally, and its menu displays, but it is obviously not possible to interface with it in any other way.
I have tried deleting preferences, with no success. Reviewing a trial version of AppDelete, I was tempted to remove Maps and its associated files completely, but was unsure as to how (or if) I could then restore a fresh copy.
Any tips or guidance about restoring Maps’ functionality would be welcomed!
item.210369
G.J. Parker
As both Arthur Van Der Harg and, previously, a ‘MacInTouch reader’ pointed out, ACL may not allow root to delete a file/folder/app. Further, the ‘MacInTouch reader’ conveniently gave the solution, namely
chmod -N path to the file or folder
would have to be issued first if sudo rm -rfpath to file, folder or app fails.
Personally, I find this breaks Unix’s purpose of root — the all powerful (and therefore potentially harmful) user. If I’m root, I expect the system to do what it’s told (even if what I told it was harmful/idiotic) and not to throw an error. I don’t want or expect root to have ‘training wheels’. In this case, the error is easily overcome by doing the ‘chmod’, so I find it redundant and pointless.
David Charlap is also correct — just because Photos.app was deleted, it doesn’t mean everything is gone concerning Photos. (In my defense, this was not asked — Shirley Sanderson wanted to delete Photos.app). One way to figure this out is to look at the BOM package for Photos to see what was installed and where and to delete it. In some sense, I think this is a red herring — the system should gracefully deal w/ any potential errors (i.e. complain to a log file and give up).
Finally, not that it matters, Arthur, but it’s ‘Mr.’..
item.210360
Vince Heuring
Years ago a colleague at Univ. of Colo. Boulder wanted to do a rm -rf A* to remove all files that started with A,but he carelessly typedrm -rf A *thus deleting all files in the directory that started with A, and then all the files in his home directory.
He was antagonistic towards Unix from that day forward.
PS: you can always alias rm to move the files to /tmp, where you can delete them later. Sort of like the way Trash works.
item.210379
Ian Wright
Comment on Item 210289 ..
My horror story involved cleaning up ‘Mac poo’ on a Linux server running a university website. I’d been working as root after a major system failure and we were about ready to turn backups back on.
I was removing the ‘invisible’ Mac files left behind, (._filename.xxx) and was using:
rm -R ._*
Or so I thought. A typo resulted in:
rm -R ._ *
That space between _ and * resulted in about a third of the site disappearing forever. In the absence of a Fairy Godmother with a magic wand, I wasn’t very popular with our sys admins for a day or two.
May. 9, 2015
item.210426
Bob Jansen
Following up on my previous reports of external display distortions:
I have an app that I have coded in Xojo. Works a treat on the main monitor of my MacBook Pro, but on the Thunderbolt-connected display it crashes. Investigation, using Xojo’s debugger indicates it is not a problem of Xojo or my code, as the debugger does not trap the condition; the debugging app just crashes the moment I move it onto the external Thunderbolt display.
I sent the error report to Apple.
Interestingly, my external USB display behaves as normal.
I thought I had it solve. but obviously I haven’t.
item.210427
Bob Jansen
Further investigation about my external Thunderbolt display corruption:
I used the Display System Preference to set the Thunderbolt display to Scaled instead of Default for Display.
The display is an HP L2445m connected via a Thunderbolt-DVI connector bought from Apple.
Soundflower For Os X 10.10.4 Version
Amazing, no corruption for about 30 minutes now.
Have I got it??
item.210486
Bob Jansen
Further to my distorted external thunderbolt display, I have found that using the Displays System Preferences pane and setting the display to Scaled instead of Default for device, seems to cure my problem, no distortion for a couple of hours work.
The only issue is that Yosemite does not remember the setting for the display and hence when I reconnect it, I have to set the Scaled value again.
item.210484
Tim Binder
Reading all these horror stories of ‘rm -rf’ (and I’ve got some of my own), I thought I’d share a Unix (bash?) tip:
Before deleting things, especially with a wildcard, list the files; for example
ls A*
This should show all the files/directories that will be affected. If it looks correct, then issue your rm -rf but use !$ — which means ‘the last value on your previous command.’ So the full command will be
rm -rf !$
This adds a little bit of safety, but you still need to be wary.
item.210437
Kevin Ohlson
When I used to be more active with Unix command lines, it was just this reason that I learned to replace rm with lsfirst. That is, first show me what files will be affected. Saved me more than once from unintended actions.
item.210424
Arthur Van Der Harg
Mr. Parker asserts that he expects the system to do what it’s told when issuing commands as root. Actually, it is. That particular ACL setting is not the default. It must have been set by root to prevent even root from inadvertently removing the file. root said unto Unix: ‘Do not let me remove this file.’ So by refusing to remove it using rm -rf, Unix actually does what it was told to do..
item.210428
David Taylor
Unless you are deleting a zillion files, it is useful to add the confirm switch ‘i’. That is;
rm -irf whatever
Even if you have many files to delete, this will let you have another chance. If happy, you can ^c then up-arrow to edit out the ‘i’ and go.
item.210508
MacInTouch Reader
Please be very careful using unix commands. The -f flag overrides the -i flag, so rm -irf whatever does not ask the user if they want to delete the files. It behaves like rm -rfwhatever and deletes the files without warning.
May. 11, 2015
item.210522
Peter Lovell
I have recently encountered a problem with AirDrop and wonder if anyone else has seen it. And perhaps has a solution?
The setup is an iPhone 5s wanting to send a file to a Mac Mini. I set the iPhone ready to send and then get the Mini ready to receive the file (in Finder).
The Mini shows the iPhone, but the iPhone doesn’t show the account on the Mini — the ‘circles’ remain to indicate it’s waiting for the handshake to complete.
This seems to be a problem with the Mini, as the same issue happens with another iPhone and an iPad.
The two iPhones and iPad can see each other fine both ways.
Restarting the iPhone doesn’t fix the problem, but rebooting the Mini makes it all work again.
All devices are running latest software (10.10.3 on Mini, iOS 8.3 on iDevices). All are signed into iCloud with the same AppleID.
This has happened twice now but doesn’t occur all the time. I have yet to find the ‘trigger’ that causes it. The same setup has worked flawlessly for months, until recently.
item.210531
Darren Redman
I have noticed that under Yosemite 10.10.3 my Date and Time function in the menu bar will sometimes read pn instead of pm. Opening the Date and Time System Preference pane will correct the problem. Has anyone else seen this weird behaviour?
item.210529
Brendan McKay
Please be very careful using unix commands. The -f flag overrides the -i flag, so rm -irf whatever does not ask the user if they want to delete the files. It behaves like rm -rfwhatever and deletes the files without warning.
Actually the behaviour depends on whether the ‘f’ or the ‘i’ appears first. rm -fi will prompt and rm -if will not.
This is documented in the man page (10.0.4).
It is also true in Ubuntu Linux, but I don’t see it on the man page there.
item.210536
Jay Hill
Turning to the MacInTouch community in the hopes someone can help..
I ‘reset’ Safari (Yosemite 10.10.3) to try and resolve issues with Top Sites, which are a hot mess in this latest version of Safari. Now WebEx sessions will not start. The WebEx app won’t launch — just get the spinner in Safari.
There’s not a current uninstaller because the WebEx uninstaller says that I need to have a version of OS X higher than 10.4 but it says I’m running 10.10.3! Imagine that, what a horrible string comparison routine!
Anyway, I cannot find a way to get Safari to launch WebEx although Chrome has no problems whatsoever starting it up. So, now, I have to use Chrome to start or join a WebEx.
Any suggestions on how to troubleshoot/resolve? I have looked for plugins and removed any that are WebEx.
15' MacBook Pro (early 2011), 16GB RAM, 1TB SSD, OS X Yosemite (10.10.3), Safari Version 8.0.5 (10600.5.17)
TIA for any suggestions on how to remove the plug-in or resolve the issue.
May. 12, 2015
item.210555
Os X 10.11.4
David Taylor
Re:
‘Please be very careful using Unix commands. The -f flag overrides the -i flag, so rm -irfwhatever does not ask the user if they want to delete the files. It behaves like rm -rfwhatever and deletes the files without warning.’
Brandon is absolutely correct. I had forgotten this little Unix jewel. As he suggests, very carefully read the descriptions of the -f and -i switches in the man page.
item.210558
a MacInTouch Reader
Is anyone else having issues with sharing the Public folder Drop Box?
From Yosemite to Yosemite, with sharing on, I cannot see the Drop Box folder. However, Yosemite to Mavericks is no problem (and I can easily drop something in).
Is this a bug or a change?
I want to be able to drop into Drop Box without logging in as usual. Thoughts? Thanks. Vix.
[You might want to try repairing permissions with Disk Utility. -Ric Ford]
item.210563
MacInTouch Reader
[Re. Safari WebEx problems]
One solution might be to try Firefox. I would argue it is a far superior browser to either Safari or Chrome, though your past ‘mileage may vary’.
item.210571
Jay Hill
Finally solved this after removing every piece of WebEx I could find, using a test user account to download the add-on, restarting the computer and installing the add-on once again.
May. 14, 2015
item.210623
Bob Jansen
Final message about my external display corruption. It has now been several days since I saw any corruption after changing the Display Preferences to Scaled from Default for device.
This has solved it for me.
item.210693
Steven Wicinski
Os X 10.12
Jay Hill wrote:
‘There’s not a current uninstaller because the WebEx uninstaller says that I need to have a version of OS X higher than 10.4 but it says I’m running 10.10.3! Imagine that, what a horrible string comparison routine!’
Well, they probably wrote the uninstaller years ago and figured, like any logical person, that Apple would never do something silly like keep their 10.x version numbers past 10.9, as anyone with a semblance of math concepts knows 10.10 =10.1. ..
item.209820
Wire
For anyone experiencing severe instability such as kernel panics after an OS upgrade, understand that for Macs other than the Mac Pro, borderline hardware problems, especially related to RAM — but anything on the peripheral buses, too — can be triggered by an OS upgrade, simply because patterns of system memory access change. This is true of disk drives too: small localized problem areas of the disk get written with key system files. Failure that in one software installation might go unnoticed, such as bits flipped in the content portion of a movie, photo, or sound file, can cause a crash when they appear in system data.
An anecdote which in this regard which I think is fascinating is a DEFCON hacker presentation by someone who discovered that random bit flips related to networking traffic generated by non-ECC RAM computers (most desktops and laptops) cause domain name look-ups to be corrupted. When millions of PCs are looking up a domain, he found he could obtain spurious traffic to domain names one bit off, so google.com might result in a connection to gnogle.com.
On consumer devices, RAM has no error detection or correction (ECC), though most other subsystems do. RAM bits can get flipped simply from cosmic radiation arriving at the chip. But more significantly, electrical noise generated within the system itself, can induce errors, and the likelihood of such errors is influenced by data patterns generated by the software running on the system.
With tools like memtest86, the whole point is to generate patterns of memory access which are likely to produce errors.
As modern systems’ I/O devices are memory-mapped, meaning that device control, status, and of course data movement, is occurring within the memory subsystem, unrelated OS changes may expose latent problems with attached devices.
Os X Download
My point here is that it’s a fact that an OS upgrade can expose a weakness in a specific system for no other reason than because of a software change — possibly minor.
For systems that have been come down a long line of OS advances, such as 10.6 to 10.10, the likelihood of such failures is affected by software that exercises the system in substantially different ways. For example, it looks like, since about OS X 10.8, RAM is much more fully utilized by the OS than in Mac OS X 10.6. Assuming this is, in fact, true, you can see how a non-ECC system with a borderline RAM problem might go from being perfectly reliable to practically useless, without a defect in the OS.
