wine-bugs February 2018

wine-bugs@winehq.org

1 participants
8011 discussions

[Bug 44485] New: makes Delphi 7 debugger generate new exceptions by itself (regression)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=44485 Bug ID: 44485 Summary: makes Delphi 7 debugger generate new exceptions by itself (regression) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: development(a)winomega.com Distribution: --- Created attachment 60433 --> https://bugs.winehq.org/attachment.cgi?id=60433 WINEDEBUG=+seh Starting with commit a75e3f734d32bd98df9017f1a94819d2b6dca85d, the Delphi 7 debugger behaves erratically after catching an exception generated by the debugged program. It generates new floating point arithmetic exceptions, making debugging impossible and forces the debugger application to abort. The test program is a trivial application which raises an exception when clicking on a button. I'm attaching a WINEDEBUG=+seh log. Also, here's an annotated excerpt describing what I'm doing when each of the traces show up: I start the program and click on the button. Then get this: trace:seh:raise_exception code=eedfade flags=1 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=00450767 trace:seh:raise_exception info[1]=00473dbc trace:seh:raise_exception info[2]=004736c0 trace:seh:raise_exception info[3]=00426c58 trace:seh:raise_exception info[4]=0033ef44 trace:seh:raise_exception info[5]=0033ef08 trace:seh:raise_exception info[6]=0033edc4 trace:seh:raise_exception eax=7b428e39 ebx=00000018 ecx=0033ed30 edx=0033eda8 esi=0033ef08 edi=0033ef44 trace:seh:raise_exception ebp=0033ed88 esp=0033ed04 cs=0023 ds=13002b es=4d43002b fs=0063 gs=006b flags=00000212 I press F9 (run) to resume execution. Then get these: trace:seh:call_stack_handlers calling handler at 0x433637 code=eedfade flags=1 trace:seh:call_stack_handlers handler at 0x433637 returned 1 trace:seh:call_stack_handlers calling handler at 0x433648 code=eedfade flags=1 trace:seh:__regs_RtlUnwind code=eedfade flags=3 trace:seh:__regs_RtlUnwind calling handler at 0x7bc81710 code=eedfade flags=3 trace:seh:__regs_RtlUnwind handler at 0x7bc81710 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x433637 code=eedfade flags=3 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043362c trace:seh:raise_exception eax=7b428e39 ebx=0043362c ecx=0033e3d0 edx=0033e448 esi=00000000 edi=0033ed1c trace:seh:raise_exception ebp=0033e428 esp=0033e3a4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:raise_exception code=eedfae0 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043364d trace:seh:raise_exception eax=7b428e39 ebx=0043364d ecx=0033e890 edx=0033e90c esi=00000000 edi=0033f104 trace:seh:raise_exception ebp=0033e8e8 esp=0033e864 cs=330023 ds=002b es=002b fs=0063 gs=006b flags=00000212 trace:seh:raise_exception code=c0000092 flags=0 addr=0x7ecdb6be ip=7ecdb6c1 tid=0031 trace:seh:raise_exception eax=00117f68 ebx=7ed32000 ecx=0013e398 edx=0013e398 esi=0033dc40 edi=00117f68 trace:seh:raise_exception ebp=0033db98 esp=0033db70 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 trace:seh:call_stack_handlers calling handler at 0x44f399 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f399 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f467 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f467 returned 1 trace:seh:call_stack_handlers calling handler at 0x403664 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x403664 returned 1 trace:seh:call_stack_handlers calling handler at 0x433637 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x433637 returned 1 trace:seh:call_stack_handlers calling handler at 0x433648 code=c0000092 flags=0 trace:seh:raise_exception code=eedfae4 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0033d84c trace:seh:raise_exception info[1]=00473dfc trace:seh:raise_exception eax=7b428e39 ebx=00000004 ecx=0033d690 edx=0033d70c esi=0033d84c edi=0033db18 trace:seh:raise_exception ebp=0033d6e8 esp=0033d664 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 A MessageBox is shown: "Debugger Exception Notification: Project xxx.exe raised exception class EInvalidOp with message 'Invalid floating point operation'. Process stopped. Use Step or Run to continue." I click OK. Debugger stops at vcl/Controls.pas class, at CallWindowProc; it appears as if the exception is triggered in CallWindowProc itself, but I can't tell for sure as the debugger environment is unreliable (if I were to single-step, it keeps triggering new exceptions). I press F9 again.... trace:seh:__regs_RtlUnwind code=c0000092 flags=2 trace:seh:__regs_RtlUnwind calling handler at 0x7bc81710 code=c0000092 flags=2 trace:seh:__regs_RtlUnwind handler at 0x7bc81710 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x44f399 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0044f33f trace:seh:raise_exception eax=7b428e39 ebx=0044f33f ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x44f467 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0044f453 trace:seh:raise_exception eax=7b428e39 ebx=0044f453 ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=110023 ds=002b es=33002b fs=0063 gs=7bc8006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x403664 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=00403669 trace:seh:raise_exception eax=7b428e39 ebx=00403669 ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:__regs_RtlUnwind calling handler at 0x433637 code=c0000092 flags=2 trace:seh:raise_exception code=eedfae1 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043362c trace:seh:raise_exception eax=7b428e39 ebx=0043362c ecx=0033d1b0 edx=0033d228 esi=00000000 edi=0033db18 trace:seh:raise_exception ebp=0033d208 esp=0033d184 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:__regs_RtlUnwind handler at 0x403844 returned 1 trace:seh:raise_exception code=eedfae0 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0043364d trace:seh:raise_exception eax=7b428e39 ebx=0043364d ecx=0033d670 edx=0033d6ec esi=00000000 edi=0033fb94 trace:seh:raise_exception ebp=0033d6c8 esp=0033d644 cs=330023 ds=002b es=002b fs=0063 gs=006b flags=00000216 trace:seh:raise_exception code=c0000092 flags=0 addr=0x7ece39b7 ip=7ece39d6 tid=0031 trace:seh:raise_exception eax=00000003 ebx=7ed32000 ecx=7b43c5ac edx=00000000 esi=00141214 edi=00000001 trace:seh:raise_exception ebp=0033ca18 esp=0033c8a0 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010297 trace:seh:call_stack_handlers calling handler at 0x44f399 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f399 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f467 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x44f467 returned 1 trace:seh:call_stack_handlers calling handler at 0x403664 code=c0000092 flags=0 trace:seh:call_stack_handlers handler at 0x403664 returned 1 trace:seh:call_stack_handlers calling handler at 0x44f159 code=c0000092 flags=0 trace:seh:raise_exception code=eedfae4 flags=0 addr=0x7b43c5ac ip=7b43c5ac tid=0031 trace:seh:raise_exception info[0]=0033c57c trace:seh:raise_exception info[1]=00473e40 trace:seh:raise_exception eax=7b428e39 ebx=00000004 ecx=0033c3c0 edx=0033c43c esi=0033c57c edi=0033c848 trace:seh:raise_exception ebp=0033c418 esp=0033c394 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000212 Again: "Debugger Exception Notification: Project xxx.exe raised exception class EInvalidOp with message 'Invalid floating point operation'. Process stopped. Use Step or Run to continue." I press OK. Debugged test app is terminated this time. Before exitting a seh error shows up: err:seh:setup_exception_record stack overflow 952 bytes in thread 0031 eip f73fb162 esp 00240f78 stack 0x240000-0x241000-0x340000 -- 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 20104] New: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=20104 Summary: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface Product: Wine Version: 1.1.29 Platform: PC URL: http://www.fotokasten.de/index.php?ftkPage=static&ftkV iew=ftksoftware OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: cweiske(a)cweiske.de Running the "fotokasten" photo album creation software fails to create certain photo books with the following error: > fixme:richedit:fnTextSrv_QueryInterface Unknown interface: > {01c25500-4268-11d1-883a-3c8b00c10000} > fixme:richedit:fnTextSrv_OnTxInplaceDeactivate 0x3a1e8e0: STUB How to reproduce: 1. Run software 2. Click on tab "Fotobücher" 3. Click on "Fotobücher" icon 4. Click on "Fun" 5. Click on "Fun A4" 6. A loading window appears but is hidden soon after. When using Fotobücher->Fotobücher->Soft->A4, the richtext window has not to be shown, and I get to the next window (meaning it works without richtext). -- 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 10913] New: start.exe doesn't support optional process title argument
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=10913 Summary: start.exe doesn't support optional process title argument Product: Wine Version: CVS/GIT Platform: Other URL: http://jedit.org OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Running real Java apps under the latest Sun win32 JRE on Wine seems like a fine stress test, even though in many cases users should run with the Linux JRE instead. The Sun JRE and jEdit install ok, but jedit has many startup problems. Here's the first one. Invoking it with the batch file provided by jEdit fails. Here's what's in the batch file: start "jEdit startup" "c:\windows\system32\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -reuseview %* And here's what happens when you run it: $ cd ~/.wine/drive_c/Program Files/jEdit $ ~/wine-git/wine cmd /c jedit.bat fixme:exec:SHELL_execute flags ignored: 0x00000500 trace:process:CreateProcessW app (null) cmdline L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" trace:process:find_exe_file looking for L"jEdit" trace:process:find_exe_file Trying native exe L"c:\\windows\\system32\\jEdit.exe" ... trace:process:find_exe_file Trying built-in exe L"c:\\windows\\system32\\jEdit startup.exe" ... trace:process:find_exe_file looking for L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found So it seems that start takes an optional process title argument. Sure enough, http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en… documents it. Who knew? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 20

[Bug 42508] New: start.exe does not detect its title argument when it should ( breaking .e.g URL opening in League of Legends)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=42508 Bug ID: 42508 Summary: start.exe does not detect its title argument when it should (breaking .e.g URL opening in League of Legends) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: hydratech(a)gmail.com Distribution: --- Created attachment 57397 --> https://bugs.winehq.org/attachment.cgi?id=57397 Trace showing League of Legends Client attempting to open a URL. When start.exe is invoked, its first argument in quotes that is not an argument of the application to be executed should be interpreted as the console title. Wine's start.exe fails to do so. -- How to reproduce -- Running the following line in Wine's cmd should open a URL in your browser: Z:\>start "" https://winehq.org/ the actual result is an application not found error. On Windows the same line opens the website as expected. -- Why this is a bug -- I know this was marked as fixed in bug 10913 but the reasoning was incorrect. The argument for stating the bug was fixed was, that when \"escaping your quotes\" in cmd to the title was parsed. This is however not consistent with with Windows behaviour. As explained at the end of that bug report, if you escape your quotes in Wine's cmd start.exe parses the argument as the console title, i.e.: Z:\>start \"hello\" cmd I will now clarify why this is incorrect by showing Windows' behaviour. The following command lines are not equivalent on Windows: C:\>start hello.exe vs. C:\>start "hello.exe" The latter will open a new cmd window titled hello.exe whereas the former attempts to execute an application named hello.exe. In other words cmd's start built-in parses its own command-line checking wether quotes where used. In fact escaping the quotes using back-slashes is invalid as it tries start a process named \hello.exe\. I have tested this on both Windows 7 and Windows XP. In other words, this is invalid: C:>start \"hello.exe\" To illustrate how unintuitive this Windows behaviour is: C:>start "C:\Program Files\Application\hello.exe" Few would guess this actually opens a console titled as such, instead of running an application. That's why I can understand the maintainers would think the bug was fixed. Wine will however correctly emulate unescaped quote-senstive behaviour with the echo built-in: Z:\>echo hoi hoi Z:\>echo "hoi" "hoi" We can see echo being "aware" of the quotes and correctly displaying them; behaviour identical to Windows' echo built-in. Looking at the wine source, start.exe relies on its "argv" parameter instead of using GetCommandLine() and thereby accessing the unmodified command-line. As a consequence the difference between a quoted argument and a non-quoted argument is lost as CreateProcess strips the quotes off the parameters when passing them to execve(). To quote the source of Wine's cmd.exe (wcmdmain.c): /* Can't use argc/argv as it will have stripped quotes from parameters * meaning cmd.exe /C echo "quoted string" is impossible */ It should now be evident that start.exe should either become a wrapper around cmd.exe's built-in start function, invoking cmd and let cmd itself implement start.exe's actual behaviour, or implement GetCommandLine() based argument parsing similar to cmd.exe's within start.exe, leading to duplicated command-line parsing code. Both are not ideal solutions. -- Why does this bug matter? -- There are actually Windows applications relying on this behaviour to open URLs in the user's browser. As an example, League of Legends executes the following shell command to open a URL: cmd.exe /c start "" "<url here>" In other words, League instructs start to launch an untitled shell window with a URL as application, effectively causing the shell to pass it to the browser. However, wine's start.exe interprets this as League trying to execute an empty string as executable name, with a URL as argument. I have attached the relevant output running League with WINEDEBUG=cmd,start,process,exec set. I will speculate that more applications will run into this exact same issue. League's client is based on CEF and it might very well be CEF which implements this style of external URL opening, furthermore there is documentation recommending the use of empty quotes as console title argument when invoking start to prevent it from accidentally parsing follow up arguments in quotes as the console title, think "C:\Program Files\etc...", establishing this as a pattern that might well have been adopted by other applications. See: https://ss64.com/nt/start.html I will also say that, given some instruction, I will be glad to help fixing this bug and write any necessary code. There is actually another issue with current start.exe's console title parsing which I will submit as a separate issue. That issue is however, significantly easier to fix. Finally this also means wine's current handling of command-line arguments might need fixing as: $ wine start '""' "http://winehq.og" will break in a fixed version of 'start.exe', while it should work. For this I will file yet another issue, although the necessity of this fix is debatable. -- 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 13

[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

[Bug 42370] New: Sniper Elite 3 stuck at "Completing Installation 1%"
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=42370 Bug ID: 42370 Summary: Sniper Elite 3 stuck at "Completing Installation 1%" Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: noonetinone(a)gmail.com Distribution: --- This is basically a repeat of the close bug reported by 'acescopezz'. Bug #41493 describes what is happening with the title SE V2. What is different about SE3 is this game includes its own copy of dllcheck.exe. 'acescopezz' posted screen grabs which relevant here. -- 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 38337] New: clang compiling warnings
by wine-bugs＠winehq.org 28 Feb '19

28 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=38337 Bug ID: 38337 Summary: clang compiling warnings Product: Wine Version: 1.7.39 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- Wine1.7.39-251-gdbf8bde compiled by Apple's clang. The wine works somehow. There are hundreds warning so I show them in one bug although there are many possible bugs. ---- keyboard.c:287:2: warning: illegal character encoding in string literal [-Winvalid-source-encoding] "?","&1","?2","\"3","'4","(5","-6","?7","_8","?9","?0",")?","=+", ^ ---- cocoa_status_item.m:100:13: warning: instance method '-discardEventsPassingTest:' not found (return type defaults to 'id') [queue discardEventsPassingTest:^BOOL (macdrv_event* event){ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 warning generated. ---- imgfactory.c:715:88: warning: implicit conversion from enumeration type 'WICBitmapAlphaChannelOption' (aka 'enum WICBitmapAlphaChannelOption') to different enumeration type 'WICBitmapCreateCacheOption' (aka 'enum WICBitmapCreateCacheOption') [-Wconversion] ...BitmapImpl_Create(bm.bmWidth, bm.bmHeight, bm.bmWidthBytes, 0, NULL, &format, option,... ~~~~~~~~~~~~~~~~~ ^~~~~~ ----- display.c:225:24: warning: unused function 'create_mode_dict' [-Wunused-function] static CFDictionaryRef create_mode_dict(CGDisplayModeRef display_mode) ^ 1 warning generated. ----- node.c:1620:37: warning: implicit conversion from enumeration type 'xmlElementType' to different enumeration type 'DOMNodeType' (aka 'enum tagDOMNodeType') [-Wconversion] *domNodeType = This->node.node->type; ~ ~~~~~~~~~~~~~~~~~^~~~ 1 warning generated. ----- locale.c:11344:13: warning: unknown attribute '__force_align_arg_pointer__' ignored [-Wattributes] call_locale_facet_vector_dtor(iter->fac, 1); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ locale.c:246:52: note: expanded from macro 'call_locale_facet_vector_dtor' #define call_locale_facet_vector_dtor(this, flags) CALL_VTBL_FUNC(this, 0, \ ^ ./cxx.h:269:59: note: expanded from macro 'CALL_VTBL_FUNC' #define CALL_VTBL_FUNC(this, off, ret, type, args) ((ret (WINAPI*... ^ ../../include/windef.h:169:21: note: expanded from macro 'WINAPI' #define WINAPI __stdcall ^ ../../include/msvcrt/crtdefs.h:48:67: note: expanded from macro '__stdcall' ...__attribute__((__stdcall__)) __attribute__((__force_align_arg_pointer__)) ^~~~~~~~~~~~~~~~~~~~~~~~~~~ ----- mach.c:93:9: warning: 'bootstrap_register' is deprecated [-Wdeprecated-declarations] if (bootstrap_register(bp, (char*)wine_get_server_dir(), ... ^ ---- warning: Small Fonts 11: missing glyph for char 05b0 ---- file.c:2124:49: warning: array index 1 is past the end of the array (which contains 1 element) [-Warray-bounds] dir_info->FileName[0] == '.' && dir_info->FileName[1] == ... ^ ~ ../../include/winternl.h:495:5: note: array 'FileName' declared here WCHAR FileName[ANYSIZE_ARRAY]; ^ 1 warning generated. ---- I omitted same warnings repeated many times. -- 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 23

[Bug 35207] New: Rendering issues in Outlast
by wine-bugs＠winehq.org 27 Feb '19

27 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=35207 Bug ID: 35207 Summary: Rendering issues in Outlast Product: Wine Version: 1.7.9 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: minor Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: stefan(a)codeweavers.com Classification: Unclassified Regression SHA1: 667f4225b5cc25c5e4f2f725d55a7c011e12c388 Created attachment 46958 --> http://bugs.winehq.org/attachment.cgi?id=46958 terminal output In certain areas like the opening scene some of the textures are missing (replaced by empty white rectangles). The problem exists when effects quality in the video options menu set anything but <very low>. The game uses Unreal Engine 3, no demo has been released. Installing native d3dx9 libraries doesn't solve the problem, but 'winetricks glsl-disable' is a workaround. The problem is present since 667f4225b5cc25c5e4f2f725d55a7c011e12c388 is the first bad commit commit 667f4225b5cc25c5e4f2f725d55a7c011e12c388 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Apr 2 14:54:01 2013 +0200 wined3d: Put local constants into the shader code again. This is essentially a revert of cd7825c89374fb9dd4c20aef2dbfd258713efe6a, with proper precision. :040000 040000 f34c4237fad97c7435396d2fe4644e6a4dd94046 a4cf4d8af7ce2b467dff61ad7e5825884c8fcb36 M dlls Let me know if you need further tests or debug logs. Fedora 19 Nvidia binary drivers 325.15 -- 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 38

[Bug 44395] New: Nvidia 384.111 page fault on write access to 0x7c002fd4 in 32-bit code Beyond Good and Evil (others?)
by wine-bugs＠winehq.org 25 Feb '19

25 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=44395 Bug ID: 44395 Summary: Nvidia 384.111 page fault on write access to 0x7c002fd4 in 32-bit code Beyond Good and Evil (others?) Product: Wine Version: 3.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: noabody(a)yahoo.com Distribution: --- Created attachment 60313 --> https://bugs.winehq.org/attachment.cgi?id=60313 Wine 3.0rc6 Geforce GT620 AMD 9950BE Beyond Good and Evil 32-bit prefix Unhandled exception: page fault on write access to 0x7c002fd4 in 32-bit code. Reproducible on multiple CPU/GPU architectures using Nvidia 384.111 Proprietary drivers. No crash with Nouveau on same hardware. Logs naming convention e.g.: w3rc6_gtx1060m_i7-7700hq_bgeubi32 Wine version_gpu_cpu_game/provider/wine prefix Wine 3.0rc6 on GeForce GTX 1060 mobile, Intel i7-7700hq, Beyond Good and Evil from Ubisoft, 32 bit wine prefix. Tested on Wine Stable 3.0, Wine Devel 3.0rc6 from WineHQ Ubuntu Artful for 17.10 64-bit, with clean wine prefix (both 32 and 64 bit) on four computers. Computers using open-source Nouveau (default) work fine. -- 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 72

[Bug 43393] New: Eagle 8 crash on startup
by wine-bugs＠winehq.org 24 Feb '19

24 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=43393 Bug ID: 43393 Summary: Eagle 8 crash on startup Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hildogjr(a)gmail.com Distribution: --- Eagle 8.2.2 by Auto desk (found in https://www.autodesk.com/products/eagle/free-download) crash on startup with the error: "The programa eagle.exe has encoutered a serious problem and needs to close. We are sorry for the inconvenience. This can be cause by a problem in the program or a deficiency in Wine. You may want to check the Application Database for tips about running this application." The Wine log is: fixme:vcruntime:__telemetry_main_invoke_trigger (0x67000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x180000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x65000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x64000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x240000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x61000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x66000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x2a0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x39d0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x3cd0000) err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:vcruntime:__telemetry_main_invoke_trigger (0x2d0000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x3d10000) fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4390000) fixme:win:EnumDisplayDevicesW ((null),0,0x23eb10,0x00000000), stub! fixme:wgl:X11DRV_wglGetPixelFormatAttribivARB unsupported 2008 WGL Attribute fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4510000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x44f0000) fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:vcruntime:__telemetry_main_invoke_trigger (0x4670000) fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0xf9f630, 0x34d97a0, 0x35ada48) stub. fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1. fixme:dwrite:get_name_record_codepage encoding 20 not handled, platform 1. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_codepage encoding 10 not handled, platform 3. fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455 fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f470, (nil) 0x23f4a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f470 (nil) 0x23f4a8) returning a dummy value (current locale) fixme:nls:GetThreadPreferredUILanguages 00000038, 0x23f470, 0x4051f90 0x23f4a8 fixme:nls:get_dummy_preferred_ui_language (0x38 0x23f470 0x4051f90 0x23f4a8) returning a dummy value (current locale) fixme:winsock:WSALookupServiceBeginW (0x23f070 0x00000ff0 0x23f068) Stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x23f370, overlapped 0x4053040): stub fixme:msvcrt:MSVCRT__set_FMA3_enable (0) stub fixme:win:RegisterDeviceNotificationW (hwnd=0x10074, filter=0x23f310,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterDeviceNotificationW (hwnd=0x10074, filter=0x23f310,flags=0x00000000) returns a fake device notification handle! fixme:win:EnumDisplayDevicesW ((null),0,0x23ebe0,0x00000000), stub! fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:ntdll:EtwRegisterTraceGuidsW (0xfcf3c0, 0x35ae7c8, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x34d9838, (null), (null), 0x35ae7e0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} fixme:file:SetFileCompletionNotificationModes 0x240 1 - stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aad3e0 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aace60 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x7aacfa0 1 C) semi-stub [0719/123943:FATAL:raw_channel_win.cc(589)] Check failed: g_vista_or_higher_functions.Get().SetFileCompletionNotificationModes( handle_.get().handle, FILE_SKIP_COMPLETION_PORT_ON_SUCCESS). wine: Unhandled exception 0x80000003 in thread 3f at address 0xfc03aa (thread 003f), starting debugger... fixme:vcruntime:__telemetry_main_invoke_trigger (0x67000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x64000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x66000000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x540000) fixme:vcruntime:__telemetry_main_invoke_trigger (0x240000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb30000) fixme:vcruntime:__telemetry_main_invoke_trigger (0xb60000) err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:vcruntime:__telemetry_main_invoke_trigger (0x180000000) fixme:vcruntime:__telemetry_main_invoke_trigger ((nil)) fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x180ccf630, 0x1832097a0, 0x1832dda48) stub. fixme:ntdll:EtwRegisterTraceGuidsW (0x180cff3c0, 0x1832de7c8, {3dada31d-19ef-4dc1-b345-037927193422}, 1, 0x183209838, (null), (null), 0x1832de7e0): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {00000000-0000-0000-0000-000000000000} fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:gdi:GdiInitializeLanguagePack stub fixme:msvcrt:MSVCRT__set_FMA3_enable (0) stub -- 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 30123] New: Mouse pointer is confined in a box lesser than the full screen
by wine-bugs＠winehq.org 23 Feb '19

23 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=30123 Bug #: 30123 Summary: Mouse pointer is confined in a box lesser than the full screen Product: Wine Version: 1.4-rc4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: kol(a)MV8660.spb.edu Classification: Unclassified Running TES5:Skyrim on the old system without Xinput2 support and on the modern Fedora 16 (but not on Ubuntu) under Wine 1.3.21 or later versions exhibits the "inertial mouse" bug described in http://appdb.winehq.org/objectManager.php?sClass=version&iId=24749 : after changing the direction of mouse movement the look continues to move in the old direction for some time. Since Wine 1.4-rc1 the old "inertial mouse" bug goes away but it is replaced by the new "clip" bug. The old bug appeared to be caused by the next strings in the dinput_mouse_hook() function in "dlls/dinput/mouse.c": if (This->clipped) pt = This->mapped_center; else GetCursorPos(&pt); which have been changed to GetCursorPos(&pt); in Wine 1.4-rc1. With new versions of Wine the mouse pointer is confined to some box lesser than the full screen. The behaviour of mouse depends on the "HKCU\Software\Wine\X11 Driver\GrabPointer" key. When it is set to "Y", the pointer is strictly confined to a box in game and in menus, when the key is set to "N", the pointer moves free in menus but mouse look in game is free within some limits and becomes very slow beyond these limits. It is similar to Bug#6971 but setting "MouseWarpOverride" to "force" does not change the mouse movement. I experimentally found a simple "patch" to workaround: in the function warp_check() in "dlls/dinput/mouse.c" file the last operator "This->clipped = ..." has to be commented out and "This->clipped = FALSE;" has to be inserted in place of. I do not know how it work but it makes the mouse look correct in Skyrim on my Fedora 10 system and, as far as I can see, does not break other games at least in fullscreen mode. -- 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 28

[Bug 43121] New: Game crashes during DLL load if sound is enabled
by wine-bugs＠winehq.org 23 Feb '19

23 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=43121 Bug ID: 43121 Summary: Game crashes during DLL load if sound is enabled Product: Wine Version: 2.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zaplo00(a)mailfence.com Distribution: --- Created attachment 58325 --> https://bugs.winehq.org/attachment.cgi?id=58325 Logs and winedump of DLL I have a game that uses DirectSound. It tries to load a DLL on new game and it succeeds if sound=disabled but with alsa or pulse program crashes in loader.c:tls_alloc_slot. The problem is that the .reloc information in DLL is corrupt. There are multiple entries for the same page, so what wine does is to "relocate twice". Game works with sound using a modified DLL where section size is changed to remove duplicates. Windows 7 and Windows 8.1 both work with original DLL and don't need compatibility mode. Attached are logs with and without sound and winedump output. -- 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

[Bug 42488] New: Accordance main window contents does not display well
by wine-bugs＠winehq.org 23 Feb '19

23 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=42488 Bug ID: 42488 Summary: Accordance main window contents does not display well Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bronsonmathews(a)gmail.com Distribution: --- Created attachment 57354 --> https://bugs.winehq.org/attachment.cgi?id=57354 screenshot See attached screenshot, you can see in this image the contents of the main window is incomplete. It flickers around as i move the mouse around and click and drag making the application unusable. Original bug is here: https://bugs.winehq.org/show_bug.cgi?id=42466 -- 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 43374] New: valgrind shows an invalid read in dlls/mshtml/tests/ script.c
by wine-bugs＠winehq.org 21 Feb '19

21 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=43374 Bug ID: 43374 Summary: valgrind shows an invalid read in dlls/mshtml/tests/script.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- ==28896== Invalid read of size 2 ==28896== at 0x5678C6D: DispCallFunc (typelib.c:6674) ==28896== by 0x680D479: invoke_builtin_function (dispex.c:1123) ==28896== by 0x680D763: function_invoke (dispex.c:1174) ==28896== by 0x680DA11: invoke_builtin_prop (dispex.c:1242) ==28896== by 0x680E964: DispatchEx_InvokeEx (dispex.c:1533) ==28896== by 0x16AC9205: IDispatchEx_InvokeEx (dispex.h:318) ==28896== by 0x16AC9205: disp_call (???:0) ==28896== by 0x16ACC7DF: exprval_call (engine.c:328) ==28896== by 0x16ACF402: interp_call_member (engine.c:1213) ==28896== by 0x16AD482D: enter_bytecode (engine.c:2787) ==28896== by 0x16AD5533: exec_source (engine.c:3040) ==28896== by 0x16AD7CF0: invoke_source (function.c:257) ==28896== by 0x16AD8152: Function_invoke (function.c:350) ==28896== by 0x16AC69A2: invoke_prop_func (dispex.c:383) ==28896== by 0x16AC7C70: DispatchEx_InvokeEx (dispex.c:684) ==28896== by 0x6856620: IDispatchEx_InvokeEx (dispex.h:318) ==28896== by 0x6856620: call_disp_func (???:0) ==28896== by 0x6856A51: call_event_handlers (htmlevent.c:961) ==28896== by 0x685748B: fire_event_obj (htmlevent.c:1095) ==28896== by 0x6857AC4: fire_event (htmlevent.c:1204) ==28896== by 0x68CD65F: handle_load (nsevents.c:282) ==28896== by 0x6B18A8A8: ??? ==28896== Address 0x7869d20 is 0 bytes after a recently re-allocated block of size 0 alloc'd ==28896== at 0x7BC51061: notify_alloc (heap.c:254) ==28896== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==28896== by 0x6809E6F: heap_alloc (mshtml_private.h:1168) ==28896== by 0x680A6FF: add_func_info (dispex.c:277) ==28896== by 0x680ABD4: process_interface (dispex.c:354) ==28896== by 0x680AEE5: preprocess_dispex_data (dispex.c:419) ==28896== by 0x680F3CA: init_dispex_with_compat_mode (dispex.c:1776) ==28896== by 0x68E753F: init_dispex (mshtml_private.h:334) ==28896== by 0x68EA736: OmNavigator_Create (omnavigator.c:1088) ==28896== by 0x68AA791: HTMLWindow2_get_navigator (htmlwindow.c:920) ==28896== by 0x4A9EAFF: IHTMLWindow2_get_navigator (mshtml.h:38483) ==28896== by 0x4A9EAFF: test_script_run (???:0) ==28896== by 0x4A9F739: ActiveScriptParse_ParseScriptText (script.c:2472) ==28896== by 0x68FEBE6: IActiveScriptParse32_ParseScriptText (activscp.h:1126) ==28896== by 0x68FEBE6: parse_elem_text (???:0) ==28896== by 0x68FF823: parse_inline_script (script.c:1103) ==28896== by 0x68FFA7A: parse_script_elem (script.c:1142) ==28896== by 0x69001FF: doc_insert_script (script.c:1285) ==28896== by 0x68B9905: run_insert_script (mutation.c:349) ==28896== by 0x68BA1B0: nsRunnable_Run (mutation.c:532) ==28896== by 0x6A83E0A0: ??? ==28896== by 0x68BAEB0: nsDocumentObserver_AttemptToExecuteScript (mutation.c:817) ==28896== -- 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 1

[Bug 42667] New: Uplay crashes after close
by wine-bugs＠winehq.org 21 Feb '19

21 Feb '19

https://bugs.winehq.org/show_bug.cgi?id=42667 Bug ID: 42667 Summary: Uplay crashes after close Product: Wine Version: 2.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: olze(a)trustserv.de Distribution: --- Created attachment 57618 --> https://bugs.winehq.org/attachment.cgi?id=57618 The error output I installed uplay and started it. Then i installed Tom Clancys Ghost Recon Wildlands. I closed uplay. Now i can not start it anymore. I always get an error saying uplay crashed and a crash dump will be generated. Could be related to https://bugs.winehq.org/show_bug.cgi?id=39870 -- 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 11070] New: Unimplemented function CRYPT32.dll.PFXIsPFXBlob
by wine-bugs＠winehq.org 19 Feb '19

19 Feb '19

http://bugs.winehq.org/show_bug.cgi?id=11070 Summary: Unimplemented function CRYPT32.dll.PFXIsPFXBlob Product: Wine Version: 0.9.52. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: mhs(a)hp.com CC: mhs(a)hp.com Created an attachment (id=10088) --> (http://bugs.winehq.org/attachment.cgi?id=10088) Dependency Walker Load List (Wine Builtin) The importpfx tool <http://home.fnal.gov/~jklemenc/importpfx.html> will run under ~/.ies4linux , however fails with builtin ntdll and crypt32 under ~/.wine. Importpfx would be very useful because it allows PKCS12 certificates to be imported to the Certificate Store without need for IE's import/export frontend. Note: Filing this bug under crypt32, though it might better belong to ntdll. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 57

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 February 2018