Red Hat Bugzilla – Bug 187685
Upgrading to kernel-2.6.16-1.2080_FC5 blocks application Moneyplex 2003
Last modified: 2008-01-19 23:38:21 EST
Description of problem:
After upgrading from kernel-2.6.15-1.2054_FC5 my homebanking software Moneyplex
2003(by Matrica) stopped working, it just reclines to start giving a
"memory access error".
This is exactly the same thing that has happened before with a kernel-upgrade
under FC3 and is filed as (closed) bug #162182.
The temporary solution to 'echo 1 > /proc/sys/kernel/exec-shield' works as before.
SELinux is disabled.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen