do you know any 3 part application that could do in my case?The menubar has lost transparency since macOS Mojave and no fix has been found with solid white or black
And the developer mentions us in the original article! 😎Great news about a patch tool to get the old Aperture, iTunes and iPhoto running on Catalina!
View attachment 873315
To anybody who sees this error, I sincerely apologize, this is my fault. 😳Crashing a lot on 10.15.1 with this:
Process: UserNotificationCenter [9359]
Path: /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter
Identifier: UserNotificationCenter
Version: ???
Build Info: UserNotificationCenter-51000000000000~12
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: UserNotificationCenter [9359]
User ID: 501
Date/Time: 2019-11-01 06:27:33.135 -0700
OS Version: Mac OS X 10.15.1 (19B88)
Report Version: 12
Time Awake Since Boot: 110000 seconds
System Integrity Protection: disabled
Crashed Thread: Unknown
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x4] Symbol missing
Dyld Error Message:
symbol '_OBJC_CLASS_$_SLSecureCursorAssertion' not found, expected in '/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight', needed by '/System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter'
Binary images description not available
Thanks. This will be tricky for me to fix since it's not reproducible on my machine, but I will take a look!Good Evening Guys
ASenitentBot this is for you
Good Evening,
Here are the latest crash reports relating to my weird login in loop when connected to secondary monitor.
See attached
Don't run Catalina on a non-Metal system unless you have a good reason to. It adds very few features, is quite unstable, and performs worse. Many functions like Sidecar, AirPlay, hibernation, auto light/dark switching, etc. are broken (and many are my fault 😢).Hi dear friends! First of all, thanks a lot (@dosdude1 and everyone - I will forget someone if I try to list here) that spent time o keeping our old Macs running like new ones!
I have a question: I'm running Mojave 10.14.6 on my MPB8,3 with Mojave Patcher. It's safe to patch my machine to Catalina 10.15.1, once it's my working notebook, or maybe better to wait next releases of Catalina and the Patcher? Someone running Catalina in MPB8,3?
Thanks a lot!
Don't run Catalina on a non-Metal system unless you have a good reason to. It adds very few features, is quite unstable, and performs worse. Many functions like Sidecar, AirPlay, hibernation, auto light/dark switching, etc. are broken (and many are my fault 😢).
Its not you fault as I tried to explain your doing your mid terms so I hope members here understand you do a great job with your fixesDon't run Catalina on a non-Metal system unless you have a good reason to. It adds very few features, is quite unstable, and performs worse. Many functions like Sidecar, AirPlay, hibernation, auto light/dark switching, etc. are broken (and many are my fault 😢).
I am running Catalina 10.15.1 on a MBP early 2011 8.2. A few features like airdrop and facetime camera do not work. A part from that I don't experience any significant challenges. Thanks to dosdude and everybody else making this possible.Its not you fault as I tried to explain your doing your mid terms so I hope members here understand you do a great job with your fixes![]()
Its not you fault as I tried to explain your doing your mid terms so I hope members here understand you do a great job with your fixes![]()
This was discussed about 3 weeks ago and no one seems to have a clue on what is broke and certainly not how to fix it. I remain hopeful that the talented group here will find the cause and the cure for this.Since updated to Catalina for my Macbook 7,1 Macbook pro 4,1 and 5,1, the built in japanese input fails
Anyone can use the built in japanese input method in 10.15?
Since updated to Catalina for my Macbook 7,1 Macbook pro 4,1 and 5,1, the built in japanese input fails
Anyone can use the built in japanese input method in 10.15?
Kind of confused by your message -- do you mean the crash is fixed or is not fixed?View attachment 874369
[automerge]1572666486[/automerge]
Got the legacy video patch update but the Notification Center crashes replaced the ones from Asentientbot seems to be holding so far knock on wood![]()
Alright, please tell me if it crashes again. It's possible that crash report was somehow leftover from before the update took effect.when I installed the legacy video patch from the patch updater as soon as it notified me as soon as I rebooted not long after the Notification Center crashed but I replaced the ones that yo posted earlier from the output folder no crashes so far its holding
It was just a Patch Updater script issue on my part, which has been fixed now. He just installed it before I caught that (which was about 10 mins after I initially pushed it). Nothing wrong with your wrappers.Alright, please tell me if it crashes again. It's possible that crash report was somehow leftover from before the update took effect.
(Also, please use a bit of punctuation if possible? You're one of the most helpful people on this forum and I appreciate that! But your messages can be really confusing... Thanks!)
hi Dosdude1. Tks for the patcher update. you men to say for non metal graphics card like I have will just have to click on your patcher update in preference and will it update the changes. In any case I have macbook air 4.2 and never faced any notifications crash, as I have been receiving notifications.Just updated Catalina Patcher to version 1.2.2, which includes @ASentientBot's latest SkyLight and CoreDisplay wrappers in the Legacy Video Card Patch. This will resolve the crashing issues related to Notification Center in 10.15.1 on machines with non-Metal video cards. These changes will be available momentarily to current users via Patch Updater.
I'm fine with keeping my 2011 MBP on Mojave. TBH I wouldn't have complained if Apple had supported non-Metal Macs with Mojave but dropped them with Catalina. Not giving these Macs Mojave was a software planned obsolescence tactic, reminiscent of the Macs that were dropped with Mountain Lion instead of Mavericks. But Catalina is a more natural cut-off point for them.Don't run Catalina on a non-Metal system unless you have a good reason to. It adds very few features, is quite unstable, and performs worse. Many functions like Sidecar, AirPlay, hibernation, auto light/dark switching, etc. are broken (and many are my fault 😢).