Bug 252391 - poppler-utils come with spurious errors from legitimate configurations
Summary: poppler-utils come with spurious errors from legitimate configurations
Alias: None
Product: Fedora
Classification: Fedora
Component: poppler   
(Show other bugs)
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kristian Høgsberg
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-15 18:51 UTC by Michal Jaegermann
Modified: 2008-06-17 02:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-17 02:10:03 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2007-08-15 18:51:38 UTC
Description of problem:

'man xpdfrc' says:

       bind modifiers-key context command ...
              Add a key or mouse button binding.

and 'man xpdf' gives: "Xpdf's key and mouse bindings are
user-configurable, using the bind and unbind options in
the config file" followed by some examples of use.  So far
so good and adding some 'bind' commands indeed works as

The catch is that poppler-utils programs seem to read those
configuration files too and at least 'pdftops', when one is
trying to use it, comes on stderr with:

Error: Unknown config file command 'bind' (/etc/xpdfrc:121)
Error: Unknown config file command 'bind' (/etc/xpdfrc:122)

Those "errors" seems to be only a noise without any real effect
on an outcome; even exit status after the above is 0.  Still
why to shout "Error:" for commands which are irrelevant and/or
unknown?  I think that such things should be simply ignored.

I did not try to check all valid xpdf configuration commands
but I would be surprised if the above applied only to 'bind'.
The next most likely candidate will be 'unbind' :-) and the list
is open-ended.

Version-Release number of selected component (if applicable):

How reproducible:

Comment 1 Bug Zapper 2008-05-14 14:00:02 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 WONTFIX if it remains open with a Fedora 'version' of '7'.

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 prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 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 please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2008-06-17 02:10:01 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.