Jaunty's release is less than two months away. Please grab a Jaunty alpha 5 or daily live cd and test! Go through the bugs you've filed and see if they still exist on the live cd. See if any new ones pop up. And do it ASAP.
In every development cycle there's a huge influx of bugs in the last two weeks because a lot of people jump from stable to beta or RC, skipping alpha completely. Great, we've got more testers, but…how many bugs can be fixed in two weeks without risking breaking anything else? Not nearly as many as are filed. That is why we need more people testing early on.
I'm not saying everybody should install the development release on their only computer or the one they use all the time, directly on the hardware. While I've been doing that for the last two years, that's generally not recommended. If you cannot function pretty much entirely from the command line, don't put it on your hardware. Put it in a VM.
VMs aren't terribly useful for testing hardware, but there are plenty of GNOME and KDE bugs you can find using a VM. Try it! Check out Virtualbox. Put Jaunty in there and play with it. Try doing anything that doesn't involve important persistent data in the VM. By that I mean: don't write your thesis in the VM without having it backed up elsewhere. Web browsing? Getting your email over IMAP? Chatting? Why not?
But for hardware, use a live cd. Very often a triager asked "is this still a problem in the current development version?" The end of that sentence is "or would it be a waste of time for us to try to hunt it down when it's already fixed?" though it's not said. Also very often, the bug reporter will reply "I don't know. I'll test it when it releases." Insert whatever development cycle you want in there. It happens in all of them. Guess what happens when the reporter says they'll test after release?
- 10 The bug gets ignored as "potentially fixed; waiting on feedback" because as I said, trying to fix what's already fixed is a waste of time.
- 20 The development release becomes a stable release.
- 30 The reporter complains that it's still not fixed.
- 40 Work starts on the next development release.
- 50 The reporter is asked "is it fixed in this one?"
- 60 The reporter doesn't answer or says again that they'll test after that release.
- GOTO 10
Bugs can't be fixed without information. Thus, bugs that have a lot of information are more likely to be fixed. If you're not giving us any information, what do you expect?