wine-bugs May 2007

wine-bugs@winehq.org

8 participants
3228 discussions

[Bug 8260] ubuntu dapper install from source fails
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8260 ------- Additional Comments From thestig(a)google.com 2007-05-05 17:34 ------- Did you download your source code from winehq.org? -- 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 8207] X2 - The threat fails to install
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8207 ------- Additional Comments From truiken(a)gmail.com 2007-05-05 17:29 ------- You can check this by reading the volume names of the two CDs and also by opening up 'X2 - The Threat.msi' with orca and reading the Media table. -- 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 8207] X2 - The threat fails to install
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8207 ------- Additional Comments From truiken(a)gmail.com 2007-05-05 17:14 ------- Hmm, I'm pretty sure you have the same copy of X2 that I have. It comes with two CDs: the labels are X2_INSTALL and X2_GAME. They're both required to install the game. Please verify this. -- 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 8295] Motorhead crashes when using hw D3D renderer
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8295 ------- Additional Comments From tom8311(a)wp.pl 2007-05-05 17:13 ------- Unfortunately I will have to attach the logs later as they are huge (one is 3 and the other is 22 MB) and my net connection is to slow to submit so big files in a reasonable time. and sorry for that mess with links in the initial post;) -- 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 8146] fr-041 (Debris) fails to render correctly
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8146 ------- Additional Comments From ns03ja(a)brocku.ca 2007-05-05 17:04 ------- For kicks, I tried this on a Radeon Mobility X1400 with 128 megs of memory and fglrx 8.35.5. It spits out a slew of errors I haven't seen before (including lots of out of memory issues and then failing to create a VBO), but it doesn't hang up at the usual spot and appears to be mostly correct with both wine-0.9.35 and wine-0.9.36-139-ge79a94d, it's extremely slow (<1 fps) though. However, I'm not sure if FBOs are even used for fglrx, as their support for it is dodgy, IIRC. With the 7950 GT again, I tried setting VideoMemorySize = 256 instead of 512, which appeared to produce identical results visually. -- 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 7698] Counter-Strike:Source crashes after a while
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=7698 ------- Additional Comments From jrliggett(a)cox.net 2007-05-05 17:02 ------- Phil: Yeah, it happens for me with long-range shots. At close range I can shoot people in the head all day long and it won't crash. It might also be relavant that I do my testing in a local listen server with bots in it so I can control the environment a little better. The bots also can get headshots all day long and it won't crash. Besides, I don't have to kill my target to get it to crash; all I have to do is hit someone. I played de_port last night, and I was able to play about 10 rounds, then it just crashed after I shot a bot in the leg (which, oddly was at close range, first time that's happened in my tests.) I guess I'll have to try joining a server with real people to see if there's a difference. -- 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. You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 8295] New: Motorhead crashes when using hw D3D renderer
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8295 Summary: Motorhead crashes when using hw D3D renderer Product: Wine Version: 0.9.36. Platform: PC URL: http://downloads.gamezone.com/demos/d1574.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tom8311(a)wp.pl In Motorhead (a 3D racing game) one can choose between a software renderer and hardware accelerated D3D renderer. The setting is made in game's menu and takes effect when starting the gameplay - the game then switches from 2D mode to 3D mode. When using the D3D hardware renderer the game crashes while switching to the 3D mode. It displays a dialog box containing a message: "The instruction at 00432905 refered to memory at 00000000 The memory could not be read from Click on OK to terminate the application" Besides, when you choose between the sw and hw modes (in "graphic options") the hw mode is named "DDraw HAL" instead of "D3D HAL" (under windows it was a name of gfx driver, so I don't know if the name is a problem). Moreover, there are always two "DDraw HAL" devices to choose from, while there should be one (I have only one gfx device). It doesn't matter which one of them I choose - the effect is always the same. BTW. there is another bug in wine (<a href="http://bugs.winehq.org/show_bug.cgi?id=3747">Bug#3747</a>) that makes it impossible to run the game w/o hacking wine (see <a href="http://bugs.winehq.org/show_bug.cgi?id=3747#c21">comment#21</a> from that bugreport) (or having a joystick connected to the PC), so reproducing the bug is not that simple;) I'm attaching the output of "WINEDEBUG=+d3d wine motor.exe" in two versions - one is from the crash, when using hw renderer, and the other is from a run w/o crash, when using sw renderer. -- 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 7698] Counter-Strike:Source crashes after a while
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=7698 ------- Additional Comments From jrliggett(a)cox.net 2007-05-05 16:57 ------- Luke: I doubt that. When programs crash, they stop executing *immediately*; they don't get the opportunity to clean up after themselves. The most a program like WINE could do here is see that a crash has happened, and attach WineDbg to get a backtrace Besides, AFAIK it would be CS's responsibility to clean up itself, not WINE. -- 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. You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 8234] Supreme Commander Install fail - Error : 87
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=8234 ------- Additional Comments From thestig(a)google.com 2007-05-05 16:56 ------- Install works fine here (all 7.5 gb of it) with latest wine-git. -- 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 1798] Keyboard focus to terminal, not the program
by Wine Bugs 05 May '07

05 May '07

http://bugs.winehq.org/show_bug.cgi?id=1798 ------- Additional Comments From bero(a)arklinux.org 2007-05-05 16:54 ------- An interesting tidbit: I've talked the programmer of an application that is still affected by this problem into giving me his source code to play with. Unfortunately, it is written in a rather obscure language (GFA-BASIC -- I've never seen that one running on anything but an Atari ST before), but it allowed me to trace the issue a bit more. This code has the keyboard focus problem: Global t$ OpenW #1,,,,,0 Repeat Sleep t$=InKey$ If t$ Print t$ EndIf Until t$ = "q" This does not: Global t$ OpenW #1,,,,,32 Repeat t$=InKey$ If t$ Print t$ EndIf Until t$ = "q" The only difference is the last parameter of OpenW - window opening flags. 0 is "no attribtues" -- no scroll bars, no title bar, nothing whatsoever. 32 is "only a close field" (still no title bar, so the close filed is not actually drawn or visible). Unfortunately I have no way of tracing what GFA-BASIC does with those flags, but I guess it's a direct translation into the bitfields passed to window creation (I have no idea about Windoze APIs -- Linux purist ;) ). -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs May 2007