Red Hat Bugzilla – Bug 1448509
Fix for Bug #1415153 causes application crashes ( Need to unpush the patch )
Last modified: 2018-05-10 04:26:32 EDT
Description of problem: In Bug 1415153, the patch which was pushed to fix the issue while navigating drop down menus with arrow keys, started causing two new issues :
 The patch (motif-2.3.4-8.1.el7_3.x86_64) that should fix this issue causes application crashes. We have confirmed that it really is the patch that causes the crashes.
The crash seems be related with removing a widgets.
 We have also noticed a change in behavior between the two motif packages motif-2.3.4-8 and motif-2.3.4-8.1
With motif-2.3.4-8 the application still has focus after the widget is removed (expected behavior). But with the new patch motif-2.3.4-8.1 the application looses focus after the widget is removed.
Following is the link to errata which was released :
Version-Release number of selected component (if applicable): motif-2.3.4-8.1
How reproducible: Always
Steps to Reproduce:
motif-2.3.4-8.1 causes the above mentioned crashes and change in behaviour after installation.
Actual results: The mentioned patch causes applications to crash.
Expected results: The top patch ( motif-2.3.4-8.1 ) needs to be unpushed.
Additional info: This is very high priority as customer's business is highly affected. This would need to go via z-stream or a hotfix packages would be required.
Unfortunately the fix broke API, as pointed by the rpmdiff https://errata.devel.redhat.com/rpmdiff/show/181645 so afaik that means it cannot be included.
What's the way forward here to have the fix included, if wanted?
After more investigation I was wrong in comment #37, the API is "public" as in they export the symbols for technical reasons, but it's not for public use.
So the update should be fine.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
*** Bug 1429298 has been marked as a duplicate of this bug. ***