Description of problem: Since installing krb5-libs-1.5-1, I get the following problem when trying "telnet localhost 110": ipop3d: g_initialize.c:97: gss_release_oid: Assertion `(&(&_m->os)->n)- >initialized == K5_MUTEX_DEBUG_INITIALIZED' failed. Version-Release number of selected component (if applicable): uw-imap-2004g-4.fc5.2 krb5-libs-1.5-1 How reproducible: Everytime, see above. Actual results: Completely unusable ipop3d. Expected results: Working ipop3d like in the past ;-) Additional info: I guess the problem is within uw-imap, as everything else krb5 related works fine and a rebuild of uw-imap didn't also resolve my problem. Please re-assign to krb5, if necessary.
Got some input that my problem is more krb5 related rather to uw-imap
ping... Nalin, comment(s)? p.s. This also affects pine, and likely any app linking against libc-client.
As already said, I'm not absolutely sure whether this problem is krb5 or uw- imap related. Sent message to krb5-bugs mailing list, but no response, yet: http://mailman.mit.edu/pipermail/krb5-bugs/2006-August/004843.html Dunno, maybe somebody at Red Hat has the knowledge and is able to figger out what goes wrong here...
Okay, the problem IS caused by krb5 and there's also a fix available now: http://mailman.mit.edu/pipermail/krb5-bugs/2006-August/004835.html http://mailman.mit.edu/pipermail/krb5-bugs/2006-August/004848.html http://mailman.mit.edu/pipermail/krb5-bugs/2006-August/004849.html Include the fix and everything works as expected like in the past. As also other applications will be affected by this regression too, I'm marking as FC6Blocker for now.