http://bugs.winehq.org/show_bug.cgi?id=12365
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from James Hawkins truiken@gmail.com 2008-04-05 04:29:38 --- (In reply to comment #4)
Yes, I have been working on this, Its the first time I have done the regression test.
Good news is that the clean .wine directory has stopped the CPU usage, but is that something that ideally still needs to be looked at ? Its not good to have to reinstall everything from scratch after each update.
Wine is beta software (or alpha, can't remember)...but the point remains. Until we have a stable release, you can expect to remove and recreate your wine prefix after an update.
It still looks like the wineserver failing to shut down still exists though. Could this be by design now ? If its a small resident program to speed up wine loads or something it might be intended ?
Yes it's be design. Marking this bug as invalid.