<< October 3, 2003 | Home | October 5, 2003 >>

Sun, Java, Bugs, ...

It's no secret that I'm frustrated with Sun's bug reporting procedures, as previously reported fifty-five days ago and thirty-nine days ago.

Just when I thought "They can't top that", they did.

I received a note today saying "your bug has been updated, click here."

I know I'm in trouble when Sun's website prompted me to login. I have always automatically logged in before. I signed up with the JDC the first day the site went public.

Of course my username and password no longer worked. In order to serve me better, Sun has consolidated the login databases. I used to have two accounts with them, one for the JDC and one for their online store. Instead of making both of them work, they opted to make neither work. And I have to reset my password.

Resetting the password is easy enough. They just asked me my secret question, and then emailed me my new password. And I logged in with it.

There is no way I can remember this password. So the first thing I tried to do is to change my password. No such luck. There is no way I can change the password. I can only reset it.

What does this mean? It means although I can use the "remember password" feature of my browser and the "automatic login" feature of the website, the moment I go to a different computer, I have to reset my password in order to login, which, in turn, invalidates all the automatic logins on all the other computers.

Finally I reached the bug. And what do I see?

Focus regression; committing to hopper and tiger.
xxxxx@xxxxx 2001-11-05

Assigning to Russia.
xxxxx@xxxxx 2001-11-06



commit to hopper and tiger




The problem is not reproducible with Hopper b06 and later.
xxxxx@xxxxx  May 28, 2002

And the status of the bug is "closed, not reproducible."

First of all, if you committed something and a bug is gone, it called "fixed!".

Secondly, the status change was dated May 28, 2002. Why does it take 494 days for Sun to send an automatic email informing me about it?