| Summary: | app-emulation/wine-vanilla: wineboot fails on mmap with "Cannot allocate memory" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alex <maniac> |
| Component: | Current packages | Assignee: | Wine Maintainers <wine> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | maniac |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info wine
strace -f wineboot kconfig-4.16.8-gentoo.txt |
||
|
Description
Alex
2018-05-15 20:38:05 UTC
Created attachment 531672 [details]
strace -f wineboot
Created attachment 531674 [details]
kconfig-4.16.8-gentoo.txt
Possibly an selinux issue...?? I'd check the selinux audit log. Perhaps try the top answer from... https://unix.stackexchange.com/questions/61032/how-to-get-wine-to-work-with-selinux Thanks for reply. Yes, I have selinux, but this happens in permissive mode too and toggling those booleans gives nothing. No complaints in audit log too. I also read yesterday that it might be cause by CONFIG_STRICT_DEVMEM option, going to check that later. No, turning off STRICT_DEVMEM (and STRICT_IO_DEVMEM alone too) gives same result. Wine-vanilla 3.x is no longer supported. Please let me know if you can reproduce this on 4.x |