wine-bugs

wine-bugs@winehq.org

1 participants
158782 discussions

[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 54694] New: Marvel's Spider-Man Remastered requires Windows 10 version 1909, build 18363 (or newer)
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54694 Bug ID: 54694 Summary: Marvel's Spider-Man Remastered requires Windows 10 version 1909, build 18363 (or newer) Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- As the title says. 8.3-258-g81976e5c3f4 -- 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 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 54419] New: RICHED20: Word Break Procedure of Rich TextBox should consider punctuation
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54419 Bug ID: 54419 Summary: RICHED20: Word Break Procedure of Rich TextBox should consider punctuation Product: Wine Version: 8.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: katayama.hirofumi.mz(a)gmail.com Distribution: --- Created attachment 73977 --> https://bugs.winehq.org/attachment.cgi?id=73977 the patch to the word break procedure of rich textbox The default word break procedure of rich textbox didn't consider punctuation. This patch will add punctuation check to the default word break procedure. -- 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 1

[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

[Bug 54671] New: netcap.exe crashes on unimplemented function npptools.dll.CreateBlob
by WineHQ Bugzilla 16 Mar '23

16 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54671 Bug ID: 54671 Summary: netcap.exe crashes on unimplemented function npptools.dll.CreateBlob Product: Wine Version: 8.3 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 74187 --> https://bugs.winehq.org/attachment.cgi?id=74187 Console output netcap.exe is the "Microsoft Network Monitor capture utility". It was included in the Windows XP Service Pack 2 Support Tools. Steps to reproduce: 1. Create a 32-bit Wine bottle and set the Windows version to XP. 2. Run `wine WindowsXP-KB838079-SupportTools-ENU.exe`. 3. Run `wine 'C:\Program Files\Support Tools\netcap.exe'`. The program will not start. $ sha256sum WindowsXP-KB838079-SupportTools-ENU.exe 7927e87af616d2fb8d4ead0db0103eb845a4e6651b20a5bffea9eebc3035c24d -- 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 1

[Bug 22675] New: TechSmith Camtasia player fails to open.
by wine-bugs＠winehq.org 15 Mar '23

15 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=22675 Summary: TechSmith Camtasia player fails to open. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mattj10973(a)hotmail.co.uk Created an attachment (id=27925) --> (http://bugs.winehq.org/attachment.cgi?id=27925) The program (MATHSWATCH), it's embedded player, the Tech Smith Camtasia player (Clip 102 etc.), and the error message. I recently purchased a revision CD for my GCSE Mathematics course, and it states the CD is compatible with Windows 98SE/Me/2000/XP/Vista. I try to run it through Lucid Lynx, but I get an error message. I'm new to Linux and open source software in general, and have pretty much zilch coding or advanced knowledge of my new system, so sorry in advance if I've done anything incorrectly, or failed to understand some of the site's instructions. Error message attached, thanks :) -- 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 54635] New: libwine backward compatibility
by WineHQ Bugzilla 14 Mar '23

14 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54635 Bug ID: 54635 Summary: libwine backward compatibility Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winecrt0 Assignee: wine-bugs(a)winehq.org Reporter: a.heider(a)gmail.com Distribution: --- v8.3 finally removed libwine. Older winegcc builds automatically link against it (just __wine_dll_register(a)WINE_1.0 in out case). Newer winegcc builds don't link against it anymore, it looks like since f6a363bc4108f3d45b7a5bac706d10579f4d2772 "winecrt0: Get rid of constructor support." v5.7. We build downloadable releases and would like to keep maximum binary compatibility. Building with >=v5.7 would likely avoid the issue, but I guess binaries won't work on older WINE versions then. For the record: Ubuntu 18.04 LTS is about to go unsupported, 20.04 LTS ships v5.0. Our current CI setup uses 20.04, so v5.0, to build releases. Is there something we can do to make built binaries work on >=v5.0? Any suggestions how to archive that? Something on our end? Or maybe WINE can get a compatibility addition to skip the libwine.so.1/__wine_dll_register(a)WINE_1.0 symbol or something? Thanks! Andre -- 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 37056] New: Rapture3D requires native dsound.dll in order to change sound layout.
by wine-bugs＠winehq.org 14 Mar '23

14 Mar '23

http://bugs.winehq.org/show_bug.cgi?id=37056 Bug ID: 37056 Summary: Rapture3D requires native dsound.dll in order to change sound layout. Product: Wine Version: 1.7.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: El_Diablo2(a)gmx.de Created attachment 49248 --> http://bugs.winehq.org/attachment.cgi?id=49248 Error message with builtin dsound.dll With builtin dsound UserLayout.exe complains it cannot change the soundcard configuration. No interessting (default channels) debug 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 7

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