Bug 277381
Summary: | SEGV error moving mouse over window related to XmToolTipGetLabel | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Steve Hild <hild> | ||||||
Component: | openmotif | Assignee: | Thomas Woerner <twoerner> | ||||||
Status: | CLOSED ERRATA | QA Contact: | |||||||
Severity: | urgent | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 5.0 | CC: | dkl, rkhadgar, tao | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | i386 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | RHBA-2008-0453 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-05-21 17:23:26 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 246139 | ||||||||
Attachments: |
|
Description
Steve Hild
2007-09-04 20:53:33 UTC
Created attachment 186611 [details]
Explanation of process to duplicate as well as possible fix code.
Also reported to bugs.motifzone.net and assigned bug# 1388. Nominating for 5.2. Fix was integrated into OpenMotif 2.3.0 and HEAD. See bug #1388 at bugs.motifzone.net. I have downloaded the change and verified that it does solve the problem I was having. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. This request will be reviewed for a future Red Hat Enterprise Linux release. Please attach your test case. BTW: Upstream has a different way to fix this. Please have a look at: http://cvs.motifzone.net/cgi-bin/cvsweb.cgi/openmotif/lib/Xm/VendorS.c.diff?r1=1.12&r2=1.12.2.1&cvsroot=openmotif (In reply to comment #9) > Please attach your test case. The best test case I can offer is described in my initial description of the problem. Created attachment 284181 [details]
Test case for MZ#1388
Please test if this test case has the same problem, you had with your
application.
Please have a look at: http://people.redhat.com/twoerner/BZ/277381/ These packages contain the upstream patch, which is solving the problem for me with the test case from #15. ---- Please remember that these are test packages, which might get pushed out as update packages later if the fixes are ok. For now, these packages are unsupported. (In reply to comment #15) Your test case does duplicate the problem we are having. Is the upstream fix also working for you? (In reply to comment #18) Yes, it appears to fix the problems were were having. I tried it with your Test Case and with our application. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. (In reply to comment #18) > Is the upstream fix also working for you? Someone on the motifzone bugzilla has questioned whether the OpenMotif fix will introduce a memory link. See the comment from pab at: http://bugs.motifzone.net/show_bug.cgi?id=1388 I added a comment there that my suggested solution only NULLed out the Label and not the entire structure. The current upstream fix is not good enough. I'll work with upstream to get a real fix. The hotfix should be postponed until this is done. I agree about postponing the hotfix :( Let me know when a new fix is available. I was in the process of making changes in anticipation of the hotfix. Any status on an updated fix? Any info would be greatly appreciated. Thanks, Steve I have made a patch, which fixed the problem for the test case. Upstream is currently working on an enhanced patch, because there are more problems with this than those shown by the test case. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. I see that there is new fix posted at bugs.motifzone.net for this problem. How soon from the time something that is posted there makes it into the RedHat system? I have tested the latest fix and it looks good. This is an OK form my side. (In reply to comment #35) > I have tested the latest fix and it looks good. This is an OK form my side. Do you have a package with this new patch we could try here? Here are updated test rpms: http://people.redhat.com/twoerner/BZ/277381/ ---- Please remember that these are test packages, which might get pushed out as update packages later if the fixes are ok. For now, these packages are unsupported. (In reply to comment #38) This latest patch works with the test case you had sent previously and with our application. Thanks. Now to get it into an update package. Fixing missing Devel ACK now that we have a working and clean fix thats also upstream. Still requires a HOTFIX request though again. Read ya, Phil *** Bug 436178 has been marked as a duplicate of this bug. *** How do I get another HotFix request? I have re-requested escalation on the RedHat Support Service Request 1767906 to request a HotFix and I have not seen any activity. Steve An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0453.html *** Bug 430492 has been marked as a duplicate of this bug. *** |