Bug 45945 - /etc/pluggerrc too optimistic about file names
/etc/pluggerrc too optimistic about file names
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: plugger (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-06-25 19:45 EDT by Michal Jaegermann
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-06-26 23:20:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2001-06-25 19:45:21 EDT
Various files "in the wild" have blanks in their names.  Therefore all
occurences of $file in /etc/pluggerrc should be quoted like this: "$file".
This really makes a difference.

Moreover 'pluggerrc' package is missing man page.  At least in the
current 3.3 there is one and a URL in README (the only really supplied
documenation) referes one to it.
Comment 1 Ngo Than 2001-06-26 08:55:22 EDT
plugger-3.3-1 in rawhide fix this problem.
Comment 2 Michal Jaegermann 2001-06-26 23:08:58 EDT
> plugger-3.3-1 in rawhide fix this problem

Not quite.  Most of $file occurences is indeed now quoted but these three

        many:xanim +Av100 -Zr +W$window +q +Ze +f $file
        many: timidity -s 65000 -a -idqqqqqqq $file
        many: mpg123 -q -b 128 $file

are still there.  Use a global replace. :-)
Comment 3 Michal Jaegermann 2001-06-26 23:20:43 EDT
BTW - could you, please, add to /etc/pluggerrc the following lines (they do
not even have to be commented as netscape plugin will default to acroread):

application/pdf: pdf: Portable Document Format
        exits : xpdf "$file"

Other platforms may not even have acroread available and this works (tested).
Comment 4 Ngo Than 2001-06-27 12:13:32 EDT
Thanks, it's fixed in plugger-3.3-2.

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