The wrapper installed by the multilingual acroread ebuild (7.0.8-r1) prevents acroread from opening file from the command line. Steps to reproduce: 1. env LINGUAS="en ja" emerge =acroread-7.0.8-r1 2. acroread /dev/null Expected results: Adobe Reader starts and shows a dialog box with the following text: Adobe Reader could not open 'null' because it is either not a supported file type or because the file has been damaged (for example, it was sent as an email attachment and wasn't correctly decoded). Actual results: Adobe Reader starts. The fix is to patch the ebuild like this: 146c146 < echo "${ll}*) exec ${INSTALLDIR}/acroread.${ll} ;;" >> bin/acroread --- > echo "${ll}*) exec ${INSTALLDIR}/acroread.${ll} \"\${@}\" ;;" >> bin/acroread 150c150 < *) exec ${INSTALLDIR}/acroread.${fl} ;; --- > *) exec ${INSTALLDIR}/acroread.${fl} "\${@}";;
Version 7.0.9 still doesn't open the filename given as parameter. This not only means you can't open from the command line, but opening a PDF in Konquerer yields en empty acroread window.
It breaks plugin support too, they wont work with the wrapper while it's missing support for sending command line options to the real scripts. The language scripts themself support command line options just fine.
This problem is fixed in 7.0.9-r1 It's still marked as testing, you can of course add $* at the end of each language option you have in wrapper to fix it manually.
7.0.9-r1 works fine for me on x86 where 7.0.9 would not work. Given that this is a regression from previous versions I think it would be good to stabilize this sooner rather than later.
This bug is a SHOWSTOPPER. It still exists on amd64 on Jan 24th, 2007. It seems that r1 fixes this, but r1 is still masked. Please commit that change ASAP.
(In reply to comment #5) > This bug is a SHOWSTOPPER. It still exists on amd64 on Jan 24th, 2007. It seems > that r1 fixes this, but r1 is still masked. > > Please commit that change ASAP. > I totally agree with this. I too have emerged 7.0.9-r1 and it works perfectly. How come a flawed ebuild with such an annoying bug goes stable without anyone noticing and then weeks pass until the fix is declared stable?
*** Bug 167599 has been marked as a duplicate of this bug. ***
x86 stable
Stable on amd64.
