LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
 
Search this Thread
Old 06-29-2013, 11:11 AM   #1
ljb643
Member
 
Registered: Nov 2003
Posts: 312

Rep: Reputation: Disabled
Adobe Reader on Slackware funny file


(I don't use Adobe Reader on Slackware much, especially since Firefox now has a built-in PDF viewer, but I keep it on one PC because occasionally a document has trouble viewing or printing with xpdf.)

After using the latest Adobe Reader 9.5.5 as a Firefox plugin on Slackware 14, I find this file left in my home directory:
Code:
C:\nppdf32Log\debuglog.txt
Yes, that is the exact filename that appears in my Slackware home directory. It seems to have some debug messages from the Reader plugin.
 
Old 06-29-2013, 12:08 PM   #2
Roberto Neri
LQ Newbie
 
Registered: Nov 2012
Location: Palermo, Italy
Distribution: Slackware
Posts: 9

Rep: Reputation: Disabled
Apparently there's not yet a way to avoid the creation of this file (e.g. a command-line option or a preference setting), so eventually I adopted a quick and dirty solution, i.e. replace the debug file name with /dev/null in the nppdf.so library, like so

sed -i.orig 's%C:\\nppdf32Log\\debuglog.txt%/dev/null %' /opt/Adobe/Reader9/Browser/intellinux/nppdf.so

HTH
 
Old 06-29-2013, 12:44 PM   #3
mancha
Member
 
Registered: Aug 2012
Posts: 399

Rep: Reputation: Disabled
Not only is it troubling that acroread is writing unsolicited files to the system but to add insult to injury
it is a "windows file". The bug seems to related to Adobe debugging code not having been turned off in the release.

I hacked a quick build script which puts things into /opt/Adobe. If you use a different path just make
the relevant change to my code below. I added this to my build script after I expand COMMON.TAR & ILINXR.TAR.

Code:
( cd $PKG/opt/Adobe/Reader9/Browser/intellinux
  /usr/bin/perl -i -pe 's|\x43\x3A\x5C\x6E\x70\x70\x64\x66\x33\x32\x4C\x6F\x67\x5C\x64\x65\
x62\x75\x67\x6C\x6F\x67\x2E\x74\x78\x74|\x2F\x64\x65\x76\x2F\x6E\x75\x6C\x6C\x00
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00|' nppdf.so
)
Note: The worry I have with Roberto's solution is it actually changes the library's size and if things are
dependent on hard offsets things can go haywire.

Last edited by mancha; 06-29-2013 at 09:51 PM.
 
Old 06-30-2013, 02:49 AM   #4
mancha
Member
 
Registered: Aug 2012
Posts: 399

Rep: Reputation: Disabled
If you looked at my Perl substitution and it conjured scary thoughts of shell-code or if you're simply the curious type and
enjoy looking under the hood, you can see exactly what is getting changed by doing this in a bash shell:

Code:
$ mkdir temp
$ cd temp
$ wget ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.5.5/enu/AdbeRdr9.5.5-1_i486linux_enu.tar.bz2
$ tar xf AdbeRdr9.5.5-1_i486linux_enu.tar.bz2
$ cd AdobeReader
$ tar xf ILINXR.TAR Adobe/Reader9/Browser/intellinux/nppdf.so --strip 4
$ /usr/bin/perl -i.orig -pe 's|\x43\x3A\x5C\x6E\x70\x70\x64\x66\x33\x32\x4C\x6F\x67\x5C\x64\x65\x62\x75\x67\x6C\x6F\x67\x2E\x74\x78\x74|\x2F\x64\x65\x76\x2F\x6E\x75\x6C\x6C\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00|' nppdf.so
$ diff <(xxd nppdf.so.orig) <(xxd nppdf.so)
--mancha
 
Old 06-30-2013, 03:08 AM   #5
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,770

Rep: Reputation: 1002Reputation: 1002Reputation: 1002Reputation: 1002Reputation: 1002Reputation: 1002Reputation: 1002Reputation: 1002
I was curious but I used this
Code:
 echo -e 's|\x43\x3A\x5C\x6E\x70\x70\x64\x66\x33\x32\x4C\x6F\x67\x5C\x64\x65\x62\x75\x67\x6C\x6F\x67\x2E\x74\x78\x74|\x2F\x64\x65\x76\x2F\x6E\x75\x6C\x6C\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00|'
 
Old 06-30-2013, 05:41 PM   #6
ljb643
Member
 
Registered: Nov 2003
Posts: 312

Original Poster
Rep: Reputation: Disabled
I was thinking that with Firefox able to view PDF files without a plugin, I might be finally rid of Adobe Reader. But today I see Slackware changing to the Firefox17.x ESR release (perhaps temporarily, perhaps not). I am guessing that 17ESR does not include the PDF viewer - can anyone confirm this? Do I need to stick to Adobe Reader and its odd debug file?
 
Old 06-30-2013, 07:53 PM   #7
Diantre
Member
 
Registered: Jun 2011
Distribution: Slackware64 14.1
Posts: 432

Rep: Reputation: 164Reputation: 164
Quote:
Originally Posted by ljb643 View Post
I was thinking that with Firefox able to view PDF files without a plugin, I might be finally rid of Adobe Reader. But today I see Slackware changing to the Firefox17.x ESR release (perhaps temporarily, perhaps not). I am guessing that 17ESR does not include the PDF viewer - can anyone confirm this? Do I need to stick to Adobe Reader and its odd debug file?
Firefox 17 ESR doesn't have the builtin pdf viewer. I'm hoping the next ESR release (to be released in September, I think...) will include it.
 
Old 06-30-2013, 08:01 PM   #8
frankbell
Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Mageia, Mint
Posts: 8,768

Rep: Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690Reputation: 1690
It's been years since I've used Adobe Reader.

I have found Okular to be a perfectly satisfactory PDF viewer.

(I use Foxit Reader on Windows.)
 
Old 06-30-2013, 09:33 PM   #9
mancha
Member
 
Registered: Aug 2012
Posts: 399

Rep: Reputation: Disabled
If you use the SBo-maintained Adobe reader you can request that its maintainer, ArTourter, add a fix (such as mine in post #3 above) or do it yourself.

As for the Mozilla reader (pdf.js), you are right, it got included as of FF18. However, you can add it to FF17 as an extension.

Also, and Pat might be interested to know this, there will be version parity between Release and ESR two versions from now. There
will be an ESR 24.x if all goes according to plans.

--mancha
 
Old 07-01-2013, 06:29 AM   #10
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, CentOS
Posts: 2,191

Rep: Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169Reputation: 1169
If you plan on using Adobe Reader, you can get rid of /usr/sbin/create-prism-cronjob.sh after the initial launch.

 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] How to install Adobe PDF Reader for Mozilla Firefox on Slackware 13.37 glupa4e Slackware 24 07-10-2012 01:27 AM
Adobe Reader 64bit Debian file is not available TigerLinux Linux - Newbie 5 12-17-2011 08:06 PM
[SOLVED] Adobe Reader 9 associated itself to every file type in Xfce 4.4. stf92 Slackware 9 02-06-2011 04:59 AM
adobe reader enu (32 bit only) on slackware 64 ponce Slackware 2 09-06-2009 12:16 AM
Adobe Reader 7.0 and Slackware 10.1, problem opening a file that required a plugin houler Linux - Software 0 05-29-2005 03:23 PM


All times are GMT -5. The time now is 08:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration