November 2006 - Wine-Bugs - list.winehq.org

[Bug 6583] Crusader Kings crash
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6583 ------- Additional Comments From murlock(a)free.fr 2006-02-11 12:33 ------- Created an attachment (id=3994) --> (http://bugs.winehq.org/attachment.cgi?id=3994&action=view) the last 200 lines with +seh,+relay -- 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.

1 0

[Bug 6583] Crusader Kings crash
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6583 ------- Additional Comments From murlock(a)free.fr 2006-02-11 12:33 ------- Created an attachment (id=3993) --> (http://bugs.winehq.org/attachment.cgi?id=3993&action=view) the last 200 lines with +seh,ù!$m$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$+relay -- 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.

1 0

[Bug 6505] WoW Random Crashes
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6505 ------- Additional Comments From atrauzzi(a)gmail.com 2006-02-11 12:10 ------- And to answer the insultingly obvious "duh" questions: So do you run in opengl or d3d? See the command line. D3D. In OpenGL there is a flicker bug for NVidia, and ATI cards crash HARD. I do not wish to use registry tweaks or workarounds to get the game working. The whole idea is to get these bugs solved. Have you tried the latest git version? Yes .23, yes .24 Do you add anything to the ./configure command line? --prefix=/home/[username]/wine Where do you get the source code from? winehq.com's distribution references. -- 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.

1 0

[Bug 6505] WoW Random Crashes
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6505 ------- Additional Comments From atrauzzi(a)gmail.com 2006-02-11 12:06 ------- To both of you. Read my first post, all your answers as there. Why don't you pay attention to me instead of using your knee-jerk reflexes to dismiss what in your eyes is "yet another moron posting bugs". I think " * Launched using: "wine 'C:\Program Files\World of Warcraft\Launcher.exe'" " is enough to answer your questions thus far. Again, I've already provided bug reports, been bopped on the head by arrogant bug wardens and have produced my own bug reporting templates. My guess is this is obviously not enough. I can continue to post my crash logs, I can continue to provide the results of WoW's crash-catcher... As for adding +d3d debug - that's a joke. I ran the game for all of four minutes before realizing the problem would not reproduce and also that I had accumulated over 100MB of data on my hard drive. The game was beyond unplayable and I think the slowdown is likely enough to prevent the bug from occuring. Adding d3d for debugging is unacceptable for tracing the problem at this point. Especially given that some of my posted logs so far contain information denoting a crash. The only update I can provide is that I'm now using the latest 0.9.24 version of Wine on all my machines and the problem is still present. This is getting ridiculous. -- 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.

1 0

[Bug 6579] Rayman 2 won't install
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6579 ------- Additional Comments From juan_lang(a)yahoo.com 2006-02-11 11:13 ------- Try WINEDEBUG=relay wine ... That might tell you more. Attach that log here if it's not too big, otherwise tail the last 500 lines or so of it and bz2 it and attach it. -- 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.

1 0

[Bug 6583] Crusader Kings crash
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6583 ------- Additional Comments From juan_lang(a)yahoo.com 2006-02-11 11:12 ------- Posting a +seh,+relay log might be more informative. -- 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.

1 0

[Bug 6583] Crusader Kings crash
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6583 juan_lang(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal ------- Additional Comments From juan_lang(a)yahoo.com 2006-02-11 11:11 ------- Not a blocker. -- 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.

1 0

[Bug 6505] WoW Random Crashes
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6505 ------- Additional Comments From the3dfxdude(a)gmail.com 2006-02-11 10:59 ------- Alexander, you really need to approach this bug differently. You should see this as a support request for you. You aren't helping anyone else by doing what you are doing. Alan is now asking for more information, and it all is pretty elementary because he doesn't understand mostly anything about it. Just like in my emails to you, and my original response, you need to fix the summary of this report and provide better information. You still have not indicated at all whether this is only a d3d problem. I asked you to do this three times now. Don't blow *us* off. I still don't know if this is only *one* problem described here either. The purpose of the WINEDEBUG=+d3d is to gather more information. No you don't have to spend time to decipher it. I'm not saying you are supposed to learn how to hack wine either. If you are able to get a log, just post it like I asked. I still take it you haven't read the guide of the link I posted. It talks about debug channels and controlling debug output. Yes, it will slow down the game, and you'll have to suffer through it and learn how to control it enough to gather some information. Considering the nature of the bug, it will be difficult to gather information, but we depend on you to provide enough because you are the reporter. This bug will continue to remain how it is until you start responding to requests. -- 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.

1 0

[Bug 6578] World of Warcraft doesnt close anymore
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6578 ------- Additional Comments From jacek(a)codeweavers.com 2006-02-11 10:53 ------- I've sent a patch: http://www.winehq.org/pipermail/wine-patches/2006-November/032428.html that reverts this patch: I apologize for it. -- 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.

1 0

[Bug 6550] Segfault (coredump)
by Wine Bugs Nov. 2, 2006

Nov. 2, 2006

http://bugs.winehq.org/show_bug.cgi?id=6550 ------- Additional Comments From kkelly(a)cinci.rr.com 2006-02-11 10:49 ------- I think autoconf ran. I'm on gentoo and know just enough about ebuilds to be dangerous. I modified the local ebuild to perform the patch and added a call to autoconf. There were no error messages, so I think it ran. I also checked the build output and confirmed -fno-stack-protector was passed to the compiler. -- 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.

1 0