#hostname

Google Chrome silently fails to launch after a hostname change. The cause is a stale SingletonLock symlink in the user profile that still encodes the old machine name; deleting the Singleton* lock files restores normal startup. Applies to every Chromium-based browser and Electron app.