wine-bugs November 2021

wine-bugs@winehq.org

1 participants
4557 discussions

[Bug 48101] New: Metatester 5 exits silently
by WineHQ Bugzilla 14 Dec '21

14 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48101 Bug ID: 48101 Summary: Metatester 5 exits silently Product: Wine Version: 4.19 Hardware: x86-64 URL: http://files.metaquotes.net/metaquotes.software.corp/m t5/mt5tester.setup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Metatester 5 exits silently after an unknown period of time. The agent starts a number of background services (that apparently install correctly), but when it exits, Wine kills off the background services along with everything else. To workaround that specific problem: 1. wineserver -p 2. wineboot 3. Anything else. (Bug 39030) Nonetheless if you let the agent, or Wine itself, start up the services the result is the same: the agent simply vanishes after an unknown amount of time. Usually less than an hour. Under Windows 8.1 and 10 it runs indefinitely. Entire log (wineserver and wineboot already run): 0190:fixme:heap:RtlSetHeapInformation 0x6a0000 0 0x22f3f0 4 stub 0190:fixme:font:get_outline_text_metrics failed to read full_nameW for font L"Ani"! 0190:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x2263e4, 0x226400 0x2263e0 0190:fixme:nls:get_dummy_preferred_ui_language (0x38 0x2263e4 0x226400 0x2263e0) returning a dummy value (current locale) 0196:fixme:kernelbase:AppPolicyGetThreadInitializationType FFFFFFFFFFFFFFFA, 0000000000C5FD80 0190:fixme:ntdll:server_ioctl_file Unsupported ioctl 9003c (device=9 access=0 func=f method=0) 0190:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x1 0190:fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x1 0190:fixme:shell:InitNetworkAddressControl stub 0198:fixme:secur32:schan_QueryContextAttributesW Unhandled attribute 0x64 0197:fixme:secur32:schan_QueryContextAttributesW Unhandled attribute 0x64 0190:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000022FCD0 No workarounds used. The app can be started again without issue. -- 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 51831] New: TrueDrive: On start shows an alert that the steering wheel is turned around too close to the bump stops, while the wheel is actually aligned on top center
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51831 Bug ID: 51831 Summary: TrueDrive: On start shows an alert that the steering wheel is turned around too close to the bump stops, while the wheel is actually aligned on top center Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 8b434bdc7fe98e3bd97e180f31bc18d87161c05a Distribution: ArchLinux Created attachment 70718 --> https://bugs.winehq.org/attachment.cgi?id=70718 0001-winebus.sys-Fix-possible-memory-access-error-in-bus_.patch In addition to the summary, the in app steering wheel animation is indeed turned around usually on left, and the high torque mode of the Simucube 2 FFB wheel is also being disabled, as the alert warns. After closing the alert, the steering wheel animation resumes proper tracking of the real wheel. After some regression testing found out that in bus_event_queue_pop() (winebus.sys/unixlib.c) the size for the memcpy operation is calculated on base of the event->input_report.length, and when the event operand is passed for first time to this function, its input_report.length is uninitialized. The bus_event structure is being allocated once per bus thread. This could lead to either insufficient bytes being copied to the event struct, or memory access error for an out of bounds copy operation of the tmp struct. The consecutive calls of this function use the event->input_report.length again, which in this case is just the length of the input buffer from the previous operation. If the device uses multiple input reports with different ReportIDs and different lengths, this could lead to serious issues. Attached a patch which fixes the issue (based on the current master) -- 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 51828] New: Simucube 2: All applications using raw HID access to communicate with devices, stopped tracking steering axis movement
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51828 Bug ID: 51828 Summary: Simucube 2: All applications using raw HID access to communicate with devices, stopped tracking steering axis movement Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: d40d8d968658dca4a75afc97f9e48acda0654b0f Distribution: ArchLinux Created attachment 70716 --> https://bugs.winehq.org/attachment.cgi?id=70716 0001-hidclass.sys-Fix-input-reports-with-ReportID-being-d.patch Found out that the dropping of input packets with lengths different than desc->InputLength, which was introduced with the regression commit is causing this issue. Since the Simucube 2 is a HID PID device, it uses multiple HID reports (with defined ReportIDs), which are different lengths. For such devices desc->InputLength specifies the biggest possible buffer length, that would fit any of the input reports. If the most essential input report for tracking the steering axis movements is smaller than desc->InputLength, it'll be dropped by that check. Only the reports with the exact same size go through in non polled mode. In this case with Simucube 2 the biggest input report is of 61 bytes, and is vendor defined. All the other input reports are smaller sizes, and will get dropped. Attached a patch which fixes the issue. It also fixes possible memory access error with report->buffer while copying it to irp->AssociatedIrp.SystemBuffer, due to the internal buffer for hid_report being just report->length which could be less than or equal to desc->InputLength. The patch is based to the current master (aa629c4c7225166f4ee46476d98702df2e142711). -- 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 51824] New: TrueDrive, SimHub, Fanaleds,etc.: Non smooth movement tracking with severe skipping/jumping of the steering wheel/controller axis
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51824 Bug ID: 51824 Summary: TrueDrive, SimHub, Fanaleds,etc.: Non smooth movement tracking with severe skipping/jumping of the steering wheel/controller axis Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 325984ded50b354686e5a454aa5aca3aafa81432 Distribution: ArchLinux Created attachment 70711 --> https://bugs.winehq.org/attachment.cgi?id=70711 0001-hidclass.sys-Fix-writing-all-new-reports-at-the-last.patch All the mentioned applications use raw HID access (through HidD/HidP calls) to the devices they controll, so the movement tracking problems appear only there. DirectInput works well. After further investigation, found that the simpler ring buffer (hidclass.sys/device.c) introduced with the mentioned regression commit is causing the issues. Appeared that all new reports are pushed at the last available ring buffer slot, due to reaching the end of the buffer before the reading has started. Usually such devices as joysticks, controllers, steering wheels, etc., use constant stream of INPUT reports to report their axis movement, so any report skipping or change of the sequence, while the interested apps are reading, would lead to such issues. Attached a patch which fixes the issue (based on the current master aa629c4c7225166f4ee46476d98702df2e142711). -- 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 11

[Bug 51822] New: Simucube 2 TrueDrive: Doesn't recognize the steering wheel device
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51822 Bug ID: 51822 Summary: Simucube 2 TrueDrive: Doesn't recognize the steering wheel device Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 51560aabcb259cb89659d96654d8ad38edbb528d Distribution: ArchLinux Created attachment 70707 --> https://bugs.winehq.org/attachment.cgi?id=70707 0001-hidparse.sys-Preserve-the-original-state-items.repor.patch, wine_6.18.log, SC2_descr.txt Simucube 2 is FFB steering wheel device using the HID PID specification for FFB. Thus the support for it is included in the Linux kernel as part of the HID specification. It still needs some patching of the usbhid kernel module, but in general is entirely functional in Wine, as long as "DisableInput" and "Enable SDL" are disabled in the Wine registry, and for the HIDRAW device is granted rw user access. TrueDrive is an application for controlling and fine tuning various parameters of the steering wheel (using HidD/HidP calls), which also includes real time animation of the steering wheel movement, buttons pushed, etc. The application is not used/needed during gameplay. The TrueDrive version used is 2020.10. The application can be downloaded from the manufacturer site: https://granitedevices.com/wiki/Simucube_2_True_Drive_releases The mentioned regression commit is the earliest in which the problem occurs. I've investigated further, and found that state->items.report_count in the parse_new_value_caps() function (hidclass.sys/descriptor.c) is not preserved properly. While being used for building the alternate value array it's set to 1, and since "Report Count" is a global item, reset_local_items() at the end of the function preserves its state. Thus if there are subsequent main items (Input, Output, etc.) with more than one usages, and with no "Report Count" specified in between, the parser would calculate wrong bit sizes, report len, etc. The particular problem was at the end of the descriptor. Here is an excerpt: /* Usage Page (FF00h), */ /* Usage (01h), */ /* Collection (Application), */ /* Usage (01h), */ /* Report ID (107), */ /* Report Size (8), */ /* Report Count (60), */ /* Logical Minimum (0), */ /* Logical Maximum (255), */ /* Output, */ /* Usage (01h), */ /* Report ID (108), */ /* Input, */ /* End Collection, */ The Input report 108 follows immediately the Output report 107, without Report Count specified in between. In our case parse_new_value_caps() would set erroneously Report Count to 1, after being called on the Output main item. Thus the next Input report size would be calculated wrongly. This is a vendor defined report, which they probably use in the process of recognizing the device. Since then the issue was mitigated a little bit with commit 7096c26a2e48089424fe90956c80c29617bce9f2, when button array value caps were introduced, which stopped modifying state->items.report_count if the parsed item is an array. The issue is still present in the new hidparse.sys (main.c), where the parsing code has been moved with commit a290c5bf7c9ddc92af56231693c6d8f00c3efd7b. It is present in Output report 2. Here is an excerpt: /* Usage (5Ah), */ /* Collection (Logical), */ /* Report ID (2), */ ... /* Report Count (2), */ /* Output (Variable), */ /* Usage (5Ch), */ /* Usage (5Eh), */ /* Unit (Seconds), */ /* Unit Exponent (-3), */ /* Logical Maximum (32767), */ /* Physical Maximum (32767), */ /* Report Size (16), */ /* Output (Variable), */ /* Physical Maximum (0), */ /* Unit, */ /* Unit Exponent (0), */ /* End Collection, */ Since the Output main items are variable, state->items.report_count is still being modified to 1. So the second Output item ends up with two usages, one 16 bit report, and one 0 bit report. This can be seen in the attached log file wine_6.18.log. For Output report 2, the RCnt for Usage 0x5E is 0. The following debug options were used for the log: WINEDEBUG=+timestamp,+pid,+hid,+hidp,+hid_report,+plugplay. The Wine build is 6.18-107-gbcdb28a563d. I've attached the Simucube 2 device descriptor in SC2_Descr.txt. Hope it can help as a real life example of a HID PID device with multiple ReportIDs. Attached also a patch which is fixing the issue (based on the latest master aa629c4c7225166f4ee46476d98702df2e142711). -- 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 11

[Bug 51710] New: 3utools doesn't see iPad
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51710 Bug ID: 51710 Summary: 3utools doesn't see iPad Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aykutboray(a)gmail.com Distribution: --- Created attachment 70586 --> https://bugs.winehq.org/attachment.cgi?id=70586 Bug moment When I wanted to install new IPad OS software 3utools doesn't see my iPad it was connected to pc. -- 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 51987] New: Multiple GUI elements are not rendered when using a theme
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51987 Bug ID: 51987 Summary: Multiple GUI elements are not rendered when using a theme Product: Wine Version: 6.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 70975 --> https://bugs.winehq.org/attachment.cgi?id=70975 All broken This is a follow up to bug 51986. See the attached 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.

1 11

[Bug 52028] New: Regression: Themed contents doesn't displays correctly in some themes
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52028 Bug ID: 52028 Summary: Regression: Themed contents doesn't displays correctly in some themes Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Created attachment 71028 --> https://bugs.winehq.org/attachment.cgi?id=71028 good vs bad Regression test result: 7c9cacd47f969181624b2c5fafd7554188d7fa47 is the first bad commit commit 7c9cacd47f969181624b2c5fafd7554188d7fa47 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Nov 5 14:34:58 2021 +0800 comctl32/button: Correctly place parts for themed group boxes. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/comctl32/button.c | 49 +++++++++++++++++++++++++++---------------------- 1 file changed, 27 insertions(+), 22 deletions(-) Procedure: 1 - Open winecfg 2 -- Apply a theme that presents this issue I've used a modified theme from VLT by evgkursai. Original msstyles file presents this issue too. You can download it here: https://www.deviantart.com/evgkursai/art/VLT-2-0-VS-36103075 -- 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 8

[Bug 52025] New: Custom color configuration is reseted if custom theme is applied
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52025 Bug ID: 52025 Summary: Custom color configuration is reseted if custom theme is applied Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Regression result: 3762a11c81455edee65881702c5c26ae5d3081b3 is the first bad commit commit 3762a11c81455edee65881702c5c26ae5d3081b3 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Thu Nov 4 14:44:47 2021 +0800 uxtheme: Fix loading a different theme when theming is on. When a theme is already active and a user tries to activate another theme, the new theme configuration should be written to the registry so that it's still in effect after a wine reboot. Fix a regression introduced in d290362. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/uxtheme/system.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) Wine 6.20 -> 6.21 Procedure: 1 - Open winecfg 2 - Apply a custom theme, theme used on this test was VLT by evgkursai: https://www.deviantart.com/evgkursai/art/VLT-2-0-VS-36103075 3 - Change any color and apply. On this test, i've changed "Selection Background" ("Fundo da Seleção" in portuguese-brazilian) color 4 - Close winecfg 5 - Open winecfg 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 11

[Bug 51934] New: Battle.Net after login bug
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51934 Bug ID: 51934 Summary: Battle.Net after login bug Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ptg76(a)ukr.net Distribution: --- Created attachment 70899 --> https://bugs.winehq.org/attachment.cgi?id=70899 backtrace log Hi, All! After updates, I cannot log in to Battle.Net nor the Starcraft game directly. After entering username and password it falls into repeating "crash"(?). I've attached the backtrace log file. Any ideas, workarounds, something? Sincerely, Peter -- 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 13

[Bug 32385] New: MSTSC (Remote Desktop) drawing issues
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=32385 Bug #: 32385 Summary: MSTSC (Remote Desktop) drawing issues Product: Wine Version: 1.5.18 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kenjiru.ro(a)gmail.com Classification: Unclassified Created attachment 42734 --> http://bugs.winehq.org/attachment.cgi?id=42734 Drawing issues. When it works, it has some drawing issues. Some windows are not drawn correctly at all, the title bars of some windows are not drawn. I see a lot of messages in the console, but I don't know which ones are to blame. I've attached the 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 3

[Bug 52113] New: Killing Floor 2 : Item Server not connectable
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52113 Bug ID: 52113 Summary: Killing Floor 2 : Item Server not connectable Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maycne.sonahoz(a)posteo.net Distribution: --- Overview: In Killing Floor 2, the Item Server cannot be reached. In consequence, neither the Inventory nor the Store are available from within the game. Steps to Reproduce: 1) Launch Killing Floor 2. 2) In the main menu, an icon should tell the connectivity with the Item Server. That icon shows the server is unreachable. 3) Access the Inventory tab. It should be filled with your custom items, but it always shows empty. 4) Access the Store tab. It should be filled with store offers, but it always shows empty. Build Date & Hardware: Manjaro stable - Xfce - kernel 5.10.79-1 - 2021-11-16 The issue has been happening from a long time now. As for today's reference: - Failed to reach the steps to reproduce the issue with Development Wine: - Development Wine built locally from source - Steam (for Windows) installed through Wine - Steam refuses to install Killing Floor 2 : "invalid platform" - Issue reproduced with: - Steam (for Linux) Beta - Proton-6.21-GE-2 (based on Wine 6.21) Additional Builds and Platforms: Manjaro stable - Xfce - kernel 5.10.79-1 - 2021-11-16 The issue does not (yet) reproduce with: - Steam (for Linux) Beta - Proton 6.3-8 (based on Wine 6.3) -- 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

[Bug 29503] New: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=29503 Bug #: 29503 Summary: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message Product: Wine Version: 1.3.36 Platform: x86 URL: http://www.fileplanet.com/207230/200000/fileinfo/Dark- Horizon-Patch-v1.0.6.1 OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 38206 --> http://bugs.winehq.org/attachment.cgi?id=38206 screenshot (patcher running in virtual desktop) The installer of the patch made for Dark Horizon uses a Stucuk's Setup System according to the file properties. The installer of the community patch made for Original War also uses this kind of patcher, sharing the same problem. The patcher for Dark Horizon consists of nearly 3000 small files. The installation process doesn't take long (15-20 seconds). At some point during the install process, the patcher is interrupted with an error message: 'Setup Thread Error: Canvas does not allow drawing', and the installer quits prematurely. This happens fairly often (maybe 8 times out of 10 attempts), but sometimes the patcher finishes the job without erroring out. Before the error message pops up, text which normally appears inside the installer window also printed and overwritten several hundreds of times in the upper left corner of the screen (see attached screenshot). This happens both in virtual desktop mode and in full-screen. To reproduce the problem with the patcher made for Dark Horizon you don't have to download the demo for the game; the patch can be installed alone in a selected directory anywhere inside a wineprefix. -- 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 5

[Bug 41615] New: Max Payne 1 and 2 crash using glsl=enabled
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=41615 Bug ID: 41615 Summary: Max Payne 1 and 2 crash using glsl=enabled Product: Wine Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Created attachment 55965 --> https://bugs.winehq.org/attachment.cgi?id=55965 backtrace-max-payne-1-glsl Max Payne 1 and 2 crash using glsl=enabled during 1st chapter Both crash during 1st chapter however if use glsl=disabled in wine register works stable both games pass 1st chapter with crashes System Specs Using in Tests Nvidia Drivers 375.10 (run package from nvidia drivers homepage) Xubuntu 16.04 64Bit - Kernel 4.4.0-44 generic (ubuntu mainline) - CPUFreq: Performance CPU: INTEL Pentium G3258 (Haswell 22nm) 4.1Ghz + Artic Cooling Alpine 11 Plus MEMORY: 8GB DDR3 1333 (2x4) Patriot value (dual channel: 21.3 gb/s) GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s) MAINBOARD: MSI H81M E33 -- 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 17

[Bug 38183] New: King of Dragon Pass crashes when loading a saved game
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=38183 Bug ID: 38183 Summary: King of Dragon Pass crashes when loading a saved game Product: Wine Version: 1.7.38 Hardware: x86 URL: http://a-sharp.com/files/KoDP-Tour.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 50954 --> https://bugs.winehq.org/attachment.cgi?id=50954 terminal output Loading a previously saved game at the title screen works properly. Loading a saved game while you are in-game results in a crash. Tested with the GOG version. The crash can be reproduced with the demo/tour version as well. The same problem in Wine 1.2.3/1.4.1/1.6.2/1.7.38. Steps to reproduce the problem with the demo version: Start the installed demo with tour.exe. Click on the highlighted <Tour>, <Skip all>, <Play> buttons. Click the button right next to <Proceed> in the lower right corner. Click <Save>...the game is saved. Now click <Restore> in the options menu and select the previously saved game. The game is loaded without errors but if you click <Proceed> the game crashes. The demo version doesn't allow to load a saved game from the title screen. KoDP-Tour.exe sha1: 445443bd6365f71257abfe0809e9a1932791d1ed -- 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 5

[Bug 26898] New: wine does not show save game screenshots
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=26898 Summary: wine does not show save game screenshots Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: vaniaz(a)msn.com Screenshots are saved in dds format. When saving game, I get the following in console fixme:d3d_surface:surface_convert_format Cannot find a conversion function from format WINED3DFMT_B8G8R8A8_UNORM to WINED3DFMT_DXT1. Saved screenshot is completely black. -- 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 34

[Bug 41653] New: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=41653 Bug ID: 41653 Summary: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging Product: Wine-staging Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donanykey(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56035 --> https://bugs.winehq.org/attachment.cgi?id=56035 Video of flickering picture Dedicating separate bug from https://bugs.winehq.org/show_bug.cgi?id=41635 for Wine-staging. The game works in plain Wine (1.9.21), but with very poor frame rate performance, while with staging - it's much more responsive, but the picture is flickering. Video and log to be attached -- 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 25

[Bug 33309] New: No keyboard input in Slender: The Arrival
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=33309 Bug #: 33309 Summary: No keyboard input in Slender: The Arrival Product: Wine Version: 1.5.27 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 6tsukiyami9(a)gmail.com Classification: Unclassified The title says all about it: the keyboard doesn't work at all in Slender: The Arrival. I can't even try the game itself because I can't get enter the license key and get to the main menu. I guess this may be a clue: fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0x1006a, filter=0x33fc6c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. I'm attaching a full log with WINEDEBUG=-all,+keyboard,+key,+dinput,+message -- 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 15

[Bug 39305] New: Sanitarium
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=39305 Bug ID: 39305 Summary: Sanitarium Product: Wine Version: 1.7.50 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: i30817(a)gmail.com Distribution: --- There are plenty of bugs with sanitarum that are closed 'FIXED' that i'm still experiencing, except if running with the game windowed mode command line switch (-w). For example the game doesn't show graphics with the native fullscreen here (with the open source radeon drivers) unless i specify : wine reg add "HKCU\\Software\\Wine\\Direct3D" /v "OffscreenRenderingMode" /t REG_SZ /d "backbuffer" before running the game (instead of default "fbo") Bug #28625 is also still a problem. In fact, it appears more of a problem because with native fullscreen and that registry setting just moving the mouse at all is liable to freeze the screen and every animation on it, no just pause while moving (the game is still running because i can press ESC to go to the settings menu). This seems like a regression, since bug #28625 is marked as fixed. -- 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 41681] New: King's Bounty crossworlds: DirectX call failed
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=41681 Bug ID: 41681 Summary: King's Bounty crossworlds: DirectX call failed Product: Wine Version: 1.6.1 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lior.inbar(a)sharecare.com Created attachment 56071 --> https://bugs.winehq.org/attachment.cgi?id=56071 terminal Hi, I'me running the game on: Model Name: MacBook Pro Model Identifier: MacBookPro11,4 Processor Name: Intel Core i7 Processor Speed: 2.2 GHz Graphics Intel Iris Pro 1536 MB The games launches fine but in some parts of the map it quits with error: http://i63.tinypic.com/oixkli.png when not running from terminal this game doesn't crash but the graphics are distorted like this: http://tinypic.com/view.php?pic=2iazrb8&s=9#.WCG--eErLGI attached is the terminal output -- 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 9

[Bug 38553] New: Die by the Sword: menus don't drawn unless mouse is moving (Mac OS X only)
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=38553 Bug ID: 38553 Summary: Die by the Sword: menus don't drawn unless mouse is moving (Mac OS X only) Product: Wine Version: 1.7.34 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs140(a)gmail.com A similar issue (Bug 27814) has already been fixed in Wine for Linux. But the problem still exists when running Wine in OS X. Important comments from the Linux bug report: "Béla Gyebrószki (In reply to Ken Thomases from comment #12) > This problem still exists for me on OS X, too. Plain Wine. (If you're > using the tip from this morning, you'll need > <http://source.winehq.org/patches/data/108886> to fix a crash.) Affects > both the Mac driver and the X11 driver. > > In my testing, it was often the case that moving the mouse was not enough to > cause the menu animation to proceed. When this happened, switching away > with Command-Tab would allow the animation to complete. This happened more > often with the Mac driver than the X11 driver, but did affect both. > > Béla, would you be willing to do a "reverse" bisect, where you hunt which > commit fixed it for you? It's hard to tell exactly which commit fixed the problem for me because the game behaves differently between 1.7.13 and .15. The problem is definitely there in 1.7.13. After this patch menus are opened but without that "pull-down animation" and screen refreshing, mouse movement is so sluggish that it makes the game unplayable: http://source.winehq.org/git/wine.git/commit/4c4552c5a1910a9d5adf8eccff0ac6… Finally this commit resolves the previous problem and menus work as intended: http://source.winehq.org/git/wine.git/commit/eef81f5ecc27cac8bc2bf4eacdc093…" -- 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 9

[Bug 50864] New: Incompatibility with Mesa 21 with several games
by WineHQ Bugzilla 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50864 Bug ID: 50864 Summary: Incompatibility with Mesa 21 with several games Product: Wine Version: 6.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bastian.beischer(a)rwth-aachen.de Distribution: --- Arch Linux recently updated mesa to 21, after which I was unable to start most of the games I play through Steams proton (Through the Ages, Race for the Galaxy, Galaxy Trucker, ...). Since proton is based on wine I later found a command line reproducer for the problem by just running "wine game.exe" with the appropriate wine prefix. After noticing that the issues appeared with Mesa 21 I found this on the Mesa gitlab: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3969 My issues are exactly the same. Apparently Mesa added an OpenGL error in this commit / line: https://gitlab.freedesktop.org/mesa/mesa/-/commit/f39fd3dce72eaef59ab39a23b… And it appears that wine fails to correctly handle / catch that error. I can play games again after reverting that change in mesa and recompiling mesa 21. While it was mesa that introduced this regression it appears that it is correct to issue the error, so the mesa developers seem to think that wine should be patched instead (they even made an attempt). Thanks for any help! -- 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 17

[Bug 44989] New: disciples 3 crashing on start
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=44989 Bug ID: 44989 Summary: disciples 3 crashing on start Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimonych85(a)ukr.net Distribution: --- Created attachment 61123 --> https://bugs.winehq.org/attachment.cgi?id=61123 Disciples 3 not working when starting the game it shows me a picture in game but no menu, its stucked -- 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 38173] New: Juiced Dont Start
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=38173 Bug ID: 38173 Summary: Juiced Dont Start Product: Wine Version: 1.7.37 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Created attachment 50923 --> https://bugs.winehq.org/attachment.cgi?id=50923 backtrace juiced Juiced dont start, unable validate settings Wine 1.7.37 Nvidia Drivers 346.47 Linux Mint 17 XFCE Edition 64Bit - Kernel 3.18.0.31 CPU: INTEL Pentium G3220 3.0Ghz MEM: 8GB DDR3 1333 (2x4) Patriot value (128 bit dual channel: 21.3 gb/s) GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s) BOARD: MSI H81M E33 -- 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 30096] New: Setting path doesn't work in Shelltreeview
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=30096 Bug #: 30096 Summary: Setting path doesn't work in Shelltreeview Product: Wine Version: 1.4-rc6 Platform: x86 URL: http://netikka.net/dev/shelltreeview.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ocean04(a)suomi24.fi Classification: Unclassified Delphi has TShelltreeview component. When trying to set path, for example: shelltreeview1.path:='C:\Windows'; -> It sets empty path. Root is set to rfMyComputer. Small sample to reproduce: http://netikka.net/dev/shelltreeview.exe -- 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

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