wine-bugs October 2019

wine-bugs@winehq.org

1 participants
7593 discussions

[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 47904] New: Jobs should also report a count of failed test units
by WineHQ Bugzilla 06 Oct '19

06 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47904 Bug ID: 47904 Summary: Jobs should also report a count of failed test units 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: --- Currently jobs report the number of individual ok() failures. That's ok when testing an individual test unit. But for WineTest jobs one can get numbers like 390 or even 2733. That's impossible to compare to the results of test.winehq.org which report the number of failed test units. In particular test.winehq.org rejects reports that have more than 50 or 70 failed test units and its impossible to tell by looking at the results on the TestBot whether the report was rejected or not. So it would be nice to report the number of failed test units in addition to the number of individual ok() failures. This would also be nice when a patch modifies a Wine module so that all its test units are re-run. -- 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 47902] New: CheckForWinetestUpdate systematically claims to have created jobs
by WineHQ Bugzilla 06 Oct '19

06 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47902 Bug ID: 47902 Summary: CheckForWinetestUpdate systematically claims to have created jobs 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: --- CheckForWinetestUpdate.pl ends with the following lines: LogMsg "Submitted jobs\n"; exit $Rc; So whenever cron runs it this line appears in the TestBot log, even if the WineTest binaries have not been updated and no job was created. So while this allows making sure the script is still running as expected, the message is misleading. It would be better if it exited either with a message saying there was no update or which jobs got created. -- 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 47878] New: VirtualProtect across page boundaries does not work
by WineHQ Bugzilla 05 Oct '19

05 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47878 Bug ID: 47878 Summary: VirtualProtect across page boundaries does not work Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: c3210606(a)urhen.com Distribution: --- Official VirtualProtect documentation states: The size of the region whose access protection attributes are to be changed, in bytes. The region of affected pages includes all pages containing one or more bytes in the range from the lpAddress parameter to (lpAddress+dwSize). This means that a 2-byte range straddling a page boundary causes the protection attributes of both pages to be changed. This however is not replicated in Wine as only the first page will have its protection changed and any pages after that resulting from the dwSize crossing the boundary will not be affected. -- 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 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 47892] New: Cinebench crashes just after finishing benchmark
by WineHQ Bugzilla 05 Oct '19

05 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47892 Bug ID: 47892 Summary: Cinebench crashes just after finishing benchmark Product: Wine Version: 4.12.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gnarlin(a)gmail.com Distribution: --- Created attachment 65382 --> https://bugs.winehq.org/attachment.cgi?id=65382 Wine running cinebench r15 console output crashinfo Cinebench crashes just after finishing benchmark just before it can display the results. -- 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 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 47757] Draugen requires mfplat.dll.MFGetConfigurationDWORD
by WineHQ Bugzilla 04 Oct '19

04 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47757 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- This has been removed from staging now. Marking this as a dupe of bug 47758. *** This bug has been marked as a duplicate of bug 47758 *** -- 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 47830] New: Exact Audio Copy (EAC) does not run with latest development release
by WineHQ Bugzilla 04 Oct '19

04 Oct '19

https://bugs.winehq.org/show_bug.cgi?id=47830 Bug ID: 47830 Summary: Exact Audio Copy (EAC) does not run with latest development release Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)konink.de Distribution: --- Created attachment 65336 --> https://bugs.winehq.org/attachment.cgi?id=65336 Problem running EAC with mono-only installation I ran Exact Audio Copy using a stock Ubuntu wine package, from the 4.0.x branch. In this installation I stumbled on the issue that the EAC plugins were not recognized. This issue is said to be fixed in #43270. I have manually compiled Wine 4.17 for 32bit, which let to the output in the attachment. After winetricks dotnet20 I was able to run EAC.exe, including the plugins that were previously missing, this resulted in not able to retrieve information about CDs. But this seems to be a side effect of the plugins "working". When selecting Build-in freedb engine under Metadata options, information was retrieved. The second attachment shows the problem using the CUETools plugin. I have reproduced the steps with winehq-devel (4.17~disco): Download: https://www.fosshub.com/Exact-Audio-Copy-DE.html?dwl=eac-1.3.exe Run: wine eac-1.3.exe Validate the output in output.txt after starting the application. Run: winetricks dotnet2 Run: cd ~/.wine/drive_c/Program\ Files\ $x86$/Exact\ Audio\ Copy/ Run: wine EAC.exe Cancel the CD-rom detection. Insert a common audio CD. Alt-G, specify e-mail. Another Alt-G. Validate the output in output-networking.txt after starting the application. -- 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

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 October 2019