wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3465 discussions

[Bug 48668] New: rFactor2 - Physics thread slower on multiplayer mode
by WineHQ Bugzilla 11 Oct '22

11 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=48668 Bug ID: 48668 Summary: rFactor2 - Physics thread slower on multiplayer mode Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alex.brrsclnt(a)gmail.com Distribution: Ubuntu Created attachment 66525 --> https://bugs.winehq.org/attachment.cgi?id=66525 Steam rfactor2 proton log This bug is created after the one that exists in the Proton github issue tracker https://github.com/ValveSoftware/Proton/issues/245 The game runs fine in single player mode since version 4.11 to the newest versions of Proton, but there is a problem in multiplayer mode that makes the game run slower. We have asked to the game devs in their discord server for some info, try to get some logs of the multiplayer execution, and finally, one dev told us that despite the graphics thread was fine, there is something wrong affecting to the physics thread in the game, and this only happens in online races, so the issue may be in the network code of Proton/Wine. (@leillo1975 tried to run the game in vanilla Wine, and the problem was also there). Is there any way to trace the network execution to find what could be the problem? I added a log file in the proton issue tracker generated running the game with the "PROTON_LOG=1 %command%" but don't know if that contains enough information. Let me know if I can add any other info. 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 22

[Bug 52330] New: iZotope software authorization process fails
by WineHQ Bugzilla 10 Oct '22

10 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=52330 Bug ID: 52330 Summary: iZotope software authorization process fails Product: Wine-staging Version: 7.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frech(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71492 --> https://bugs.winehq.org/attachment.cgi?id=71492 journalctl log during authorization process Authorizing iZotope software will result in an error. According to the iZotope Support, the attempt is visible, but the local application did not recognize that. Also see attachment. -- 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 18

[Bug 38409] New: Wine Task Tray does is not in the taskbar KDE 5
by wine-bugs＠winehq.org 09 Oct '22

09 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=38409 Bug ID: 38409 Summary: Wine Task Tray does is not in the taskbar KDE 5 Product: Wine Version: 1.7.40 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jack(a)emoss.org Distribution: --- The wine System Tray is not linked to the KDE desktop at all in KDE 5 but it worked fine in KDE 4. -- 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 99

[Bug 45364] New: Frostpunk
by wine-bugs＠winehq.org 08 Oct '22

08 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=45364 Bug ID: 45364 Summary: Frostpunk Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hewanci(a)gmail.com Distribution: --- Frostpunk is so dark that it's unplayable due to not being able to see what's happening. Steam version Staging 3.10 Arch Linux There is already a bug about glitches but I doN't know how related that is: bug 45098 -- 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 17638] New: NOLF GotY: Sluggish mouse reaction when in zoom mode
by wine-bugs＠winehq.org 08 Oct '22

08 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=17638 Summary: NOLF GotY: Sluggish mouse reaction when in zoom mode Product: Wine Version: 1.1.16 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquid.acid(a)gmx.net CC: jb.faq(a)gmx.de Mouse input in NOLF is generally a bit "inprecise", but one thing is broken for sure. Some weapons feature a zoom mode, but when this zoom mode is switched on it's almost impossible to accurately use it since the mouse input becomes very sluggish then. Turn zoom off again and mouse input stabilizes again. I suppose that's a dinput problem, but I'm not sure about that. The wine-0.9.46 testresult here (http://appdb.winehq.org/objectManager.php?sClass=version&iId=305&iTestingId…) mentions a "weird mouse problem", but I'm not sure if that's what I'm encountering. Haven't tried any native DLLs though. -- 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 20

[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

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