wine-bugs June 2021

wine-bugs@winehq.org

1 participants
5115 discussions

[Bug 48094] New: Simplify debugging test timeouts
by WineHQ Bugzilla 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=48094 Bug ID: 48094 Summary: Simplify debugging test timeouts Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: testcases Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When a Wine test times out one has to manually add traces to figure out where it gets stuck, or what the slow parts are. This is all the more difficult when the timeout is random and happens on a TestBot VM. I propose to leverage the ok() calls to simplify getting timing information on the tests. * Recognize the $WINETEST_TIME environment variable and, if it is set, add the elapsed time since the test started to the trace() and ok() messages. * Ideally this elapsed time would have sub-second precision for those cases where it's more an issue of a long loop being slow. How many decimals to print is a matter of taste: one may be enough, three would feel quite standard if maybe a bit overkill. * Also when $WINETEST_TIME is set, an ok() call would be printed even if successful when more than 1 second has elapsed since adding a message to the report (trace/ok/skip). This should allow identifying which part of the test causes trouble without altering its timing with thousands of traces. * And when combined with $WINETEST_REPORT_SUCCESS of course every ok() call would print the elapsed time. Once the Wine side is implemented a few other components should be updated: * The TestBot should allow setting $WINETEST_TIME when submitting a job. * The TestBot should recognize the failure/todo/skip lines even with the extra timing information. * The TestBot could be modified to automatically rerun and set $WINETEST_TIME if a test times out. * The above may be particularly interesting for the full WineTest runs. * We may also want to have test.winehq.org recognize the new failure/todo/skip line formats. -- 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 34746] New: Dino Crisis Demo doesn't play video sequences even though Indeo codecs are installed
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=34746 Bug #: 34746 Summary: Dino Crisis Demo doesn't play video sequences even though Indeo codecs are installed Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46322 --> http://bugs.winehq.org/attachment.cgi?id=46322 Dino Crisis Demo Log without Indeo Tested with: Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313) Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11 -- 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 19

[Bug 31310] New: TIE: Fighter: Collectors Edition -- Application Crashes on Launch
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=31310 Bug #: 31310 Summary: TIE: Fighter: Collectors Edition -- Application Crashes on Launch Product: Wine Version: 1.5.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: muleyryan(a)fastmail.fm Classification: Unclassified Wine running on 3.4.6-1-ARCH, with S3 Inc. SuperSavage IX/C SDR (rev 05) xf86-video-savage and MESA savage drivers installed. Using gdi as d3d renderer. Application (TIE95.exe) crashes on launch Backtrace here: http://pastebin.com/mTX4bPet Regression test pending. -- 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 10

[Bug 50988] New: New ProcessBasicInformation() failure in kernel32:process
by WineHQ Bugzilla 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=50988 Bug ID: 50988 Summary: New ProcessBasicInformation() failure in kernel32:process Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:process has a new test failure which happens on all test configurations from Vista to the latest Windows 10: process.c:4206: Test failed: ProcessBasicInformation info modified See: https://test.winehq.org/data/tests/kernel32:process.html This failure was introduced by the following commit: commit fdf6d7de2e77f0986b01532c4e1913602e006d6b Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Thu Mar 11 18:04:48 2021 +0100 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Thu Mar 11 18:10:42 2021 +0100 kernel32/tests: Add some tests for the behavior of queries on a dead process. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 49801] New: Freight Yard Manager: Crashes on start
by WineHQ Bugzilla 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=49801 Bug ID: 49801 Summary: Freight Yard Manager: Crashes on start Product: Wine Version: 5.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue(a)blu3wolf.com Distribution: --- Created attachment 68114 --> https://bugs.winehq.org/attachment.cgi?id=68114 exception text On running, Freight Yard Manager V5.9.17 (and all previous versions tested) throws an unhandled System.InvalidProgramException: Invalid IL code. This does not happen on any tested Windows system. -- 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 51216] New: In Wine riched20:txtsrv has a succeeding todo in the ar-MA, he-IL and ja-JP locales
by WineHQ Bugzilla 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=51216 Bug ID: 51216 Summary: In Wine riched20:txtsrv has a succeeding todo in the ar-MA, he-IL and ja-JP locales Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- In Wine riched20:txtsrv has a succeeding todo in the ar-MA, he-IL and ja-JP locales: https://test.winehq.org/data/patterns.html#riched20:txtsrv txtsrv.c:807: Test succeeded inside todo block: got wrong width: 72, expected: 72 {+1}. The succeeding todo was introduced in this commit: commit e7b42deaf2a18e32313e2da02566905180986760 Author: Huw Davies <huw(a)codeweavers.com> AuthorDate: Thu Mar 25 09:10:28 2021 +0000 riched20: Implement TxGetNaturalSize(). Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> References: https://www.winehq.org/pipermail/wine-devel/2021-March/183576.html https://www.winehq.org/pipermail/wine-devel/2021-April/185835.html >From that email: | So I don't know how to avoid getting this failure in every | nightly WineTest run. | | Is it a font problem? | Making the todo conditional on the locale feels iffy. | Same for skipping the test based on the locale. Fix the | implementation some more so it works on all locales? -- 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 34734] New: Dino Crisis 2 Demo website-like launcher doesn't run the game (it doesn't respond to clicking)
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=34734 Bug #: 34734 Summary: Dino Crisis 2 Demo website-like launcher doesn't run the game (it doesn't respond to clicking) Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46311 --> http://bugs.winehq.org/attachment.cgi?id=46311 Dino Crisis 2 Demo Launcher Log If you try to launch the game with it, nothing happens. Also, if you click on, for example, 'Help' the content isn't displayed. -- 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 4

[Bug 29011] New: Non-standard serial baud rates are not reported correctly.
by wine-bugs＠winehq.org 03 Jun '21

03 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=29011 Bug #: 29011 Summary: Non-standard serial baud rates are not reported correctly. Product: Wine Version: 1.2.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: jstutch(a)googlemail.com Classification: Unclassified Running VCDS-Lite 1.1 (connects to car diagnostics), with a FTDI-based USB-Serial cable, when a non-standard baud rate is set on the port (10.4Kbps I think), and the rate is read back by the program, wine reports "err:comm:get_baud_rate unknown speed 1000", and returns an error to the program. This breaks the serial port in the program until it is reset. Replacing the offending lines in dlls/ntdll/serial.c: get_baud_rate with "sbr->BaudRate = speed; break;", removes the error, and the program operates correctly, although this may not be the right way to do this. This was noted running Ubuntu Maverick (10.10), kernel 2.6.35-25-generic. Running wine from the Maverick ubuntu package, rebuilt from package source to correct the error as above. Thanks, JStutch -- 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 8

[Bug 2571] Itunes error when trying to run in Wine
by WineHQ Bugzilla 02 Jun '21

02 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=2571 Sabbir <robinssgraphics(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robinssgraphics(a)gmail.com -- 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 51211] New: BioShock 2 Remastered crashes when enabling/disabling vertical sync
by WineHQ Bugzilla 02 Jun '21

02 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=51211 Bug ID: 51211 Summary: BioShock 2 Remastered crashes when enabling/disabling vertical sync Product: Wine Version: 6.9 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 70084 --> https://bugs.winehq.org/attachment.cgi?id=70084 backtrace Can be enabled manually with changing UseVSync=0 to 1 in [Engine.RenderConfig] section of Bioshock2SP.ini file located in 'drive_c/users/user_name/Application Data/BioshockHD/Bioshock2' wine-6.9-248-g96030ce738a -- 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

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 June 2021