https://bugs.winehq.org/show_bug.cgi?id=50869
Bug ID: 50869
Summary: Regressions caused by new start.exe behaviour in Wine
6.5 (stdout redirect, killing inferior, wine start
/unix)
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)robbertvanderhelm.nl
Distribution: ---
I noticed a few regressions and new weird behaviours after updating to Wine 6.5
with regards to launching applications now that everything gets launched
through
start.exe:
1. When launching Winelib applications all STDOUT output gets lost. I tested
this with a simple C++ file compiled with wineg++ that tries to print some
text using both `printf()` and `std::cout`. Printing to STDERR using
`std::cerr` still works fine.
2. When spawning a Wine child process from another application, you can no
longer kill that child process by raising SIGINT or SIGKILL for the pid of
the child. In Wine 6.5 this now kills the start.exe process, but it leaves
the inferior process running in the background. To reproduce this, run `wine
notepad&` in `fish` (bash seems to kill the child process by itself), use
`ps -aux | grep notepad` or `jobs` to find the pid of the process just named
`notepad`, and then run `kill -SIGKINT <pid>` (or with SIGKILL). Even though
the process launched using `wine notepad&` has exited, Notepad is still
running in the background.
3. (duplicate of bug 50867, but I still wanted to mention it here for
completeness' sake) Launching binaries with Wine from the GUI by clicking on
them (using the bundled wine.desktop) no longer works. This uses
`wine start /unix`, which was already reported to no longer work as of Wine
6.5 in the other issue because `ShellExecuteEx` cannot find the file.
4. And lastly, as discovered by @stefand, `wine https://google.com` now
launches
the regular system browser. This is probably not really a bug as much as a
consequence of the start.exe change, but I just wanted to mention it.
Please let me know if I should split this up into separate tickets.
--
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=50352
Bug ID: 50352
Summary: Maximum sockets per process is set very low
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: skreech(a)skree.ch
Distribution: ---
Created attachment 68942
--> https://bugs.winehq.org/attachment.cgi?id=68942
TWGS warning at startup
Within wine-5.22/dlls/ws2_32/socket.c, the maximum number of sockets per
process is set and used like so:
> #define WS_MAX_SOCKETS_PER_PROCESS 128 /* reasonable guess */
and:
> lpWSAData->iMaxSockets = WS_MAX_SOCKETS_PER_PROCESS;
This became relevant when I ran the TradeWars 2002 game server (TWGS) under a
maximum license allowing 100 simultaneous players. On startup, it logs a
message warning that the OS's number of sockets per process is limited to 128,
therefore no more than 63 players will be able to connect. This makes sense,
since two sockets are required per player connection, and one SysOp connection
is reserved.
Changing WS_MAX_SOCKETS_PER_PROCESS to 1024 and recompiling WINE results in
TWGS not experiencing this limit and not giving the warning.
Also, I tested TWGS under ReactOS and did not experience limit nor warning.
Peeking into their socket.c, I notice that their limit is set to 32767, or 0,
depending:
https://github.com/reactos/reactos/search?q=iMaxSockets
It seems likely that WS_MAX_SOCKETS_PER_PROCESS should be set to 32767 here if
any value is being set, given that the underlying OS should be the one imposing
its own limits or lack of limit.
--
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=44202
Bug ID: 44202
Summary: undname.c fails to parse symbols with rvalue-reference
semantics '&&'
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shulgaaa(a)gmail.com
Distribution: ---
For example, the symbol
??4QDnsDomainNameRecord@@QAEAAV0@$$QAV0@@Z
should be de-mangled as:
public: class QDnsDomainNameRecord & __thiscall
QDnsDomainNameRecord::operator=(class QDnsDomainNameRecord &&)
undname returns NULL
--
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=52616
Bug ID: 52616
Summary: SteelSeries GG Fails to install properly and refuses
to open.
Product: Wine-staging
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: upton.upton.joseph(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Different processes seem to fail during the installation. Random each time.
On the first boot I'm met with a black screen, using bottles I can make it show
up but I need to reset the PC to get the device to show.
This is normal but after that the program will NOT boot for any reason.
--
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=52583
Bug ID: 52583
Summary: ApiSetView does not display export ordinals correctly
Product: Wine
Version: 7.2
Hardware: x86-64
URL: https://web.archive.org/web/20210726071744/https://github.com/zodiacon/ApiSetView/releases/download/v0.8/Api
SetView.exe
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: bunglehead(a)gmail.com
Depends on: 44658
Distribution: ---
For some api sets marked with a green arrow, which I think means api-set dll
with an actual file, export ordinal column is filled with export name. On
Windows it's empty. I suspect this happens because LVN_GETDISPINFO does not
initialize output text string, and it old buffer is reused.
--
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=51900
Bug ID: 51900
Summary: regression: REAPER scrollbars flash between themed and
non-themed
Product: Wine
Version: 6.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: uxtheme
Assignee: wine-bugs(a)winehq.org
Reporter: s_chriscollins(a)hotmail.com
Distribution: ---
Created attachment 70847
--> https://bugs.winehq.org/attachment.cgi?id=70847
video showing the bug
Starting with Wine 6.13, scrollbars in REAPER will flash between themed and
non-themed graphics when the mouse cursor passes over or interacts with them.
The attached video shows the behavior in Wine 6.12 (correct) followed by Wine
6.13 (glitchy).
A regression test pinpoints the following commit as the culprit:
-------------------------------------------------------------------
commit 883878e550d263fd9caedd4ba5ee8c142407c010
Author: Zhiyi Zhang <zzhang(a)codeweavers.com>
Date: Tue Jul 20 21:12:15 2021 +0800
uxtheme: Support scroll bar state tracking in non-client areas.
Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/user32/controls.h | 3 +++
dlls/user32/defwnd.c | 11 +++++++++++
dlls/user32/nonclient.c | 33 +++++++++++++++++++++++++++++++++
dlls/user32/scroll.c | 37 ++++++++++++++++++++++++++++++++++---
4 files changed, 81 insertions(+), 3 deletions(-)
-------------------------------------------------------------------
This bug is still present in master as of today (10/18/21) and can be
reproduced in a VirtualBox VM. REAPER can be downloaded for free from:
http://reaper.fm/
--
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=50370
Bug ID: 50370
Summary: Gothic 1 doesn't start correctly when screen
resolution of the game matches display resolution
Product: Wine
Version: 5.13
Hardware: x86-64
URL: https://www.fileplanet.com/archive/p-5260/Gothic-Demo-
English
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: f90d607c67768f19e36d9d74b498594252faa3fd
Distribution: ---
I'm starting Gothic 1 v1.08k using in-game resolution 1440x900 which matches my
native display resolution.
The game does start up because I can hear the sound of the intro movie, but no
visible window is created (the screen is black).
This used to work up until
commit f90d607c67768f19e36d9d74b498594252faa3fd
ddraw: Use the WINED3D_SWAPCHAIN_NO_WINDOW_CHANGES flag.
Reverting that commit on top of 6.0-rc3 fixes the problem for me.
To reproduce the problem in the demo:
1. Before starting the game modify GOTHIC.INI located in the Program
Files/Piranha Bytes/Gothic 1 Demo/system directory.
Look for the section [Video] and change in-game screen resolution there so that
it matches your display resolution:
zVidResFullscreenX=
zVidResFullscreenY=
You also need to set 32-bit color depth (the problem doesn't occur with
16-bit):
zVidResFullscreenBPP=32
2. run gothic.exe
setupg1demo-en.exe
md5sum: 2932bcb79118abadca0d394a7a86c096
wine-6.0-rc3
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.46.04
--
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=52787
Bug ID: 52787
Summary: Invalid function prototype for "RegisterUserApiHook"
when compiling for C++
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tayarani(a)google.com
Distribution: ---
This change added a function prototype which does not compile in C++:
https://source.winehq.org/git/wine.git/blobdiff/e02a7e579cc48079d70f2ef0095…
This is invalid C++ syntax as "new" is a reserved keyword:
WINUSERAPI BOOL WINAPI RegisterUserApiHook(const struct user_api_hook *new,
struct user_api_hook *old);
This is what the compiler generates:
"error: invalid parameter name: 'new' is a keyword"
This means any C++ code trying to include "windows.h" will fail with that
error.
The fix is fairly simple. That line should be changed to this to fix it:
WINUSERAPI BOOL WINAPI RegisterUserApiHook(const struct user_api_hook
*new_hook, struct user_api_hook *old_hook);
(i.e., rename the variable).
--
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=52581
Bug ID: 52581
Summary: unhandled exception in Internet MIDI with Light Blue
theme
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: comctl32
Assignee: wine-bugs(a)winehq.org
Reporter: s_chriscollins(a)hotmail.com
Distribution: ---
Created attachment 71906
--> https://bugs.winehq.org/attachment.cgi?id=71906
debug output
When starting the application "Internet MIDI" by Timewarp Technologies
(http://timewarptech.com/shop/music-software-apps/software/internet-midi/) with
Wine's new Light Blue theme enabled, I get the following unhandled exception
error: "Given combination of Class, Part, and State is not defined by the
current visual style."
I've reproduced this error using wine-staging, wine-devel, and using a fresh
~/.wine profile. Debug output attached.
OS: KDE Neon 5.24 User Edition (Plasma Desktop 5.24.1, KDE Frameworks 5.91.0,
Qt 5.15.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.