May 2023 - Wine-bugs - list.winehq.org

[Bug 53806] New: Archicad 26: crash at launch
by WineHQ Bugzilla 31 Jul '23

31 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=53806 Bug ID: 53806 Summary: Archicad 26: crash at launch Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: doubleboogieblues(a)yahoo.it Distribution: --- Created attachment 73316 --> https://bugs.winehq.org/attachment.cgi?id=73316 terminal output Wine crash when launched archicad.exe installation ok, but the software does not start installed: dotnet452, vcrun2019, vcrun2013 download DEMO Archicad 26: https://graphisoft.com/dl/AC/26/INT/Archicad-26-INT-3001-1.1.exe -- 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 6

[Bug 21448] New: RollerCoaster Tycoon 3 does not accept the original disc
by wine-bugs＠winehq.org 31 Jul '23

31 Jul '23

http://bugs.winehq.org/show_bug.cgi?id=21448 Summary: RollerCoaster Tycoon 3 does not accept the original disc Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thomas.mertes(a)gmx.at Created an attachment (id=25828) --> (http://bugs.winehq.org/attachment.cgi?id=25828) Error log and content of message box when starting RollerCoaster Tycoon 3 When starting RollerCoaster Tycoon 3 it asks for the original disc although the original disk is in. There are some errors logged (see attachment) and then a message box appears: Please insert the original disc instead of a backup. See www.securom.com/copy for more details Greetings Thomas -- 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 46

[Bug 52242] New: Mouse cursor disappears in GTA V when Social Club overlay is on
by WineHQ Bugzilla 28 Jul '23

28 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52242 Bug ID: 52242 Summary: Mouse cursor disappears in GTA V when Social Club overlay is on Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vutov.martin97(a)gmail.com Distribution: --- Whenever you try to open the Social Club overlay, the cursor disappears. If you manage to press something with it, it works, it just can't be seen. Sometimes it works, but very rarely. Haven't figured why it works in said cases. To reproduce: Start GTA V Wait for it to load to home screen Press "Home" button for Social Club overlay to appear No mouse I am new when it comes to Linux so I've no idea where to get a log from. If someone tells me how I'll be more than glad to do so. I am launching the game via Lutris with the Rockstar Games Launcher installer. -- 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 38690] New: corrupted serial communications
by wine-bugs＠winehq.org 28 Jul '23

28 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=38690 Bug ID: 38690 Summary: corrupted serial communications Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpyle490(a)gmail.com Distribution: --- Serial communications are corrupted/laggy/ugly. Tested on a Dell Latitude D630 running Linux Mint 17.1 and Wine 1.7.38 from WineHQ PPA, as well as Wine 1.6.2 on the same hardware from the Ubuntu repo. The issue occurs whether it's the hardware 16550 serial port or a USB attached one. (In this Linux system case the USB adapter was Prolific-based.) I observed the same symptoms on Mac OS X Mavericks, compiling Wine 1.7.43 via Macports, using an FTDI-based USB adapter. The primary test scenario included Tera Term 4.87 talking to a Cisco router's console port at 9600 N,8,1 without flow control. Data back from the Cisco was incomplete, latent and just generally ugly. Using the same hardware and minicom running natively in either Linux or OS X there were no issues. Tera Term to a router provided the cleanest environment in which to observe what was happening. I can't get serial communications to work properly regardless of the Windows app or the serially-connected device. -- 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 54822] New: ddraw:visual - createObjects() crashes on fg-deb64 (Intel GPU)
by WineHQ Bugzilla 27 Jul '23

27 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54822 Bug ID: 54822 Summary: ddraw:visual - createObjects() crashes on fg-deb64 (Intel GPU) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 74321 --> https://bugs.winehq.org/attachment.cgi?id=74321 ddraw/tests: Prevent the visual tests from crashing the X server on Intel GPUs. ddraw:visual - createObjects() crashes on fg-deb64 (Intel GPU[1]): ddraw:visual start dlls/ddraw/tests/visual.c ddraw:visual:06d0 done (0) in 2s 0B See https://test.winehq.org/data/patterns.html#ddraw:visual So this is a case of premature exit. A look at the logs immediately reveals the cause of the silent crash: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 7 (RRSetScreenSize) Value in failed request: 0x0 Serial number of failed request: 35 Current serial number in output stream: 36 Running the test with WINETEST_REPORT_SUCCESS=1 and adding some traces shows the X error happens on this createObjects() line: 112 hr = IDirectDraw7_SetDisplayMode(DirectDraw, 640, 480, 32, 0, 0); Replacing the 32 bit depth with 24 results in the call returning 0x80004001 (E_NOTIMPL) instead of crashing (that's an odd error code btw). So an easy workaround would be to use the attached patch. However: * This causes most (if not all) of the tests to be skipped. * My GPU and screen do support 640x480. * Also running ddraw:visual from my development tree results in 0 skips and 0 failures! So getting successful runs should be possible (just not in the 3 clean out-of-tree builds I use to run WineTest :-( ). It's either a matter of figuring out which is the miraculous patch or where the memory corruption comes from. [1] This is an Intel HD Graphics 4600 GPU (comes in the i7-4790K CPU). -- 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 52065] New: Rockstar Games Launcher Installer is leaking memory
by WineHQ Bugzilla 27 Jul '23

27 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=52065 Bug ID: 52065 Summary: Rockstar Games Launcher Installer is leaking memory Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- When installing Rockstar Games Launcher via its installer, the installer never quits and is shown to be stuck on the loading bar. During that, the app is leaking memory really fast, filling up my 32GBs of ram in approximately 1 minute. I can only track the issue down to 6.20 since that's the version the installer started working at, but it's present in 6.22 too. Strangely enough, after you kill its process, the installer actually succeeds at its jos and successfully installs the launcher. I don't know what I can provide to help with this, apart from the link to the installer, so let me know. -- 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 10

[Bug 54885] New: The child window flickers after using SetParent API to set parent-child window between windows from different processes.
by WineHQ Bugzilla 27 Jul '23

27 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54885 Bug ID: 54885 Summary: The child window flickers after using SetParent API to set parent-child window between windows from different processes. Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bcjon07(a)gmail.com Distribution: --- After using the SetParent API to set parent-child window relationship between windows from different processes, the child window flickers heavily. This issue seriously affects the user experience of applications that has any different processes parent-child window. For convenience, I have created a simple demo program that can reproduce this issue and attached the download link. Steps to Reproduce: 1.Download the demo program that can reproduce this issue and open it (SetParentDemo.exe inside) with Wine tool. 2.Click the first button in the program window (the program may crash occasionally, but it is not the focus of this bug report, just retry the operation). 3.Drag child window or switch to activate parent child windows, or move mouse to hover buttons, observe the display of the child window. Download link of the demo program: https://drive.google.com/file/d/1MCrnb1N6cLUzVoX_vO4tFO4qlS_qhAwi/view?usp=… Other clues: After testing, this issue will occur in WPF form programs packaged using. NET 6 standalone mode, but it does not occur in programs packaged under the .NET Framework project (will run on wine mono). Unfortunately, many applications released using Dotnet standalone mode will only run on their built-in NET runtime and not on Wine Mono. System architecture: x86_64 Ubuntu 20.04 wine 8.6 I appreciate your attention to this matter. If you need further cooperation or assistance, please feel free to contact me. -- 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 54189] New: Fail in SetupDiEnumDeviceInfo: err=259: No more data available.
by WineHQ Bugzilla 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=54189 Bug ID: 54189 Summary: Fail in SetupDiEnumDeviceInfo: err=259: No more data available. Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 73724 --> https://bugs.winehq.org/attachment.cgi?id=73724 winedebug logfile trying to install winsupp.exe/ced1401 drivers under wine/8.0rc1 Trying to install ced1401 drivers [1,2] fails with the attached debug log. The attached log was generated with WINEARCH=win32, when using WINEARCH=win64 the same error is shown, only the 64bit driver is mentioned in the log file. [1] https://ced.co.uk/files/winsupp.exe [2] https://appdb.winehq.org/objectManager.php?sClass=version&iId=41230 -- 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 7

[Bug 38101] New: Devil May Cry 4 flickering/texture tearing to eventual white screen
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=38101 Bug ID: 38101 Summary: Devil May Cry 4 flickering/texture tearing to eventual white screen Product: Wine Version: 1.7.34 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shomari.sharpe(a)gmail.com Distribution: --- on starting the game (Directx 9c version) there is lots of flicker present. Upon turning "ON" the VSYNC option in the game the flicker is reduced. The title screen will display until it eventually turns to a black and white alternating flickering. -- 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 6

[Bug 39806] New: Devil May Cry 4 Frozen Screen Glitch
by wine-bugs＠winehq.org 26 Jul '23

26 Jul '23

https://bugs.winehq.org/show_bug.cgi?id=39806 Bug ID: 39806 Summary: Devil May Cry 4 Frozen Screen Glitch Product: Wine Version: unspecified Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: dijscales(a)gmail.com Created attachment 53141 --> https://bugs.winehq.org/attachment.cgi?id=53141 Details of the Problem The screen will randomly freeze while I am playing the game. I can't even play for very long before it freezes. I tried to fix it by changing the config.ini, but that did nothing. -- 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