March 2018 - Wine-bugs - list.winehq.org

[Bug 29628] New: Sylenth1: crashes at startup
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=29628 Bug #: 29628 Summary: Sylenth1: crashes at startup Product: Wine Version: 1.3.37 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: realnc(a)gmail.com Classification: Unclassified Created attachment 38384 --> http://bugs.winehq.org/attachment.cgi?id=38384 Wine crash log When trying to load the Sylenth1 VSTi in any kind of host, Wine crashes with a stack dump and backtrace. You can download Sylenth1 from: http://www.lennardigital.com/modules/downloads (5MB, no sign up required.) This happens in all hosts I tried, native Linux ones (LMMS, QTractor) as well as Windows ones running in Wine (FL Studio, Reaper.) The easiest and fastest way to reproduce the error is: * Install LMMS (should be available in all distros) * Install Sylenth1 with Wine * Run LMMS * Insert the "VeSTige" instrument into the song editor. You do that by clicking on the "Instruments" icon in the vertical bar to the left and drag&dropping the "VeSTige" item into the song editor. * In the VeSTige GUI (click the newly added VeSTige instrument to bring up the GUI), click the folder icon, select the Sylenth1Demo.dll and click OK. At the moment the DLL runs, Wine crashes. I'm using Wine 1.3.37 on Gentoo Linux AMD64. -- 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 30538] New: Touhou 11, 12, and 13 are incredibly slow with Intel, Nouveau, and Nvidia drivers
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=30538 Bug #: 30538 Summary: Touhou 11, 12, and 13 are incredibly slow with Intel, Nouveau, and Nvidia drivers Product: Wine Version: 1.5.3 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: erappleman(a)gmail.com Classification: Unclassified No matter which libraries I use (i965 Mesa, Nouveau Gallium, or Nvidia) on my Optimus machine, I can't get the games to exceed 20fps. Linux kingfisher 3.3.0-3.dmz.1-liquorix-amd64 #1 ZEN SMP PREEMPT Mon Apr 23 22:15:14 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux My hardware is Intel i7-2630QM (HD3000) and a GT 555M. Yes, I know how to use the Nvidia GPU properly. X and Mesa are latest git versions. eric(a)kingfisher:~/touhou/TH11 ~ Subterranean Animism$ LIBGL_DEBUG=verbose wine th11e libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/tls/i965_dri.so libGL: OpenDriver: trying /usr/lib/i386-linux-gnu/dri/i965_dri.so fixme:win:EnumDisplayDevicesW ((null),0,0x32f800,0x00000000), stub! fixme:font:WineEngAddFontResourceEx Ignoring flags 10 fixme:d3d:wined3d_swapchain_get_raster_status swapchain 0x185380, raster_status 0x32fc80 semi-stub! -- 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 44

[Bug 38623] New: Bogus values in GDI+: Image:GetPropertySize
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=38623 Bug ID: 38623 Summary: Bogus values in GDI+: Image:GetPropertySize Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mathieu.malaterre(a)gmail.com Distribution: --- Created attachment 51529 --> https://bugs.winehq.org/attachment.cgi?id=51529 source code One cannot compile and run the following example on wine 1.6.2: https://msdn.microsoft.com/en-us/library/ms535372(v=vs.85).aspx See attached code. To reduce file size, I've reused the PNG image from bug id 38622. Download it from: https://bugs.winehq.org/attachment.cgi?id=51528 -- 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 44843] New: Cursor icons when resizing "wine windows" aren' t the same as the system theme
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=44843 Bug ID: 44843 Summary: Cursor icons when resizing "wine windows" aren't the same as the system theme Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: katsunori.kumatani(a)gmail.com Distribution: --- This is a somewhat old regression that I noticed now when I updated wine after a while. When you move the cursor to resize a "wine window" (windows decorated by wine, not the WM, usually windows within a wine app), it now uses a hardcoded wine cursor instead of the system "resize" cursor icon. (I posted this on forum first; I am talking about the "resizing arrows" that show up when you move to the edge or corner of a resize-able window) I did a regression test, and it turns out this commit 32ccc0b9e0f1536655b7fca6e68823e1bf05374a: commit 32ccc0b9e0f1536655b7fca6e68823e1bf05374a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Jul 14 12:46:45 2017 +0200 user32: New high resolution cursors generated from SVG. Based on a cursor set published by Ludvig Hummel under the X11 license. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 bc61cafa0d7f95b519fb91875fa3085ca1ffffe4 f9fc1db316529e3d61a9abd89e82babd7e1061c7 M dlls forces wine's own cursor icons to be used in those cases. But I want the cursor to look like the normal (system) cursor again. I was told to file a bug report at least for enhancement request to disable it and make it back, somehow, as an option perhaps? If it's not a bug, that is. I mean, an option to let wine use the normal cursor as before. Or any workarounds available? -- 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 34097] New: Mega Man Unlimited: Game works, sound is choppy and slow
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=34097 Bug #: 34097 Summary: Mega Man Unlimited: Game works, sound is choppy and slow Product: Wine Version: 1.6-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jessetalavera(a)aol.com Classification: Unclassified Created attachment 45337 --> http://bugs.winehq.org/attachment.cgi?id=45337 Terminal output for WINE So Mega Man Unlimited just came out, which is nice. http://megaphilx.com/ It runs at adequate speed on my Linux machine (Ubuntu 13.04, Samsung QX411). To my knowledge, it doesn't crash. Only problem is, the sound is slow and choppy, and is quite unbearable. -- 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 13

[Bug 38829] New: This was reported a way back, fixed, now recurs
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=38829 Bug ID: 38829 Summary: This was reported a way back, fixed, now recurs Product: Wine Version: 1.7.46 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: d_baron(a)012.net.il Distribution: --- Bug filed with Debian 790340(a)bugs.debian.org, 790340-submitter(a)bugs.debian.org Re-filed here at their request. All file menus crash out on click OK, cancel, etc. Backtrace at Debian link. -- 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 41320] New: Starcraft 2 crashes with "Unexpected Fatal Error" immediately after opening.
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=41320 Bug ID: 41320 Summary: Starcraft 2 crashes with "Unexpected Fatal Error" immediately after opening. Product: Wine Version: 1.9.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vijayronbar(a)gmail.com Distribution: --- I installed Battle.net on Ubuntu 16.04 using this link http://askubuntu.com/questions/803785/battle-net-wont-launch-after-latest-u… and installed Starcraft 2 in the Battle.net app. But when I start the game by clicking Play it crashes immediately with the message "Unexpected Fatal Error" and an ID along with it. I have checked in the settings and the game runs in 32 bit mode. Has anyone faced the same problem? Is there a fix for this? -- 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 43209] New: Doom (2016) no longer boots
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=43209 Bug ID: 43209 Summary: Doom (2016) no longer boots Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: abienz(a)gmail.com Distribution: --- Running both the openGL and Vulkan exe files, Doom no longer boots since Wine-staging v2.9 Attached is the log output from 'WINEDEBUG=+seh,+tid,+err wine .wine/drive_c/Program\ Files\ $x86$/Doom/DOOMx64vk.exe' -- 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 43605] New: Wine does not support elliptic curve cryptography
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

https://bugs.winehq.org/show_bug.cgi?id=43605 Bug ID: 43605 Summary: Wine does not support elliptic curve cryptography Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raydongf(a)gmail.com Distribution: --- Let's Encrypt and CloudFlare distribute ECC SSL certificates. If someone tries to use it or connect to an HTTPS website that uses an ECC certificate, Wine will claim that the certificate is invalid, and throw an error. If you try to view the public key directly, the dialog also claims that the certificate is invalid. This is evident if you view the properties of the CloudFlare ECC root certificate: https://support.cloudflare.com/hc/en-us/articles/218689638-What-are-the-roo… -- 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 34182] New: Empire Earth v2.0: mouse cursor only moves at high mouse movement
by wine-bugs＠winehq.org 30 Mar '18

30 Mar '18

http://bugs.winehq.org/show_bug.cgi?id=34182 Bug #: 34182 Summary: Empire Earth v2.0: mouse cursor only moves at high mouse movement Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: toxatec(a)web.de Classification: Unclassified Created attachment 45468 --> http://bugs.winehq.org/attachment.cgi?id=45468 WINEDEBUG="+dinput"; simulated mouse movement with xdotool Moving the cursor in Empire Earth v2.00.3466 is not possible unless you move the mouse very quickly. When you do, the cursor moves by only a few pixels. Generating mouse movement with xdotool [1] showed that the cursor moves by 1 "unit" for each 120 pixels the mouse moves. One "unit" seems to be more than 1 pixel and depend on in-game settings... $ xdotool mousemove_relative -- 0 119 # --> no cursor movement $ xdotool mousemove_relative -- 0 120 # --> moves cursor by 1 unit $ xdotool mousemove_relative -- 0 239 # --> moves cursor by 1 unit $ xdotool mousemove_relative -- 0 240 # --> moves cursor by 2 units About the logfile: Started the game, then in main menu: no mouse movement except 3x 119, then 3x 120 pixels downwards using xdotool, then alt-F4 Those parts look interesting but with I'm lacking the skills to figure out what's wrong or even fix it: $ bzcat dinput-120.log.bz2 | grep -B10 -A30 120 $ bzcat dinput-120.log.bz2 | grep -B10 -A30 119 I hope this is helpful.. Using native dinput, behavior is completely different and hard to describe. I'm not sure if it's relevant: The game seems to remember the amount of pixels you have moved in X or Y direction, moving the cursor by a corresponding value on every mouse event (also clicks). After moving the mouse to the right, the cursor keeps going right even when you move the mouse left. Moving the mouse in the other direction lowers that "memory", stopping the cursor eventually. You have to set "Mouse Sensitivity" to "1" in regedit, otherwise the cursor is uncontrollably fast. This is different from the issues with the Demo version or 1.00 (bug 13351), therefore I'm creating a new bug report. [1]: http://www.semicomplete.com/projects/xdotool/ -- 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 11