Resolve common installation problems with Dermi Atlas Manager, including SmartScreen warnings, Gatekeeper blocks, Linux .deb package errors, and license key issues.
Symptom: Blue warning window on Windows preventing installation.
Solution:
Symptom: Error message saying "Dermi Atlas Manager is damaged and can't be opened."
Dermi Atlas Manager macOS builds are code-signed with a Developer ID Application certificate and notarized by Apple, so this message typically indicates an incomplete or corrupted download. Re-download the .dmg from the Dermi Portal first, then reinstall. If the error persists, use the fallback below.
Solution:
As a fallback, open Terminal and run:
xattr -cr /Applications/Dermi\ Atlas\ Manager.appSymptom: "Cannot be opened because it is from an unidentified developer."
A properly signed, notarized, and stapled build downloaded normally should not trigger this message, so it usually points to an incomplete or corrupted download. Re-download the installer from the Dermi Portal first; the steps below are fallbacks if the message still appears.
Solution:
Symptom: Running dpkg -i reports unmet dependencies.
Solution:
Update the package index and resolve broken dependencies, then re-run the installation:
sudo apt update && sudo apt install --fix-broken -ySymptom: Application crashes or reports missing .so files (e.g., libwebkit2gtk-4.1).
Solution:
sudo apt install -y libwebkit2gtk-4.1-0Note: Runtime dependencies are normally resolved automatically during .deb installation.
Symptom: "dpkg frontend lock" or "another process is using the package database" error.
Solution:
Wait for any running package manager operations to complete, then retry. If the lock file is stale:
sudo rm /var/lib/dpkg/lock-frontend && sudo dpkg --configure -aSymptom: "Invalid license key" error.
Solutions:
Your feedback helps us improve our documentation
Contact our support team for personalized help