Hide Forgot
Description of problem: After upgrading libAfterImage to libAfterImage-1.20-1.el6.x86_64 aterm gives the error: aterm: symbol lookup error: aterm: undefined symbol: dpy Version-Release number of selected component (if applicable): aterm-1.0.1-6.el6.x86_64 How reproducible: Steps to Reproduce: 1.install libAfterImage-1.20-1.el6.x86_64 and aterm-1.0.1-6.el6.x86_64 2.run /usr/bin/aterm 3. Actual results: aterm: symbol lookup error: aterm: undefined symbol: dpy Expected results: new window with aterm application running Additional info:
same here.... any one?
This link http://www.mail-archive.com/debian-bugs-closed@lists.debian.org/msg235751.html suggests that the problem has been solved upstream. Maybe just update the version in EPEL and it will be fine ?
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.