https://bugs.winehq.org/show_bug.cgi?id=52772
Bug ID: 52772
Summary: winetricks wmp9 fails to install (kernel32 version
string doesn't match windows version)
Product: Wine
Version: 6.6
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: download, Installer, regression
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.…
[View More]org
Reporter: austinenglish(a)gmail.com
Regression SHA1: 04a8213ba9e3b8aa1f980d19b240929948da5abe
Distribution: ---
After:
commit 04a8213ba9e3b8aa1f980d19b240929948da5abe
Author: Arkadiusz Hiler <ahiler(a)codeweavers.com>
Date: Tue Apr 20 14:38:09 2021 +0300
kernel32: Update version to Win 10.
This fixes the game Evil Genius 2 complaining about unsupported OS.
Signed-off-by: Arkadiusz Hiler <ahiler(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
`winetricks wmp9` no longer installs; instead an error dialog saying that <=
WINXP is required:
0124:trace:text:DrawTextExW L"This version of Windows Media Player can be
installed only on Windows 98 Second Edition, Windows Millennium Edition,
Windows 2000, Windows XP, and Windows .NET Server.", -1, [(0,0)-(237,52)]
00000850
winetricks is setting the windows version of the wineprefix to winxp before
installing, but it seems that the installer is checking the kernel32 version
strings, and failing to install as a result.
Still present in wine-7.5-175-g0de8d01b09b, reverting the patch allows the
installer to proceed.
I'm not sure what we can do here. Currently the version string is hardcoded
regardless of what version of windows we're reporting. I'd guess either we need
to allow overriding the string/shipping different resource files for different
reported windows versions, or call this a WONTFIX?
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54319
Bug ID: 54319
Summary: wrc doesn't find locales.nls
Product: Wine
Version: 8.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: steve.schnepp(a)gmail.com
Distribution: ---
Created attachment 73883
--> https://bugs.…
[View More]winehq.org/attachment.cgi?id=73883
tools/wrc/wrc.c.diff
When building 8.0rc4 in a i386 chroot I have an error :
tools/wrc/wrc -u -o dlls/aclui/aclui.res --nostdinc --po-dir=po
-Idlls/aclui -Iinclude -Iinclude/msvcrt -D_UCRT \
-D__WINESRC__ dlls/aclui/aclui.rc
Error: unable to load locale.nls
make: *** [Makefile:1459: dlls/aclui/aclui.res] Error 2
If I launch the command with a --nls-dir=nls it works. It actually works with
*any* directory.
It seems that the 1st NULL is never replaced correctly in the line 145 of
tools/wrc/wrc.c.
const char *nlsdirs[3] = { NULL, NLSDIR, NULL };
When I replace it with ...
const char *nlsdirs[3] = { "whatever", NLSDIR, NULL };
... it does work. But only if wine is already installed, as there's a
-DNLSDIR="\"/opt/wine-devel/share/wine/nls\""
when compiling tools/wrc/wrc.c
So, I'm using
const char *nlsdirs[3] = { "nls", NLSDIR, NULL };
and it does work even without the wine package being installed.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54269
Bug ID: 54269
Summary: WM_GETMINMAXINFO message should be sent when manually
resizing the window
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: 399989567(a)qq.com
…
[View More]Distribution: ---
Created attachment 73834
--> https://bugs.winehq.org/attachment.cgi?id=73834
demo
In actual application, it may be necessary to limit the maximum or minimum size
of the window. The maximum or minimum size of the window is controlled by the
WM_GETMINMAXINFO message. Therefore, in a form that needs to control the
maximum or minimum size of the window, this message needs to be mapped.
I wrote a 32-bit program running under Windows 10, when a WM_GETMINMAXINFO
message is received, the text position of the output changes.
This works fine under windows10, but in wine, when the window is resized, the
program cannot receive the WM_GETMINMAXINFO message
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54099
Bug ID: 54099
Summary: Stdout redirection broken when running Linux binaries
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 73634
--> …
[View More]https://bugs.winehq.org/attachment.cgi?id=73634
Test program
When running Linux binaries form inside Wine, using CreateProcessA, and
redirecting stdout, it doesn't work.
It works fine when executing Windows binaries.
See attached test program.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=52681
Bug ID: 52681
Summary: Google Chrome Stopped working after 7.2
Product: Wine-staging
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ndk+whq(a)esperanca.biz
CC: leslie_alistair(a)hotmail.com, z.…
[View More]figura12(a)gmail.com
Distribution: ---
Hi!
I have been using Google Chrome Portable for some time now.
It was working with some options (--no-sandbox) right until wine-staging-7.3.
It stopped starting after 7.3. The installation process from portableapps is
smooth, it just does not want to start (no 'usual' black screen, just fails
starting).
I have tried to use old wine directory, new wine directory, installed corefonts
as someone suggested in some of the bugs, etc.
I also have tried to use wine-staging-7.4 with no luck.
After I downgraded back to 7.2 - chrome started working again with
--no-sandbox.
The system: the latest Gentoo x64.
Video card: AMD Radeon 480 (amdgpu Xorg driver).
Command: WINEPREFIX=/path/to/wine wine /path/to/chrome --no-sandbox
Expected Behavior (works until wine-staging-7.3):
Chrome starts and is usable
Actual Behavior (wine-staging-7.3; wine-staging-7.4):
Chrome fails to start.
Let me know if there are any debug info is needed (preferrably which options to
enable for WINEDEBUG).
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54292
Bug ID: 54292
Summary: Dumping shaders using VKD3D_SHADER_DUMP_PATH= fails
with the bundled vkd3d
Product: Wine
Version: 8.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
…
[View More]Distribution: ---
The problem is in the bundled vkd3d, couldn't find the corect component for
that.
Also I'm using a PE enabled build (if that is relevant).
IIUC the bundled vkd3d code is built against the windows runtime and therefore
the shader dump path requires backslash instead of slash.
The following patch seems to be enough to restore functionality
diff --git a/libs/vkd3d/libs/vkd3d-shader/vkd3d_shader_main.c
b/libs/vkd3d/libs/vkd3d-shader/vkd3d_shader_main.c
index 7e153bce27a..4c0aa48aa55 100644
--- a/libs/vkd3d/libs/vkd3d-shader/vkd3d_shader_main.c
+++ b/libs/vkd3d/libs/vkd3d-shader/vkd3d_shader_main.c
@@ -376,7 +376,7 @@ static void vkd3d_shader_dump_blob(const char *path,
const char *prefix,
id = InterlockedIncrement(&shader_id) - 1;
- snprintf(filename, ARRAY_SIZE(filename), "%s/vkd3d-shader-%s-%u.%s",
path, prefix, id, suffix);
+ snprintf(filename, ARRAY_SIZE(filename), "%s\\vkd3d-shader-%s-%u.%s",
path, prefix, id, suffix);
if ((f = fopen(filename, "wb")))
{
if (fwrite(data, 1, size, f) != size)
I think it would also be nice to print failure details on the failure path.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=53539
Bug ID: 53539
Summary: maybe a --with-wine-64 build should call widl with
-win32 option
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
Assignee: wine-bugs(a)winehq.org
Reporter: j-r(a)online.de
Distribution: -…
[View More]--
Using just --with-wine-64 results in a Makefile calling widl from the win64
build directory without any target architecture specified resulting in early
build failure:
...
WIDL dlls/actxprxy/actxprxy_activscp_p.c
WIDL dlls/actxprxy/actxprxy_activscp.h
CC dlls/actxprxy/actxprxy_activscp_p.cross.o
dlls/actxprxy/actxprxy_activscp_p.c:9084:2: error: #error Invalid build
platform for this proxy.
9084 | #error Invalid build platform for this proxy.
| ^~~~~
Hacking Makefile to add -win32 to the widl invocation works around this. I have
no clue whether that is the right solution, though.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=52567
Bug ID: 52567
Summary: 16-bit version of Project Pluto Guide 8.0 crashes on
start with division by zero exception
Product: Wine
Version: 7.1
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
…
[View More]Distribution: ---
Created attachment 71888
--> https://bugs.winehq.org/attachment.cgi?id=71888
Console output
Steps to reproduce:
1. Run `wine setup16.exe`
2. Select "Windows 3.1 software (16 bit)"
3. Run `cd ~/.wine/drive_c/GUIDE8 && wine guide8a.exe`
Console output is 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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54393
Bug ID: 54393
Summary: rFactor 2 dedicated server: Severe performance
degradation with additional clients joining
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madbad82(a)…
[View More]gmail.com
Distribution: ---
I'm using the rFactor2 dedicated server to host races for our team on a Fedora
system.
Everything seems fine up to 6 drivers joining, above that everyone ping started
to rise each time a new driver entered the server and we reached 500/600 ping
with 13 driver on the server.
I could still ping google from the server with low numbers.
The ping issue seemed to be strictly related to the number of drivers.
I know I was able to host with this same system on windows races for up to
13/14 drivers without issues in the past.
Some data about the test:
Speed-test for the machine running the dedicated server:
* 50 Mbps download speed
* 17 Mbps upload speed
* 8ms ping
Whie running the dedicated server the band usage during the test was
* lower than 2 Mbps upload
* lower than 2 Mbps upload
RAM used 4 Gb used out of 12 of RAM
CPU at 40% (none of threads were maxed)
I remember there being a similar issue with the game itself related to
networking, operations not sure if this may be somewhat related:
https://bugs.winehq.org/show_bug.cgi?id=48668
Let me know if you need any other info to investigate the bug.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=54388
Bug ID: 54388
Summary: wine64: crashing avaya ip office
AdminCD_11.1.2.0.0_Build_239 Manager.exe
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vmxevilstar(a)gmail.com
…
[View More]Distribution: ---
Created attachment 73952
--> https://bugs.winehq.org/attachment.cgi?id=73952
crash dump
Dear Maintainer,
If you want I can give you the installation file just please tell me how can I
send you 1.6G of AdminCD_11.1.2.0.0_Build_239.tgz
I find it comfortable to use the windows desktop emulation.
I have installed the required jdk-19_windows-x64_bin.msi and winetricks install
dotnet45 inside wine
After that I have successfully installed Avaya Ip Office unzipping the
installation zip and launching wine64 setup.exe
tried to launch Manager.exe from
\Program Files (x86)\Avaya\IP Office Admin Suite\Manager\Manager.exe
what I have got is the program crashing
Thanks for your time
--
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.
[View Less]