[SOLVED] Adobe Acrobat and multilib

arubin · 03-21-2022, 08:49 AM

In another thread I asked about Adobe reader not running in 15.0. I thought I might be a locale problem but I now suspect the problem is 86_64.

I am running multilib. The page for the slackbuild says enigmatically

Quote:

This only works on the x86 architecture (no x86_64, arm, ...), although
it may work on x86_64 systems with alienBOB's multilib installed.

Curious because I have always used multilib and never had a problem with acroreader in previous releases of Slackware.

Does anyone have Acrobat/acroreader running in 15.0 multilib? Running from the terminal gives no error messages at all.

kjhambrick · 03-21-2022, 09:08 AM

arubin --

Yes, I have the SBo SlackBuild working on Slackware64 15.0 + Multilib.

See my post in your other thread.

I do run LC_ALL=C on my system (

we don't need no steenkin UTF in Texas

)

-- kjh

aikempshall · 03-22-2022, 02:20 AM

I too have Acroread running on Slackware64 15.0 plus multilib.

You might need to carry forward ~/.adobe from a working Slackware64 14.2 plus multilib

Even though It starts and I can view documents the menu options "save a copy" and "print" cause acroread to shut down unexpectedly.

Alex

kjhambrick · 03-22-2022, 03:53 AM

Good call aikempshall

I can view .pdf files, print-to-a-postscript file and save-as with acroread which is all I need it for.

However, I have an existing $HOME/.adobe/ that came over with the rest of my $HOME/ from my previous Laptop running Slackware64 14.2 + Multilib.

If I rename ~/.adobe/ and try to start acroread it flashes the screen and then fails immediately without any feedback.

It did create a new ~/.adobe/ directory but it's pretty sparse compared to the old ~/.adobe/ directory.

However, I am going to retract my statement that adobe-reader-9.5.5_enu works in Slackware64 15.0 + Multilib.

It apparently only works because I have an existing, legacy ~/.adobe/ directory.

I restored my Slackware 14.2 ~/.adobe/ directory and I'll keep my fingers crossed ...

Sorry to send all'Y'all down a rabbit hole.

-- kjh

p.s. I use acroread to make nice-clean postscript from time-to-time and I can still do this on Slackware 15.0 even without my old Slackware 14.2 ~/.adobe/ directory

I tried a few things with the new ( Slackware64 15.0 + MultiLib ) ~/.adobe/ directory:

Code:

$ man acroread                                                           # works ( :) of course :) ) 
$ acroread -h                                                            # works 
$ acroread -toPostScript /home/tmp/foo.pdf /home/tmp                     # works and produces a valid /home/tmp/foo.ps
$ acroread -toPostScript -optimizeForSpeed /home/tmp/foo.pdf /home/tmp   # produces a valid /home/tmp/foo.ps file

p.p.s. I see a similar theme error on my old Slackware64 14.2 Laptop when I start acroread at the commandline:

Code:

$ acroread PR-99-PP-self-mailer-logom.pdf 2>/tmp/foo &

(acroread:14038): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",

(acroread:14038): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",

kgha · 03-22-2022, 04:46 AM

I wonder if there's some crucial difference between Slackware-15 and -current affecting acroread? I'm on -current and I've been using (occasionally) acroread for ages without issues. I now did what kjhambrick wrote: renamed my ~/.adobe/ directory and started acroread. It still works just fine - I can open, print, select text and so on.
The new ~/.adobe/ directory does not include all the stuff in the older one that also include e.g the directories Dictionaries, JavaScripts, Security but that may have to do with what documents I've opened over the years.

arubin · 03-22-2022, 01:27 PM

When I installed 15.0 I kept my old 'home' which is on a separate partition but moved all the hidden files and folders to archive. So, I did as suggested and moved over my old .adobe

The result is that acroread does start and will open any file in the recent files list of the file menu. But as soon as I click File/open it crashes out with no error message.

joghi · 03-22-2022, 02:30 PM

I have had the same problems with acroread when I switched to 15.0. This was at a time, when current and 15.0 still shared the same base. I thought this might be due to an ancient home-directory, which I kept over the years and that I should move on to a modern alternative. Renaming my .adobe directory after reading of this thread had the result that acroread didn't even start.

According to gdb, there seems to be a problem with the current librsvg. After noticing, that arch seems to link acroread to librsvg2.40, which was also used in Slackware 14.2, I got the last version used in 14.2 (librsvg2.40.20) and tried to built it on Slackware15. However, this needs the libcroco-headers. libcroco seems still to be provided by AlienBob in his multilib-packages but is no longer installed in Slackware64 15.0.

So again, I got the slackbuild from 14.2 and installed libcroco, using the same version as in AlienBob's compatibility-package (0.6.13). I then build the 32bit version of librsvg2.40.2 and copied the .so files to the lib directory of my acroread installation (/usr/local/Adobe/Reader9/Reader/intellinux/lib/ in my case). Now acroread seems to run as before. It no longer crashes when I try to click the print button.

kjhambrick · 03-22-2022, 03:41 PM

Joghi --

Excellent work !

Thanks for the report.

I need to go look around in a few nooks and crannies on my new Slackware64 15.0 Laptop ... you may have explained why acroread was working for me but nobody else.

I've got 'a ton' of Alien Bob's goodies on my Slackware64 15.0 +Multilib system and I might have some 14.2 cruft in a ld.so.conf directory that I don't recall installing ...

-- kjh

arubin · 03-22-2022, 04:24 PM

Thanks. I don't get the libcroco bit.
Do I have to build 0.6.13 using the slackware script from 14.2? Would that be the regular slackbuild.org script? Do I need to do this with a specific ARCH?

joghi · 03-23-2022, 01:17 AM

Yes, this is what I did. Since I didn't found it at SBo, I got the slackbuild script for libcroco from 14.2 sources, which comes with version 0.6.11. I replaced the source file with that for version 0.6.13 an used the slackbuild script. It detects the version of the sources automatically.

Since if you installed AlienBob's multilib packages, you already should have the 32bit lib of libcroco installed (maybe you want to check that) but not the headers. What you will need for building librsvg are the libcroco headers. Therefore you can build libcroco as 64bit. Installing libcroco package then provides the headers and the 64bit version of the library.

Now you can built librsvg as 32bit, using the provided environment from AlienBob's multilib packages. This will use the headers from the 64bit package but link to AlienBob's 32bit lib. After librsvg is build (you don't need a slackbuild for this, just use configure + make. The libs then can be found under .libs in the source directory) it should be safe to remove the 64bit libcroco package but I didn't test that.

arubin · 03-23-2022, 01:33 PM

I have followed your instructions and acroread seems to be working fine. That's great! Thank you very much joghi,

longus · 03-23-2022, 03:37 PM

Well, it doesnt seems to be solvet. I did what is described. Print dialog could be opent with no crash, but when Properties window is opend the program disappear with no output to console.

joghi · 03-23-2022, 04:13 PM

Just tried it and properties window (from file menu as well as from context menu) is working here.

What you can try to do is to attach gdb to the acroread process using

Code:

gdb -p pid

where pid is the id of the acroread process. You then have to press [Enter] and "c" to continue the acroread process. If the reader crashes now, the gdb output might give you a hint what the problem might be. It set me on the right track yesterday.

longus · 03-24-2022, 08:08 AM

GNU gdb (GDB) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 28050
[New LWP 28109]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0xf6168e5a in poll () from /lib/libc.so.6
warning: File "/usr/lib/libstdc++.so.6.0.29-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /usr/lib/libstdc++.so.6.0.29-gdb.py
--Type <RET> for more, q to quit, c to continue without paging--
line to your configuration file "/home/incognitus/.config/gdb/gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/home/incognitus/.config/gdb/gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual. E.g., run from the shell:
info "(gdb)Auto-loading safe path"
(gdb) c
Continuing.
[New Thread 0xf3b28b00 (LWP 28124)]
[New Thread 0xf2252b00 (LWP 28125)]
[Thread 0xf3b28b00 (LWP 28124) exited]
[Thread 0xf2252b00 (LWP 28125) exited]
[New Thread 0xf2252b00 (LWP 28126)]
[New Thread 0xf3b28b00 (LWP 28127)]
[Thread 0xf2252b00 (LWP 28126) exited]
[Thread 0xf3b28b00 (LWP 28127) exited]
[New Thread 0xf3b28b00 (LWP 28128)]
[New Thread 0xf2252b00 (LWP 28129)]
[Thread 0xf2252b00 (LWP 28129) exited]
[Thread 0xf3b28b00 (LWP 28128) exited]
[New Thread 0xf3b28b00 (LWP 28130)]
[New Thread 0xf2252b00 (LWP 28131)]
[Thread 0xf2252b00 (LWP 28131) exited]
[Thread 0xf3b28b00 (LWP 28130) exited]
[New Thread 0xf3b28b00 (LWP 28132)]
[New Thread 0xf2252b00 (LWP 28133)]
[Thread 0xf3b28b00 (LWP 28132) exited]
[New Thread 0xf3b28b00 (LWP 28134)]
[New Thread 0xf454db00 (LWP 28135)]
[Thread 0xf2252b00 (LWP 28133) exited]
[Thread 0xf3b28b00 (LWP 28134) exited]
[Thread 0xf454db00 (LWP 28135) exited]

Thread 1 "acroread" received signal SIGSEGV, Segmentation fault.
0xf5f51154 in std::istream::seekg(long long, std::_Ios_Seekdir) () from /usr/lib/libstdc++.so.6
(gdb) c
Continuing.
[Thread 0xf18ffb00 (LWP 28109) exited]
[Inferior 1 (process 28050) exited with code 01]
(gdb)

aikempshall · 03-24-2022, 12:25 PM

Quote:

Originally Posted by joghi

Now you can built librsvg as 32bit, using the provided environment from AlienBob's multilib packages. This will use the headers from the 64bit package but link to AlienBob's 32bit lib. After librsvg is build (you don't need a slackbuild for this, just use configure + make. The libs then can be found under .libs in the source directory) it should be safe to remove the 64bit libcroco package but I didn't test that.

I ran AlienBob's

Code:

. /etc/profile.d/32dev.sh

change to the directory storing the librsvg.SlackBuild and source

Code:

export ARCH=i586
sh librsvg.SlackBuild
cp /tmp/package-librsvg/usr/lib/librsvg-2.so.2.40.16 /opt/Adobe/Reader9/Reader/intellinux/lib
cd /opt/Adobe/Reader9/Reader/intellinux/lib
ln -s librsvg-2.so.2.40.16 librsvg-2.so.2

I did nothing with the /tmp/librsvg-2.40.16-i586-1.txz created by the librsvg.SlackBuild

For some reason the configure/make route didn't work for me

Strangely acroread works on one of my machines without doing the above! Something to investigate later in the week.