[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 #6 from Alois Schlögl <alois.schloegl at gmail.com> ---
Created attachment 71996
  --> https://bugs.winehq.org/attachment.cgi?id=71996
log file running wine with and without nvidia-drm kernel module



The attached file is the (unprocessed) log file with all control codes. I
assume you can handle this. 


It starts with a new wineprefix, and nvidia-drm kernel module loaded. 
Running cuda-z as well as winefile, results in these error 

wine: Unhandled page fault on execute access to 00007FC243AA2070 at address
00007FC243AA2070 (thread 0050), starting debugger...
wine: Unhandled page fault on execute access to 00007F5063378660 at address
00007F5063378660 (thread 0048), starting debugger...
wine: Unhandled page fault on execute access to 00007F2A25A75660 at address
00007F2A25A75660 (thread 0148), starting debugger...
wine: Unhandled page fault on execute access to 00007FE2871AE660 at address
00007FE2871AE660 (thread 015c), starting debugger...


Then I'm trying to kill wine, wineserver, etc. to start new. At some point, I
do 
  rmmod nvidia-drm 
then the behaviour changes. That error does not occur anymore, and I can
actually start "winefile". cuda-z starts as well, but fails with "no
cuda-device available..." . At least the error above does not occur anymore. 

When loading the nvidia-drm kernel module again, the above errors appear again. 

We see also some libGL errors: 
libGL: libGL: Can't open configuration file /etc/drirc: No such file or
directory.Can't open configuration file /etc/drirc: No such file or directory.
Not sure what that means, and whether this is related

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