[Bug 52647] wine-staging 7.3 fails to run on debian11 (but work on Debian10)

[WineHQ Bugzilla]

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

--- Comment #13 from Alois Schlögl <alois.schloegl at gmail.com> ---

Please note, that winedbg is already triggered when running wineboot, and
winefile. so that is unrelated to cuda-z. The winefile window is only opened
when nvidia-drm is not loaded. 

And the issue is unrelated whether wineprefix is on a local or an NFS share. 
(machine is part of a larger computational cluster, so the home directories are
on nfs). 

I've now compiled wine-staging 7.4 from source, and I do see the same
behaviour. 


I do not know whether it matters, but I had to limit the stacksize, otherwise,
I'd see this error: 

/opt/wine-staging/bin/wine: error while loading shared libraries:
libpthread.so.0: cannot create shared object descriptor: Operation not
permitted

or this in the version I compiled from source. 

/nfs/scistore07/clustersw/debian/bullseye/wine-staging/7.4/bin/wine: error
while loading shared libraries: out of memory: Operation not permitted


Currently, I run the tests with these limits: 

$ ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 1031179
max locked memory           (kbytes, -l) unlimited
max memory size             (kbytes, -m) unlimited
open files                          (-n) 65530
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 665544
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 1031179
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited


Let me know if I should run further tests, in order to identify the cause of
this issue.

-- 
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.