"Nightly is damaged" message on first run after upgrade to macos 13.0.1, but works fine on second try
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: jhirsch, Unassigned)
Details
I upgraded from macos 13.0 to 13.0.1 today. I'm on a 2021 16" Apple Silicon MBP.
After restarting, I observed the following weird sequence of events when trying to open the (whoops, apparently rather stale build!) Nightly 108.0a1 (2022-11-14) (64-bit):
-
clicked on the Nightly app icon in the deck, saw the little dot under the deck icon appear indicating the app was starting, but no dock bouncing animation. Then the dot went away and Nightly didn't start. No error message.
-
clicked the deck Nightly app icon again, the deck icon was replaced with the broken app icon, Nightly failed to start, and I got an OS warning dialog: "Nightly is damaged or broken"
-
clicked the formerly-Nightly broken app icon in the deck a third time, and Nightly started normally, and the icon went back to its normal appearance.
After going through these steps once, Nightly is now starting normally.
I'm not sure how to diagnose further, but it appears the 13.0.1 Ventura update was a security fix for some libxml2 bugs[1], so maybe that's related? Let me know if there are any startup logs I could attach to help us understand what is going on with macos here.
|
||
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:mossop, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Comment 2•3 years ago
|
||
Might be useful to see the app update log. I suspect that the first launch started applying a previously downloaded app update.
|
Reporter | |
Comment 3•3 years ago
|
||
Good idea. Sadly, it looks like the app update log has since been overwritten: I'm on macOS and looked at the logs in the caches directory, ~/Library/Caches/Mozilla/updates/Applications/Firefox/updates, and the last-update.log and backup-update.log files have dates from mid-December. The log file contents don't include any earlier errors or failures, just some log lines indicating that the most recent updates completed successfully.
Closing this as incomplete for now. I'll reopen if I can find an older error log someplace on my system.
Description
•