Using defaults write com.apple.CrashReporter DialogType none really should disable it, just like using defaults write com.apple.CrashReporter DialogType crashreport should switch it back on.
However, if it's not working for you, you can try the following two commands:
launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
After having opened something that crashes an app, subsequent launches will automatically try to reopen the file that crashed it... & round you go in circles.
The usual 'first-fix' for this type of issue is to clear the 'history' of what it was trying to open.
Many apps store data in this way, that's how they can set everything back up exactly as you ...
If only one application is 'frozen', then you should normally still be able to switch to another application (click on another app's window, or the Desktop, or the Dock icon, etc) at which point you should be able to access the Apple menu.
You can also right click on an app's icon in the Dock and Force Quit from there.
However, if you are regularly needing ...
You can use Karabiner to customize shortcut on your keyboard as you please, give it a try !
You can remap the Esc key to another key or combination or just add another force quit rule than Command+Option+Esc (like Command+Option+Q).
From Karabiner Manual :
Change a key to another key
You can change a key to another key in Simple Modifications tab.
I fixed my issues by clearing up some network shares that couldn't connect. I had three network shares in my user's System Preferences>Users>Login Items. These were all on a server that I couldn't connect to at the time.
For some reason when I opened either Slack or Zoom, they'd attempt to connect to that server.
I can't think why either of those apps were ...
You most probably do not want to avoid macOS from suspending apps when the system runs out of RAM when you know that the only alternative is to kill the program. I.e. stop the program from running now and here without saving its data or anything like that.
However, you do not have to restart the programs that are paused as in "close the program and start it ...
I had this same issue. I lodged a ticket with steam support and they told me to enable beta client.
Here is a link about how to do just that that
After signing up for beta it is now quitting for me and my double quits are gone. If you don't want to participate in the beta, hold on to your butts; a fix is probably coming soon when they get a stable beta.
Here's what I would try:
Login as your 'other' user.
Type login shortname (where shortname is the username that is having problems with Finder) and enter your password when prompted. (Then type whoami to verify you are logged in the correct account.)
Run these commands:
mv -v ~/Library/Caches/com.apple.finder/ ~/Desktop/
mv -v ~/...
This is by design and expected behavior if your memory pressure is green in activity monitor. Both iOS and macOS will keep some apps resident until compressed memory or paging is called for and then purge them. Changes in the kernel relating to App Nap, sudden termination, background processing allow many more states for applications than just running and ...
Use the macOS built-in Activity Monitor in /Applications/Utilities/Application Monitor.app.
Select the process you want to terminate and press the cross icon on the top left of the window. In the dialogue that opens, it will offer you the option to 'Force Quit'.
This is same as the shortcut you're trying. Apple logo in the menu bar in top left corner-> Force Quit. This should be done from an app whose menu bar is not in the hang(spin-ball) state. To achieve this, I normally click on desktop to get Finder.
A different approach, type Activity Monitor.app in spotlight(cmd+space) or via launchpad or via Applications ...
At boot time a file consistency check is performed, usually a quick check to see if the filesystem was unmounted cleanly. If the filesystem is dirty (not unmounted cleanly) then some form of fsck is performed. fsck attempts to fix filesystem metadata not a files actual data. So, there is always the potential for data loss. fsck will not fix some ...
If the OS has managed to keep running though slowly, if you can CMD-TAB to Finder, or use the mouse to navigate to a different application of Finder, then you can get the Apple menu open.
Whatever macro you're using, you should find a way to have it work in batches, or accept that your laptop will not be usable during that process.
Given that you are able ...
From searching online, I think I may have run into an edge case. My best guess is that, having just installed Mojave, one of the many new permissions dialogs was generated but hidden behind another window. As I closed programs, some permissions dialogs appeared, including for Chrome. This doesn’t make much sense as a cause but it was related to a major ...
I have this problem too, I don't know how to fix but I do have a workaround. You go to the Mission Control and switch to another apps, I think it'll be OK. My apps usually freezes in their own space only.
I have Mojave 10.14.6 (MacBook Pro with touch bar) and cmnd+option+esc works using either cmnd+option from the right or the left of the space bar & esc is on the touch bar...
Have you checked that the key combo has not been altered?
As found here:
Wifi can be turned on and off using
networksetup -setairportpower en0 off
and back on using
networksetup -setairportpower en0 on
When I use this, it says something along the lines of en0 is not wifi, turning on/off en1 instead, presumably because en0 is my ethernet connection.
EDIT: Also, this should be a comment, but I cannot yet ...
I think installing new OS X is premature at this time and should remain as option.
But it looks like you have problems with some 3D party apps.
What is https //vk.com/ ?
To test... Log in as Different user and see if it works to confirm my assumption.
You can also run the EtreCheck to get a report on your system.
And disable any app launching at start ...
If you don't mind using the Terminal.app, I would suggest trying:
sudo shutdown -h now
(-h is for 'halt')
That should shut the computer off as cleanly as possible, and is better than holding the power button down.
If you want to reboot instead of shutting down, try this instead:
sudo shutdown -r now
n.b. This assumes you have an administrator account. ...
You can take one of the 2 approaches one-by-one:
1) Command + Option + Escape brings up a window to force quit running apps.
2) In Terminal window, get the process_id by running ps -a and execute kill -9 <process_id> for the matching process.
If this doesn't work, quit all the other apps you can, make one last backup to time machine or equivalent ...
This applescript works for me using the latest version of Sierra
You can paste this code into ScriptEditor app and save it as an application. Then run your new app anytime you need it
do shell script "killall SystemUIServer"
This happens a lot. Preview is supposed to auto-terminate – but often cannot.
As of this writing: this is a bug not fixed in Sierra and not fixed in High Sierra.
Even force quitting the app from the Dock might surprise you: after one trigger-the-bug files hangs Preview, force quit the app from the Dock and open Activity Monitor. Even though the app has lost ...
Have you tried opening the Force Quit menu from the top menu? Just click on the Apple in the top left corner and manually select Force Quit. It should open up the menu without having to use the touchbar.