http://bugs.winehq.org/show_bug.cgi?id=2082
--- Comment #35 from Stefan Dösinger stefandoesinger@gmx.at 2007-11-30 14:53:52 --- Regarding the status, that is just a bugzilla category. A new bug is "UNCONFIRMED", when people confirm it it becomes "NEW". The next step is "RESOLVED" - with various reasons, e.g. FIXED, WONTFIX, ABANDONED, ..., after that CLOSED. So "NEW" doesn't mean that the bug isn't older than $DAYS. The "NEW" is what you mean with confirmed propably.
As far as fixing this bug is concerned, an open source project isn't something where you can drop in and order something to be done. Possible reasons why this bug isn't fixed could be
a) None of the developer has personal or commercial interest in the specific games b) None of the developers has time to fix it. Remember, many are working on Wine in their free time. c) No volunteer got around to fix it yet(as everyone only demands that it gets fixed) d) The bug is harder to fix than the simple workaround suggests. There might even be architectural differences between Windows and X11 which make it impossible to fix correctly.
In case of this bug, it's a combination of all 3 issues.
-
wine-bugs＠winehq.org