Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(Sorry for the boggle) Description of problem: When the man page for dbus-binding-tool is displayed as html, there is a table, under the ATTRIBUTES heading, which does not display correctly. How reproducible: Always. Steps to Reproduce: 1. View "man dbus-binding-tool", noting the table displayed under the ATTRIBUTES heading. 2. Do "man -Hfirefox dbus-binding-tool", noting the display under the ATTRIBUTES heading. 3. Do "man -Hlynx dbus-binding-tool", noting the display under the ATTRIBUTES heading. 4. Do "man --troff-device=html dbus-binding-tool", noting the error messages generated. Actual results: Under Firefox, the table/image shows up as a line of text, "Image grohtml-....png" - no table displayed, no link to the image of the table. Under lynx, the table/image shows up as a link, "Image grohtml-....png". However, when the link is followed, the viewer (in my case Eye of Mate), complains: "Could not load image ... Unrecognized image file format". Eye of Mate can display png images. Expected results: In the browser, either the table displays correctly, or there is a link to an image, which can be displayed correctly. Additional info: Also, the bullet points under "server side bindings" are mis-aligned (in the html renderings).
Version-Release number of selected component (if applicable): groff-base-1.22.3-8.fc24.x86_64
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's 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 Fedora 'version' of '24'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's 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 Fedora 'version' of '25'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 Fedora 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.