Description of problem: SELinux is preventing maxima from changing the access protection of memory on the heap. Version-Release number of selected component (if applicable): maxima.i586 5.17.1-7.fc11 How reproducible: always Steps to Reproduce: 1.just launch maxima 2. 3. Actual results: The maxima application attempted to change the access protection of memory on the heap (e.g., allocated using malloc). This is a potential security problem. Applications should not be doing this. Applications are sometimes coded incorrectly and request this permission. The SELinux Memory Protection Tests web page explains how to remove this requirement. If maxima does not work and you need it to work, you can configure SELinux temporarily to allow this access until the application is fixed. Please file a bug report against this package. Expected results: Additional info: Linux localhost.localdomain 2.6.29.5-191.fc11.i686.PAE #1 SMP Tue Jun 16 23:19:53 EDT 2009 i686 i686 i386 GNU/Linux
Created attachment 354492 [details] message of selinux
What maxima-runtime are you using? ie, output of: $ rpm -qa maxima-runtime-*
In particular, maxima-runtime-gcl is known to be problematic atm, I'd recommend using maxima-runtime-sbcl instead.
rpm -qa maxima-runtime-* maxima-runtime-gcl-5.17.1-7.fc11.i586
it seems to work after installing maxima-runtime-sbcl. May I uninstall maxima-runtime-gcl?? I installed only wxmaxima and maxima and maxima-runtime-gcl were loaded automatically. From point of view of functionality are they equivalent?
Most maxima-runtime-* pkgs are functionally equivalent, so you can remove -gcl, sure. It's just unfortuate because we intend -sbcl to be the default, but yum currently satisfies (virtual) dependencies by pkgs with the shortest name. *** This bug has been marked as a duplicate of bug 496124 ***