FS#55954 - [wine] 32 bit wine: error while loading shared libraries: out of memory: Operation not permitted
Attached to Project:
Community Packages
Opened by Owen Barton (grugnog) - Wednesday, 11 October 2017, 17:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 12 May 2018, 01:06 GMT
Opened by Owen Barton (grugnog) - Wednesday, 11 October 2017, 17:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 12 May 2018, 01:06 GMT
|
Details
Description:
32 bit wine fails with the message "/usr/bin/wine: error while loading shared libraries: out of memory: Operation not permitted" when starting any windows program. winecfg also fails with the same error. 64 bit wine functions correctly. Additional info: * package version(s) wine-2.18-2-x86_64 $ wine --version wine-2.18 * config and/or log files etc. This occurs with a freshly created user account, so is not related to user environment or .wine directory permissions etc. There are no configuration files or wine related environment present. I have also tried reinstalling wine and all dependencies (as well as optional dependencies). I tried rolling back wine and several of the dependencies but was not able to resolve the issue and narrow down the change that caused the issue (I may try this further if I have time). Rolling back wine itself does not appear to resolve the issue however. I also noted that running 32 bit wine as root does work (don't run it as sudo of course, because that will change .wine ownership). Looking at the library file permissions they appear correct. Running it with strace it appears the main issue is with /usr/bin/wine-preloader loading libwine in preparation for running wine itself - see attached strace log. Steps to reproduce: * Create new test user and login as test user * Run "wine cmd.exe" - observe error * Run "winecfg" - observe error Expected behavior (with wine64): * Create new test user and login as test user * Run "wine cmd.exe" $ wine64 cmd.exe wine: created the configuration directory '/home/testuser/.wine' ... wine: configuration in '/home/testuser/.wine' has been updated. Microsoft Windows 6.1.7601 (2.18) Z:\home\testuser> 
cmd-strace.txt
(10.7 KiB)
|
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Saturday, 12 May 2018, 01:06 GMT
Reason for closing: Upstream
Additional comments about closing: I don't think there is a reason to track this any longer in this tracker. It appears to be an upstream bug that only appears to a handful of users. Documenting this on the wiki would likely give this a better visibility to affected users.
Saturday, 12 May 2018, 01:06 GMT
Reason for closing: Upstream
Additional comments about closing: I don't think there is a reason to track this any longer in this tracker. It appears to be an upstream bug that only appears to a handful of users. Documenting this on the wiki would likely give this a better visibility to affected users.
Filled a bug entry at winehq:
https://bugs.winehq.org/show_bug.cgi?id=43963
I am unclear if just adding this sysctl configuration to the package is the best solution - the issues linked from the wiki page seem to suggest this is still the only functional approach. It's strange that this was working previously though?
mmap2(NULL, 65536, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = -1 EPERM (Operation not permitted)
This one is the page zero allocation, it's OK for it to fail.
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = -1 EPERM (Operation not permitted)
This one is a normal memory allocation, there's no MAP_FIXED so it shouldn't fail.
https://bugzilla.kernel.org/show_bug.cgi?id=198355