Created attachment 308993 [details] emerge --info This is quite a complicated bug, so please bear with me... Since the update to acroread-9.5.1 I have noticed that in some situations acroread's nsplugin part (I suppose) writes to the user's home directory a file, which causes KDE's dolphin file manager (and konqueror, too) to crash. The name of the mentioned file is 'C:\nppdf32Log\debuglog.txt' (Yes, with backslashes and all, that's probably the reason which causes dolphin to crash), with the content: NPP_GetValue is called NPP_GetValue is called NPP_GetValue is called NPP_GetValue is called NPP_Initialize : called NPP_Initialize : called NPP_Initialize : called So far, I have found two ways to reproduce the generation of the file: 1) start dolphin (4.8.2) 2) either a) start liferea (1.8.4) and browse to a feed, which has embedded videos, flash or such (http://icanhascheezburger.com/ RSS feed is good for testing), or b) start opera (11.62.1347-r1) 3) immediately, kcrashhandler announces that dolphin has segfaulted 4) the mentioned file has appeared in the home directory I first noticed this while using Liferea. I have no other applications using webkit-gtk, so I cannot tell how they would behave. However, if I remove the offending file, liferea and dolphin will continue to work for the rest of the day, the file is generated only in the first time. On later testing, I found out that Opera also triggers this bug every time it is started. So far I've been unable to reproduce this with Firefox, Chromium or Konqueror browsers. I think Adobe should be immediately notified about this. Acroread should NEVER be allowed to write a file with such a filename on Unix systems.
Oh, and acroread is installed with USE="cups minimal nsplugin -ldap"
*** Bug 412195 has been marked as a duplicate of this bug. ***
Eurgh. Actually two bugs: * acroread should not write any file * konqueror should not crash on a *valid* filename
(In reply to comment #3) > * konqueror should not crash on a *valid* filename That's right, because nautilus (which I rarely use) handles the file just fine. I have already made a bug report about this in KDE bugzilla.
(In reply to comment #4) > (In reply to comment #3) > > > * konqueror should not crash on a *valid* filename > > That's right, because nautilus (which I rarely use) handles the file just > fine. I have already made a bug report about this in KDE bugzilla. Link please? :)
Oh, sorry https://bugs.kde.org/show_bug.cgi?id=298199
Well, the second part of the bug, dolphin crash, was solved: it was caused by kde-base/dolphin-box-plugin from 'calculate'-overlay (provides Dropbox-KDE integration). Removal of it allowed dolphin to resume function without segfaults. But the first part of the bug still remains...
Maybe this recipe can help: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/986841/comments/3
(In reply to comment #8) > Maybe this recipe can help: > > https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/986841/comments/3 Yeah. Used this trick to "fix" the sillyness in 9.5.1-r1. Please test.
(In reply to Andreas K. Hüttel from comment #9) > > https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/986841/comments/3 > > Yeah. Used this trick to "fix" the sillyness in 9.5.1-r1. Please test. I'm seeing this 'C:\nppdf32Log\debuglog.txt'-file created with 9.5.5; has the fix been added to that version?
(In reply to Erik Quaeghebeur from comment #10) > (In reply to Andreas K. Hüttel from comment #9) > > > https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/986841/comments/3 > > > > Yeah. Used this trick to "fix" the sillyness in 9.5.1-r1. Please test. > > I'm seeing this 'C:\nppdf32Log\debuglog.txt'-file created with 9.5.5; has > the fix been added to that version? Yes the fix is there... please remove the file to make 100% sure it hasn't been created with an older version, and try to recreate the problem... If you get the file again, we'll reopen the bug
(In reply to Andreas K. Hüttel from comment #11) > Yes the fix is there... please remove the file to make 100% sure it hasn't > been created with an older version, and try to recreate the problem... If > you get the file again, we'll reopen the bug I have still the same problem, to be sure I have just reemerged acroread. Looking at the hex dump of nppdf.so I can see the string C:\nppdf32Log\debuglog.txt.
Created attachment 360132 [details] emerge-info.txt.gz emerge configuration on my system
If I substitute "C:\nppdf32Log\debuglog.txt" with "/dev/null" (and trailing zeros) in the hex file, I get the following base64-coded patch: QlNESUZGNDBGAAAAAAAAADkAAAAAAAAAYL0CAAAAAABCWmg5MUFZJlNZd+YjIAAAFehR+jQCIAAQ QAAEAAAIQAAgACGSGjIzUKYAAemnm9OSR1jFrI8oWLCEr4u5IpwoSDvzEZAAQlpoOTFBWSZTWe+t fxQAAWBiCMAACAAABAIAAAggACClIwZoNiJ7FKm/oINyBThdyRThQkO+tfxQQlpoOTFBWSZTWUaj bYYAAALBAEAAAIAgACEAgpMXckU4UJBGo22G
I'm sorry, in #14 I made a bsdiff using a wrong nppdf.so... the right patch is the following: QlNESUZGNDBGAAAAAAAAAC8AAAAAAAAAoK8CAAAAAABCWmg5MUFZJlNZQBbHOQAAFOxgeDgkIAAQ ABRAIAEAIAAhqekMmjR6hTAATRkg7TkAW4RBG9TSowH75fF3JFOFCQQBbHOQQlpoOTFBWSZTWRZR rZgAAVlEAMAAAgAACCAAMMwFKaZFJsUUni7kinChICyjWzBCWmg5MUFZJlNZMxj0RgAAABGAAACG BQMAIAAiB6m1CGAHQRfF3JFOFCQMxj0RgA==
Archlinux has a patch for this that maybe could work :/ https://aur.archlinux.org/packages/acroread/
Created attachment 383994 [details] nppdf.bsdiff
acroread has been recently updated to 9.5.5-r2 but this bug has not been fixed yet. Any plan?
*** Bug 547924 has been marked as a duplicate of this bug. ***
I am not sure about what I need to do to test if the file is still created... but can you check if replacing all the bdiff magic by this sed statement from Arch does the trick? sed -i 's#C:\\nppdf32Log\\debuglog\.txt#/dev/null\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00#g' \ Adobe/Reader9/Browser/intellinux/nppdf.so
I just applied the sed commands, will see when they pop up back again. BTW, I applied the sed over two files: /opt/Adobe/Reader9/Browser/intellinux/nppdf.so /usr/lib32/nsbrowser/plugins/nppdf.so
(In reply to Martin Mokrejš from comment #21) > I just applied the sed commands, will see when they pop up back again. BTW, > I applied the sed over two files: > > /opt/Adobe/Reader9/Browser/intellinux/nppdf.so > /usr/lib32/nsbrowser/plugins/nppdf.so the second one is a sym link to the first
(In reply to Pacho Ramos from comment #20) > I am not sure about what I need to do to test if the file is still > created... but can you check if replacing all the bdiff magic by this sed > statement from Arch does the trick? > sed -i > 's#C:\\nppdf32Log\\debuglog\.txt#/dev/ > null\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00#g' \ > Adobe/Reader9/Browser/intellinux/nppdf.so I confirm that the sed command works, same result as bsdiff solution in #15
+*acroread-9.5.5-r3 (09 May 2015) + + 09 May 2015; Pacho Ramos <pacho@gentoo.org> +acroread-9.5.5-r3.ebuild, + -acroread-9.5.5.ebuild: + Don't create bogus file (#412051), fix .desktop file (#476096 and #543592) +
