Today I tried to set up one of our QA guys with a smart card. He wanted to try
out the new technology and was willing to work through problems and file bug
I ran into a lot of issues that ended up being because the cseng server isn't
suitable for use with rawhide. Eventually we figured things out, but all
throughout the process we were greeted with dialogs that gave error codes.
Error code 28 was the big one, but we also got error code 14 when we tried to
use his kerberos username and password with the air server.
Since the error codes have no meaning to the user, we shouldn't show them. We
should give a specific message about what happened, when possible, and when not
possible give a generic message and tell the user to contact their cert server
We could still put the error codes in a log file of course, it if it will help
in isolating bugs in the code.
Is this bug report still valid given the changes that have been made recently?
If so, should we change the title to "ESC should show human readable errors
instead of numeric error codes" ?
Per todays bug council it was decided that this bug was fixed. Marking modified.
If this bug isn't fixed please set it back to assigned otherwise I will re-test.
I triggered a bunch of errors via ESC which came from the deployed TPS / CA The
error numbers are still presented but there are human readable messages
underneath. At least for the error conditions I was able to trigger.
Marking this bug VERIFIED fixed against candidate build RHEL5-Client-20061006.2
If someone comes across an error which does not also have accompanying human
readable text please feel free to reopen this bug
Closing out as resolved with the 20061111.0 trees.