Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1396751

Summary: "Authentication is required to create a color managed device" prompt on login screen.
Product: Red Hat Enterprise Linux 7 Reporter: amit yadav <ayadav>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: cww, fmuellner
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-25 19:33:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description amit yadav 2016-11-19 17:48:20 UTC
Description of problem:

When trying to connect RHEL7.3 system remotely using xdmcp getting following message before logging into the system:
 
 Authentication Required
 Authentication is required to create a color managed device
 Password:

If I cancel the prompt or enter credentials I am able to login into the xdmcp session. But once I login into the system 
Getting Two prompt:

 Authentication Required
 Authentication is required to set the network proxy used for downloading software
 Password:

 and 

 Authentication Required
 Authentication is required to create a color managed device
 Password:

Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.14.4-12.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Enable xdmcp on RHEL7.3 by adding "Enable=true" in [xdmcp] section of /etc/gdm/custom.conf file.
2. Restart gdm using: systemctl restart gdm.service
3. Try to connect to the xdmcp server from RHEL using Xephyr:

   # Xephyr -query SERVER_IP :1

Actual results:
Getting Authentication prompt when connecting to the system via XDMCP 

Expected results:
Should not get any prompt.

Additional info:

"Authentication is required to create a color managed device"
This issue was tracked for rhel7.2 in following bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1300937

Comment 4 Florian Müllner 2017-04-04 19:24:30 UTC
This doesn't sounds like a gnome-shell issue - it does show the authentication dialogs on polkit's behalf, but it isn't involved at all in the policy decision.

Looking at the two policies you mention, both allow the actions in questions for the active session on the *local* console, but have "<allow_any>auth_admin</allow_any>" which applies in the non-local case. So as far as gnome-shell is involved, everything looks like it is working as expected. To avoid those dialogs, either the policies need to be adjusted, or color-manager/packagekit need to be changed to not intent to perform the actions in question in remote sessions.