January 2019 - Wine-Bugs - list.winehq.org

[Bug 39814] New: choppy pulseaudio after ->Remove legacy pulseaudio/alsa latency workaround (closes: #807403).
by wine-bugs＠winehq.org Jan. 26, 2019

Jan. 26, 2019

https://bugs.winehq.org/show_bug.cgi?id=39814 Bug ID: 39814 Summary: choppy pulseaudio after ->Remove legacy pulseaudio/alsa latency workaround (closes: #807403). Product: Wine Version: 1.8-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nexxxxen(a)gmail.com Distribution: --- After 1.8-rc4 on debian testing my REAPER DAW sound is choppy and noisy. I use it for long time (years), and had no problems until this workaround (#807403) they removed. Thanks, and sorry for my bad english. :( -- 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

[Bug 40247] New: Wine returns bad MAC address for loopback interface, fails to run licensed programs.
by wine-bugs＠winehq.org Jan. 26, 2019

Jan. 26, 2019

https://bugs.winehq.org/show_bug.cgi?id=40247 Bug ID: 40247 Summary: Wine returns bad MAC address for loopback interface, fails to run licensed programs. Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: netcfgx Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com There are some (poorly written) programs that base their licensing off the system's MAC address. Unfortunately, some of them are necessary for engineering work. These are old programs with brittle source but valid licenses that cannot be run because Wine cannot ever tell them what Windows would tell them. Wine always returns a MAC address of "00:00:00:00:00:00" to these programs. I assume that's because the loopback interface is first in `ifconfig`, and thus is enumerated first to Windows programs by Wine, and has no MAC address. In most cases, programs like these choose the MAC address of the first "network adapter" that would have been printed by `ipconfig /all`. Again, in Wine, the first such adapter printed is the loopback interface. This problem can't be solved by normal MAC address spoofing techniques, because the loopback interface simply doesn't have a MAC address according to the host. And Windows tricks to change the MAC address, like modifying the "NetworkAddress" key of "HKLM\System\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\XXXX", don't seem to have any effect in Wine. Particularly with respect to affecting the loopback interface. There needs to be a Wine option, possibly a key somewhere in "HKLM\Software\Wine", to override (at the very least) the loopback interface's apparent MAC address, so that these programs can work. -- 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 46358] New: CUDA acceleration not detected by Radiant Viewer ( regression)
by wine-bugs＠winehq.org Jan. 26, 2019

Jan. 26, 2019

https://bugs.winehq.org/show_bug.cgi?id=46358 Bug ID: 46358 Summary: CUDA acceleration not detected by Radiant Viewer (regression) Product: Wine Version: 4.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: nvcuda Assignee: wine-bugs(a)winehq.org Reporter: bozkar(a)gmail.com Distribution: --- CUDA rendered is not available as an option in RadiAnt DICOM Viewer build 4.9.12.21058 BETA (64 bit) - used to work with 4.6.5.18450 and 3.13-staging. What debug could I provide? -- 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 2

[Bug 46515] New: Divide by zero error Zoombinis Mountain Rescue
by wine-bugs＠winehq.org Jan. 26, 2019

Jan. 26, 2019

https://bugs.winehq.org/show_bug.cgi?id=46515 Bug ID: 46515 Summary: Divide by zero error Zoombinis Mountain Rescue Product: Wine Version: 4.0 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bec.cass(a)hotmail.com Created attachment 63371 --> https://bugs.winehq.org/attachment.cgi?id=63371 Zoombinis Mountain Rescue Backtrace Hi! I was wondering if anyone can help with a bug I'm having. I've managed to install and play and old game from my childhood (Zoombinis Mountain Rescue) on my Mac. I installed it from an iso file I downloaded and plays perfectly up to a point (Beetle Bug Alley) at which point it freezes and I get the error (attached). It occurs even when accessing the level directly in practice mode as well as when progressing sequentially in normal game mode. I've mostly been figuring things out through lots of googling and manual and forum reading (and hoping I don't mess up my computer!) so I'm definitely a complete beginner in terms of understanding wine! I can't figure this one out and would love some help if anyone knows the answer to this problem! Thanks :) -- 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 26807] New: MS Powerpoint 2007 does not start in 1.3.18
by wine-bugs＠winehq.org Jan. 25, 2019

Jan. 25, 2019

http://bugs.winehq.org/show_bug.cgi?id=26807 Summary: MS Powerpoint 2007 does not start in 1.3.18 Product: Wine Version: 1.3.18 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bozkar(a)gmail.com 1. Installation MS Office with SP1/SP2 in updates/ → successful 2. Word and Excel runs correctly 3. PowerPoint crashed @startup. In XP mode terminates with no error In Vista mode asks whether to send debug info to MS. As far as i remember it was running in 1.3.17 → regression. -- 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 46506] New: Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL?
by wine-bugs＠winehq.org Jan. 25, 2019

Jan. 25, 2019

https://bugs.winehq.org/show_bug.cgi?id=46506 Bug ID: 46506 Summary: Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL? Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zefkerrigan(a)gmail.com Distribution: --- Hi! Thank you very much for you great work! Why are you still not using Vulkan for WineD3D for D3D9, D3D10, D3D11? Why are you still using OpenGL? The dizzying success of the DXVK project proved that using Vulkan provides excellent performance in D3D10 and D3D11 games. There is a huge amount of evidence that when using the Wine+DXVK bundle, usually only about ~10% performance loss is obtained relative to launching the same Windows game natively on Windows. But if you run the same game using the usual WineD3D, then the loss of performance is usually about ~80%, and this in turn deprives we of any reason to launch games using WineD3D. But DXVK has a free ZLIB license and open source code. Why not replace the WineD3D with the DXVK inside of the Wine code? Or at least it might be worth using the default DXVK in Wine, with the option of optionally choosing WineD3D for a GPUs without Vulkan support? Or perhaps DXVK would be used by default in Wine, and if some user couldn’t use Vulkan, would Wine automatically switch to WineD3D mode? I believe that the benefits of high performance, which gives the use of DXVK and Vulkan are very important. Please, see here: https://github.com/doitsujin/dxvk Thank you! -- 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 46464] New: Strong hold 2 needs a native dll fallback mechanism
by wine-bugs＠winehq.org Jan. 22, 2019

Jan. 22, 2019

https://bugs.winehq.org/show_bug.cgi?id=46464 Bug ID: 46464 Summary: Strong hold 2 needs a native dll fallback mechanism Product: Wine Version: 4.0-rc6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: zzhang(a)codeweavers.com Distribution: --- Created attachment 63272 --> https://bugs.winehq.org/attachment.cgi?id=63272 patch See https://github.com/ValveSoftware/Proton/issues/506 for details. Strong hold 2 doesn't run. For it to run, use the following steps: $ STEAM_COMPAT_DATA_PATH=~/.steam/steam/steamapps/compatdata/40960 ~/.steam/steam/compatibilitytools.d/proton/proton run ~/.steam/steam/steamapps/compatdata/40960/pfx/drive_c/windows/system32/winecfg.exe And set msvcr100.dll and msvcp100.dll to builtin. And FFLauncher.exe is a .NET application. Since proton doesn't have mono support yet. We need to rename rename Stronghold2.exe to FFLaucher.exe, then it will launch. $ cd ~/.steam/steam/steamapps/common/Stronghold\ 2/ $ file msvcp100.dll msvcp100.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows $ file FFLauncher.exe FFLauncher.exe: PE32 executable (GUI) Intel 80386, for MS Windows So the reason that the game doesn't run on proton is that it is bundled with dlls of wrong architecture in its application folder. On Windows, there is a dll architecture check[1] when loading dlls, whereas wine currently loads the first found. [1] Windows Internals # Known Dll Redirection: https://books.google.com/books?id=y83LDgAAQBAJ&pg=PT282&dq=dll+of+wrong+arc… -- 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 4

[Bug 5402] Multiple MFC-based apps crash during non-modal child dialog control creation with active window being zero (Canon PhotoStitch 3.1.13, Flexible Renamer v8.4)
by wine-bugs＠winehq.org Jan. 22, 2019

Jan. 22, 2019

https://bugs.winehq.org/show_bug.cgi?id=5402 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.2.0 |3.0.x -- 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 0

[Bug 46491] New: "harddisk_ioctl Unsupported ioctl 2d0c00 (and 4d004)" breaks Olympus camera firmware updater
by wine-bugs＠winehq.org Jan. 21, 2019

Jan. 21, 2019

https://bugs.winehq.org/show_bug.cgi?id=46491 Bug ID: 46491 Summary: "harddisk_ioctl Unsupported ioctl 2d0c00 (and 4d004)" breaks Olympus camera firmware updater Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: bero(a)lindev.ch Distribution: --- The Olympus camera firmware updater (http://support.olympus-imaging.com/ou1download/) installs correctly, but fails to detect the camera. The camera is supposed to be connected in USB storage mode (that works overall, I see the camera as drive f: in "wine explorer.exe"); chances are the firmware updater would work if only it could identify the camera correctly instead of seeing it as some generic storage device. While probing for the camera, wine says 0019:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d0c00 (device=2d access=0 func=300 method=0) 0019:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d004 (device=4 access=3 func=401 method=0) I don't know anything about Windows IOCTLs, but I suppose those read a hardware identifier? -- 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 0

[Bug 46486] New: Problem with mouse input when using two monitors
by wine-bugs＠winehq.org Jan. 20, 2019

Jan. 20, 2019

https://bugs.winehq.org/show_bug.cgi?id=46486 Bug ID: 46486 Summary: Problem with mouse input when using two monitors Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bedp4488(a)protonmail.com Distribution: --- I'm using two monitors and have problem with mouse input. Monitor on my right is the main monitor. This picture explain when mouse input doesn't work in wine : https://imgur.com/a/hNAqvvS -- 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 4