June 2018 - Wine-Bugs - list.winehq.org

[Bug 45327] New: I have been playing League of Legends fine until I tried to open it tonight and it keeps giving me fatal and critical errors. League of legends 8.12

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45327 Bug ID: 45327 Summary: I have been playing League of Legends fine until I tried to open it tonight and it keeps giving me fatal and critical errors. League of legends 8.12 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: brandon_bunning1(a)mymail.eku.edu Distribution: --- Created attachment 61615 --> https://bugs.winehq.org/attachment.cgi?id=61615 Error report? I have been playing League of Legends fine until I tried to open it tonight and it keeps giving me fatal and critical errors. I have tried different wine versions, i have tried uninstalling and reinstalling EVERYTHING:playonlinux, league, wine. -- 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.

June 15, 2018

[Bug 44997] Installation support is broken for ElsterFormular 19.3.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44997 --- Comment #2 from Markus Elfring <Markus.Elfring(a)web.de> --- (In reply to Fabian Maurer from comment #1) Another installation attempt seems to work better for the application “ElsterFormular 19.5 (2018-06-14)” together with the software “Wine 3.10-820.1”. Corresponding log messages contain information for further software development considerations, don't they? elfring(a)Sonne:~/geladen/Freeware> wine start ElsterFormularPrivat.msi 0009:fixme:exec:SHELL_execute flags ignored: 0x00000100 elfring(a)Sonne:~/geladen/Freeware> 0038:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0039:fixme:msi:AutomationObject_GetIDsOfNames Unknown member L"actionData", clsid {000c109e-0000-0000-c000-000000000046} 0039:fixme:msi:AutomationObject_GetIDsOfNames Unknown member L"objFSO", clsid {000c109e-0000-0000-c000-000000000046} 0038:err:richedit:ReadColorTbl malformed entry … 0038:err:richedit:ReadStyleSheet skipping optional destination 0056:fixme:msi:AutomationObject_GetIDsOfNames Unknown member L"appdir", clsid {000c109e-0000-0000-c000-000000000046} 0056:fixme:vbscript:Global_InStr unsupported compare argument 0x5bfad8 {VT_I2: 1} 0056:fixme:vbscript:show_msgbox No IActiveScriptSiteWindow 0056:fixme:vbscript:Global_Replace 006c:fixme:advapi:CreateProcessAsUserW 0x64 L"C:\\windows\\system32\\cmd.exe" L"/C \"C:\\users\\elfring\\Temp\\{F887D266-E5F8-45E9-B635-6D61B30C437B}.bat\"" (nil) (nil) 1 0x08000000 (nil) (null) 0x45f3e0 0x45f42c - semi-stub … 0097:fixme:dbghelp:i386_stack_walk new PC=1bd120 different from Eip=1101c8 009b:fixme:sc:wmain command not supported 0038:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5) … 00a7:fixme:msvcrt:type_info_name_internal_method type_info_node parameter ignored 00a7:fixme:file:FindFirstFileExW flags not implemented 0x00000002 … The menu is unusable in the main application at the moment. Which other system functionality is still missing for the evolving run time environment? -- 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.

June 15, 2018

[Bug 45320] cmd creates an environment variable with an empty name

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45320 --- Comment #3 from Dima Ryazanov <dima(a)gmail.com> --- Jason: wow, you're correct. I ran Example 3 from https://msdn.microsoft.com/en-us/library/windows/desktop/ms682009(v=vs.85).… ; it uses GetEnvironmentStrings to print out environment variables. On Wine, it produces exactly the same output as my testcase. On Windows, however, I see three extra variables: =::=::\ =C:=C:\Users\dima\Documents =ExitCode=00000000 So looks like they're just hidden from the POSIX APIs? -- 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.

June 15, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #15 from Hans Leidekker <hans(a)meelstraat.net> --- (In reply to Piotr Caban from comment #9) > I've done much more testing and I think that the correct way is to do a > "major upgrade" on every mono update. I think so because of the way how > update needs to be installed by the user: > - major upgrade - it's enough to click on the msi file to install the > update, depending on msi file content old version will be preserved or > removed > - minor upgrade - has identical user deployment methods as small update > - small update - needs to be installed as patch or complete reinstall, if > you decide to do the minor upgrade new mono versions will need to be > installed in following way: > msiexec /I wine-mono-4.7.2.msi REINSTALL=ALL REINSTALLMODE=vomus Most users don't handle these updates directly. I don't think it's too much to ask users who want to test an update to type a few extra characters. We could add an exe wrapper if we really needed a single click installer. > There are also many restrictions regarding what can be done in small and > minor upgrade, I don't think you want to pay attention to that on every > release. Don't know about 'many', but you can't modify the feature tree. This hasn't been an issue so far, wine-mono has had a single feature from the beginning. Note that you can still add features and components. A major upgrade defines a new product, which means that the old product will be removed first. So even if there's a small number of files that have changed (a typical update), all of them will be deleted and rewritten. -- 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.

June 15, 2018

[Bug 45326] New: unimplemented function ntoskrnl.exe.__C_specific_handler, aborting

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45326 Bug ID: 45326 Summary: unimplemented function ntoskrnl.exe.__C_specific_handler, aborting Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stevedonato(a)gmail.com Distribution: --- wine: Call from 0x7bc5b99c to unimplemented function ntoskrnl.exe.__C_specific_handler, aborting wine: Call from 0x7bc5b99c to unimplemented function ntoskrnl.exe.__C_specific_handler, aborting wine: Call from 0x7bc5b99c to unimplemented function ntoskrnl.exe.__C_specific_handler, aborting The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. -- 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.

June 15, 2018

[Bug 45310] Unimplemented function KERNEL32.dll.MoveFileTransactedW

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45310 --- Comment #1 from Alex <vicenzi.alexandre(a)gmail.com> --- I was browsing Wine source code and in fact, MoveFileTransacted functions are not implemented, actually, nothing related with Transactional NTFS is implemented. The functions CreateTransaction, CommitTransaction, RollbackTransaction are implemented, but they don't do what it should be done. If these functions are dummy, I guess MoveFileTransacted could also be dummy. Dummy in this scenario should be that if we call MoveFileTransacted it could call MoveFileWithProgress. MoveFileTransacted has almost the same signature as MoveFileWithProgress, the only missing item is the transaction handler. As MSDN says (https://msdn.microsoft.com/en-us/library/windows/desktop/aa363764(v=vs.85).…) Microsoft strongly recommends developers utilize alternative means to achieve your application’s needs. Many scenarios that TxF was developed for can be achieved through simpler and more readily available techniques. Furthermore, TxF may not be available in future versions of Microsoft Windows. If this solution could be a temporary permanent fix, I would be happy to submit a patch. -- 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.

June 14, 2018

[Bug 45311] Skyrim Special Edition: ambient sounds do not attenuate with distance

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45311 --- Comment #6 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Olivier F. R. Dierick from comment #5) > The workaround is to set xaudio2_7 to "native, builtin". > Does it work with Skyrim? I mean without installing xact with winetricks. -- 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.

June 14, 2018

[Bug 45311] Skyrim Special Edition: ambient sounds do not attenuate with distance

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45311 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- I don't have Skyrim but I'm experiencing the same issue with at least two other games: Orion Prelude and Far Cry 3. Environment sounds (river/water, wind, fire, etc.) are full volume and cuts in and out when walking towards/away from the source. Normally, the sound volume should decrease/increase smoothly with distance. commit b747d6f6ccdf1699a9242a570d681fa246de592e is the culprit. It makes xaudio2 default to builtin. The workaround is to set xaudio2_7 to "native, builtin". Does it work with Skyrim? -- 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.

June 14, 2018

[Bug 45109] Implement debugging 32-bit processes using 64-bit winedbg

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45109 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |5caaba7e3e8e283f11bb9ce79cb | |68c4bca2c44f3 Status|NEW |RESOLVED --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- This is functional as of 5caaba7e3e8e283f11bb9ce79cb68c4bca2c44f3. -- 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.

June 14, 2018

[Bug 41403] Ri-li 2.0.1: No window content shown (just title bar)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41403 --- Comment #13 from Tobias (:Tobbi) Markus <tobbi.bugs(a)googlemail.com> --- Just a small update on this: I get a black background with Ri-li. In the console, I get this: 008e:err:d3d:wined3d_check_gl_call >>>>>>> GL_INVALID_ENUM (0x500) from extension detection @ ../../../wine/dlls/wined3d/directx.c / 4291. 008e:fixme:win:EnumDisplayDevicesW ((null),0,0x6ff578,0x00000000), stub! 008e:err:d3d:wined3d_check_gl_call >>>>>>> GL_INVALID_ENUM (0x500) from extension detection @ ../../../wine/dlls/wined3d/directx.c / 4291. 008e:fixme:win:EnumDisplayDevicesW ((null),0,0x6ff5d8,0x00000000), 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.

June 14, 2018