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.…
[View More]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.
[View Less]
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://…
[View More]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.
[View Less]
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
…
[View More]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.
[View Less]
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: …
[View More]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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=51163
Bug ID: 51163
Summary: WinOffice Pro 5.3 stops after splashscreen
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 70031
--> …
[View More]https://bugs.winehq.org/attachment.cgi?id=70031
Console Output (wine 6.8)
Hello everyone,
I came across a forum question where somebody asked how to get the German
accounting application WinOffice Pro 5.3 to run. There is a 60 day trial
version available and I noticed that the application requires mdac27 and jet40
in a 32-Bit prefix to perform a successful installation.
Starting the application works until the splashscreen but then the application
terminates. 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=45916
Bug ID: 45916
Summary: x64dbg does not open executables, nothing happens
Product: Wine
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: jimbo1qaz(a)gmail.com
Distribution: ---
When I File/Open or drag a .exe file …
[View More]into x32dbg (x64dbg 32-bit), the exe does
not load onto the graphs, and Ctrl+G doesn't work. I think the EXE is not
loaded by the debugger at all.
Fixed by ~/bin/winetricks vcrun2013 .
Wine 3.16 on Debian on Virtualbox.
--
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]
http://bugs.winehq.org/show_bug.cgi?id=25257
Summary: Enabling Virtual desktop by default cannot be turned
off for specific applications
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: zzarko(a)gmail.com
My system is Ubuntu 10.10 and Wine …
[View More]is installed from Ubuntu Wine team's PPA.
Steps to reproduce the problem:
1. Select Default settings in Configure Wine/Applications tab and check
Graphics/Enable virtual desktop
2. Add an application (in my case, Subtitle Workshop) to Applications tab and
uncheck the same option for this application
3. Start the application -> application is started in virtual desktop, despite
the different setting for that application
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=50936
Bug ID: 50936
Summary: Several games (The suicide of Rachel Foster, Far lone
sails & Virginia) crashes after some times with vulkan
rendeder
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-…
[View More]bugs(a)winehq.org
Reporter: titan.costa(a)gmail.com
Distribution: ---
The suicide of Rachel Foster & Virginia just crashes. For Far lone sails it
becomes very slow before crashing.
No backtrace. The console output is pretty silent.
With the GL renderer, Virginia & Far lone sails just works fine and can be
finished from start to end without interruption.
I can't test GL renderer with The suicide of Rachel Foster due to bug
https://bugs.winehq.org/show_bug.cgi?id=50764 which makes the game unplayable.
Setup is wine-6.5-156-g2fcc1d0ecde + Ubuntu 20.10 + GTX1070 + nvidia driver
460.39.
--
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]
http://bugs.winehq.org/show_bug.cgi?id=19661
Summary: Lotus Approach 3.1 causes a page fault on load
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: win16
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Created an attachment (id=22944)
--> (http://bugs.winehq.org/…
[View More]attachment.cgi?id=22944)
Wine 1.1.27 console output
Lotus Approach 3.1 causes a page fault on loading and has to be killed.
--
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.
[View Less]