June 2021 - Wine-bugs - list.winehq.org

[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

[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

[Bug 9504] New: Cannot close CMonthCalCtrl popup by clicking outside popup
by wine-bugs＠winehq.org 02 Jun '21

02 Jun '21

http://bugs.winehq.org/show_bug.cgi?id=9504 Summary: Cannot close CMonthCalCtrl popup by clicking outside popup Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter(a)cendio.se I have an application that uses a custom control: A wrapper that displays a CMonthCalCtrl in a popup window. In Windows, it's possible to close the popup by clicking outside the popup. With Wine, however, it is necessary to either select a date or press Escape. The popup will also be closed if the user tries to move the popup window (which has X11 WM decorations). When clicking outside the popup with Wine, Wine generates a beep through X11 (I believe this happens since a WM_SETCURSOR with HTERROR is generated). A demo program is available as http://www.cendio.se/~astrand/wine/6-close-popup/. Requires Visual C++ 2005 runtime libraries. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 28

[Bug 51208] New: Failed to parse proc stat file
by WineHQ Bugzilla 01 Jun '21

01 Jun '21

https://bugs.winehq.org/show_bug.cgi?id=51208 Bug ID: 51208 Summary: Failed to parse proc stat file Product: Wine Version: 6.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jaap.aarts1(a)gmail.com Distribution: --- This is not reliably reproducable since it only occurred (to me) after updating the wargaming game center (wgc) (with APItrace enabled) Just a short log, hope you dont mind me just putting it here: ``` 053c:err:thread:get_thread_times Failed to parse "/proc/283161/task/283187/stat" wineserver: ../wine/server/process.c:339: release_job_process: Assertion `job->num_processes' failed. ``` I got the full log if relevant. I did not manage to cat the proc file, probably my fault but I didnt think of it. This is on version `wine-6.9-35-g94eb8d36461`. If I ware to be able to reliably test this, I would test with stable/staging but it only happens after the wgc update so I cant try again. -- 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