https://bugs.winehq.org/show_bug.cgi?id=54531
Bug ID: 54531
Summary: jsproxy:jsproxy crashes on Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
jsproxy:jsproxy crashes on Windows 11:
jsproxy.c:52: Test failed: got 3735928559
jsproxy.c:56: Test failed: got 3735928559
jsproxy.c:59: Test failed: got 3735928559
jsproxy.c:60: this is the last test seen before the exception
054c:jsproxy: unhandled exception c0000005 at 004013FA
See https://test.winehq.org/data/patterns.html#jsproxy:jsproxy
Where 3735928559 == 0xdeadbeef
So InternetGetProxyInfo() fails but does not set LastError. Furthermore the
proxy pointer is not initialized either so the test crashes when trying to free
it.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54504
Bug ID: 54504
Summary: psapi:psapi_main - The 32-bit
test_EnumProcessModules() gets a partial copy error on
Windows 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 32-bit test_EnumProcessModules() gets a partial copy
error on Windows 11:
psapi_main.c:133: Test failed: got 0, error 299
psapi_main.c:134: Test failed: expected non-NULL module
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
Where 299 == ERROR_PARTIAL_COPY
This failure is specific to the 32-bit tests running on Windows 11, that is the
64-bit test has other (possibly related) failures, and Windows 10 and lower
don't have failures.
Also this failure has been present ever since the Windows 11 VM was added.
--
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=54686
Bug ID: 54686
Summary: LibvirtTool sometimes fails to update the time
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When reverting to a live snapshot it is necessary to update the VM's time so
certificate checks and more work as expected. This is handled by LibvirtTool.pl
via using the SetTime TestAgent RPC.
However there are some cases where this fails as is evidenced by job 130592:
w10pro64v2004 LocalTime: 2023-03-14 2 10:47:10.744
w10pro64 LocalTime: 2022-12-11 0 14:18:16.343
w10pro64_fr LocalTime: 2023-03-14 2 10:46:42.143
So the time did not get updated on w10pro64 while it did get updated on all of
that job's 4 other VMs. Furthermore there is evidence that during that day's
nightly WineTest runs it is w10pro64v2004 that did not get a time update (or
the time reverted back?).
Failure to update the time can cause test failures so it needs to be reliable.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54685
Bug ID: 54685
Summary: The localized VMs don't have a localized timezone
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The base VM configurations are all in the Minnesota timezone (CST / CDT).
But the localized ones should be in the timezone corresponding to the country.
For instance the French test configuration should be in the CET / CEST
timezone.
But SetWinLocale does not support changing the timezone.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54659
Bug ID: 54659
Summary: d3d8:device & d3d9:device sometimes get floating point
underflow in GenerateRampFromGamma() in Wine
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: ---
d3d8:device & d3d9:device sometimes get an floating point underflow exception
in GenerateRampFromGamma() in Wine:
d3d8:device start dlls/d3d8/tests/device.c
Unhandled exception: floating point underflow in 32-bit code (0x7e91438f).
[...]
Backtrace:
=>0 0x7e91438f in libm.so.6 (+0x2538f) (0x0069ef68)
1 0x7e922d3b in libm.so.6 (+0x33d3b) (0x0069ef68)
2 0x7e55c181 GenerateRampFromGamma+0x51(ramp=00197C4C, gamma=0.000300)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:336] in
winex11.so (0x0069ef68)
3 0x7e55c9b2 X11DRV_XF86VM_GetGammaRamp+0x60(ramp=<internal error>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:519] in
winex11.so (0x0069ef68)
4 0x7e55c9b2 X11DRV_GetDeviceGammaRamp+0x82(dev=<couldn't compute location>,
ramp=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\winex11.drv\xvidmode.c:569] in
winex11.so (0x0069ef68)
5 0x7ea32408 NtGdiGetDeviceGammaRamp+0x88(hdc=<couldn't compute location>,
ptr=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\win32u\dc.c:1247] in win32u.so
(0x0069efb8)
6 0x64a8d74c NtGdiGetDeviceGammaRamp+0x2c(hdc=<couldn't compute location>,
ptr=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\win32u\wrappers.c:280] in win32u
(0x0069efe8)
7 0x6ccf9d3d wined3d_output_get_gamma_ramp+0x4d(output=00140E10,
ramp=00197C4C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\directx.c:1741] in
wined3d (0x0069f028)
8 0x6cd5fcb0 wined3d_swapchain_get_gamma_ramp+0x30(swapchain=00197C30,
ramp=00197C4C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:385] in
wined3d (0x0069f058)
9 0x6cd61190 wined3d_swapchain_init+0x3c0(swapchain=<register EBX not
accessible in this frame>, device=<register EDI not accessible in this frame>,
desc=<internal error>, state_parent=00140D5C, parent=00140D50,
parent_ops=67CDE7D4, swapchain_ops=6CE6933C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:1633] in
wined3d (0x0069f168)
10 0x6cc8d9f3 adapter_gl_create_swapchain+0x73(device=0017B3E8,
desc=0069F2BC, state_parent=00140D5C, parent=00140D50, parent_ops=67CDE7D4,
swapchain=0069F1FC)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\adapter_gl.c:4701] in
wined3d (0x0069f1b8)
11 0x6cd5fdd1 wined3d_swapchain_create+0x41(device=0017B3E8, desc=0069F2BC,
state_parent=00140D5C, parent=00140D50, parent_ops=67CDE7D4,
swapchain=00140D58)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\swapchain.c:1724] in
wined3d (0x0069f208)
12 0x67ccfe84 swapchain_init+0x48(swap_interval=<internal error>,
desc=<internal error>, device=<internal error>, swapchain=<internal error>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\swapchain.c:180] in d3d8
(0x0069f248)
13 0x67ccfe84 d3d8_swapchain_create+0x84(device=001468F0, desc=0069F2BC,
swap_interval=0xffffffff, swapchain=0069F290)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\swapchain.c:199] in d3d8
(0x0069f248)
14 0x67ccc467 device_init+0x217(device=001468F0, parent=00140A90,
wined3d=00140AB0, adapter=0, device_type=D3DDEVTYPE_HAL, focus_window=0003004A,
flags=0x42, parameters=0069F53C)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\device.c:3744] in d3d8
(0x0069f478)
15 0x67ccd649 d3d8_CreateDevice+0xa9(iface=<couldn't compute location>,
adapter=<couldn't compute location>, device_type=<couldn't compute location>,
focus_window=<couldn't compute location>, flags=<couldn't compute location>,
parameters=<couldn't compute location>, device=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\d3d8\directx.c:438] in d3d8
(0x0069f4e8)
16 0x004010ce in d3d8_test (+0x10ce) (0x0069f588)
...
This does not happen in the nightly Wine test runs but impacted at least two
merge requests:
* MR2072, repeatedly
* MR2217, repeatedly
There are three immediate questions:
* Where does the 0.000300 gamma come from?
I don't think such a value makes sense so I suspect it's caused by a bug
somewhere.
* Should xvidmode.c's GenerateRampFromGamma() crash in case of underflow (or
overflow for that matter)?
If not, ComputeGammaFromRamp() should probably be fixed too. Which other
functions have the same issue? (not just in xvidmode.c)
* By default underflows don't cause exceptions. So which piece of code in
d3d8:device does a _control87(0, _EM_UNDERFLOW) ?
Then, why does this failure not happen more often?
The debian11 VM ran the tests multiple times in a row to test various locales:
en -> success
ar:MA -> success
de -> success
fr -> underflow
he:IL -> underflow
hi:IN -> underflow
ja:JP -> underflow
zh:CN -> underflow
While the wineprefix is recreated for each test, all the tests run on the same
X server session. So my theory is that one of the tests in the first three runs
progressively degraded the gamma at the X level, such that all the tests that
followed got a bad gamma from the X server and crashed. Furthermore note that
the first plain 32-bit run ran the full Wine test suite. That may have been a
factor too.
MR2217 caused the following tests to run so the guilty party should be among
them:
d3d8:device d3d9:device ddraw:ddraw1 ddraw:ddraw2 ddraw:ddraw4 ddraw:ddraw7
That explains why this failure does not happen in the nightly Wine test runs:
each is done after restoring the VM to a clean state. Similarly, other merge
requests may run fewer tests so that the gamma does not get degraded that much.
That leaves a mystery though: I don't get this issue on my desktop (fg-deb64)
despite running the tests every night and not ever restarting the X server
(thankfully!). Maybe this gamma issue is caused by a bug that only happens with
the VM environment (likely QXL GPU or dual screen configuration, such that it
does not happen on single-screen Intel GPUs)?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53553
Bug ID: 53553
Summary: F.E.A.R. won't work with DSOAL surround sound
restoration DLL replacement
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dsound
Assignee: wine-bugs(a)winehq.org
Reporter: mr.matt.eastwood(a)gmx.de
Distribution: ---
Steps to Reproduce:
1. Install F.E.A.R. (e.g., "Fear Platinum" from GOG)
2. Get DSOAL from https://github.com/kcat/dsoal and compile dsound.dll
3. Get latest OpenAL-Soft bin from https://openal-soft.org/
4. Unzip soft_oal.dll from its bin\Win32 directory
5. Rename that file to dsoal-aldrv.dll
6. Place both dsoal-aldrv.dll and DSOAL's dsound.dll in same directory as
FEAR.exe
7. Run game
8. Enter sound menu
Expected Results:
When running F.E.A.R. with the DLL replacement DSOAL for surround sound
restoration, the advanced sound options "Enable HW mixing", "Enable EAX 2.0"
and "Enable EAX Advanced HD" should be available in the sound menu and surround
sound including EAX effects should work.
Current Results:
The sound options remain greyed-out.
Observations:
F.E.A.R. won't load dsound.dll from anywhere but syswow64. If one places the
DSOAL dsound.dll there (replacing Wine's own), and then sets dsound.dll to
"native" e.g. through winecfg, everything works. Screenshot:
If one sets dsound.dll to "native" e.g. through winecfg and then loads the game
without replacing Wine's dsound.dll in syswow64 (but with the DSOAL files in
the F.E.A.R. folder): "Failed to initialize sound driver 'SndDrv.dll' on
startup. Screenshot: https://paste.pics/I4DO0. No sound during game or menus,
only during intro movie. Available sound options: https://paste.pics/I4DOD
--
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.
https://bugs.winehq.org/show_bug.cgi?id=49915
Bug ID: 49915
Summary: can not register COM server
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ysong2180(a)yahoo.com
Distribution: ---
Created attachment 68286
--> https://bugs.winehq.org/attachment.cgi?id=68286
two log files. one is the winecfg log. The other one is the application log
I tried to install an windows application on Ubuntu 20.04. The installer can
run and install files. But it fails at the end when it tries to register COM
servers. It is a win32 application. I used winecfg to create a win32
wineprefix and used the win32 wineprefix to start the 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.
https://bugs.winehq.org/show_bug.cgi?id=54677
Bug ID: 54677
Summary: Wine cannot find tools in tool dir when cross
compiling
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: ale.schenberg(a)yandex.com
Distribution: ---
Created attachment 74193
--> https://bugs.winehq.org/attachment.cgi?id=74193
config.log
Hello. When trying to cross build wine, configure's execution breaks due to it
to not find wine tools in the tools dir.
My building command:
LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so ./configure
--host=i686-gnu-linux --with-wine-tools=tools/
I attached config.log, although it appears to contain no useful information.
The bug applies to wine 8.3 and any other wine version that I tested (such as
1.9)
I think its worthy to mention that cross build it is more a necessity imposed
by the configure script than my wish. As I am forced to pass
"LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so" to configure (if not, the
building won't be able to run any auxiliary 32bit components, such as makedep,
unless I statically build them), configure demands the use of host, and then of
--with-wine-tools
--
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.
https://bugs.winehq.org/show_bug.cgi?id=47000
Bug ID: 47000
Summary: Make WineHQ available as flatpak in Flathub
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: yousifjkadom(a)yahoo.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Hi.
I would like, here, to suggest to make WineHQ available as flatpak in Flathub.
This will be very useful since flatpak is secure & sandboxed, so user will be a
way from infect heir/his PC by a virus or spywar. If flatpak Wine run a virus,
then it will be like if Wine sandboxed by firejail run such virus.
Moreover, flatpak can minimize time & efforts in packaging because it is a
generic package working in many Linux distro regardless OS version.
Also, Wine contain huge number of 32 bit packages that are, mostly, not needed
by any other application.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=54674
Bug ID: 54674
Summary: Add Flatpak to Download page
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: peter.eszlari(a)gmail.com
Distribution: ---
Since February 2022 Wine has been available as a Flatpak.
To try it:
0. ($ apt install flatpak)
1. $ flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
2. $ flatpak install org.winehq.Wine
3. $ flatpak run org.winehq.Wine prog.exe
build manifest source: https://github.com/flathub/org.winehq.Wine
I think it would make sense to add this to list of binary packages on:
https://wiki.winehq.org/Download
(Note: Wine cannot be found on the Flathub web interface at
https://flathub.org, because only GUI apps are listed there, not CLI apps.)
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37640
Bug ID: 37640
Summary: Opening Windroy and it crashes.
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fholiveira1(a)hotmail.com
Distribution: ---
Created attachment 50094
--> https://bugs.winehq.org/attachment.cgi?id=50094
Extract from Wine report of bug.
I was trying to open Windroy and it crashes. The system open a bug report,
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.