From: Nilesh Govindrajan <me@nileshgr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] acroread 9.5.5 segfault
Date: Thu, 13 Feb 2014 07:23:17 +0530 [thread overview]
Message-ID: <52FC258D.3010500@nileshgr.com> (raw)
In-Reply-To: <CAGCL9KhyxvWPC1dyw0w4Tsxc=nHwq2PWEwhi8OiC7YqcRR9oQQ@mail.gmail.com>
On Thursday 13 February 2014 07:06 AM, Tim wrote:
> I am trying to use acroread 9.5.5 only for its ability to display
> animations. If I run:
>
> $ ACRODEBUG=1 ACRO_CRASHLOG=1 acroread
>
> and then try to open a file (or include the filename on the command
> line), I simply get "Segmentation fault". If I try
>
> $ acroread -DEBUG acroread
>
> I get:
>
> Loading PlugIn /opt/Adobe/Reader9/Reader/intellinux/plug_ins/Annots.api
> ... [dlopen success for Annots.ap940]
> Loading PlugIn /opt/Adobe/Reader9/Reader/intellinux/plug_ins/EScript.api
> ... [dlopen success for EScript.api, handle = 0xc60bf80]
> Crashlog has been dumped in /tmp/acroCrashLogs/0212_2024_DKRaHb
>
> where the contents of the crashlog is
>
> /opt/bin/acroread [0x850ab41] [@0x8048000]
> linux-gate.so.1(__kernel_sigreturn+0x0) [0xb77cd400] [@0xb77cd000]
>
> I noticed a bug concerning the use of glibc-2.18, but I am using 2.17.
> I've run 'emerge @preserved-rebuild', nothing was built. I got a
> confirmation from someone on IRC about a working, standard setup, so I'm
> asking here rather than on the Adobe forums.
>
> Help!
I shouldn't be saying this, but is there any specific reason you're
using acroread? It hasn't been updated for over 2 years now -- even if
you manage to fix it now, it'll definitely break again in future when
all dependencies move forward.
The open source PDF readers like evince, okular, pdf.js
(firefox/chromium) are decent enough.
next prev parent reply other threads:[~2014-02-13 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 1:36 [gentoo-user] acroread 9.5.5 segfault Tim
2014-02-13 1:53 ` Nilesh Govindrajan [this message]
2014-02-13 6:28 ` Alan McKinnon
2014-03-19 9:07 ` Tom Wijsman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52FC258D.3010500@nileshgr.com \
--to=me@nileshgr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox