I've written a little hack to hopefully take care of this. Basically, each time the inner timer triggers (to change the expiry message), it checks to see if credentials are still expiring. If so, it sends a "cancel" to the dialog which destroys the inner timer, but keeps the outer timer running. In my limited testing, this seems to work, but I'd love for some others to try it out. I'm not much of a C programmer and this is my first attempt at mods on a GUI trigger-driven app. :-)
I also added a little snippet to take the realm off of the username (confusing in our environment) and put it on a different line. To make it look nice, I should probably tweak the .glade file, but haven't done this yet. Also, for those who may know more than I: I'm thinking that the timers should be run with g_timeout_add_seconds since we don't really need the granularity. Doea this make sense? Also, is there any harm to keeping the dialog constructed but hidden? This code hides the dialog, but never destroys it. I'm guessing the memory footprint is small, but it seems it might be better to just destroy it and re-create when needed again. Let me know if my patch blows anything up or if there's a better way to fix this... ** Attachment added: "Patch for krb-auth-dialog.c" http://librarian.launchpad.net/7128033/krb5-auth-dialog.patch -- Should dissappear when credentials are obtained through other mechanism https://bugs.launchpad.net/bugs/73550 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
