On 07.09.2016 22:42, Erik de Castro Lopo wrote:
> Jens Reyer wrote:
>
>> Hmm, probably that points to the same issue as in
>> https://bugs.debian.org/836911.
>>
>> I assume that Wine forks permanently if another wineserver is already
>> running. So does this happen for you, if previously no
Jens Reyer wrote:
> Hmm, probably that points to the same issue as in
> https://bugs.debian.org/836911.
>
> I assume that Wine forks permanently if another wineserver is already
> running. So does this happen for you, if previously no wineserver was
> running, e.g.:
>
> $ wineserver -k
> $ wine
On 04.09.2016 15:12, Jens Reyer wrote:
> Hi,
>
> thanks for your report.
>
> I can't really read backtraces, but wonder if these identical lines are
> normal:
>
>> 22 0x7bf00d99 _start+0x28() in (0x)
> [...]
>> 200 0x7bf00d99 _start+0x28() in
Hi,
thanks for your report.
I can't really read backtraces, but wonder if these identical lines are
normal:
> 22 0x7bf00d99 _start+0x28() in (0x)
[...]
> 200 0x7bf00d99 _start+0x28() in (0x)
Maybe try to install the dbgsym packages for at
Package: wine64
Version: 1.8.4-1
Severity: normal
My main usage of Wine is for running the test suite for software when
I cross compile from Linux to Windows. I've been doing this successfully
for many years which the occassional problem like the one today.
I recently upgraded to wine64 1.8.3
5 matches
Mail list logo
