September 2019 - Wine-bugs - list.winehq.org

[Bug 47750] New: Linker complaining about multiple logf_finite definitions
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47750 Bug ID: 47750 Summary: Linker complaining about multiple logf_finite definitions Product: Wine Version: 4.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janarvottin(a)gmail.com Distribution: --- Created attachment 65231 --> https://bugs.winehq.org/attachment.cgi?id=65231 compilation log When compiling 4.15 with patches from staging repository linker fails to assemble libmvec_nonshared.a. Same problem aried with 4.14. Partial log attached. -- 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.

2 2

[Bug 47104] New: Cannot click anywhere on VST plugins
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47104 Bug ID: 47104 Summary: Cannot click anywhere on VST plugins Product: Wine-staging Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: paulalbertdev(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi ! Just wanted you to know that 10mins ago everything was working fine but then I upgraded the staging version of wine and, since that, when I'm using windows VSTs plugins through vst-bridge and wine, clicks on the interface are not taken into account... So I cannot use no win VST anymore. Gonna downgrade to dev version but got other problems (less disturbing) with it. Good luck for fixing the bug ! Cheers -- 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.

2 14

[Bug 40378] New: Monitor AOC I-menu not running
by wine-bugs＠winehq.org 07 Oct '19

07 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=40378 Bug ID: 40378 Summary: Monitor AOC I-menu not running Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: fatihfawaz(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 54084 --> https://bugs.winehq.org/attachment.cgi?id=54084 Program error i can't running application from AOC, I-menu becouse i have a bug, a bug i attach the file. 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.

2 5

[Bug 47835] New: `-funroll-loops` breaks wine, "wine: Unhandled page fault on write access to 0x00000000 at address ..."
by WineHQ Bugzilla 05 Oct '19

05 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47835 Bug ID: 47835 Summary: `-funroll-loops` breaks wine, "wine: Unhandled page fault on write access to 0x00000000 at address ..." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zegentzy(a)protonmail.com Distribution: --- As the name implies, compiling with `-funroll-loops` breaks wine. Every part of it, from winedbg, to wine, to wineboot. Tested against both the latest wine on git, wine 4.15, and wine 4.15. GCC 9.1.0. Arch Linux. This is `winedbg`, for example: ``` wine: created the configuration directory '/home/gentz/.wine' 000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0012:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0014:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. wine: Unhandled page fault on write access to 0x00000000 at address 00006BB2783C2DB9 (thread 0014), starting debugger... 0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 80" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on write access to 0x00000000 at address 0000634EEE5AADB9 (thread 0012), starting debugger... 0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 88" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on write access to 0x00000000 at address 000062C321ACADB9 (thread 0010), starting debugger... 0010:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 15 84" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger ^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr 0xea872929 ``` Here is `winecfg`: ``` winecfg wine: created the configuration directory '/home/gentz/.wine' 000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 000b:fixme:winediag:start_process Wine Staging 4.16 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0012:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. 0014:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. wine: Unhandled page fault on write access to 0x00000000 at address 000060CC8A44ADB9 (thread 0012), starting debugger... 0012:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 17 80" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger wine: Unhandled page fault on write access to 0x00000000 at address 00006628B5FD2DB9 (thread 0014), starting debugger... 0014:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 19 88" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger ^C0009:err:seh:raise_exception Unhandled exception code c000013a flags 0 addr 0xe16b1929 ``` I'm marking this as minor, as the workaround is trivial: just don't build with `funroll-loops`, but hopefully someone looks into it. I did some searching, and couldn't find this already reported, but feel free to close if it's a dupe, sorry! -- 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 46102] New: Wine cannot recognize Turkish keyboard layout
by wine-bugs＠winehq.org 04 Oct '19

04 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=46102 Bug ID: 46102 Summary: Wine cannot recognize Turkish keyboard layout Product: Wine Version: 3.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yurnerolinux(a)yandex.com Distribution: --- I noticed that in some games , both on plain Wine ( i'm using staging ) and both on Proton. On Fallout: New Vegas , you can't type "i" when Turkish keyboard layout selected. Game ( or Wine probably , since game doesn't know about it ) just shows it as " when you pressed "i" button. Same behaviour is also going on with Skyrim. When i set my keyboard layout to English thorugh my system , "i" starts to work again. Another example is Deus EX: Human Revolution - Director's Cut on Proton. I realized i can't open up tab menu ( tab key ) when my keyboard set to Turkish. If i set my keyboard English again , it starts to work. My keyboard layout is Turkish Q keyboard. -- 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.

2 11

[Bug 45508] New: wine staging and gallium patches
by wine-bugs＠winehq.org 03 Oct '19

03 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=45508 Bug ID: 45508 Summary: wine staging and gallium patches Product: Wine-staging Version: unspecified Hardware: x86 URL: https://github.com/sarnex/wine-d3d9-patches OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hasculdr(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello. It's possible to add this patches: https://github.com/sarnex/wine-d3d9-patches to wine-staging project? 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.

2 13

[Bug 47845] New: Bug to x86_64
by WineHQ Bugzilla 02 Oct '19

02 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47845 Bug ID: 47845 Summary: Bug to x86_64 Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haasesaah(a)gmail.com Distribution: --- My original architecture was x64 but as I like play some games in x86 I did convert with add-apt-repository ppa: architecture i386 to turn over x86_64 and after that I had trouble within ever runnig up the games at x86 architecture. Well, I thought the x86_64 architecture would support both. As x86 and x64. Sorry about my barely english typewriting. Thank you so very much. -- 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 21312] New: Sony Vegas Movie Studio Platinum 9.0b: Serious issues making video production impossible
by wine-bugs＠winehq.org 01 Oct '19

01 Oct '19

http://bugs.winehq.org/show_bug.cgi?id=21312 Summary: Sony Vegas Movie Studio Platinum 9.0b: Serious issues making video production impossible Product: Wine Version: 1.1.35 Platform: x86-64 URL: http://www.softpedia.com/get/Multimedia/Video/Video-Ed itors/Sony-Vegas-Movie-Studio-Platinum.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gaming4jc2(a)yahoo.com Created an attachment (id=25649) --> (http://bugs.winehq.org/attachment.cgi?id=25649) Numerous FixMes and some Errs... Well, I finally got it installed using winetrick's dontnet20 and wmp9 as suggested on my previous bug report for not being able to install it. It only works on Windows Vista and above compatibility modes, so the log attached was using Windows 7 which seems best. I'm not sure where to start on this bug report. Sony Vegas Movie Studio 9.0b Platinum has several serious issues, all of which we should be able to be determined from the short log attached. I'll list them below: * No plug-ins were found. (This includes the Media Generator, Transitions, and Video FX tabs making them totally unusable) This effects the majority of the application and the "Video Event FX..." window, making the program somewhat useless. * The Audio "Track FX..." and "Apply Non-Real Time Event FX..." windows are both totally unusable since nothing can be clicked in them. The audio plugins there are at least detected, just borked. * Video Preview Window doesn't show anything, and occasionally flickers a different color only when rendering. Terminal cycles a never ending "fixme:msvideo:DrawDibDraw" bug when attempting to play the movie. This also effects the "Video Event Pan/Crop..." window, making it nearly impossible to do animation effects since determining your current location in the window is simply a black screen. * All icons have a black rectangle around them (trivial and probably just a simple alpha transparency bug) Note: Keyword download can be added since Sony Vegas Movie Studio has a free trial. I made this log using the retail version, but it's using the same exe as the one on the softpedia link provided. -- 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.

2 3

[Bug 42316] New: Cannot play multiplayer in Gwent
by wine-bugs＠winehq.org 30 Sep '19

30 Sep '19

https://bugs.winehq.org/show_bug.cgi?id=42316 Bug ID: 42316 Summary: Cannot play multiplayer in Gwent Product: Wine-staging Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stas5978(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When tried to start Multiplayer's "Casual Math" and wait about 5 sec you will get wine fixme: fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"ECDSA_P384" not supported -- 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.

2 21

[Bug 47850] New: Automatically restart the TestBot Engine if it crashes
by WineHQ Bugzilla 30 Sep '19

30 Sep '19

https://bugs.winehq.org/show_bug.cgi?id=47850 Bug ID: 47850 Summary: Automatically restart the TestBot Engine if it crashes Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The CheckWineTestBot.pl script is supposed to automatically restart the TestBot Engine if it crashes (such as because of a Perl error that only happens in specific code paths). However it does not work in the current usage scenario. I think what happens is that the script is run in a non-root account for security reasons so the call to 'service winetestbot restart' fails with a permission denied error. So a different approach is needed, probably one where there are two scripts: * One which communicates with the Engine and returns whether it runs. This script would be run through su. * And a second script that uses the first script's exit code to decide when to restart the Engine. It may even be possible to have systemd handle the task of this second script (to be investigated). Another totally different approach would be to parse the Engine log and check the presence of messages logged by SafetyNet() which runs every 10 minutes. But that would not really guarantee that the Engine is reachable through its socket. Yet a third option would be to have systemd start the Engine automatically when its socket is accessed. That may allow for systemd to automatically restart the Engine when it crashes (to be investigated). -- 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