wine-bugs November 2022

wine-bugs@winehq.org

1 participants
3243 discussions

[Bug 52948] New: gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=52948 Bug ID: 52948 Summary: gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - test_EnumFonts() fails on Arial Bold on Windows in Russian: font.c:5409: Test failed: font Arial Bold is not enumerated font.c:5412: Test failed: expected FW_BOLD got 400 font.c:5419: Test failed: font Arial Bold Italic is not enumerated font.c:5421: Test failed: expected Arial got Arial Bold font.c:5422: Test failed: expected FW_BOLD got 400 https://test.winehq.org/data/patterns.html#gdi32:font Maybe this can happen in other locales, but among those that are tested this only happens with the Russian one (w10pro64-ru). -- 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 51848] New: Performance Regression in Secondhand Lands
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=51848 Bug ID: 51848 Summary: Performance Regression in Secondhand Lands Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: escomk3(a)hotmail.com Distribution: --- After 4261369e5d8 [1], FPS will be near zero, and the game area will be black, with the actual should-be content sometimes appearing and disappearing. Standard output with default'ish debug channels doesn't show any difference with a build prior to this commit. 1. https://source.winehq.org/git/wine.git/commit/4261369e5d8f1d71e8d2074747515… -- 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 54003] New: vbscript:run sometimes fails on Windows UTF-8 locales
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54003 Bug ID: 54003 Summary: vbscript:run sometimes fails on Windows UTF-8 locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com vbscript:run sometimes fails on UTF-8 locales: === w10pro64_en_AE_u8 (64 bit report) === vbscript: run.c:1206: Test failed: api.vbs: L"Err.number = 0" run.c:1206: Test failed: api.vbs: L"Err.description = " run.c:1206: Test failed: api.vbs: L"Err.number = 0" See https://gitlab.winehq.org/wine/wine/-/merge_requests/1534 Strangely enough so far this has not happened in the nightly WineTest runs but it did happen in another unrelated merge request (MR!1561). According to Nikolay (probably s/testChrError/testCStrError/): > This is happening on utf-8 locale, in testChrError(). > Needs to be fixed, but unrelated to this MR. -- 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 53172] New: advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53172 Bug ID: 53172 Summary: advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales: registry.c:558: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of 'foobar' or x's, data_count=21 registry.c:576: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of 'foobar' or x's, data_count=21 https://test.winehq.org/data/patterns.html#advapi32:registry The line 558 and 576 failures happen about with the same frequency (~13% each) but independently from each other so that most times there is at most one in the report. And they only happen in the TestBot's two UTF-8 test configurations: w10pro64-en-AE-u8 and w10pro64-hi-u8. -- 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 54019] New: The 64-bit ntdll:wow64 fails on Windows 11
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54019 Bug ID: 54019 Summary: The 64-bit ntdll:wow64 fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit ntdll:wow64 fails on Windows 11. There are two failure modes: wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 / 00000013640C5000 wow64.c:273: Test failed: wrong len 0 wow64.c:290: Test failed: wrong len 0 wow64.c:312: Test failed: wrong len 0 wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 75cec0-75d884 wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210 wow64.c:321: Test failed: wrong CommandLine ptr 0 / 75cec0-75d884 wow64.c:321: Test failed: wrong CommandLinelen 0 / 66 wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 75cec0-75d884 wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210 wow64.c:323: Test failed: wrong Desktop ptr 0 / 75cec0-75d884 wow64.c:323: Test failed: wrong Desktoplen 0 / 30 wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 75cec0-75d884 wow64.c:326: Test failed: wrong size 0 / 3222 wow64.c:338: Test failed: wrong len 0 wow64.c:339: Test failed: BeingDebugged is 0 or with 2 extra failures and different values: wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 / 000000A7ECDDA000 wow64.c:273: Test failed: wrong len 0 wow64.c:290: Test failed: wrong len 0 wow64.c:291: Test failed: BeingDebugged is 117 wow64.c:309: Test failed: wrong ptr32 0000000000000000 / 00000298B3F80000 wow64.c:312: Test failed: wrong len 0 wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 0-9c4 wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210 wow64.c:321: Test failed: wrong CommandLine ptr 0 / 0-9c4 wow64.c:321: Test failed: wrong CommandLinelen 0 / 66 wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 0-9c4 wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210 wow64.c:323: Test failed: wrong Desktop ptr 0 / 0-9c4 wow64.c:323: Test failed: wrong Desktoplen 0 / 30 wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 0-9c4 wow64.c:326: Test failed: wrong size 0 / 3112 wow64.c:338: Test failed: wrong len 0 wow64.c:339: Test failed: BeingDebugged is 117 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The values are pretty stable from one run to the next but do change from time to time (causing false positives). Note also that the 32-bit version fails on Windows 11 too. -- 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 52895] New: advapi32:service - EnumServicesStatusA() does not support UTF-8 on Windows?
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=52895 Bug ID: 52895 Summary: advapi32:service - EnumServicesStatusA() does not support UTF-8 on Windows? Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:service fails on Windows with a UTF-8 codepage: service.c:1283: Test failed: Expected success, got error 8 service.c:1285: Test failed: Expected some returned services service.c:1312: Test failed: Expected the needed buffer size for this one service service.c:1313: Test failed: Expected fewer services to be returned service.c:1314: Test failed: Expected ERROR_MORE_DATA, got 1783 service.c:1326: Test failed: Expected the needed buffer size for this one service service.c:1327: Test failed: Expected fewer services to be returned service.c:1328: Test failed: Expected a resume handle service.c:1329: Test failed: Expected ERROR_MORE_DATA, got 1783 service.c:1340: Test failed: Expected success, got error 8 service.c:1342: Test failed: Expected 559038737 services to be returned service.c:1610: Test failed: Expected success, got error 8 service.c:1627: Test failed: Expected the needed buffer size service.c:1628: Test failed: Expected fewer services to be returned service.c:1629: Test failed: Expected ERROR_MORE_DATA, got 1783 service.c:1641: Test failed: Expected the needed buffer size service.c:1642: Test failed: Expected fewer services to be returned service.c:1643: Test failed: Expected a resume handle service.c:1644: Test failed: Expected ERROR_MORE_DATA, got 1783 service.c:1655: Test failed: Expected success, got error 8 service.c:1657: Test failed: Expected 559038737 services to be returned service.c:1702: Test failed: Expected success 8 https://test.winehq.org/data/patterns.html#advapi32:service The first failure is an ERROR_NOT_ENOUGH_MEMORY in this call: services = HeapAlloc(GetProcessHeap(), 0, needed); bufsize = needed; needed = 0xdeadbeef; returned = 0xdeadbeef; SetLastError(0xdeadbeef); ret = EnumServicesStatusA(scm_handle, SERVICE_WIN32, SERVICE_STATE_ALL, services, bufsize, &needed, &returned, NULL); Where needed was calculated from a previous call (30890 in my case). So the buffer should be big enough but EnumServicesStatusA() fails anyway. I tried increasing the buffer size to the max 256KB but EnumServicesStatusA() still complains about insufficient memory which does not make sense. Later, when given a resume handle, the tests return RPC_X_BAD_STUB_DATA (1783) instead of ERROR_MORE_DATA (234). So this looks like the underlying RPC code that accesses the service control manager is buggy and does not support UTF-8. So win_skip() the whole thing on the first failure? Move the resume test with the RPC_X_BAD_STUB_DATA first and skip if that fails? -- 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 53461] New: advapi32:service - test_EventLog() fails on Windows 10 2004 and 2009
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53461 Bug ID: 53461 Summary: advapi32:service - test_EventLog() fails on Windows 10 2004 and 2009 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:service - test_EventLog() fails on Windows 10 2004 and 2009: service.c:2751: Test failed: got 0x1 --> SERVICE_STOPPED service.c:2753: Test failed: got 0 service.c:2757: Test failed: got 0x42b --> ERROR_PROCESS_ABORTED service.c:2761: Test failed: got 0 https://test.winehq.org/data/patterns.html#advapi32:service The failures appear to be happening because the EventLog service is stopped following some sort of error (crash?). These failures are systematic when running WineTest.exe but don't happen when running advapi32:service on its own. So it seems likely that some other test is causing EventLog to crash. -- 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 53460] New: advapi32:service regularly fails on Windows when services stop / start
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53460 Bug ID: 53460 Summary: advapi32:service regularly fails on Windows when services stop / start Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:service regularly fails on Windows when services stop / start. Because this may happen at any time the failures can take many forms: service.c:1729: Test failed: Expected a process id for this running service (sppsvc) service.c:1746: Test failed: Active services mismatch 4294967295 service.c:1747: Test failed: Inactive services mismatch 1 or service.c:1729: Test failed: Expected a process id for this running service (SgrmBroker) ... or service.c:1746: Test failed: Active services mismatch 1 service.c:1747: Test failed: Inactive services mismatch 4294967295 or service.c:1342: Test failed: Expected 114 services to be returned service.c:1612: Test failed: Expected the same number of service from this function or service.c:1729: Test failed: Expected a process id for this running service (edgeupdate) or service.c:1729: Test failed: Expected a process id for this running service (MapsBroker) or service.c:1729: Test failed: Expected a process id for this running service (W32Time) or service.c:1729: Test failed: Expected a process id for this running service (BITS) or service.c:1729: Test failed: Expected a process id for this running service (DoSvc) https://test.winehq.org/data/patterns.html#advapi32:service The service names give a hint as to what happened: * An Edge update got triggered: edgeupdate, probably BITS too. * A time synchronization happened: W32Time. * Some application caused the on-demand "Downloaded Maps Broker" service to start: MapsBroker. * Something caused Windows Update Delivery Optimization to start (despite it being disabled in the settings): DoSvc. * The 'System Guard Runtime Monitor Broker Service' got started for some reason: SgrmBroker. * The 'Microsoft Software Protection Platform Service' which is involved in the license checking got started: sppsvc. So I don't think it would be reasonable to disable all these services. We would still likely have a steady trickle of other services causing trouble, and we'd have the problem again when a new Windows version introduces another service. Instead advapi32:service should be more resilient. That may mean accepting small variations in the number of running services, or checking that a service is still running before complaining that it does not have a pid. -- 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 53562] New: SWAT 4: mouse wrapping issues
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53562 Bug ID: 53562 Summary: SWAT 4: mouse wrapping issues Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matheus.venturini(a)acad.ufsm.br Distribution: --- When beginning a mission in SWAT 4, the mouse will (most often) not allow you to fully rotate your vision in 360 degrees. This can be "fixed" by simply right-clicking, which will cause it to start acting normal. I've had times where this did not occur when starting a mission so I can't say it's a "can always reproduce" issue, and sometimes, very sporadically, the mouse starts acting faulty again during gameplay for seemingly no reason. Doing a search, I found an entry for the same issue in Codeweavers' forum: https://www.codeweavers.com/compatibility/crossover/forum/swat-4?msg=108881 The fix suggested in that page, to set "MouseWarpOverride" to "force_edge" in the registry, was not necessary since doing a right-click will make it go back to normal. Apparently some other games are also affected (GTA Vice City and Bioshock according to the discussion in https://forum.winehq.org/viewtopic.php?t=29663). I will try to reproduce the issue and attach the log file. -- 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 33008] New: UDP listening on specific IP address does not work properly
by wine-bugs＠winehq.org 17 Mar '23

17 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=33008 Bug #: 33008 Summary: UDP listening on specific IP address does not work properly Product: Wine Version: 1.5.24 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: decimusmaximus(a)seznam.cz Classification: Unclassified Wine updated from 1.5.6 to 1.5.24. My app uses UDP listening on specific address (not 0.0.0.0). It is running on machine with NAT, there are two interfaces with IP A.A.A.A (public) and IP B.B.B.B (private) My app is set to listen only on one IP address, IP A.A.A.A It works properly on Wine 1.5.6. Traffic from subnet B.B.B.B is NATed to A.A.A.A interface and application running in wine receives it correctly. After update to 1.5.24 it does not work anymore. Application does not receive data from private subnet B.B.B.B, however it works properly for traffic incoming on A.A.A.A interface. Please see attached schema. results of "netstat --listening" with Wine 1.5.6 it is listening on A.A.A.A address correctly. with Wine 1.5.24 it is listening on 0.0.0.0 (obviously incorrect, socket binding is set to A.A.A.A address in application and although it is saying 0.0.0.0 app does not receive any data from B.B.B.B network) This application has to be listening only on one interface and do not mix public and private addresses. In this case it is not accessible for clients in private network, so it is critical bug. Main strange thing is, that it is listening on all addresses 0.0.0.0 although socket binding in application is set to address A.A.A.A -- 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 33

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 2022