Font Explorer was closed during ID crash, and just the system fonts were activated. I use Font Explorer X 5.5.1 for font management, but I don't use any auto-activation plugin. ![]() Here's the link for my logs: and my last crash report Please provide the log files from your machine? You can get them using log collector tool.Does Trashing preference and cache help to resolve the issue? No.Is the file located on network location? If Yes, Is the issue reproducible if you open the document locally? Not trying to open any document.Is the issue related to a specific document? If Yes, Can you please provide the document? No, it is not.Just clicked on the app to open, and after the message "starting up service registry" it dies. Reproducible Steps – What were you doing when InDesign crashed? Nothing else was opened.System configuration: MacBook Pro (13-inch, Mid 2009), 2,26 GHz Intel Core 2 Duo,8 GB 1333 MHz DDR3, NVIDIA GeForce 9400M 256 MB.Some people that have upgraded from Catalina to Big Sur have actually experienced such triggered, verified hardware failures.Anyone that has done much in the way of mechanical, electrical, or computer hardware work, knows that changes in load can trigger “borderline” hardware issues.(The hardware “thing” was brought up because: Quite frankly, I’ve been surprised there haven’t been more issues with third-party software! Upgrades, on the other hand-especially the more major the upgrade-are seldom expected not to require corresponding upgrades to associated software. Updates are seldom expected to suddenly change interactions with other software. ![]() In the «universe of possibilities»-barring triggered hardware issues-the greatest range of possibilities is in software interactions: especially with a major Operating System (OS) upgrade: after all, all software interacts with the OS. However, as large as that pool may be, it still cannot cover the entire «universe of possibilities». This is, of course, why Apple has their Beta test program, so a larger set of users, sampling a larger portion of that «universe of possibilities» can be tested. You are absolutely correct, Tim Lovern, that «The universe of possibilities is quite large.» Since booting into Safe Mode includes performing a repair of your filesystem (which is why it can take extended time to boot into Safe Mode), there are cases where this can actually correct some issues even running normally. If you have no trouble in Safe Mode, then try rebooting into normal mode, and see if the problem recurs. ![]() If you have trouble in Safe Mode, without running any third-party software, this greatly narrows the possible causes. This suggests there is either a hardware or other, third-party, software interaction.Ī recommended test for the third-party software possibility is to boot into Safe Mode, and try Music there, without running any third-party software. Unfortunately, all I can provide y’all with, at this time, is the assurance that this is, most certainly, not a fault in just the Big Sur software (which includes Music), since many of the rest of us have experienced no such troubles. I’m sorry y’all seem to be having trouble with the Music app on Big Sur. (I have a MacBook Pro, late 2011, 2.8GHz i7, 8GB RAM, 256SSD). When I clicked Open, it's showing a message 'Patched Sur quit unexpectedly'. Welcome, Tim Lovern and to Apple Support Communities! After installation, I went to finder < Application < Patched Sur.
0 Comments
Leave a Reply. |