wine-bugs October 2009

wine-bugs@winehq.org

1 participants
6167 discussions

[Bug 17900] New: RenderTargetLockMode=disabled required for playable display
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=17900 Summary: RenderTargetLockMode=disabled required for playable display Product: Wine Version: 1.1.18 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael(a)araneidae.co.uk On at least two games (Thief 2 and Jedi Knight Dark Forces II, I've not tried others of this vintage yet) unless the key Wine/Direct3D/RenderTargetLockMode is set to disable the game display is completely unplayable. Of course, disabling this key has undesirable side effects: in JKDF2 the HUD is overlaid by the game display, in Thief2 the in game menu is unusable -- but this must be a strong clue as to what is going wrong here. I've tried setting this key to default, readtex, texdraw, textex, and in all of these cases the effect is a sort of upside-down shimmering stripes. This visual effect may be a side effect of what's really going on, because any attempt at a screen shot capture either a good image or an upside down image. I think what is actually happening is that the image is constantly alternating between upsidedown and rightside up! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 18

[Bug 16017] New: Counter Strike Source Stutters
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=16017 Summary: Counter Strike Source Stutters Product: Wine Version: 1.1.8 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: nheinen(a)gmail.com Hardware: AMD X2 3800+ nVidia GF 6600GT 128MB Kernel 2.6.27 Wine 1.18 Drivers 177.80 nVidia Description: The games runs smooth 60+ fps otherwise. When this bug occurs the screen stutters/hitches/freezes and sounds will repeat(usually a grenade being thrown or exploding seem to be commond sounds that play when this happens). This can last from 1 to 5 seconds. The Hud will often redraw. After this the game is playable again but occurs frequently, every 2-3 rounds of play. This occurs on all maps while playing online. It occurred on both 64bit and 32 bit builds of linux. There doesn't seem to be any meaningful output from the console. This bug does not occur using windows operating system on my hardware. It only occurs when using wine. I think it is related to this. http://half-life.wikia.com/wiki/Source_Engine#Stutter heres a whole webpage dedicated to it http://www.blep.net/hl2stutter/ I have tried dxlevel 7 8 and 8.1 In winecfg audio acceleration Full, Standard, and Basic I've tried all the suggested solutions on the second url above. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 16

[Bug 9468] New: Mortal Kombat Trilogy crashes
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=9468 Summary: Mortal Kombat Trilogy crashes Product: Wine Version: 0.9.44. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: rchayster(a)gmail.com Created an attachment (id=7810) --> (http://bugs.winehq.org/attachment.cgi?id=7810) output I have Mortal Kombat Trilogy, patched to version 1.1. The game crashes on startup. When I run $ wine MKTRILW.EXE The wine outputs: err:wgl:X11DRV_wglGetProcAddress (wglMakeContextCurrentARB) - not found err:wgl:X11DRV_wglGetProcAddress (wglGetCurrentReadDCARB) - not found fixme:win:EnumDisplayDevicesW ((null),0,0x33f688,0x00000000), stub! fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x125ce0) : stub, simulating 64MB for now, returning 64MB left And just stucks there. When I press ctrl+c wine outputs this and quits: The program encountered a problem at address 00432252 and cannot continue I'm putting the WINEDEBUG=+all debug log here as an attachment. It's the last 1000 lines. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 19

[Bug 20012] New: Implement HalGetBusDataByOffset for the PCIConfiguration BusDataType
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=20012 Summary: Implement HalGetBusDataByOffset for the PCIConfiguration BusDataType Product: Wine Version: 1.1.29 Platform: PC URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk Created an attachment (id=23551) --> (http://bugs.winehq.org/attachment.cgi?id=23551) Scren capture showing example code working With the fix http://bugs.winehq.org/show_bug.cgi?id=19966 SIV (http://rh-software.com/) no longer crashes when run under Wine, however none of the PCI Bus reporting actually works. As an experiment I wrote some code to read the PCI confutation data from "/sys/bus/pci/devices/0000:bb:dd.f/config" where bb:dd:f are the Bus, Device and Function numbers (the Device and Function are bits 7...3 and 2...0 of the slot number. The attached screen shot you can see I was able to read the data what HalGetBusDataByOffset() should return. I actually did this using the Windows API functions using the following code: if( ( fhl = CreateFile( file_name, GENERIC_READ, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL ) ) != INVALID_HANDLE_VALUE ) { if( ReadFile( fhl, data, sizeof( data ) &len, NULL ) ) { ... } CloseHandle( fhl ); but I would expect the Unix/Linux Native API should be used were this to be implemented. I am concerned that different Unix/Linux systems may have different device names, but looking at the lspci source there seems to be a pci library to address this. I could try and work-a-round this within SIV, but as SIV would probably not be able to use the Unix/Linux pci library that solution would be less portable than implementing a solution within HalGetBusDataByOffset() within Wine. For systems where this data could not be returned then the current return of 0 (PCI Bus does not exist) would be made. Note that in the case of the Bus existing and the slot being empty a return of 2 is expected. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[Bug 17618] New: winecfg does not set drive type correctly for Local Hard Disk choice
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=17618 Summary: winecfg does not set drive type correctly for Local Hard Disk choice Product: Wine Version: 1.1.16 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lordhavoc(a)ghdigital.com The Drives panel in winecfg has a Type: dropdown which allows Auto-detect, Local Hard Disk, Network Share, Floppy Disk, or CD-ROM to be chosen for each drive. Each of these sets a registry value, except for Auto-detect and Local Hard Disk which simply remove the registry value for the respective drive. Local Hard Disk should set the registry value for the drive to "hd". -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 17

[Bug 20335] New: Uninitialised memory reference in X11DRV_DIB_SetImageBits()
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=20335 Summary: Uninitialised memory reference in X11DRV_DIB_SetImageBits() Product: Wine Version: 1.1.31 Platform: PC OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com I think this is one of the first valgrind warnings I ever ran into in wine, and it's still here. Nowadays Wine gives better warnings, so it's a little easier to see where these are coming from. Running chromium's base_unittests.exe (and probably lots of other apps) in valgrind yields this warning: Conditional jump or move depends on uninitialised value(s) at XcursorImageHash (xlib.c:294) by XcursorNoticePutBitmap (xlib.c:365) by _XNoticePutBitmap (CrGlCur.c:202) by XPutImage (PutImage.c:1042) by X11DRV_DIB_SetImageBits (dib.c:3670) by X11DRV_SetDIBits (dib.c:4040) by SetDIBits (dib.c:361) ... Uninitialised value was created by a client request at RtlAllocateHeap (heap.c:187) by X11DRV_DIB_SetImageBits (dib.c:3543) by X11DRV_SetDIBits (dib.c:4040) by SetDIBits (dib.c:361) ... Presumably adding HEAP_ZERO_MEMORY to the allocation at dib.c:3543 would do the job, but maybe there's a smarter way. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 10

[Bug 20508] New: F/A-18 PSF Mouse control stops working in 3d view
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=20508 Summary: F/A-18 PSF Mouse control stops working in 3d view Product: Wine Version: 1.1.29 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: bgoodwin91006(a)yahoo.com The mouse works correctly in all menus. On entering the 3D cockpit view, it works correctly for a few seconds; long enough to take-off. In flight, the control becomes less and less responsive. The plane noses down and crashes. Using a joystick instead of the mouse works correctly but I prefer mouse control because it's smoother and there's no convenient place to put the joystick with my small desk and chair. The mouse control works correctly under WindowsXP. The problem has been the same for a long time (several years.) and through a steady migration from Fedora 3 to my current Fedora 11. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 19871] New: Cusom CWnd component redraw flicker
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=19871 Summary: Cusom CWnd component redraw flicker Product: Wine Version: 1.1.28 Platform: PC URL: http://www.jtagtest.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: martin(a)hinner.info See bug: http://bugs.winehq.org/show_bug.cgi?id=17394 Window repainting is flickering under Wine. Native Win32 works fine (or at least I cannot see anything). Can provide "closed" source code of the component to person who will be dealing with this stuff. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 7

[Bug 16069] New: VC6 debugging not working
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=16069 Summary: VC6 debugging not working Product: Wine Version: 1.0.1 Platform: PC OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kresander(a)yahoo.com I have used Wine to compile and run fairly large programs (more than 75 source files and 2GB, 5GB of source code). Background is available in my post at Wine User's forum under title Cannot install Visual C++ version 6.0 (VC6). My last reply in the thread is this: +++ begin +++ So far, I have tried four projects from Windows to Linux/Wine. All compiled using VC6 on Wine and ran ok the first time. The two largest contained 78 and 105 cpp files with approximate source file sizes 2GB and 5GB. Features used: GUI: most standard and extended controls via dialog calls/macros and CreateWindow, various window positioning/resizing functions, messageboxes GDI: most except paths CHARS: most functions defined by <tchar.h> FILES: fopen,fread, fwrite, ftell, fseek, fclose, _findfirst, _findnext, _mkdir, remove, _tunlink MEMORY new,delete and most memory and <string.h> functions. Did not use MFC or ATL frameworks, just plain, Windows API functions and as few of these as I could manage. Did not use Windows file and directory functions. Did not use c++ exception handling Did not use Windows memory allocation function or older mallocs. BUT could not get the debugging to work. 1. on entry to the Windows main program: int PASCAL WinMain( ...) { WNDCLASS wc; MSG msg; int a = 1; // for testing debug int b = a + 1 ; // testing debug hmodule = fhInstance ; <<< put breakpoint here Values of variables a and b were reported as unknown expressions. 2. a little bit further into WinMain at call to CreateWindow for main window: hwndmain = CreateWindow( "GenericAppClass", .... The program entered CreateWindow, but never returned. Does debugging work, or have I entered unchartered waters? +++ end +++ I don't write bigger and more resource-demanding programs than those mentioned above. The VC6 compiled these with ease, ran without a single glitch and the IDE behaved as I was used to see it. With debugging working there is no reason for me to be on Windows any more. Have wanted to leave for years. VC6 is an excellent product (too good to be Microsoft) and it now seems it can offer cross-development on Linux. Really worth pursuing in my view. You can reach me at kresander(a)yahoo.com. Best regards Ken Resander -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 14

[Bug 19761] New: RollerCoaster Tycoon: Wrong background colour in some menus.
by wine-bugs＠winehq.org 22 Nov '14

22 Nov '14

http://bugs.winehq.org/show_bug.cgi?id=19761 Summary: RollerCoaster Tycoon: Wrong background colour in some menus. Product: Wine Version: 1.1.24 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: debian(a)carbon-project.org Created an attachment (id=23139) --> (http://bugs.winehq.org/attachment.cgi?id=23139) In-game screenshot depicting the problem The game RollorCoaster Tycoon (with the Loopy Landscapes add-on) shows a wrong background colour (see attached image) in a menu, where all occurred events are logged. The colour shouldn't be the green but the grey you see in the background of the ride menu in the lower left corner. Testsystem: - AMD Athlon XP (1.2GHz) - 1.5 GB RAM (DDR) - ATI Radeon R300 (with the radeon driver, v6.12.2) If you need further information, feel free to ask. Kind regards, Kai Wasserbäch -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

1 24

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 October 2009