rawhide-20040304 Running some userhelper-ified tool, after entering the (correct) password, I get: Could not set exec context to user_u:sysadm_r:sysadm_t. and it exits.
Running 'su ; system-config-display' works.
This looks like a duplicate of bug #115684 (although I was vague at the time ;-))
Definitely maybe. There's no GUI popups in this case, though.
Here is the same bug resubmitted, please read: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119406 Bill, any idea why this is happening? How can we fix it? To me it happens on ALL authentication-required system panels. It gives me the password box, I enter it, but the pref panel never comes up!!
I also found these (more people with the problem): http://www.redhat.com/archives/fedora-test-list/2004- March/msg00220.html http://www.redhat.com/archives/fedora-test-list/2004- March/msg01479.html
*** Bug 119406 has been marked as a duplicate of this bug. ***
*** Bug 119414 has been marked as a duplicate of this bug. ***
*** Bug 119433 has been marked as a duplicate of this bug. ***
When yesterday I logged in as "root" for the first time from the command line, it asked me about a profile as: root:sysadm_r:sysadm_t (or something to this effect). Now, the error message we get here on this bug when we try to load an authenticated application is "Could not set exec context to user_u:sysadm_r:sysadm_t." My gut feeling (this is a wild guess) says that this bug is a simple typo. In my case it should have said "eugenia:sysadm_r:sysadm_t" but instead it said "user_u:sysadm_r:sysadm_t". It seems to me that the code somewhere prints and executes as login name the $variable name instead of the actual value of the $variable and that's why it's failing (and it also pops up to us the "uknown user" alert box as seen on bug #115684 when trying to reboot/shutdown the machine) With this theory, I think a few similar bugs filed since yesterday (which have to do with users and authentication on particular apps) seem resolved. Could someone have a look for this wild guess?
*** Bug 119746 has been marked as a duplicate of this bug. ***
*** Bug 120002 has been marked as a duplicate of this bug. ***
Fixed in FC3