What is the file: C:\nppdf32Log\debuglog.txt [closed]


After I updated to 12.04, a file named C:\nppdf32Log\debuglog.txt occurs in my home directory. The content of the file is as the follow:

NPP_Initialize : called NPP_GetValue is called NPP_SetWindow : called for instance 920c0e28 Window from browser - 77594625 NPP_SetWindow : called for instance 920c0e28 Window from browser - 77594625 NPP_SetWindow : called for instance 920c0e28 Window from browser - 77594625 NPP_NewStream : called for instance 920c0e28, stream 913403b0, URL http://www.xxxxxx.com/attachments/soft/CDGM%20Optical%20Glass%20Catalog.pdf, stream size 36177984, seekable 1 NPP_Write : called for instance 920c0e28, stream 913403b0, offset = 0, length = 16384, streamlength = 36177984 Trying for window attributes Trying for query tree NPP_Write : called for instance 920c0e28, stream 913403b0, offset = 16384, length = 16384, streamlength = 36177984 Trying for window attributes Trying for query tree ......

It seems this file is related to Firefox, what's exactly the...

0 0

> Is there a particular reason you need to use Adobe Reader? I

> personally abandoned it years ago in favour of Evince, and I haven't

> looked back. I can only remember one instance I had problems opening a

> PDF, and that was in regard to security settings being interpreted

> wrongly. That was over a year ago though, and it might no longer be an

> issue.


> On Sun, Apr 29, 2012 at 12:56 PM, Piscium

[hidden email]

> wrote:

> On 29 April 2012 05:20, Darlene Wallach


[hidden email]

> wrote:

> > What does this file mean? I don't understand how I got it in

> my home directory

> >

> > Thank you

> >

> > Darlene Wallach

> >

> > $ cat C\:\\nppdf32Log\\debuglog.txt



> It was only last week that I realised I had that file in my

> home

> directory. I do have Acrobat...

0 0

Steps to reproduce:
1. Start Firefox (do this from the command-line to get a specific working-directory since the log is saved relative to the FF working dir)
2. Open a PDF, e.g. http://partners.adobe.com/public/developer/en/xml/AdobeXMLFormsSamples.pdf
3. Close Firefox

Result: In the working directory from step 1 there will be a file called "C:\nppdf32Log\debuglog.txt" (yes, this Windows-like path will be present on a Linux filesystem)

Exected result: No debug log should be produced.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

$ uname -a
Linux xpc 3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l | grep acroread
ii acroread 9.5.1-1oneiric1 Adobe Reader
ii acroread-common 9.5.1-1oneiric1 ...

0 0
Additional info: libreport version: 2.0.18 kernel: 3.7.6-102.fc17.i686.PAE description: :SELinux is preventing /usr/lib/xulrunner/plugin-container from 'append' accesses on the file C:\nppdf32Log\debuglog.txt. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that plugin-container should be allowed append access on the C:\nppdf32Log\debuglog.txt file by default. :Then you should report this as a bug. :You can generate a local policy module to allow this access. :Do :allow this access for now by executing: :# grep plugin-containe /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c : 0.c1023 :Target Context unconfined_u:object_r:user_home_dir_t:s0 :Target Objects C:\nppdf32Log\debuglog.txt [ file ] :Source plugin-containe :Source Path /usr/lib/xulrunner/plugin-container...
0 0

I notice after running casper --engine=slimerjs that "C:\nppdf32Log\debuglog.txt" sometimes appears in that directory (I'm using Mint 17, aka Ubuntu 14.04) (It probably happens running slimerjs directly, but I hardly ever use it that way.)

I found some information about it here: http://askubuntu.com/a/144429/93794

I believe I'm running a vanilla clone of latest github slimerjs, and it should be using the default gecko engine, not my local firefox, but if I'm the only person seeing this let me know and I will try and narrow down which command, or which configuration, is triggering it. My local Firefox does have the Adobe PDF 9.5 plugin installed.

P.S. This can be flagged low priority. It is an annoyance, nothing...

0 0


latest Adobe Reader for Linux (9.5.5) - its plugin for firefox named nppdf32.so creates junk debug files named: 'C:\\nppdf32Log\\debuglog.txt' in directories from where a firefox was executed.

This happens since Acrobat Reader 9.5.1 release.

How to make Adobe fixing this bug?

How to contact them efficiently?

This bug exists since 9.5.1 dated 04/09/2012 and Adobe do not care. Fix is trivial for Adobe: disable debug logging in release versions and stop using Windows path 'C:\\nppdf32Log\\debuglog.txt' in Linux products.

Workaround for this bug is trivial: open in hex editor: nppdf32.so file installed by Adobe Reader, go to position 0x0002193a in this file (or simply search for C:\ - there is only one place), and replace string:




Because string /dev/null is shorter than C:\\nppdf32Log\\debuglog.txt fill remainings of previous string with hex zeroes: 00 to keep...

0 0

Due to a bug ("feature") in the PDF plugin module for

Adobe Acrobat Reader, use of the plugin from within a

browser or email reader results in the creation of the

file "C:\nppdf32Log\debuglog.txt" in whatever working

directory the plugin runs in. In Thunderbird, this

creates a new bogus mail folder. Various posters have

noted that creating a symbolic link with this name

pointing at "/dev/null" will prevent the data from


However, the file will still exist. An alternative is to
do a binary patch to fix the problem. The filename in
question is a string constant in the module "nppdf.so",
of which your system may have multiple copies associated
with different browsers, email handlers, etc. In each of
these use 'ht' to search for "C:\nppdf32Log\debuglog.txt"
and change it. In my system (Slackware 14 with Adobe
Acrobat Reader 9.5.1 installed), nppdf.so is 179552...

0 0
0 0
Luis Arias kaaloo at gmail.com
Wed May 2 13:41:42 UTC 2012 Previous message: Stuck on Starting container... since upgrade to precise :( Next message: Stuck on Starting container... since upgrade to precise :( Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] It's strange but the complete name of the file was ' C:\nppdf32Log\debuglog.txt'. Luis On Wed, May 2, 2012 at 2:32 PM, Serge E. Hallyn wrote: > Quoting Luis Arias (kaaloo at gmail.com): > > Hi, > > > > I found that C:\nppdf32Log\debuglog.txt file in my home dir and deleted > it. > > Googling around it seems this file is created by Adobe Reader. Anyhow, > I > > cleared as many caches as I could find ~/.juju/cache, /var/cache/lxc, > > I don't understand. What is your host system, that on which you are > running juju? How does it find a 'C:'? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: Previous message: Stuck on...
0 0

I have a few commited files in my GIT branch which I don't want to push it to my repository. How do I unstage them and remove the files from my branch.

I always get this file: "C:\nppdf32Log\debuglog.txt"

In my commit included, I don't understand how to remove this from my git commit now.

when I do a diff between branches I get the following:

git diff feature_mentoring_connections_v2 --name-only "C:\\nppdf32Log\\debuglog.txt" app/controllers/mentoring_models_controller.rb app/helpers/mentoring_models_helper.rb app/models/object_permission.rb app/models/program_observer.rb

Now I need to remove "C:\nppdf32Log\debuglog.txt" from my branch.

This is the solution:

git rm "C:\\nppdf32Log\\debuglog.txt" git commit -m "Remove...
0 0

I had this same problem, but it was not due to Firefox and I wonder if the original asker might have made the same mistake I did in configuring his xdebug.

As a newbie, in setting the value for xdebug.remote_log in my php.ini (actually in separate xdebug.ini), I used the windows file path to my project on my local machine. Why? Because the value called "remote_log", so I mistakenly thought it wanted the path on my windows machine, which I thought was very strange at the time. But I am new to remote debugging, so... Oops.

Using windows path is wrong:


And it results in:


(the bolded part is the actual file name)

This is right:


And presumably results in:


(the bolded part is the actual file name)

It appears...

0 0

You should be able to achieve this with AppArmor, which allows one to block access based on pathname. File system type doesn't play any role in this case.

Another option is of course using another PDF viewer. If you insist on having it in the browser then for example Firefox from version 19 on has a built-in JavaScript one.

You can also hack the plugin as mentioned in the Ubuntu bug. I now remember doing that long time ago (either the bug has been there for ages or it has been reintroduced lately), when I was still using it. If you have Perl installed, you can "fix" the plugin with:

perl -p -e 's,C:\\nppdf32,/dev/null\0,' /usr/lib/browser-plugins/nppdf.so

(you may need to update the path to the file for your...

0 0

User Help for Mozilla Firefox

aaa237pw Posts: 3Joined: April 18th, 2012, 7:13 am


I am using the uptodate ESR on uptodate Debian Wheezy with KDE 4.7.4.

I searched and found that earlier versions of Firefox had issues with a file named nppdf32.so.

The subject file in my main users directory. It grows substantially when Firefox opens and it can contain up to 7,000 lines with each line stating, "NPP_GetValue is called". Nothing else.

It has something to do with Adobe Reader but after that I know nothing. All issues that I have looked at deal with Windows and I have absolutely nothing on my system to do with Windows. The file looks to want to reside in the main Windows directory.

I have added a line to my hourly incremental backup to remove the file if it exists but that is not really a solution just a temporary workaround.

Any suggestions or observations?


I would get rid of Adobe Reader. I don't know why...

0 0