Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 119406
Summary: | GDMsetup asks root passwd, then doesn't launch | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Benjamin Thompson <bt3819> |
Component: | gdm | Assignee: | Havoc Pennington <hp> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | eloli |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:02:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Benjamin Thompson
2004-03-30 06:34:28 UTC
I concur. This happens here too. I can't load "Services" or "User and Groups" or *anything else* that requires authentication. It gives me the same stuff Ben said: Could not set exec context to user_u:sysadm_r:sysadm_t. When logged in as "root" it works fine, but when logged in as "eugenia" it just bails out. Please note that this is an "Everything" installation, I installed all packages. I thought I will say this here just in case it has something to do with the problem (however my gut feeling says that it has something to do with SELinux). Please note that this is *not* a GDMSetup bug, it happens on ALL pref panels that require authentication. See bug #117499 too. The same here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119414 I think thats a problem with SELinux?! *** This bug has been marked as a duplicate of 117499 *** I had this problem on a linux-ppc. I changed the su and gdmsetup files in /etc/pam.d/ and it worked at least for su. I'm still muddling with the gdmsetup entries there, but I suppose the problem is pam, not selinux. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |