| Summary: | It tells me my Kerberos tickets have expired, when I've never used Kerberos at all | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Horst H. von Brand <vonbrand> |
| Component: | krb5-auth-dialog | Assignee: | Itamar Reis Peixoto <itamar> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | amessina, ibmalone, itamar, nalin |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | krb5-auth-dialog-3.2.1-2.fc16.x86_64 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-18 14:53:37 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Horst H. von Brand
2011-10-12 15:15:33 UTC
This is happening to me too. The following is from Trever Adams on the users list: > It is happening because of one of two things. Either the > krb5-auth-dialog is broken and isn't recognizing that krb5_cc for the > user doesn't exist, and that it shouldn't complain, OR it isn't started > with -a (that is LOWERCASE -a) which will cause it to not start if you > have no valid credentials. > > It appears that whoever set it up in Fedora15/16 (I just upgraded from > 14) has it as -A and not -a. I use kerberos so, it really doesn't affect > me. You may want to file a bug. Not sure about low priority, this will be visible to most people who use F16 as the first thing they see when they log in and doesn't give a polished impression. (At odds with how F16beta actually compares to F15.) I updated to Fedora 16, which broke Gnome. Under XFCE I don't see any of this nonsense. krb5-auth-dialog-3.2.1-2.fc16.x86_64 fixes this. BTW, I gave it low priority, as it is just an annoying message. Confirmed, it's been fixed since this package installed, thanks. |