Open huangzonghao opened 5 years ago
Thanks for reporting, I'm still using Mojave on my machines so this hasn't been updated to work with it, if it's even possible. off the top of my head I know that apple tightened the security regarding applications that alter system processes... and I think something about signed/certified releases needing a signed cert from apple...
Since this is a personal fork, it won't be updated until I upgrade my OS.
This needs a lot of research, that I currently don't have time for.
Community contributions and PRs are always welcome!
Right! I made the post solely for reporting and stating the issue. This is in no way that I am asking for maintenance.
And of course thanks for maintaining and sharing Asepsis for us!
I'll update this thread if I figure out the issue.
Update for anyone who also has problem uninstalling asepsis on Catalina.
Apple introduced a read-only system volume on your hard drive designated for the system files(the /System
directory) in this update. So any file locates in /System
directory will be untouchable even with root privilege. That's why the uninstallation script failed to change back the altered the system process for desktop service, which locates in /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/
. And it is that altered process that kept causing crashes on Finder.
So to move the original files back, you'll need to go to Mac's recovery mode (Cmd + R
when powering up), mount the drive, and then go to terminal and replace /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A
with
/System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A_Backup
Given that going into recovery mode seems to be the only way to change system files at the moment, I assume future installation of asepsis will happen in recovery mode. So should we keep pushing forward or should we just sign a petition to Apple and ask them to give us an option to disable the .DS_Store
files.
@huangzonghao, rather than doing the work in Recovery Mode, you can simply remount /System
as read-write rather than read-only. SIP still needs to be disabled in order to do this, but provided that it is, you can then just do sudo mount -uw /
to remount all partitions as read-write rather than read-only.
@jivanpal Haha YES! I wasn't aware of this. But this is obviously the better way of doing it. Thanks!
Mark, I am still running Mojave
The current build seems to cause Finder crashing repeatedly. So anyone who is running Catalina should wait for further updates.
And right now I have uninstalled asepsis, but the
asepsis_openx_np + 794
still seems to be there and keep causing crashes. How can I remove this leftover?