December 2020 - Wine-bugs - list.winehq.org

[Bug 50352] New: Maximum sockets per process is set very low
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

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.

1 6

[Bug 50370] New: Gothic 1 doesn't start correctly when screen resolution of the game matches display resolution
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

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.

1 19

[Bug 45916] New: x64dbg does not open executables, nothing happens
by wine-bugs＠winehq.org 08 Nov '22

08 Nov '22

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 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.

2 11

[Bug 25257] New: Enabling Virtual desktop by default cannot be turned off for specific applications
by wine-bugs＠winehq.org 08 Nov '22

08 Nov '22

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 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.

2 7

[Bug 19586] New: Everest editor does not start
by wine-bugs＠winehq.org 05 Nov '22

05 Nov '22

http://bugs.winehq.org/show_bug.cgi?id=19586 Summary: Everest editor does not start Product: Wine Version: 1.1.26 Platform: PC URL: http://everesteditor.chat.ru/Download/Everest.zip OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: neptunia(a)mail.ru Everest is a freeware TeX-compatible WYSIWYG editor. It does not start under Wine 1.1.26 returning a message of stack overflow. It can be downloaded here: http://everesteditor.chat.ru/Download/Everest.zip http://download.ware.ru/win/Everest.zip -- 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 14

[Bug 47925] New: Panel in dialog incorrectly drawn
by WineHQ Bugzilla 01 Nov '22

01 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=47925 Bug ID: 47925 Summary: Panel in dialog incorrectly drawn Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dav75uk(a)yahoo.co.uk Distribution: --- Created attachment 65425 --> https://bugs.winehq.org/attachment.cgi?id=65425 snapshot of problematic dialog In Chessbase 11, inputting incorrect security key details results in a dialog. The panel that rests in it is not correctly drawn. In this case pictured the white background does not fill the dialog, and sometimes is of different sizes. Sometimes the message is missing. This happens every time. Using full screen on a 4K display. Suggestion of an incorrect (or order of) initialisation issue, 4K/screen size issue or a data race? -- 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 7

[Bug 47990] New: Wine64: Candidate of CJK input method is invisible on macOS Catalina.
by WineHQ Bugzilla 01 Nov '22

01 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=47990 Bug ID: 47990 Summary: Wine64: Candidate of CJK input method is invisible on macOS Catalina. Product: Wine Version: 4.18 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com Created attachment 65509 --> https://bugs.winehq.org/attachment.cgi?id=65509 WINEDEBUG=+tid,+pid,+imm,+keyboard,+key,+macdrv Tested with wine-4.18-112-g717109ce79: 1. $ wine64 notepad 2. Switch to Chinese Pinyin input method, and try to type something You will find that candidate didn't display, though you still can type some Chinese characters into notepad with the input method. I didn't see similar on macOS 10.14, so I think this is a Catalina special issue. -- 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 15679] New: cygwin symlinks not working in wine
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=15679 Summary: cygwin symlinks not working in wine Product: Wine Version: 1.1.6 Platform: Other URL: http://cygwin.com OS/Version: other Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Surprisingly, cygwin seems to work nowadays, as long as you do everything inside a wineconsole running cygwin.bat. (Perhaps cygwin apps should work outside wineconsole; that would be a separate bug report.) However, cygwin's gcc doesn't work unless you replace certain cygwin symlinks with unix ones, e.g. $ cd .wine/drive_c/cygwin/usr/i686-pc-cygwin/bin $ for a in *; do ln -sf ../../../bin/$a; done Likewise, /bin/vi doesn't work, as it's a symlink to vim.exe. In fact, cygwin's ls -l doesn't even recognize cygwin's symlinks as such: $ ls -l vi -rw-r--r-- 1 dank mkpasswd 18 Oct 19 05:53 vi $ cat vi !<symlink>vim.exe So either they're not being created right, or they're not being recognized properly by cygwin for some reason, or both. -- 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 40

[Bug 38604] New: winedbg: internal crash when valgrinding ieframe/tests/ie.c with pdb debug symbols
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=38604 Bug ID: 38604 Summary: winedbg: internal crash when valgrinding ieframe/tests/ie.c with pdb debug symbols Product: Wine Version: 1.7.43 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Created attachment 51499 --> https://bugs.winehq.org/attachment.cgi?id=51499 log See also bug 38594 for a similar issue, though this one causes winedbg to crash. Log 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.

2 5

[Bug 29998] New: Crysis 2 (>1.0) huge graphical issues after loading a savegame
by wine-bugs＠winehq.org 31 Oct '22

31 Oct '22

http://bugs.winehq.org/show_bug.cgi?id=29998 Bug #: 29998 Summary: Crysis 2 (>1.0) huge graphical issues after loading a savegame Product: Wine Version: 1.4-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: christian.frank(a)gmx.de Classification: Unclassified Created attachment 39060 --> http://bugs.winehq.org/attachment.cgi?id=39060 Crysis 2 log Hi, if you try to use a saved game in Crysis 2 which is patched to a higher level than 1.0, you will have huge graphical issues. Either you get a black scree with only the hud displayed, or completely broken graphics, or a whiet screen etc.. This does only happen if you use a savegame or if you want to replay a mission. If you start the campaign from the beginning, the game will look fine. This behaviour happens with tons of wine version i have testet, so doesnt seem to be a regression right now. CryEngine 3 is planned to be used in other upcoming games and is somehow a engine which really pushes d3d9 to its limits.I think it would make a lot of sense to get this issue fixed . Many thanks, Christian -- 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 55