August 2020 - Wine-bugs - list.winehq.org

[Bug 47180] New: Nocturne unhandled exception bug on startup
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=47180 Bug ID: 47180 Summary: Nocturne unhandled exception bug on startup Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jagsoul87(a)gmail.com Distribution: --- Created attachment 64434 --> https://bugs.winehq.org/attachment.cgi?id=64434 Unhandled exception register dump/log file When trying to run Nocturne the game crashes displaying an error message, when I click on "show details" it shows the following message: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code. The following register dump and full log file it's attached to this bug report. -- 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 41253] New: GZDoom Builder : Unable to make a new project
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=41253 Bug ID: 41253 Summary: GZDoom Builder : Unable to make a new project Product: Wine Version: 1.9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janusczpawlacz(a)protonmail.ch Distribution: --- Created attachment 55547 --> https://bugs.winehq.org/attachment.cgi?id=55547 Terminal error outpot of Builder.exe So every time I try to open a new project or opening a existing map for editing a error appears and it just plain crashes. Error Message: Fatal Windows Forms error occured: CompilationException While [unreadable] Fatal Windows Forms Error http://devbuilds.drdteam.org/doombuilder2-gzdb/GZDoom%20Builder%20R2364%20I… sha1sum: aa65a19b1275deb09680f4227f81218d27308422 Distribution: Linux Mint 18 Mate X86_64 (64bit) -- 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 12

[Bug 46320] New: Kindle don't get installed: abnormal program temrination
by wine-bugs＠winehq.org 04 Jun '21

04 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=46320 Bug ID: 46320 Summary: Kindle don't get installed: abnormal program temrination Product: Wine Version: 4.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raffamaiden(a)gmail.com Distribution: --- Created attachment 63054 --> https://bugs.winehq.org/attachment.cgi?id=63054 command line log file + screenshot Kindle for PC version 1.24.51068 don't even get installed. After the installer showing up the dialog in which it says it is decompressing the files, after the dialog in which it says it is copying (I presume?) the files, an error message shows up "abnormal program termination" I attach log and screenshot -- 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 16

[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 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 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 10204] New: Incorrectly raised FD_WRITE socket event
by wine-bugs＠winehq.org 02 Jun '21

02 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=10204 Summary: Incorrectly raised FD_WRITE socket event Product: Wine Version: 0.9.48. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: wine-net AssignedTo: wine-bugs(a)winehq.org ReportedBy: rraptorr(a)nails.eu.org Created an attachment (id=8812) --> (http://bugs.winehq.org/attachment.cgi?id=8812) FD_WRITE event on socket test program According to MSDN WSAEventSelect function description (http://msdn2.microsoft.com/en-us/library/ms741576.aspx) FD_WRITE event should be raised only once after: a) successful connection b) WSAEWOULDBLOCK error while in nonblocking mode. MSDN description: "The FD_WRITE network event is handled slightly differently. An FD_WRITE network event is recorded when a socket is first connected with connect/WSAConnect or accepted with accept/WSAAccept, and then after a send fails with WSAEWOULDBLOCK and buffer space becomes available. Therefore, an application can assume that sends are possible starting from the first FD_WRITE network event setting and lasting until a send returns WSAEWOULDBLOCK. After such a failure the application will find out that sends are again possible when an FD_WRITE network event is recorded and the associated event object is set." Unfortunately, it seems that in Wine 0.9.48 (and a few earlier versions too) this event is raised every time it is possible to write to the socket. I've created a simple test program (FD_WRITE-test.c) that shows this problem. When ran on Windows I get: lNetworkEvents: 2 lNetworkEvents: 0 but when ran on Wine: lNetworkEvents: 2 lNetworkEvents: 2 which means that FD_WRITE was raised twice and it shouldn't. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 53

[Bug 12366] New: Acclaim Cashbook startup failure - recompile visual basic
by wine-bugs＠winehq.org 02 Jun '21

02 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=12366 Summary: Acclaim Cashbook startup failure - recompile visual basic Product: Wine Version: 0.9.58. Platform: PC URL: http://www.acclaim.co.nz/download.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pcpavnz(a)gmail.com Install routine executes properly, but when trying to run the installed program, an error message pops up with a message about having to recompile the visual basic module. I suspect the message indicates the cashbook program is what it thinks requires recompiling, not the environment it is running from, but thought I'd submit it anyway because so many people want accounting software packages to work inside Linux and wine is so close very now to getting it right. url provided in the report form is for the free 90 day trial download, which is no different to a full version. -- 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 16