[Bug 51006] Running 32-bit wineboot to create a new 64-bit WINEPREFIX results in a wineboot fork bomb with Wine 6.6-149-g39263558a20

WineHQ Bugzilla wine-bugs at winehq.org
Fri Apr 16 06:39:00 CDT 2021


https://bugs.winehq.org/show_bug.cgi?id=51006

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|'wineboot' fork bomb when   |Running 32-bit wineboot to
                   |creating new 64-bit         |create a new 64-bit
                   |WINEPREFIX with Wine        |WINEPREFIX results in a
                   |6.6-149-g39263558a20        |wineboot fork bomb with
                   |                            |Wine 6.6-149-g39263558a20
           Severity|blocker                     |normal

--- Comment #2 from Anastasius Focht <focht at gmx.net> ---
Hello Alexandre,

--- quote ---
I assume you are running 32-bit wineboot by hand?
--- quote ---

yes, I should have posted the command line in first place. I often initialize a
new prefix this way, without using builtin programs.

--- snip ---
$ rm -rf ~/.wine
$ wineboot
<fork bombs>
--- snip ---

Works:

--- snip ---
$ rm -rf ~/.wine
$ notepad
--- snip ---

Works as well:

--- snip ---
$ rm -rf ~/.wine

$ wine64 wineboot
--- snip ---

I've refined the summary and downgraded the severity to reflect this is limited
to a specific use-case.

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.



More information about the wine-bugs mailing list