wine-bugs December 2017

wine-bugs@winehq.org

1 participants
7821 discussions

[Bug 31644] New: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver )
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=31644 Bug #: 31644 Summary: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver ) Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tizbac2(a)gmail.com Classification: Unclassified Calls to glMapBufferRange are extremely slow on nvidia drivers with resident evil 5, if this should be reported to nvidia instead just close it over 90% of frame time is taken by glMapBufferRange -- 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 20

[Bug 38488] New: Wrong taces in functions *_invalidate_location
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=38488 Bug ID: 38488 Summary: Wrong taces in functions *_invalidate_location Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- I got a plenty of messages like fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. It rises because the function wined3d_volume_invalidate_location() is used with reversed parameter For example dlls/wined3d/device.c: wined3d_volume_invalidate_location(dst_volume, ~WINED3D_LOCATION_TEXTURE_RGB); The function assumed location and not ~location. ----- void wined3d_volume_invalidate_location(struct wined3d_volume *volume, DWORD location) { TRACE("Volume %p, clearing %s.\n", volume, wined3d_debug_location(location)); volume->locations &= ~location; TRACE("new location flags are %s.\n", wined3d_debug_location(volume->locations)); } ----- Here wined3d_debug_location() will message like above. Same about wined3d_resource_invalidate_location(struct wined3d_resource *resource, DWORD location) -- 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 6

[Bug 18496] New: BREW simulator always shows a black display
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=18496 Summary: BREW simulator always shows a black display Product: Wine Version: 1.1.21 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jon.dufresne(a)gmail.com Tested with wine-1.1.21 I am attempting to use the Qualcomm BREW simulator under wine. After installing, I attempted to run the example applets. The application launches and I am able to select an applet directory, but the simulated device's screen always shows black and not the usual list of icons that represent available applets. The BREW simulator installer is found here: https://brewx.qualcomm.com/bws/content/gi/products/sdk/3.1/en/3.1.5.179/ins… Steps to reproduce: 1. Download and install BREW SDK simulator 2. Run simulator 3. Use menu to selec "File->Change Applet Dir..." 4. Navigate to c:/Program Files/BREW 3.1.5/sdk/examples/ 5. Hit "OK" 6. Notice screen is black Expected results: Under windows, the BREW simulator will show a listing of the available BREW applets (one for each *.mif file in the directory chosen). This list appears as a series of icons inside the device's display area. -- 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 15703] New: LEGO Star Wars controller options
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=15703 Summary: LEGO Star Wars controller options Product: Wine Version: 1.1.6 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: infernux(a)web.de Going to "Controller Options" freezes the game, pressing "Esc" does not make it playable again. I don't know what other information / logs would be helpful, if you need anything specific just say so. This only affects the _first_ of the two games - but the 2nd seems to have a different input system anyway (requires xinpit1_2.dll for example). -- 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 43659] New: Jurassic Park: Operation Genesis does not launch unless winegstreamer is set to disabled
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=43659 Bug ID: 43659 Summary: Jurassic Park: Operation Genesis does not launch unless winegstreamer is set to disabled Product: Wine Version: 2.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: arnfranke(a)yahoo.com Distribution: --- Created attachment 59097 --> https://bugs.winehq.org/attachment.cgi?id=59097 Win7 64-bit wineprefix crash Low priority as this bug has a work-around which is to disable winegstreamer. Reproducible on Xubuntu 16.04 64-bit, with AMD Radeon 6520G graphics, on both 32-bit and 64-bit wineprefixes, and set to WinXP and Win7 mode. I have attached crash reports for Win7 mode on a 64-bit prefix and WinXP/32bit. Interestingly enough, the game runs fine without any overrides when it is launched from POL. Interesting that POL would work when ~/.wine does not. https://www.reddit.com/r/wine_gaming/comments/6xwy7o/can_anyone_explain_why… https://appdb.winehq.org/objectManager.php?sClass=version&iId=6088 -- 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 37

[Bug 19777] New: Ad Astra game runs very slow glBlitFramebuffer
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=19777 Summary: Ad Astra game runs very slow glBlitFramebuffer Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P3 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: chrisyate+wine(a)gmail.com CC: chrisyate+wine(a)gmail.com Ad Astra is a free space flight sim available at www.a-astra.com. The game runs (as in starts) successfully, with a clean .wine prefix folder. However once it enters 3D mode the disk starts to grind, wine spits out lots of fixmes and the program runs slowly with fps around 3, max maybe 5. The following is output, over and over until you stop the game. <quote> fixme:d3d:stretch_rect_fbo >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION_EXT (0x506) from glBlitFramebuffer() @ device.c / 6532 fixme:d3d:state_ckeyblend Render state WINED3DRS_COLORKEYBLENDENABLE not implemented yet (repeated 6 times)... </quote> My System is Athlon XP2400+, a NVidia 6200 clone (the Zotac with 256Mb), 1.5Gb ram. Unfortunately I can't confirm whether it would work on my machine if I was running Windows natively. Any other info, please ask. -- 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 21023] New: SetupDiOpenDevRegKey() returns wrong HKEY
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=21023 Summary: SetupDiOpenDevRegKey() returns wrong HKEY Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: mdealencar(a)gmail.com Created an attachment (id=25222) --> (http://bugs.winehq.org/attachment.cgi?id=25222) bug example In a Windows XP system SetupDiOpenDevRegKey() returns the "Device Parameters" HKEY under the device instance corresponding to the supplied (DeviceInfoSet, &DeviceInfoData) pair. Wine's SetupDiOpenDevRegKey() returns the device instance HKEY instead. The relevant registry keys are not created by Wine, so I had to import them from a Windows XP system Example: Windows HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1\Device Parameters Wine HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1 The attached registry patches and source code enable the reproduction of the bug. -- 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 12

[Bug 39932] New: bat-script with quotes cann't be called using CreateProcess
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39932 Bug ID: 39932 Summary: bat-script with quotes cann't be called using CreateProcess Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: andrej.skvortzov(a)gmail.com Distribution: --- Created attachment 53340 --> https://bugs.winehq.org/attachment.cgi?id=53340 executable with source code to reproduce the problem This problem exists in software to configure HMI panels from OWEN and Xinje. http://www.owen.ru/catalog/graficheskaya_panel_operatora_s_sensornim_upravl… (Russian) To reproduce this problem easily minimal test program is created. See attached archive cmd_call_batch.tar.xz. Here are technical details of the problem. To appear following conditions need to be met: - bat-script is called using CreateProcess - name of bat-script is quoted - some parameters of bat-scrits are quoted. For example, "test2.bat" "param1" param2 wine runs bat-script using cmd. cmd /c "test2.bat" "param1" param2 On Windows cmd fails if name of bat-script and parameters both are quoted. To avoid this problem attached patch always removes quotes from bat-script's name before cmd is called. -- 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 32374] New: List box with LBS_NODATA set, has very low performance, depending on items count.
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=32374 Bug #: 32374 Summary: List box with LBS_NODATA set, has very low performance, depending on items count. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: johnfound(a)evrocom.net Classification: Unclassified Created attachment 42719 --> http://bugs.winehq.org/attachment.cgi?id=42719 Test application that illustrates the bug. Source code included. List box control, when has LBS_NODATA style set, needs very big time to process LB_SETCOUNT message (this message works only for list box with LBS_NODATA set). On Windows this message is handled for less than 1ms regardless of the count sent by LB_SETCOUNT (because the list box has nothing to allocate/reallocate when LBS_NODATA is set. It only need to set the scroll bar parameters). In WINE (every version but in v1.4 and v1.5 it is really slow) processing this message needs some amount of time, proportional to the item count set by LB_SETCOUNT. As long as this list box style is provided because of its speed, such a behavior can block the execution of the application for very long time. Small test application is attached which measures the time needed for LB_SETCOUNT to be executed on list box with LBS_NODATA set. Source code included. -- 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 43395] New: Wine intermittently crashes after any program terminates
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=43395 Bug ID: 43395 Summary: Wine intermittently crashes after any program terminates Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Every so often, I see one of the following two outputs appear after Wine closes: err:ntdll:RtlLeaveCriticalSection section 0x110940 is not acquired and wine: Unhandled page fault on write access to 0x695de019 at address 0x7bc4f41e (thread 0018), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 96") (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger In the first message the section 0x110940 is constant; in the second the address 0x7bc4f41e is constant but the written address varies. The critical section message appears because a critical section is deleted while owned. The critical section in question appears to be that of the database in services.exe. The crash address is in ntdll/heap.c:HEAP_CreateFreeBlock. It is probably being triggered by code in RtlLeaveCriticalSection(), although it may have a different source. -- 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 8

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 December 2017