How to Fix “Authentication is required to create a color profile” on Ubuntu & Other Polkit-Based Distros

Introduction

If you’ve ever connected to a Linux system (such as Ubuntu, Debian, or Kali) via RDP and encountered the prompts “Authentication is required to create a color profile” or “Authentication is required to create a color managed device,” you’re not alone. This issue stems from Polkit (PolicyKit), which checks permissions for certain system actions. By default, connecting remotely can trigger these annoying authentication popups. Below, we’ll focus on Ubuntu (24.04, 22.04, 20.04), but the same Polkit fix can apply to other distros that use .pkla overrides.

The Culprit: Polkit

Polkit (short for PolicyKit) is an application authorization framework used by many Linux distributions (Ubuntu, Debian, Kali, Fedora, Arch, etc.). It determines whether a user is allowed to perform certain actions, such as managing color profiles. When connecting remotely via RDP, Polkit may not recognize your session as fully authenticated, causing these popups to appear.

How to Fix “Authentication is required to create a color profile/managed device”

On Ubuntu and other Debian-based distros, the most straightforward fix is to create a new .pkla file that allows color-profile actions without requiring authentication. This method should also work on other distros that support .pkla rules in /etc/polkit-1/localauthority/. (Note: Some distributions, like Fedora or Arch, may encourage using JavaScript-based rules in /etc/polkit-1/rules.d/, but often still accept .pkla overrides.)

For Ubuntu (24.04, 22.04, 20.04) and similar Debian-based systems, create or edit the following file:

sudo nano /etc/polkit-1/localauthority/50-local.d/45-allow-colord.pkla

Paste in the following content:

[Allow Colord all Users]
Identity=unix-user:*
Action=org.freedesktop.color-manager.create-device;org.freedesktop.color-manager.create-profile;org.freedesktop.color-manager.delete-device;org.freedesktop.color-manager.delete-profile;org.freedesktop.color-manager.modify-device;org.freedesktop.color-manager.modify-profile
ResultAny=no
ResultInactive=no
ResultActive=yes

Save and exit (press CTRL + X, press Y, then press ENTER)

Then, either reboot the system or run:

sudo systemctl restart polkit

Once you reconnect via RDP (or any other remote desktop), those prompts should disappear.

Potential Side Effects & Troubleshooting

While this fix removes the color-profile authentication prompts, some users have reported side effects, such as:

• Loss of color calibration or Night Light functionality
• Inability to authenticate for certain admin tasks (e.g., uninstalling apps or mounting drives) if the policy is too broad
• System error popups in some desktop environments

If you experience these issues, you can try the following:

• Revert Changes: Remove the 45-allow-colord.pkla file (e.g., sudo rm /etc/polkit-1/localauthority/50-local.d/45-allow-colord.pkla) and reboot or restart polkit.
• Use More Granular Polkit Rules: Instead of granting all color-manager actions, tailor them to only what’s needed in your environment.
• Consider Disabling Remote Services: If you’re not using RDP or a similar remote desktop, disabling or reconfiguring those services might remove the prompt during local logins.

Works on Other Distros: Kali, Debian, Fedora, and More

According to community feedback, this method also works on Kali Linux, Debian 11, and other distributions that rely on Polkit. Just be aware that:

• Debian-based distros: Use the same .pkla approach.
• Fedora/Arch/OpenSUSE: May prefer JavaScript-based rules in /etc/polkit-1/rules.d/. Check your distro’s Polkit documentation.

Comment Highlights & Real-World Experiences

Visitors have shared that this fix worked on various setups—Ubuntu 20.04, 22.04, Debian 11 with Xfce, Kali Linux, etc. Some users, however, encountered additional issues with color calibration or lost some Polkit prompts. One user pointed out that simply restarting the Polkit service (sudo systemctl restart polkit) is enough to apply changes—no full reboot needed. Another discovered that Chrome Remote Desktop was causing local prompts similar to the RDP issues, so disabling it resolved the error locally.

Conclusion

If you’re tired of dismissing or re-entering your password for color-profile prompts, creating a Polkit override is a straightforward solution. Just be mindful of potential side effects, and remove or adjust the policy file if you find it interferes with other administrative tasks. With a bit of fine-tuning, you can enjoy hassle-free remote desktop sessions without losing essential color features. Good luck!

Let me know if this helped. Follow me on Twitter, Facebook and YouTube, or 🍊 buy me a smoothie.