Summary: | app-text/acroread-9.5.5 - nsplugin writes C:\nppdf32Log\debuglog.txt in home directory (which crashes kde-base/dolphin) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jouni Rinne <l33tmmx> |
Component: | [OLD] Printing | Assignee: | Printing Team <printing> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mmokrejs, pacho, rossi.f, vityokster |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
emerge-info.txt.gz nppdf.bsdiff |
Description
Jouni Rinne
2012-04-15 04:41:58 UTC
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? :) 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) + |