Bug 1190525
Summary: | Using alt+enter to fullscreen any rpgmaker XP game causes system to freeze | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Timothy Arceri <t_arceri> |
Component: | marco | Assignee: | Wolfgang Ulbrich <fedora> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 21 | CC: | andreas.bierfert, besser82, dan.mashal, fedora, mike, stefan, t_arceri |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | marco-1.10.1-2.fc21 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-10 09:57:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Timothy Arceri
2015-02-08 23:07:04 UTC
Example app: http://www.itsqueeze.com/wp-content/uploads/2015/02/Custom_Mouse_System.tar.gz Just run Game.exe and press alt+enter I can't run your app: "RGSS-RTP Standard not found." Please file upstream. https://bugs.winehq.org/ They will want you to perform regression testing since you noted an earlier version works. http://wiki.winehq.org/RegressionTesting Sorry, not that upstream. This upstream: https://github.com/wine-compholio/wine-staging/issues Whoops sorry about that you also need the run time package for Rpgmaker XP http://www.rpgmakerweb.com/download/additional/run-time-packages I still can't run it. "Script 'Win32 Wrapper' line 330: NoMethodError occurred." Please post the upstream bug link when you have created it. Please download and try the example app again I forgot to remove a script that's not needed. I managed to get the SELinux trouble shoot detail from the issue. SELinux is preventing /usr/bin/systemctl from using the sys_resource capability. ***** Plugin sys_resource (91.4 confidence) suggests ********************** If you do not want processes to require capabilities to use up all the system resources on your system; Then you need to diagnose why your system is running out of system resources and fix the problem. According to /usr/include/linux/capability.h, sys_resource is required to: /* Override resource limits. Set resource limits. */ /* Override quota limits. */ /* Override reserved space on ext2 filesystem */ /* Modify data journaling mode on ext3 filesystem (uses journaling resources) */ /* NOTE: ext2 honors fsuid when checking for resource overrides, so you can override using fsuid too */ /* Override size restrictions on IPC message queues */ /* Allow more than 64hz interrupts from the real-time clock */ /* Override max number of consoles on console allocation */ /* Override max number of keymaps */ /* Override resource limits. Set resource limits. */ /* Override quota limits. */ /* Override reserved space on ext2 filesystem */ /* Modify data journaling mode on ext3 filesystem (uses journaling resources) */ /* NOTE: ext2 honors fsuid when checking for resource overrides, so you can override using fsuid too */ /* Override size restrictions on IPC message queues */ /* Allow more than 64hz interrupts from the real-time clock */ /* Override max number of consoles on console allocation */ /* Override max number of keymaps */ /* Override resource limits. Set resource limits. */ /* Override quota limits. */ /* Override reserved space on ext2 filesystem */ /* Modify data journaling mode on ext3 filesystem (uses journaling resources) */ /* NOTE: ext2 honors fsuid when checking for resource overrides, so you can override using fsuid too */ /* Override size restrictions on IPC message queues */ /* Allow more than 64hz interrupts from the real-time clock */ /* Override max number of consoles on console allocation */ /* Override max number of keymaps */ Do fix the cause of the SYS_RESOURCE on your system. ***** Plugin catchall (9.59 confidence) suggests ************************** If you believe that systemctl should have the sys_resource capability by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep shutdown /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:apmd_t:s0 Target Context system_u:system_r:apmd_t:s0 Target Objects Unknown [ capability ] Source shutdown Source Path /usr/bin/systemctl Port <Unknown> Host localhost.localdomain Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name localhost.localdomain Platform Linux localhost.localdomain 3.18.5-201.fc21.x86_64 #1 SMP Mon Feb 2 21:00:58 UTC 2015 x86_64 x86_64 Alert Count 8 First Seen 2015-02-10 16:29:56 AEDT Last Seen 2015-02-10 23:35:12 AEDT Local ID db55916b-46a2-48ab-ae7d-ab97874a181b Raw Audit Messages type=AVC msg=audit(1423571712.831:708): avc: denied { sys_resource } for pid=7340 comm="shutdown" capability=24 scontext=system_u:system_r:apmd_t:s0 tcontext=system_u:system_r:apmd_t:s0 tclass=capability permissive=0 type=SYSCALL msg=audit(1423571712.831:708): arch=x86_64 syscall=setrlimit success=no exit=EPERM a0=7 a1=7fff9c275790 a2=0 a3=a382d4654552e42 items=0 ppid=7315 pid=7340 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=shutdown exe=/usr/bin/systemctl subj=system_u:system_r:apmd_t:s0 key=(null) Hash: shutdown,apmd_t,apmd_t,capability,sys_resource That alert has nothing to do with wine. Changing component to Marco. Most of the problems are fixed by this patch: https://github.com/mate-desktop/marco/pull/167 More information is in the upstream wine bug report. (In reply to Timothy Arceri from comment #9) > Changing component to Marco. Most of the problems are fixed by this patch: > https://github.com/mate-desktop/marco/pull/167 > > More information is in the upstream wine bug report. A link to upstream report is helpful. The initial bug report was about fixing something slightly different, but it solves this bug too. https://github.com/mate-desktop/marco/issues/166 (In reply to Timothy Arceri from comment #11) > The initial bug report was about fixing something slightly different, but it > solves this bug too. > > https://github.com/mate-desktop/marco/issues/166 I meant the wine report, but i found it for myself :/ It's up the top under External Trackers :) Here is a scratch build for testing. http://koji.fedoraproject.org/koji/taskinfo?taskID=9205213 But i need to test this build a while locally. Sorry, i can't push this build to fedora repos yet, with a patch which isn't reviewed by upstream. Did the scratch build helps? Hi sorry, I previously created my own RPM with the patch applied and yes it fixed the issue. I can try your build too, but I guess the real issue is getting upstream to review it. I've just added the info about this bug to the upstream issue tracker as it was about fixing a different but related bug, hopefully the kickstarts the conversation again. marco-1.10.1-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/marco-1.10.1-2.fc21 Package marco-1.10.1-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing marco-1.10.1-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12562/marco-1.10.1-2.fc21 then log in and leave karma (feedback). marco-1.10.1-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |