http://bugs.winehq.org/show_bug.cgi?id=6547
------- Additional Comments From julliard(a)winehq.com 2006-01-11 06:36 -------
That's very possible, there's a bug in Xlib where XFilterEvent calls the filters
with the display lock held, so if an IM filter gets the lock it deadlocks. I
added a workaround for the standard XIM lib, but others input methods probably
need the same treatment. If we know exactly what causes the deadlock we may be
able to find a way around it too.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6547
------- Additional Comments From ajackso2(a)connect.carleton.ca 2006-01-11 06:29 -------
Sorry for posting second-hand information, but I've been told by some Japanese
users that other input methods (Canna, UIM) are also causing Wine >= 0.9.23 to
hang, not just SCIM.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6574
------- Additional Comments From purple_skunk(a)msn.com 2006-01-11 05:52 -------
Working with the very latest git, though the game doesn't quit properly (Ctrl+C
required in the terminal window).
Also made a regression test, strangely all the versions compiled were good, I
did not had any regressing patch. Maybe I made a mistake during the test, I
don't know.
Also going to try latest CVS.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6577
------- Additional Comments From winehq(a)paniq.org 2006-01-11 04:30 -------
i understand. i will do a regression test this weekend.
but please be aware that such solutions as "user does regression tests using
git" have been implemented into the project in good faith that they will be
helpful. it does not necessarily mean that they are the fastest and simplest
solution. additionally, the longer such rules are in effect, the more people
tend to assume that they have proven to be effective, and it becomes
successively harder to change those processes.
i understand that maintenance is not an easy process. perhaps you can discard
what i say altogether, because you are the professionals.
but this is not the place to discuss such a topic.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6578
mike(a)codeweavers.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jacek(a)codeweavers.com
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6577
------- Additional Comments From mike(a)codeweavers.com 2006-01-11 04:10 -------
Leonard,
If doing a regression analysis takes 2 hours, and developers had to do them all,
then we'd be spending most of our day doing regression analysis.
Indeed, the problem might just be a bad configuration at your end, in which case
we'd end up wasting 2 hours of our time because of your mistake.
Open source scales by encouraging participation, not by trying to hold people
responsible for every line of code they write. The author "responsible" for
"breaking" the code may have left the project.
You can always go back and use an old "unbroken" version of the software.
If you want the bug fixed, spend some time to help us. If you prefer that we
waste our time on your problem, you'll be waiting longer.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6578
Summary: World of Warcraft doesnt close anymore
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-net
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: natoforce(a)gmx.net
when i hit exit button the music goes on and wow doesnt close, ingame mouse is not
moveable anymore all i can do is to kill WoW.exe
i did a regression testing
(ty mike_m for supporting me)
and found out that
760043c2455a90cd74178d98b7c81bfbfc81793f is first bad commit
commit 760043c2455a90cd74178d98b7c81bfbfc81793f
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Sun Oct 29 18:58:06 2006 +0100
wininet: Call SendCallback in destructor instead of InternetCloseHandle.
:040000 040000 ab0570d3e312fb133ba6dbe7e229e9a177bc3871
065b01adcecde1119fa0980f4bf432f0a87921df M dlls
is the problem.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6577
------- Additional Comments From hverbeet(a)gmail.com 2006-01-11 03:33 -------
Not really. I do read wine-bugs, and so do most other people who work on d3d.
However, like most other people, I don't exactly have an abundance of time to
work on this stuff, and you're not being particularly helpful here.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=6577
------- Additional Comments From winehq(a)paniq.org 2006-01-11 03:08 -------
with the bureaucratic procedure you suggest, it takes some ignorance and 5
minutes for a skilled programmer to break the code, and good will and more than
two hours for an unskilled user to find the problem.
given this entropic ratio as a general rule, will the project ever reach a
stable state?
perhaps you can find a simpler procedure?
what about forwarding this to all people who have done modifications to the d3d
parts between .23 and .24 and see whose brain feels tickled by the report? would
that be a viable alternative?
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.