[pkg-wine-party] Bug#836911: Bug#836911: /usr/bin/winecfg-development: winecfg-development is a fork bomb

Jens Reyer jre.winesim at gmail.com
Wed Sep 7 18:27:19 UTC 2016


thanks for your report. I think I can reproduce this: Wine starts a
wineserver which all other Wine processes connect to. This wineserver
has to be from the same build as the connecting process. Now if wine
(stable)'s wineserver is already running and I then start
wine-development I can observe this issue.

But if no wine process is running previously this doesn't happen.

E.g. everything should be fine, if  you first kill an eventually running
wineserver, and then start winecfg:
$ wineserver-development -k
$ winecfg-development

$ winecfg-stable &
$ winecfg-development
... leads to this bug.

Can you confirm this?

AFAIK in the past Wine aborted if the "wrong" wineserver was already

Now I have to investigate if the whole issue is caused by the
alternatives system (which was introduced in wine-development 1.9.16-1
and wine 1.8.3-3), or if you just ran into this because the alternatives
system made this easier for you to get wrong.


More information about the pkg-wine-party mailing list