Bug#836911: /usr/bin/winecfg-development: winecfg-development is a fork bomb

2016-09-09 Thread Jens Reyer
On 07.09.2016 20:27, Jens Reyer wrote: > 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 >

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

2016-09-07 Thread Jens Reyer
Hi, 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

Bug#836911: /usr/bin/winecfg-development: winecfg-development is a fork bomb

2016-09-07 Thread Ph. Marek
Package: wine-development Version: 1.9.18-1 Severity: normal File: /usr/bin/winecfg-development Running winecfg-development just made my machine unusable. Excerpts of my "ps fax" output: 5836 ?Ts 0:00 C:\windows\system32\explorer.exe /desktop 5843 ?Ts 0:00