Comment 1 for bug 250367

The 8.04 Hardy Heron release seems to have a problem with Audacity. I cause
it to become unusable on a variety of systems by simply editing a WAV file.
Since I use this feature quite regularly for cleaning up my old vinyl
records (see http://mysite.verizon.net/hal.bower/music.htm), it is rather
important to me. This problem exists with the audacity_1.3.4xxx package but
is absent under earlier 1.2.4 and 1.2.6 packages on Hardy (although my crude
efforts to make them work broke the package system), and all efforts to
configure with different options were fruitless.

The symptoms can be seen by the following procedure:
 1. Edit a 2:30 to 4:00 minute WAV file
 2. Remove (or add) a few tenths of second leadin
 3. Go to end of file and cut 0.5 Secs or more from end
 4. Try to save the file (Export as WAV). Sometimes it will, others not
At this point, CPU usage (from gkrellm and top from another window) goes to
100% with about 2/3 attributable to X and 1/3 to audacity, yet nothing moves
or seems to refresh in the audacity window. I have left things this way for
20 minutes (with the CPU getting gradually hotter) with no change. The rest
of the system is usable and audacity can be killed from a terminal window.

This had been verified on:
 - Biostar Turion 3200 Motherboard with ATI AIW 7500 video, CF 8GB hda
 - Biostar Sempron64 3000 Motherboard (as above w/onboard VIA video)
 - EeePC 4g (Mobile Celeron 900 MHz, Intel 915 graphics)
 - EeeBox (where dual-threading altered CPU loads but similar results)
            Intel Atom 1.6 GHz, Intel 945 graphics.

As a result, I still keep a Dapper Drake system in daily use.