wine-bugs July 2022

wine-bugs@winehq.org

1 participants
3865 discussions

[Bug 31157] New: Filemaker Pro 12 Trial crashes
by wine-bugs＠winehq.org 07 Oct '22

07 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=31157 Bug #: 31157 Summary: Filemaker Pro 12 Trial crashes Product: Wine Version: 1.2.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: maikwagner(a)yahoo.com Classification: Unclassified Created attachment 40903 --> http://bugs.winehq.org/attachment.cgi?id=40903 Crash Output on Filemaker 12 I would like to report some issues with Filemaker 12 Trial which can be downloaded from Filemaker.com. The application installs okay and I can start "Filemaker 12" from the command line. When opening a sample solution (I selected "Invoices") the application crashes. I have attached my console output. -- 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 36

[Bug 30666] New: MPEG movie does not play in Capitalism 2 demo
by wine-bugs＠winehq.org 07 Oct '22

07 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=30666 Bug #: 30666 Summary: MPEG movie does not play in Capitalism 2 demo Product: Wine Version: 1.5.4 Platform: x86 URL: http://www.cnwcentral.com/capitalism-2/demo.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer AssignedTo: wine-bugs(a)winehq.org ReportedBy: jeremielapuree(a)yahoo.fr Classification: Unclassified Created attachment 40144 --> http://bugs.winehq.org/attachment.cgi?id=40144 console output While playing intro movie of Capitalism 2 demo, one can hear the sound, but video is playing. -- 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 11

[Bug 48912] New: Allow blacklisting unreliable and always new failures
by WineHQ Bugzilla 06 Oct '22

06 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=48912 Bug ID: 48912 Summary: Allow blacklisting unreliable and always new failures 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: --- A number of tests produce false positives because: * Either the failure message contains a value that changes with each run (e.g. an HWND). In some cases these values are really necessary for diagnosis and moving them to a separate line would make the code quite a bit more complex. * Or the test fails intermittently and is hard to fix. Sometimes the cause of the failures may also come from external factors such as bugs in QEmu (for instance long execution delays causing timeouts). * Sometimes the intermittent failure is the product of a new Windows version or configuration, which requires investigating before a fix is found. In all cases the tests should be fixed eventually, but a solution is needed for the interim so these tests to not make the TestBot so unreliable that its results are ignored. So the goal is to provide a way to blacklist some test failures so they do not cause a patch to be rejected. Some safeguards are needed to ensure that: * Failures are not blacklisted lightly. The preference should always be to fix the test. * The blacklist does not get so large that it becomes hard to maintain. * Once a test is fixed the corresponding blacklist entries are removed in a timely fashion. * There is still an incentive to fix the tests. So here is a proposal for implementing this blacklist: * Each blacklist entry should be associated with a Wine bug describing the issue. That bug should provide some minimal diagnosis: whether it's a new Windows behavior, a race condition or some issue that was reported to QEmu. That would ensure we know why the blacklist entry was added. One could also check the status of the bug when reviewing the blacklist entries. A closed bug would be a strong hint that the blacklist entry is no longer needed. * Rather than blacklisting whole test units, blacklist entries should target specific test failures via a regular expression. Besides being finer grained this would be useful for cases like user32:win which has different issues depending on the locale and where each should be linked to a different bug (bugs 48815, 48819 and 48820). * The TestBot should record when each blacklist entry was last used. This relies on having the above regular expression since without it the TestBot would not know anything beyond 'the test unit was run and had failures'. Also the regular expression would only be used against *new* failures. So this would really record the last time the blacklist entry was actually useful. An entry that was unused for a long time would be a prime candidate for reviewing the corresponding bug and for removal. (Note: The blacklist would also be used on WineTest reports so it would get a chance of matching its target at least 5 days / week). * The blacklist entries would only be needed for 'base' test configurations since they are the only ones wine-devel patches run on. * There should be a page listing the blacklist entries so developers have a good starting point to work on them. * Ideally the blacklist page would also point to the tasks where the blacklist was last used. Since most of the blacklisted failures are either intermittent or specific to a given test configuration this would make it easier for developers to find reports where the failure did happen. Note that Wine VMs often test multiple configurations per task (e.g. wow32 and wow64, different locales), each producing its own test report. So pointing at just the task would leave the developer guessing which report should be looked at. But that may be sufficient guidance. * (test:unit, testbot-vm) tuples make it impossible to target a specific Wine test configuration such as a specific locale since they all run on the same VM. Similarly it would make blacklisting bitness-blind on Windows VMs. If necessary the tuple could be extended either with the specific mission the blacklist applies to, or with the basename of the corresponding report (the latter being easier to use in comparisons). Whether that's practical and worth the effort remains to be determined. One complication for instance is that this would lead to more blacklist entries: many 64 bit VMs would need two entries, one for 32 bit tests and one for 64 bit tests. * Pseudo database schema and sample use: FailureBlacklists ----------------- PK Bug 48815 PK TestModule user32 PK TestUnit win Name 0x738 message FailureRegExp Test failed: hwnd [0-9A-F]{8,16} message 0738 LastUse 2020-03-27 FailureBlacklistVMs ------------------- PK Bug 48815 PK TestModule user32 PK TestUnit win PK VMName Entries for w1064v1709, w1064v1809, etc. (48815, user32, win, w1064v1709) (48815, user32, win, w1064v1809) (48815, user32, win, w1064v1809_2scr) ... FailureBlacklistUses (optionally) --------------------------------- PK Bug PK TestModule PK TestUnit PK JobId PK StepNo PK TaskNo (48815, user32, win, 68507, 1, 7) (48815, user32, win, 68508, 1, 7) ... -- 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 5

[Bug 48209] New: Ignore random parts of test failure messages
by WineHQ Bugzilla 06 Oct '22

06 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=48209 Bug ID: 48209 Summary: Ignore random parts of test failure messages 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 TestBot needs to detect if a patch introduces NEW test failures. To do so it compares the failure messages with those from reference WineTest runs. But in some cases part of the message changes from one run to the next, causing the failure to look new. Of course in all cases the ideal solution is to fix the test so it does not fail. Barring that there are also cases where the varying value is not really useful (e.g. handle or pointer values) and in that case it should just be removed from the message. But there may be cases where knowing the value is still useful. So one solution would be to tag such values so the TestBot knows it can ignore them when comparing failure messages. For instance they could be enclosed in double braces, curly braces, or other. -- 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 5

[Bug 52689] New: NVCUDA: Daz Studio 4.20 and CUDA SDK11 implementation
by WineHQ Bugzilla 04 Oct '22

04 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=52689 Bug ID: 52689 Summary: NVCUDA: Daz Studio 4.20 and CUDA SDK11 implementation Product: Wine-staging Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cybermax(a)dexter.no CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 72031 --> https://bugs.winehq.org/attachment.cgi?id=72031 Series of patches to implement basic SDK11 functionality Recently DAZ Studio4 updated to 4.20 and the Iray engine also got updated to the point it requires support for CUDA 11.4 I have worked through a great deal of the issues regarding support for SDK 11.4, aside from the D3D9/10/11 elements that have no equivalent Linux support. The result is adding a few functions to the nvcuda implementation in wine-staging. (Attachment with a series of 4 patches). I have not yet been able to get SDK 11.6 samples to run, as this will (for now) fail the CUDA runtime validation.. but DAZ Studio 4.20.1 is running fine. 2022-03-17 22:24:11.731 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : NVIDIA display driver version: 510.54 2022-03-17 22:24:11.732 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Your NVIDIA driver supports CUDA version up to 11.6; iray requires CUDA version 11.4; all is good. 2022-03-17 22:24:11.732 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : Using iray plugin version 5.3, build 349500.7063 n, 18 Jan 2022, nt-x86-64-vc142. 2022-03-17 22:24:11.768 Iray [INFO] - IRAY:RENDER :: 1.1 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 2070): compute capability 7.5, 7.773 GiB total, 7.229 GiB available, display attached I have built and run the main demo samples from the cuda-samples source github, aswell as 30 some samples in addition to that, compiled with VS2019 and using the SDK11.4 runtime library. -- 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 36103] New: kernel32/tests/loader shows lots of invalid reads in thread.c
by wine-bugs＠winehq.org 01 Oct '22

01 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=36103 Bug ID: 36103 Summary: kernel32/tests/loader shows lots of invalid reads in thread.c Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==9219== Invalid read of size 4 ==9219== at 0x7BC55D91: MODULE_DllThreadAttach (loader.c:1287) ==9219== by 0x7BC8E3D2: start_thread (thread.c:423) ==9219== by 0x4218F92: start_thread (pthread_create.c:309) ==9219== by 0x431D7ED: clone (clone.S:129) ==9219== Address 0x611eb04 is on thread 1's stack ==9219== ==9219== Invalid read of size 4 ==9219== at 0x7BC1EAF3: __x86.get_pc_thunk.bx (in /home/austin/wine-valgrind/dlls/ntdll/ntdll.dll.so) ==9219== by 0x7BC8E3D2: start_thread (thread.c:423) ==9219== by 0x4218F92: start_thread (pthread_create.c:309) ==9219== by 0x431D7ED: clone (clone.S:129) ==9219== Address 0x611eacc is on thread 1's stack ==9219== there's also one: ==30099== 2,020 bytes in 1 blocks are possibly lost in loss record 225 of 244 ==30099== at 0x7BC4C735: notify_alloc (heap.c:255) ==30099== by 0x7BC50F79: RtlAllocateHeap (heap.c:1716) ==30099== by 0x4E07A19: get_tls_data (test.h:244) ==30099== by 0x4E07B03: winetest_set_location (test.h:279) ==30099== by 0x4D836B8: dll_entry_point (loader.c:1433) ==30099== by 0x7BC52FC0: ??? (loader.c:138) ==30099== by 0x7BC555FE: MODULE_InitDLL (loader.c:1068) ==30099== by 0x7BC55DE7: MODULE_DllThreadAttach (loader.c:1281) ==30099== by 0x7BC8E446: start_thread (thread.c:423) ==30099== by 0x4EA7BD89: start_thread (in /usr/lib/libpthread-2.18.so) ==30099== by 0x4E95CA0D: clone (in /usr/lib/libc-2.18.so) ==30099== -- 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 53400] New: wine-gecko 2.47.3 fails to build on host systems with python 3.11
by WineHQ Bugzilla 28 Sep '22

28 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=53400 Bug ID: 53400 Summary: wine-gecko 2.47.3 fails to build on host systems with python 3.11 Product: Wine-gecko Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: mike(a)cchtml.com Distribution: --- In similar vain as bug 51918 it is that time again. Fedora 37 (Rawhide, unreleased) has Python 3.11. There are currently two failures I have encountered. I've patched one. 1. inspect.getargspec() changes in Python 3.11 --- a/python/mach/mach/decorators.py 2022-07-12 08:33:06.000000000 -0500 +++ b/python/mach/mach/decorators.py 2022-07-22 08:55:21.510849725 -0500 @@ -111,7 +111,7 @@ pass_context = False if inspect.isfunction(cls.__init__): - spec = inspect.getargspec(cls.__init__) + spec = inspect.getfullargspec(cls.__init__) if len(spec.args) > 2: msg = 'Mach @CommandProvider class %s implemented incorrectly. ' + \ 2. Setting up the python virtualenv fails. 0:01.29 checking for python3... /usr/bin/python3 0:01.29 Creating Python environment 0:01.31 /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py:10: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives 0:01.31 import distutils.sysconfig 0:01.31 /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py:10: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead 0:01.31 import distutils.sysconfig 0:01.34 /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/virtualenv/virtualenv.py:24: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives 0:01.34 import distutils.spawn 0:01.35 /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/virtualenv/virtualenv.py:25: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead 0:01.35 import distutils.sysconfig 0:01.37 Using base prefix '/usr' 0:01.37 New python executable in /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3 0:01.37 Not overwriting existing python script /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python (you must use /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3) 0:01.37 ERROR: The executable /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv/bin/python3 is not functioning 0:01.37 ERROR: It thinks sys.prefix is '/usr' (should be '/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv') 0:01.37 ERROR: virtualenv is not compatible with this system or executable 0:01.38 Traceback (most recent call last): 0:01.38 File "/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py", line 486, in <module> 0:01.38 manager.ensure() 0:01.38 File "/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py", line 128, in ensure 0:01.38 return self.build() 0:01.38 ^^^^^^^^^^^^ 0:01.38 File "/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py", line 382, in build 0:01.38 self.create() 0:01.38 File "/builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3/python/mozbuild/mozbuild/virtualenv.py", line 147, in create 0:01.38 raise Exception( 0:01.38 Exception: Failed to create virtualenv: /builddir/build/BUILD/wine-gecko-2.47.3/wine-gecko-2.47.3-x86/_virtualenv -- 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 52493] New: CPU architecture entry on AppDB test reports
by WineHQ Bugzilla 27 Sep '22

27 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=52493 Bug ID: 52493 Summary: CPU architecture entry on AppDB test reports Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- I've talk about it on the forum https://forum.winehq.org/viewtopic.php?f=11&t=36163&p=135972#p135972 Today, AppDb only asks us for GPU and GPU driver on the hardware section before posting data reports. With the adoption of ARM architecture on mainline Windows and popularization of ARM laptops, more Windows applications will be released for ARM architecture aswell, some Linux distributions are being ported to ARM too. That means, before Wine did had compatibility on other CPU architectures but Windows applications didn't had it, so tests reports were mostly focused for x86 architectures and other architectures had 0 guarantee to be supported, things are about to change today with x64 and ARM becoming supported by Microsoft. There's options to emulate x86 and x64 architectures on ARM, even on Windows. There's Rosetta on MacOS and box86/box64 on GNU/Linux. However, emulators aren't perfect and CPU architecturse, emulated or natively, are going to imply in app compatibility and in future test reports. While another application might work perfect on x86, it might fail or be buggy in ARM both natively or emulated, even if the application has support to it. To prevent confusion on the next reports, we'll need to leave CPU architectures in consideration. ¿What do you think about it? -- 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 1

[Bug 48468] New: Add "Bronze" and "Garbage" top-10 lists to the appdb landing page
by WineHQ Bugzilla 27 Sep '22

27 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=48468 Bug ID: 48468 Summary: Add "Bronze" and "Garbage" top-10 lists to the appdb landing page Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jonwsb(a)gmail.com Distribution: --- The top-10 lists on appdb.winehq.org are a very nice feature of the site. Their purpose of showing off what popular programs work in wine is very useful to new users and I think adding the "Bronze" and "Garbage" ratings to the page will also provide valuable information to new users as well as contributors. For new users it will give quick access to information on programs they may be planning on attempting to use with wine. For advanced users and contributors it will be a useful tool to gauge which programs need high quality testing and possibly give inspiration for developing patches to improve bronze and garbage rating entries. My biggest concern with adding these top-10 lists would be increasing the size of the page even more than it already is though it will also probably drive users of the appdb to vote for more applications overall. -- 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 3

[Bug 51980] New: Fedora 35 repo link is brokern
by WineHQ Bugzilla 27 Sep '22

27 Sep '22

https://bugs.winehq.org/show_bug.cgi?id=51980 Bug ID: 51980 Summary: Fedora 35 repo link is brokern Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: craig.ziesman(a)gmail.com Distribution: --- Trying to add the Fedora 35 repo using ```dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/35/winehq.repo``` but it returns a 404 status code -- 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 3

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 July 2022