SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all,
I've installed acrobat reader 9 on my slackware64-14.1
I've used the multilib from AlienBob
I've installed (converting the packages) oxygen-gtk2,oxygen-gtk3 and acroread
When I try to start acrobat I receive:
Quote:
$ /usr/bin/32/acroread
Unable to initialize user interface.
I cannot see anything else, and I have no idea where to look
Any help?
No I have no idea why you would want it but purely for the sake of testing I just installed AdbeRdr9.5.5-1_i486linux_enu.bin on my multilib Slackware64 14.0 install and it ran just fine.
So I can confirm that this install method works on multilib Slackware64 14.0 at least.
P.S. I never really trust *.bin self installers, so I tracked the files it installed to ensure they were all removed on uninstall. Good thing too, since after running the /opt/Adobe/Reader9/bin/UNINSTALL script I noticed it left behind some files in /usr/share/mime/, e.g.:
On my system /usr/local/share/applications/defaults.list was also created (if that file was already on your system it would simply have been edited). The uninstall script also left this behind but I don't see that as too big a problem, as all the Acrobat entries had been removed from within the file.
Last edited by ruario; 05-30-2014 at 06:26 AM.
Reason: Linked to a faster download location
I've installed (converting the packages) oxygen-gtk2,oxygen-gtk3 and acroread
I didn't convert and install oxygen-gtk2 and oxygen-gtk3 and it didn't stop Acrobat Reader from working.
I don't think you need to convert your acroread package. In fact that might be the source of the issue since Acrobat might not be able to find some of its files if they are shifted around.
I'm pretty happy with Okular and X PDF; they ship with Slackware.
+1 to that. As I said earlier, not sure why anyone would want Acrobat Reader. Previously Acrobat Reader's unique selling point was browser integration but PDF.js can largely fill that role now, for those that want it. There is also the Kparts plugin or mozplugger to embed the likes of Okular.
P.S. PDFium also starts to become a viable option for a range of browsers, now that Google has open sourced it. It already forms the base of the PDF viewer built into Chrome.
I know that it works on 14.0: I had it installed on slackware64-14.1
I tried both installing it with or without converting it (/usr/bin/32 is the path for executable after converting a package)
for the package source, I've taken it from slacky, same source where I've taken the package for 14.0
In this package all is under /opt/Adobe
As for "why you want to use it", I need to use acroread for work issues
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Quote:
Originally Posted by ruario
+1 to that. As I said earlier, not sure why anyone would want Acrobat Reader. Previously Acrobat Reader's unique selling point was browser integration but PDF.js can largely fill that role now, for those that want it. There is also the Kparts plugin or mozplugger to embed the likes of Okular.
Acrobat Reader can handle some forms that Okular (and others) won't; e.g., fill-in-the-boxes type forms will not always (frequently, but not always) be usable with some forms. Additionally, Okular doesn't like to jump to some links in documents (like, say, the table of contents or an index in some documents created with Adobe Acrobat). Not always but enough to be annoying.
I just wish that Adobe would get on the stick and release a 64-bit version of both Acrobat and Reader that will work on Linux systems; they do a really nice job when dealing with PDF documents that just isn't quite "there" with the tools available in Linux (yet?).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Rep:
Quote:
Originally Posted by ruario
No I have no idea why you would want it but purely for the sake of testing...
XFA forms (fill in the blanks) that are not supported by Okular and security protected forms that are also not supported by Okular.
Edit in: solarfields and tronayne beat me to the punch.
BTW, ruario, while we are here, so to speak , are we ever going to see a
Linux version of the Opera chrome clone?
Last edited by cwizardone; 05-29-2014 at 09:03 AM.
As for "why you want to use it", I need to use acroread for work issues
Fair enough. I might try it on Slackware64 14.1 later if I get a moment. If I do, I'll let you know how (or if) it works for me. I be a little surprised if it didn't work on 14.1 but it is certainly possible.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.