Adobe reader and Kompozer crashing on a multilib system running KDE
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.
Adobe reader and Kompozer crashing on a multilib system running KDE
Hi to all.
I am running Slackware64 14.0 multilib with KDE. Two of my 32bit applications are Adobe reader and Kompozer. However, they both crash when I go to the Open dialog. The dialog opens, stays for several seconds and the program exits. The strange thing is -- I do not see this behaviour in XFCE.
Well, I would have to be able to look at the referenced run-mozilla.sh script to see what it is they are trying to do in there, but for the acroread, it seems they are expecting an argument of the path to the file you want to read.
Either try running:
Code:
~ $ acroread <path to the PDF doc you want to read>
Or, if you don't have a local PDF in your home directory, you should be able to find one on your system using:
Code:
~ $ find /usr/share/doc/ -iname "*.pdf" -print
See if that gets acroread running, or what new error output it gives.
(As a note, my experience is that Adobe isn't really careful with security, ESPECIALLY in Linux. As an alternative, you *could* just try qpdfview. I know that program comes up without having to start with a file... Just my 2¢.)
Let me see if I can figure out the kompozer situation...
EDIT: Well, I can't find it as a separate package in my portage tree. Is this an extension for Konquerer? (Konquerer being KDE's default browser that is built on the Mozilla codebase.)
HTH. Let us know.
Last edited by ShadowCat8; 08-09-2013 at 04:42 PM.
~/Bibliography/apoptosis$ acroread Tait_2010.pdf
dirname: missing operand
Try 'dirname --help' for more information
I occasionally need the Adobe Acrobat reader to fill PDF forms. Otherwise I use Evince in XFCE or Ocular in KDE, which is great.
Kompozer is not part of KDE, don't be fooled by the name. It is "a complete web authoring system that combines web file management and easy-to-use WYSIWYG web page editing". I installed it from SBo. The script just repackages the i686 binary.
I installed acroread on one of my tech support guy's systems (a Gentoo build), and it too came up with the same error:
Code:
~ $ acroread
dirname: missing operand
Try 'dirname --help' for more information.
BUT, it *did* launch the program after that. So, at this point, I think we may need to get "down-n-dirty" on this one and use strace to see what is killing it on your system. If you don't have strace installed on your system, go ahead and install it and then run:
Code:
~ $ strace -o ~/acroread_strace_run.log acroread
When it completes and returns the prompt to you, you can start looking at the bottom of the acroread_strace_run.log and work your way up to find the REAL error that is killing acroread on your system.
And to give you an idea, here is the tail of the strace log from having brought acroread up and closed it out:
Code:
munmap(0xfffffffff4764000, 188416) = 0
munmap(0xfffffffff46f0000, 475136) = 0
stat64("/home/user/.adobe/Acrobat/9.0", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
access("/home/user/.adobe/Acrobat/9.0/TMDocs.sav", F_OK) = -1 ENOENT (No such file or directory)
stat64("/home/user/.adobe/Acrobat/9.0", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
access("/home/user/.adobe/Acrobat/9.0/TMDocs.sav", F_OK) = -1 ENOENT (No such file or directory)
write(4, "\1\0\0\0\0\0\0\0", 8) = 8
munmap(0xfffffffff4792000, 8220) = 0
exit_group(0) = ?
+++ exited with 0 +++
=============================================
Now as far as komposer, I took a look at the page you linked and, as you pointed out, the script repackages the i686 binary... Which, as the page points out, is built on GCC 4.2. It sticks in my mind that there may be an issue there. Do you know what GCC you have installed? Try doing this:
Code:
~ $ gcc-config -l
and post the results up here. I'm not certain that it is an issue, but I get the impression it might be.
i will do this in the evening when i get to my KDE computer. The funny thing is, Kompozer and Adobe reader work when I run them in XFCE. They crash when I try to start them in KDE...
Shall I paste more, or is there something specific that I should look for in the log files? I can attach them, but the one for acroread is more than 6 MB big...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.