Struggling to troubleshoot permanently crashing Dock, Mission Control, Launchbar

Ask Different Asked by brutalist receptacle on December 20, 2020

Background: I need help troubleshooting this very bizarre bug that I can’t figure out. This is on macOS 10.15.6 (before and after the most recent supplementary update) on a 2020 16" MBP. The only thing I could think of that changed right before this issue occurred is I was playing around with BitBar and some BitBar plugins, but the issue persists regardless of BitBar being running/quit or even BitBar being completely uninstalled.

The Bug: The Dock is gone, the process is not showing up in Activity Monitor, and it is unable to be restarted or even quit using killall Dock (shows up as a no matching process error). Additionally, CMD+TAB does not work, and the same permanently dead process is happening for Launchpad and Mission Control. Neither of them run when called from Spotlight, nor do they show up in activity monitor, nor can they be killed using killall.

Troubleshooting Thus Far: I’ve tried killall and some of the defaults write terminal commands floating around on the internet for killing/restarting these processes. I’ve tried poking around Activity Monitor for clues, and the Force Quit menu (relaunched Finder from there too just in case). I’ve rebooted, installed the most recent Catalina Supplementary Update, reset PRAM/NVRAM. I also cannot find anyone with the same issue anywhere on the internet, asked around on Reddit, and these are the closest I could find to my issue despite them not being the same and the solutions not working for me: SO1, SO2

One Answer

Very Long Story Short

BitBar script for automatically changing desktop background somehow got run without my intent and set my desktop background image to a broken URL string. My desktop background was black so there was no visual change that alerted me to this being the culprit, but looking through ~/Library/Application Support/Dock/, I catted everything inside it just in case and turns out that desktoppicture.db was not gibberish but instead a URL.

This had the effect of keeping the Dock process stuck in limbo, where I could not kill or run it, nor could I actually witness it in any system diagnosis or crash report. It never crashed but it also wasn't running; a ghost.

Correct answer by brutalist receptacle on December 20, 2020

Add your own answers!

Related Questions

Python 3 Not Updating in Shell on Mac Mini M1

1  Asked on February 5, 2021 by fsa4


2018 MacBook Pro + LG 4k display = no 60hz

15  Asked on February 4, 2021 by alexander-eliseyev


Can’t install apps on Watch following iOS update

0  Asked on February 3, 2021 by orome


Word crashes with documents with “track changes” on

6  Asked on February 1, 2021 by matteo list search in a specified folder in mac

0  Asked on February 1, 2021 by ytyyutianyun


How much space for bootcamp?

2  Asked on January 31, 2021 by twlvseconds


Will Macbook Air 2017 benefit from Catalina upgrade?

2  Asked on January 30, 2021 by ccbunney


Can you batch rename files if they contain certain criteria?

2  Asked on January 30, 2021 by mugawump


Settings reset after slowdown

0  Asked on January 29, 2021 by giraffeman3125


Ask a Question

Get help from others!

© 2022 All rights reserved. Sites we Love: PCI Database, MenuIva, UKBizDB, Menu Kuliner, Sharing RPP