Same here on -CURRENT r320620. r319481 (I think) was working fine.
I'm using the i386-wine-devel package from the official repository.
Cheers,
Jan
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To u
On Sun, Jul 09, 2017 at 01:53:24PM +0200, Jan Kokem??ller wrote:
> Same here on -CURRENT r320620. r319481 (I think) was working fine.
>
> I'm using the i386-wine-devel package from the official repository.
This should fix creation of the unkillable processes, but untested.
After that, if wine st
> This should fix creation of the unkillable processes, but untested.
Thank you, wine works fine again with this patch applied.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
On 09.07.2017 14:23, Konstantin Belousov wrote:
On Sun, Jul 09, 2017 at 01:53:24PM +0200, Jan Kokem??ller wrote:
Same here on -CURRENT r320620. r319481 (I think) was working fine.
I'm using the i386-wine-devel package from the official repository.
This should fix creation of the unkillable pr
With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to
process the panic completely, but the backtrace looks mysteriously similar to
those provided with PR219146.
Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a
VirtualBox client. The pa
With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics. I haven't been able to
process the panic completely, but the backtrace looks mysteriously similar to
those provided with PR219146.
Initially, the VM-IMAGE booted just fine. The VM-IMAGE is then configured as a
VirtualBox client. The p
