https://bugs.winehq.org/show_bug.cgi?id=55015
Bug ID: 55015
Summary: wine8.9 syswow64 dir is empty, win32 exe cannot run
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: szl19921231(a)gmail.com
Distribution: ---
wine8.9 enable-archs=i386,x86-64
After initializing with "wineboot", there are no 32-bit libraries generated in
the "syswow64" directory of the prefix, causing errors when running 32-bit
programs.
--
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=50308
Bug ID: 50308
Summary: Starting certain Wine builtin apps with explicit
SysWOW64 path in 64-bit WINEPREFIX causes infinite
process restart loop (wineboot, winecfg, ...)
Product: Wine
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
found while playing around with Wow64 file system redirection.
Certain Wine builtin apps restart themselves as 64-bit process when running
under Wow64 environment by design to avoid synchronization issues of registry
data (shared/redirected/reflected).
Although most users will never try this, explicitly specifying SysWOW64
directory will result in an infinite process restart loop. SysWOW64 is used to
bypass the filesystem redirector. In this case it's questionable but still it
shouldn't result in the observed behaviour.
--- snip ---
$ wine cmd.exe /c "%WINDIR%\\syswow64\\winecfg.exe"
<will infinitely restart>
--- snip ---
Affected apps:
* regedit
* uninstaller
* wineboot
* winecfg
* winedbg
* wusa
The process restart code is mostly identical across these.
Wine source:
https://source.winehq.org/git/wine.git/blob/76c9dbd4fb99f1257734908906c846a…
--- snip ---
139 int WINAPI wWinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPWSTR
lpCmdLine, int nCmdShow)
140 {
141 MSG msg;
142 HACCEL hAccel;
143 BOOL is_wow64;
144
145 if (ProcessCmdLine(GetCommandLineW())) {
146 return 0;
147 }
148
149 if (IsWow64Process( GetCurrentProcess(), &is_wow64 ) && is_wow64)
150 {
151 STARTUPINFOW si;
152 PROCESS_INFORMATION pi;
153 WCHAR filename[MAX_PATH];
154 void *redir;
155 DWORD exit_code;
156
157 memset( &si, 0, sizeof(si) );
158 si.cb = sizeof(si);
159 GetModuleFileNameW( 0, filename, MAX_PATH );
160
161 Wow64DisableWow64FsRedirection( &redir );
162 if (CreateProcessW( filename, GetCommandLineW(), NULL, NULL,
FALSE, 0, NULL, NULL, &si, &pi ))
163 {
164 WINE_TRACE( "restarting %s\n", wine_dbgstr_w(filename) );
165 WaitForSingleObject( pi.hProcess, INFINITE );
166 GetExitCodeProcess( pi.hProcess, &exit_code );
167 ExitProcess( exit_code );
168 }
169 else WINE_ERR( "failed to restart 64-bit %s, err %d\n",
wine_dbgstr_w(filename), GetLastError() );
170 Wow64RevertWow64FsRedirection( redir );
171 }
--- snip ---
'regsvr32' has some code that might be useful:
https://source.winehq.org/git/wine.git/blob/76c9dbd4fb99f1257734908906c846a…
Although that case is a bit different as it supports restart in both
directions.
$ wine --version
wine-6.0-rc1-39-g76c9dbd4fb9
Regards
--
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=45271
Bug ID: 45271
Summary: Silence winemenubuilder.exe error if it is disabled by
user
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tim110011(a)163.com
Distribution: ---
wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe"
000b:err:wineboot:ProcessRunKeys Error running cmd
L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2)
This is not a error if it is disabled manually by user.
--
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=43938
Bug ID: 43938
Summary: wine-gecko does not have an arm build
Product: Wine-gecko
Version: unspecified
Hardware: arm
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wine-gecko-unknown
Assignee: jacek(a)codeweavers.com
Reporter: austinenglish(a)gmail.com
Distribution: ---
This is blocked until mingw64 supports arm targets in a release, but for now,
dlls/mshtml/tests/* and friends fail on arm.
--
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=49416
Bug ID: 49416
Summary: FarmingSimulator2019Patch1.6.0.exe crashes while
trying to install
Product: Wine
Version: 5.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: torben(a)drejoe.net
Distribution: ---
Created attachment 67498
--> https://bugs.winehq.org/attachment.cgi?id=67498
Zip-file with what I had done plus log-files
Trying to install newest patch for Farming Simulator 19.
Please find what I've done in the attached zip-file including wine outputs.
--
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=49245
Bug ID: 49245
Summary: Wineboot takes very long time
Product: Wine
Version: 5.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: magist3r(a)gmail.com
Distribution: ---
I've noticed that since maybe wine 5.0 the init times increased significantly.
A simple command on the clean prefix like:
WINEPREFIX=~/test wineboot
now takes about 30 seconds, but earlier (before 5.0) took about 5 seconds. And
it affects loading times of every program I use with wine.
Please advise me what to do to figure out what is going on.
--
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=49319
Bug ID: 49319
Summary: Services don't stop when the application stops (macOS
only)
Product: Wine
Version: 5.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: mterrisse(a)free.fr
Distribution: ---
Hello,
Wine 5.7 x64, macOS Catalina 10.15.5
I have a prefix with an application installed and a Windows service registered.
When I run the application, the service starts. But when I close the
application, the service doesn't stop and the processes wineserver and
wine64-preloader are still running.
Even if I call wineboot -s, the service doesn't stop.
I tested with the same application and service on Ubuntu 20.04, and closing the
application stops the service and all the processes exit.
So the problem looks specific to macOS.
Any idea to help understanding what is wrong?
Regards,
Michel Terrisse
--
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=50921
Bug ID: 50921
Summary: network error on wineboot / programm launch
Product: Wine
Version: 6.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: prinz2018j(a)gmail.com
Distribution: ---
when I try to launch any programm .exe or call wineboot i get the error
0150:err:winediag:WS_getaddrinfo Failed to resolve your host name IP
kernel : ArtixLinux 5.11.10
--
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=54339
Bug ID: 54339
Summary: Wine doesn't recognize RTX 3xxx and 4xxx
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: kohen.d(a)gmail.com
Distribution: ---
Wine does not recognize RTX 30xx and 40xx Nvidia cards, it prevents games from
auto-configuring the performance.
https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/wined3d/adapter_gl.c…
Tested on 3050, but should be on 3070, 3070, 3090, 4070, 4090...
--
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=42888
Bug ID: 42888
Summary: Adobe Flash CS6 crashes after a few minutes
Product: Wine
Version: 2.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: demurgos(a)demurgos.net
Distribution: ---
Created attachment 58012
--> https://bugs.winehq.org/attachment.cgi?id=58012
Adobe Flash CS6 crash 1
Hi,
I just installed Flash CS6 with Wine 2.6 on two of my computers. It seems to
work fine on my older computer by I encounter some stability issues with my new
laptop. Both computers run Arch Linux 64 bits so the difference must come
either from the fact that I have less libraries on the new laptop or there are
some hardware issues.
Concretely, my issue is that if I start Adobe Flash CS6 and leave it open for
about 5 minutes, it crashes. I saved two backtraces (see the attachments). The
issue happens even if I do not mess with the program: leaving it open is enough
to cause the crash.
I documented the exact installation steps here:
https://github.com/demurgos/notes/blob/master/tools/emulation/wine/adobe-cs…
(I used the same steps for both computers.)
Here are the commands I used:
sudo pacman -S wine winetricks wine-mono wine_gecko
sudo pacman -S samba lib32-mpg123
mkdir -p /opt/wine/adobe-cs6
export WINEPREFIX=/opt/wine/adobe-cs6
export WINEARCH=win32
cd $WINEPREFIX
wine wineboot
winetricks msxml3 vcrun2008 vcrun2010 atmlib gdiplus allfonts
wine /patch/to/adob-cs6/Set-Up.exe
I then started Adobe Flash from the start menu.
--
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.