don't think this is a 2.3 vs 2.2 issue. It probably has to do with the
problem itself. In addition to posting to this list, you can
automatically place it in bugzilla, our database for bugs.
1. While viewing the problem click "Edit this problem" link^(you have to have instructor privileges to see this.)
2. Now that you are on the editor page you will see a row of links, the right most one will say "report problem bugs".
3. Clicking on this will take you to bugzilla. If this is your first
time reporting the bug, there is a short setup sequence because
bugzilla needs to know who you are in order to record the bug. It will
ask you to enter your email. It will then email you a password. Once
you are signed up with bugzilla you can change your password to
something easy to remember. (This only happens the first time, after
that you can enter your email address and password to login, or if you
always use the same computer a cookie will be saved automatically and
you won't have to do anything -- you will be taken straight to
4. Once in bugzilla fill out a description of the problem. The address
of the problem and the seed used which produces the error have been
entered for you automatically. (If the PG problem is one you created
and is not in a library you should include the code at the end of your
5. That's it. This method has been particularly useful for bugs found
in library problems -- we are slowly getting rid of them all as the bug
reports come in from across the country.
<| Post or View Comments |>