Discussion:
acrobat dependencies for -current64
(too old to reply)
John Forkosh
2022-06-26 06:36:45 UTC
Permalink
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.

The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.

How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Javier
2022-06-26 14:50:04 UTC
Permalink
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
The best is to run xpdf, which has been improved recently.

But if you need to use acroread have a look at this:

https://aur.archlinux.org/packages/acroread

mxr commented on 2014-11-10 04:53 (UTC)
I got segfaults too (only when actually loading a file), but changing
the GTK2 theme helped. GNOME3 uses Adwaita for GTK2 and it seems to
work. If you do not want to change your GTK2 theme it can be set via
the cmdline as an environment variable:
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread This
actually solves the segfault problem for me.

I personally don't like 'adawita' and use a custom gtk2rc that
looks like this:

# gtk-cursor-theme-name = "Raleigh"
# gtk-icon-theme-name
# gtk-fallback-icon-theme
gtk-theme-name = "Raleigh"
style "user-font"
{
font_name="Cantarell 11"
}
widget_class "*" style "user-font"

There are several other bugs, one that crashes acroread the second
time you open a print dialog.

tattsan commented on 2020-08-02 10:36 (UTC) (edited on 2020-08-06 07:38 (UTC) by tattsan)
There's still another crashing issue. If we open the printing dialog and open properties in it TWICE (open - close - reopen), acroread will crash.
[SOLVED] 2020-08-06
Downgrading lib32-libcups to 2.2.10-1 solved this issue.
John Forkosh
2022-06-28 08:23:24 UTC
Permalink
Post by Javier
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
Thanks, Javier...
Post by Javier
The best is to run xpdf, which has been improved recently.
Hey, I said don't do that :) But if you really must know,
it's print density. acroread prints pdfs nice and dark and thick,
just like I like for reading arXiv preprints and similar technical
stuff with lots of math that's particularly difficult to read
when it's inline ($...$ rather than $$...$$).
Okular just sucks, sucks, sucks in this regard -- stuff prints
very thin and light, and no adjustments that I can find change it.
Printing directly from firefox, when pdfs are opened in firefox,
works maybe 1/2-to-2/3 as well as acroread. xpdf's in-between,
so to speak, okular and firefox. And I've tried various others,
e.g., gv, evince, etc. acroread's best by far, in my experience,
and well worth the trouble installing it...as long as that's possible.
Post by Javier
https://aur.archlinux.org/packages/acroread
mxr commented on 2014-11-10 04:53 (UTC)
I got segfaults too (only when actually loading a file), but changing
the GTK2 theme helped. GNOME3 uses Adwaita for GTK2 and it seems to
work. If you do not want to change your GTK2 theme it can be set via
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread This
actually solves the segfault problem for me.
Thanks, tried it, no change. But note that I use fvwm2 (with an fvwm95
"overlay"). But I tried running /etc/X11/xinit/xinitrc-->xinitrc.kde
just in case, but it made no difference whatsoever.
Post by Javier
I personally don't like 'adwaita' and use a custom gtk2rc that
# gtk-cursor-theme-name = "Raleigh"
# gtk-icon-theme-name
# gtk-fallback-icon-theme
gtk-theme-name = "Raleigh"
style "user-font"
{
font_name="Cantarell 11"
}
widget_class "*" style "user-font"
There are several other bugs, one that crashes acroread the second
time you open a print dialog.
tattsan commented on 2020-08-02 10:36 (UTC) (edited
on 2020-08-06 07:38 (UTC) by tattsan)
There's still another crashing issue. If we open the printing dialog
and open properties in it TWICE (open - close - reopen), acroread
will crash.
[SOLVED] 2020-08-06
Downgrading lib32-libcups to 2.2.10-1 solved this issue.
Hmm... don't seem to have lib32-libcups,
just /usr/lib/libcups.so-->libcups.so.2
But that seems to be coming from multilib's
cups-compat32-2.4.2-x86_64-1compat32.txz (no libcups in slack64 at all).
so maybe I should try "downgrading" from what's apparently 2.4.2.
But I'm not seeing a crash, just that message.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
John Forkosh
2022-06-28 08:56:01 UTC
Permalink
<<snip>>
Post by Javier
https://aur.archlinux.org/packages/acroread
mxr commented on 2014-11-10 04:53 (UTC)
I got segfaults too (only when actually loading a file), but changing
the GTK2 theme helped. GNOME3 uses Adwaita for GTK2 and it seems to
work. If you do not want to change your GTK2 theme it can be set via
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread This
actually solves the segfault problem for me.
Thanks, tried it, no change. But note that I use fvwm2 (with an fvwm95
"overlay"). But I tried running /etc/X11/xinit/xinitrc-->xinitrc.kde
just in case, but it made no difference whatsoever.
Oops, I lied.
That works like a charm (even better than any charm I have)!!!
Trouble was I'd just tried
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
and then ran acroread on a separate line. And that still fails.
But I forgot to
export GTK2_RC_FILES
so I only had a shell variable, not an environment variable.
Once I did that, it still emits the original error message
(acroread:2571): Gtk-WARNING **: 04:46:56.025: Unable to locate
theme engine in module_path: "adwaita"
(in fact, it now emits the identical message twice), but it then
goes on to open a window containing my requested document.
And so far (which has been all of five minutes), no other
problems as far as I can tell (not seeing Rob's problem).
So thanks so very much for solving the problem! And such an easy fix.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
John Forkosh
2022-07-22 03:10:06 UTC
Permalink
Post by John Forkosh
<<snip>>
Post by Javier
https://aur.archlinux.org/packages/acroread
mxr commented on 2014-11-10 04:53 (UTC)
I got segfaults too (only when actually loading a file), but changing
the GTK2 theme helped. GNOME3 uses Adwaita for GTK2 and it seems to
work. If you do not want to change your GTK2 theme it can be set via
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread This
actually solves the segfault problem for me.
That works like a charm (even better than any charm I have)!!!
Trouble was I'd just tried
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
and then ran acroread on a separate line. And that still fails.
But I forgot to
export GTK2_RC_FILES
so I only had a shell variable, not an environment variable.
Once I did that, it still emits the original error message
(acroread:2571): Gtk-WARNING **: 04:46:56.025: Unable to locate
theme engine in module_path: "adwaita"
(in fact, it now emits the identical message twice), but it then
goes on to open a window containing my requested document.
And so far (which has been all of five minutes), no other
problems as far as I can tell (not seeing Rob's problem).
So thanks so very much for solving the problem! And such an easy fix.
One additional minor irritation...
Logged in as an ordinary user, acroread starts up fine.
But if you click the File menu (which itself comes up fine),
and then click Print (or any other submenu link), it just
immediately exits. No error reported, just exits.
However, if you now su as root and run acroread, then the
submenus come up fine, and everything works as it should,
at least as far as I can tell, so far. But why do I have to su?
I'm assuming it's some file permissions somewhere that are
denying read and/or write access to some file(s) that acroread
needs to read/write. And I tried looking at lsof output to
determine which file(s) -- compared output after clicking File
and then before/after clicking Print. But it's too much stuff
for me to figure out any significant diffs, if there are any.
So what's the problem? Which file(s) do I have to chmod to
run acroread, and print from it, without su'ing?
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Henrik Carlqvist
2022-07-22 04:44:32 UTC
Permalink
Which file(s) do I have to chmod to run acroread, and print from it,
without su'ing?
I don't have the answer, but you might be able to find the answer by
running:

strace -f acroread

and study the output from strace after acroread has crashed.

regards Henrik
John Forkosh
2022-07-22 06:59:37 UTC
Permalink
Post by Henrik Carlqvist
Which file(s) do I have to chmod to run acroread, and print from it,
without su'ing?
I don't have the answer, but you might be able to find the answer by
strace -f acroread
and study the output from strace after acroread has crashed.
regards Henrik
Thanks, but no luck studying that, at least not for my level of
understanding, which is ground floor at best. The 44,149 lines
of strace output end with...

--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
getpid() = 3616
rt_sigaction(SIGABRT, {sa_handler=SIG_DFL, sa_mask=[ABRT],
sa_flags=SA_RESTART}, {sa_handler=0x850aafa, sa_mask=[],
sa_flags=0}, 8) = 0
exit_group(1) = ?
+++ exited with 1 +++

And there are various "No such file..." messages before that.
But there are a zillion "No such file..." messages starting
at line#3 of the output, and I'm not seeing any particular
reason for the SIGABRT signal. (Also trying --trace=%file
didn't make the output any easier for me to sift through.)
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Henrik Carlqvist
2022-07-23 10:22:26 UTC
Permalink
Post by John Forkosh
Post by Henrik Carlqvist
Which file(s) do I have to chmod to run acroread, and print from it,
without su'ing?
I don't have the answer, but you might be able to find the answer by
strace -f acroread
and study the output from strace after acroread has crashed. regards
Henrik
Thanks, but no luck studying that, at least not for my level of
understanding, which is ground floor at best. The 44,149 lines of strace
output end with...
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
getpid() = 3616 rt_sigaction(SIGABRT,
{sa_handler=SIG_DFL, sa_mask=[ABRT],
sa_flags=SA_RESTART}, {sa_handler=0x850aafa, sa_mask=[],
sa_flags=0}, 8) = 0
exit_group(1) = ?
+++ exited with 1 +++
And there are various "No such file..." messages before that.
But there are a zillion "No such file..." messages starting at line#3 of
the output, and I'm not seeing any particular reason for the SIGABRT
signal. (Also trying --trace=%file didn't make the output any easier for
me to sift through.)
I was hoping that you would find some "EACCES (Permission denied)" that
would explain why the program works better when run as root.

A SIGSEGV (segmentation violation) is usually some kind of bug. It is
possible to set the limit of a core dump size with something like "ulimit
-c 500M" and that generated core file might be usable to find the bug,
but that would only be usable if you had access to the source code of the
application.

In lack of source you might have to resort to the simple problem fixing
routine well known to all users of commercial OS and applications:

1) restart
2) reinstall
3) upgrade

However, as acrobat reader are not expected to come with any new version
for Linux you might instead want to try to downgrade.

regards Henrik
John Forkosh
2022-07-23 13:19:43 UTC
Permalink
Post by Henrik Carlqvist
Post by John Forkosh
Post by Henrik Carlqvist
Which file(s) do I have to chmod to run acroread, and print from it,
without su'ing?
I don't have the answer, but you might be able to find the answer by
strace -f acroread
and study the output from strace after acroread has crashed. regards
Henrik
Thanks, but no luck studying that, at least not for my level of
understanding, which is ground floor at best. The 44,149 lines of strace
output end with...
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
getpid() = 3616 rt_sigaction(SIGABRT,
{sa_handler=SIG_DFL, sa_mask=[ABRT],
sa_flags=SA_RESTART}, {sa_handler=0x850aafa, sa_mask=[],
sa_flags=0}, 8) = 0
exit_group(1) = ?
+++ exited with 1 +++
And there are various "No such file..." messages before that.
But there are a zillion "No such file..." messages starting at line#3 of
the output, and I'm not seeing any particular reason for the SIGABRT
signal. (Also trying --trace=%file didn't make the output any easier for
me to sift through.)
I was hoping that you would find some "EACCES (Permission denied)" that
would explain why the program works better when run as root.
Yeah, I'd tried stuff like chown -R /usr/local/Adobe so that I owned
everything, but that (and anything else I tried) didn't work.
Post by Henrik Carlqvist
A SIGSEGV (segmentation violation) is usually some kind of bug. It is
possible to set the limit of a core dump size with something like "ulimit
-c 500M" and that generated core file might be usable to find the bug,
but that would only be usable if you had access to the source code of the
application.
In lack of source you might have to resort to the simple problem fixing
1) restart
2) reinstall
3) upgrade
However, as acrobat reader are not expected to come with any new version
for Linux you might instead want to try to downgrade.
regards Henrik
Nah, thatnks, but I'll just su whenever I want to use acroread to print.
That ain't so often. And I can still use acroread just for reading
without su. Moreover, I typically navigate and read with firefox
anyway. It's just the occasional hardcopy print that I find
acroread does more to my liking.
By the way, note that this guy seems to have the same problem,
https://unix.stackexchange.com/questions/239617
although he seems to be having some explicit ldap problem that
isn't relevant to my situation.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Robert Komar
2022-06-26 16:54:56 UTC
Permalink
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
I needed to fill in PDF forms for my taxes a few months ago, and found
out that the PDF viewer in firefox actually supports it. It wasn't
great, but it worked. So, if you haven't tried it out, do that and
see if it meets your needs. Otherwise, you'll probably have to set
up some kind of chroot system with the old versions of libraries that
your acroread needs. You could copy the necessary libraries and
executables from whatever slackware32 version was official at the
time acroread was produced. Or, you could install an old version
of slackware32 in VirtualBox and run acroread in there.

Cheers,
Rob Komar
John Forkosh
2022-06-28 08:29:56 UTC
Permalink
Post by Robert Komar
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
I needed to fill in PDF forms for my taxes a few months ago, and found
out that the PDF viewer in firefox actually supports it. It wasn't
great, but it worked. So, if you haven't tried it out, do that and
see if it meets your needs. Otherwise, you'll probably have to set
up some kind of chroot system with the old versions of libraries that
your acroread needs. You could copy the necessary libraries and
executables from whatever slackware32 version was official at the
time acroread was produced. Or, you could install an old version
of slackware32 in VirtualBox and run acroread in there.
Cheers, Rob Komar
Well, I do have some extra partitions so that a bootable old version
ought to be pretty straightforwardly installable. Seems to be 14.1
as far as I can tell from http://mirrors.kernel.org/slackware/
If nothing less complicated works, maybe I'll give that a try.
Thanks,
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Jim Diamond
2022-06-26 21:11:54 UTC
Permalink
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
Not to answer your question, but I installed that Slackbuild on my
15.0 system (with multilib) and I don't get that error, so it may be
something more in your system's setup or in your personal
configuration, rather than some issue with the slackbuild.
(Or maybe it is a "current64" problem.)

On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also do
that?

Jim
John Forkosh
2022-06-28 08:37:05 UTC
Permalink
Post by Jim Diamond
Post by John Forkosh
Have -current64 (as of 6/21/22) installed, along with multilib.
Used to run acrobat under 14.2x64+multilib from adobe's
AdbeRdr9.5.5-1_i486linux_enu.tar.bz2, which hasn't changed since 2013.
But as soon as acroread starts to execute it emits
(acroread:8707): Gtk-WARNING **: 02:09:07.837: Unable to locate
theme engine in module_path: "adwaita"
and quits.
The adobe-reader.SlackBuild script in adobe-reader.tar.gz from
https://slackbuilds.org/repository/14.2/office/adobe-reader/
looks very slightly different from the earlier one I originally
used, but I'm not seeing anything substantive in the diffs.
How do I fix the problem(s), resolve any missing dependencies, etc,
to get it running?
(P.S. Yeah, I know the answer "don't use adobe". I have my reasons,
which I'm not posting to avoid long chains of discussion down that
road. Just want to get it running on my box, not on yours.)
Not to answer your question, but I installed that Slackbuild on my
15.0 system (with multilib) and I don't get that error, so it may be
something more in your system's setup or in your personal
configuration, rather than some issue with the slackbuild.
(Or maybe it is a "current64" problem.)
Well, like usual for me, I just did a "full install", and sat back
and let it do its thing. So I don't think it's a "personal configuration"
issue. And odds are not a recent current64 problem, but some problem
with acroread compatibility that maybe snuck in some time back.
Post by Jim Diamond
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also do
that? Jim
No. That error message just displays directly on the command line console,
and the program immediately exits without ever opening any window.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
John Forkosh
2022-06-28 09:03:49 UTC
Permalink
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Jim Diamond
2022-06-29 13:07:24 UTC
Permalink
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
This is very interesting (but annoying).

When I start acroread (from the shell) without that environment
variable, I get no complaints, and acroread runs (and except for the
issue with looking at my preferences, it is fine).

But when I set the variable as above, and then run acroread, I get
------------------------------------------

(acroread:25478): Gtk-WARNING **: 09:58:30.600: Unable to locate theme engine in module_path: "adwaita",

(acroread:25478): Gtk-WARNING **: 09:58:30.603: Unable to locate theme engine in module_path: "adwaita",
------------------------------------------
In this case it does run (I'm surprised yours doesn't run at all,
which I did not note when I first replied to you (mea culpa)). But
once again it crashes a couple of seconds after I bring up the
preferences window.

My install of 15.0 is mostly complete, except I did not install much
of kde (I installed a few packages to get one or two kde tools).
Do you mind telling me what window manager or desktop environment you
use?

Cheers.
Jim
John Forkosh
2022-06-29 13:47:21 UTC
Permalink
Post by Jim Diamond
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
oops, just for the record, that should be
export $GTK2_RC_FILES
or just the single line
export GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
Post by Jim Diamond
Post by John Forkosh
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
This is very interesting (but annoying).
When I start acroread (from the shell) without that environment
variable, I get no complaints, and acroread runs (and except for the
issue with looking at my preferences, it is fine).
But when I set the variable as above, and then run acroread, I get
------------------------------------------
(acroread:25478): Gtk-WARNING **: 09:58:30.600: Unable to
locate theme engine in module_path: "adwaita",
(acroread:25478): Gtk-WARNING **: 09:58:30.603: Unable to
locate theme engine in module_path: "adwaita",
------------------------------------------
In this case it does run (I'm surprised yours doesn't run at all,
which I did not note when I first replied to you (mea culpa)).
Mine gave exactly those messages both before and after I added
Javier's suggestion
export GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
But before that, it emitted the message and exited immediately,
returning to the command line without ever opening any window.
Afterwards, i.e., now, it still emits the message but then
opens a window with my requested document and behaves perfectly.
Not seeing your edit/preferences problem, or any other problem,
in any way whatsoever.
Post by Jim Diamond
But once again it crashes a couple of seconds after I bring up the
preferences window.
My install of 15.0 is mostly complete, except I did not install much
of kde (I installed a few packages to get one or two kde tools).
Do you mind telling me what window manager or desktop environment you
use? Cheers. Jim
fvwm2, with an fvwm95 "overlay". But just to check whether my wm was
causing the problem, I tested /etc/X11/xinit/xinitrc-->xinitrc.kde,
and ran kde instead. Same acroread behavior both with/without that
GTK2_RC_FILES regardless of wm. I can only suggest a Full Install,
but that's just a wild guess. I have no idea what kde dependencies
acroread actually has. But the fact that your acroread ran, at least
until it crashed, without that GTK2_RC_FILES suggests acroread's
behaving differently in our two environments.
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Jim Diamond
2022-06-30 13:49:59 UTC
Permalink
Post by John Forkosh
Post by Jim Diamond
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
oops, just for the record, that should be
export $GTK2_RC_FILES
I think you were correct the first time.
Post by John Forkosh
Post by Jim Diamond
Post by John Forkosh
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
This is very interesting (but annoying).
When I start acroread (from the shell) without that environment
variable, I get no complaints, and acroread runs (and except for the
issue with looking at my preferences, it is fine).
But when I set the variable as above, and then run acroread, I get
------------------------------------------
(acroread:25478): Gtk-WARNING **: 09:58:30.600: Unable to
locate theme engine in module_path: "adwaita",
(acroread:25478): Gtk-WARNING **: 09:58:30.603: Unable to
locate theme engine in module_path: "adwaita",
------------------------------------------
In this case it does run (I'm surprised yours doesn't run at all,
which I did not note when I first replied to you (mea culpa)).
Mine gave exactly those messages both before and after I added
Javier's suggestion
export GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
But before that, it emitted the message and exited immediately,
returning to the command line without ever opening any window.
Afterwards, i.e., now, it still emits the message but then
opens a window with my requested document and behaves perfectly.
Not seeing your edit/preferences problem, or any other problem,
in any way whatsoever.
This is really weird. I'd love to know what the significant
difference is between your system and my system is.

I've tried running acroread via strace, but I don't see anything in
strace's output to give me a hint as to what the problem is.

If anyone else is still reading this, I'd love to hear other ideas.
Post by John Forkosh
Post by Jim Diamond
But once again it crashes a couple of seconds after I bring up the
preferences window.
My install of 15.0 is mostly complete, except I did not install much
of kde (I installed a few packages to get one or two kde tools).
Do you mind telling me what window manager or desktop environment you
use? Cheers. Jim
fvwm2, with an fvwm95 "overlay".
Huh. I'm using fvwm2 as well, although not with the fvwm95 stuff.

I was thinking that if you were using kde (or xfce or ...) it might
modify your environment in some significant way (significant to
acroread). I suppose fvwm2 might still do that, but since fvwm2 is
far less intrusive than "desktop environments", I'm not confident of
that.

For anyone reading this who is a strace wizard, here are the last few
lines I get before acroread crashes when I open the preferences dialog;

[pid 11773] openat(AT_FDCWD, "/usr/lib/gconv/UTF-32.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 24
[pid 11773] read(24, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240\20\0\0004\0\0\0"..., 512) = 512
[pid 11773] statx(24, "", AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT|AT_EMPTY_PATH, STATX_BASIC_STATS, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, stx_mode=S_IFREG|0755, stx_size=19084, ...}) = 0
[pid 11773] mmap2(NULL, 20528, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 24, 0) = 0xf3d0f000
[pid 11773] mmap2(0xf3d10000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 24, 0x1000) = 0xf3d10000
[pid 11773] mmap2(0xf3d12000, 4096, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 24, 0x3000) = 0xf3d12000
[pid 11773] mmap2(0xf3d13000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 24, 0x3000) = 0xf3d13000
[pid 11773] close(24) = 0
[pid 11773] mprotect(0xf3d13000, 4096, PROT_READ) = 0
[pid 11773] mkdir("/home/<my home dir>/.adobe/Linguistics/UserDictionaries/Adobe Custom Dictionary", 0755) = -1 EEXIST (File exists)
[pid 11773] mkdir("/home/<my home dir>/.adobe/Linguistics/UserDictionaries/Adobe Custom Dictionary/eng", 0755) = -1 EEXIST (File exists)
[pid 11773] openat(AT_FDCWD, "/opt/Adobe/Reader9/Reader/../Resource/Linguistics/LanguageNames2/DisplayLanguageNames.en_US.txt", O_RDONLY|O_LARGEFILE) = 24
[pid 11773] read(24, "\377\376\"\0$\0$\0$\0/\0L\0i\0l\0o\0/\0D\0i\0s\0p\0l\0"..., 8191) = 8191
[pid 11773] --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} ---
[pid 11773] getpid() = 11773
[pid 11773] close(10) = 0
[pid 11773] unlink("/home/<my home dir>/.adobe/Acrobat/9.0/AdobeIDataSync/Preferences_Dialog") = 0
[pid 11773] rt_sigaction(SIGABRT, {sa_handler=SIG_DFL, sa_mask=[ABRT], sa_flags=SA_RESTART}, {sa_handler=0x850aafa, sa_mask=[], sa_flags=0}, 8) = 0
[pid 11773] exit_group(1) = ?
[pid 11790] <... poll resumed> <unfinished ...>) = ?
[pid 11790] +++ exited with 1 +++
+++ exited with 1 +++

One might assume that something acroread does with the contents of
.../DisplayLanguageNames.en_US.txt causes the segmentation violation,
but I wonder why it happens on my system and not John's system (or
maybe anyone else's system).

For anyone interested, to get the strace I did
(1) cp /opt/Adobe/Reader9/bin/acroread /opt/Adobe/Reader9/bin/acroread.ldd
(2) In the .ldd file I
(a) replaced #!/bin/sh with #!/bin/bash
(b) replaced (line 22)
exec ${1+"$@"}
with
strace -f /lib/ld-linux.so.2 ${1+"$@"}
(3) And then ran
/opt/Adobe/Reader9/bin/acroread.ldd somefile.pdf
Post by John Forkosh
But just to check whether my wm was causing the problem, I tested
/etc/X11/xinit/xinitrc-->xinitrc.kde, and ran kde instead. Same
acroread behavior both with/without that GTK2_RC_FILES regardless of
wm. I can only suggest a Full Install, but that's just a wild
guess. I have no idea what kde dependencies acroread actually
has. But the fact that your acroread ran, at least until it crashed,
without that GTK2_RC_FILES suggests acroread's behaving differently
in our two environments.
Thanks for taking the time to do the test. The mystery continues.

Jim
Jim Diamond
2022-06-30 20:21:50 UTC
Permalink
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
I installed acroread in a "fresh" S15-64+compat32 virtual machine.
And, like you, acroread didn't start (*) without the GTK2_RC_FILES
value. (Rather than exporting the variable as above, I just did
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread file.pdf
to get the value to acroread.)

(*) I discovered that (in the virtual machine) I only needed to use
that if the ~/.adobe directory (and subdirectories) have are not
there. After the first run, I didn't need to use that environment
variable again. But if I deleted ~/.adobe, then acroread won't run
without the variable being in the environment.

Now I can do some binary search to find the difference between my VM
and my bare-iron installations. Not my idea of a good time, but...

Jim
John Forkosh
2022-07-01 04:24:06 UTC
Permalink
Post by Jim Diamond
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
I installed acroread in a "fresh" S15-64+compat32 virtual machine.
And, like you, acroread didn't start (*) without the GTK2_RC_FILES
value. (Rather than exporting the variable as above, I just did
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread file.pdf
to get the value to acroread.)
(*) I discovered that (in the virtual machine) I only needed to use
that if the ~/.adobe directory (and subdirectories) have are not
there. After the first run, I didn't need to use that environment
variable again. But if I deleted ~/.adobe, then acroread won't run
without the variable being in the environment.
Thanks for that additional info.
I hadn't noticed that myself.
Post by Jim Diamond
Now I can do some binary search to find the difference between my VM
and my bare-iron installations. Not my idea of a good time, but...
Well, at least we know it consistently works under the same environment
on both machines. And I suppose there's clearly some minimum environment
it needs to run. Please followup again if you find the components of
that minimum environment your "bare-iron install" is missing. Thanks,
--
John Forkosh ( mailto: ***@f.com where j=john and f=forkosh )
Jim Diamond
2022-07-03 15:52:18 UTC
Permalink
Post by John Forkosh
Post by Jim Diamond
Post by John Forkosh
<<snip>>
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also
do that? Jim
As previously, nope, mine doesn't do that.
But as it turns out, Javier's suggestion (see my second followup
to him) immediately solves all my acroread problems...
from the command line
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
export GTK2_RC_FILES
and then run acroread. And I've got no edit/preferences problem, either.
So try that, and then let us know whether or not that edit/preferences
problem you're having is (or isn't) also fixed. Hopefully, it's all good.
Very nice to have acroread available again.
I installed acroread in a "fresh" S15-64+compat32 virtual machine.
And, like you, acroread didn't start (*) without the GTK2_RC_FILES
value. (Rather than exporting the variable as above, I just did
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread file.pdf
to get the value to acroread.)
(*) I discovered that (in the virtual machine) I only needed to use
that if the ~/.adobe directory (and subdirectories) have are not
there. After the first run, I didn't need to use that environment
variable again. But if I deleted ~/.adobe, then acroread won't run
without the variable being in the environment.
Thanks for that additional info.
I hadn't noticed that myself.
Post by Jim Diamond
Now I can do some binary search to find the difference between my VM
and my bare-iron installations. Not my idea of a good time, but...
Well, at least we know it consistently works under the same environment
on both machines. And I suppose there's clearly some minimum environment
it needs to run. Please followup again if you find the components of
that minimum environment your "bare-iron install" is missing. Thanks,
It turns out I wasn't missing anything, there is an inconsistency in
some of the compat32 stuff. Read on...

Shortly after I installed S64-15.0, I installed Alien Bob's compat32
stuff. Some time after, I reinstalled (ask me not why) some of the
packages which Alien Bob says to install first; i.e., these packages:
aaa_glibc-solibs-2.33_multilib-x86_64-5alien.txz
compat32-tools-3.10-noarch-2alien.tgz
gcc-11.2.0_multilib-x86_64-2alien.txz
gcc-brig-11.2.0_multilib-x86_64-2alien.txz
gcc-g++-11.2.0_multilib-x86_64-2alien.txz
gcc-gdc-11.2.0_multilib-x86_64-2alien.txz
gcc-gfortran-11.2.0_multilib-x86_64-2alien.txz
gcc-gnat-11.2.0_multilib-x86_64-2alien.txz
gcc-go-11.2.0_multilib-x86_64-2alien.txz
gcc-objc-11.2.0_multilib-x86_64-2alien.txz
glibc-2.33_multilib-x86_64-5alien.txz
glibc-i18n-2.33_multilib-x86_64-5alien.txz
glibc-profile-2.33_multilib-x86_64-5alien.txz

Here's the kicker. There are some libraries which are found in
multiple packages, and the copies in the above packages are different
than in 15.0/a-compat32/aaa_libraries-compat32-15.0-x86_64-19compat32.txz
*and* they cause the problem with acrobat. For example:

% tar xfv glibc-2.33_multilib-x86_64-5alien.txz | grep lib/libnsl
-rwxr-xr-x root/root 118900 2022-01-24 18:59 lib/libnsl-2.33.so
% md5sum lib/libnsl-2.33.so
08bab6a645f9cf39e6f86fe0e006a50c lib/libnsl-2.33.so


% tar xfv aaa_glibc-solibs-2.33_multilib-x86_64-5alien.txz lib/libnsl-2.33.so
-rwxr-xr-x root/root 118900 2022-01-24 18:59 lib/libnsl-2.33.so
% md5sum lib/libnsl-2.33.so
08bab6a645f9cf39e6f86fe0e006a50c lib/libnsl-2.33.so


% tar xfv a-compat32/aaa_libraries-compat32-15.0-x86_64-19compat32.txz lib/libnsl-2.33.so
-rwxr-xr-x root/root 118900 2022-01-24 17:03 lib/libnsl-2.33.so
% md5sum lib/libnsl-2.33.so
69a71379a573f10b456b664c2aaf925c lib/libnsl-2.33.so

You see they all have the same size, but as md5sum shows, they are not
the same. (Sing with me: "One of these things is not like the other,
one of these things does not belong.")

After discovering this, I did
# upgradepkg --reinstall --install-new 15.0/a-compat32/aaa_libraries-compat32-15.0-x86_64-19compat32.txz
and the edit/preferences problem is gone.

I'm not sure whether I should reinstall all the other packages under
15.0, but that is another issue for a rainy day.

Jim
Jim Diamond
2022-07-01 21:07:20 UTC
Permalink
Post by John Forkosh
I just did
GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc acroread file.pdf
I can't say for sure about your acroread installations, but on my
Slackware 14.2 system with a very old installation of acroread
/usr/bin/acroread is a symbolic link to /opt/Adobe/Reader8/bin/acroread
and the file /opt/Adobe/Reader8/bin/acroread is a simple bash script
which does some setup before calling
/opt/Adobe/Reader8/Reader/intellinux/bin/acroread which is a 32 bit
executtable.
My suggestion would be to patch the bash script to export GTK2_RC_FILES
before calling the binary if that would help the installation to work out
of the box also on Slackware 15.0.
Hi Henrik,

your 14.2 acroread is even older than the one in the slackbuild
(Reader9 there!), but in the same way, the slackbuild makes
/usr/bin/acroread a link to (in this case)
../../opt/Adobe/Reader9/bin/acroread
and that is a shell script. (Which does make it simple to shoe-horn a
"strace", "ldd" and other things into things, should one wish.)

Cheers.
Jim
Javier
2022-06-28 13:34:10 UTC
Permalink
Post by Jim Diamond
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also do
that?
Acrobat is quite picky on the library versions being used. The
opening preferences crash is related to the precise version of some
library or possibly to the usage of IPv6. Bugs and workarounds are
documented here:

https://aur.archlinux.org/packages/acroread

Adobe for linux has abandonware for many years, but there is still
many people using it (myself sometimes). As John Forkosh said the
quality of the PS files produced when printing is quite good.
I find quite useful for producing many pages booklets.
Jim Diamond
2022-06-30 13:51:27 UTC
Permalink
Post by Javier
Post by Jim Diamond
On the other hand, if I select Edit/Preferences, acroread crashes
about three seconds later. Just out of curiosity, does yours also do
that?
Acrobat is quite picky on the library versions being used. The
opening preferences crash is related to the precise version of some
library or possibly to the usage of IPv6. Bugs and workarounds are
https://aur.archlinux.org/packages/acroread
Adobe for linux has abandonware for many years, but there is still
many people using it (myself sometimes). As John Forkosh said the
quality of the PS files produced when printing is quite good.
I find quite useful for producing many pages booklets.
Hi Javier,

thanks for the pointer. I skimmed though that page, and I didn't see
anything that jumped out as helping my particular situation, but I
will go through it more carefully and see what I can learn

Cheers.
Jim
Loading...