Hello all, I've been trying to get Adobe Reader 9 working on a machine I take care of, and it won't run when not run by root.
I have installed the adobe-release repo, and installed adobe reader with yum install AdobeReader_enu Users log into this machine and their home directory is mounted over NFS. The machine is 64 bit "Scientific Linux release 6.0 (Carbon)" $ yum info AdobeReader_enu Loaded plugins: refresh-packagekit Available Packages Name : AdobeReader_enu Arch : i486 Version : 9.4.6 Release : 1 Size : 57 M Repo : adobe-linux-i386 Summary : Adobe Reader, an application to easily view, print and collaborate on PDF files. URL : http://www.adobe.com License : Commercial Description: Adobe Reader software is the global standard for electronic document sharing. It is the only PDF file viewer that can open and interact with all PDF documents. Use Adobe Reader to view, search, : digitally sign, verify, print, and collaborate on Adobe PDF files. (this the yum info is after having uninstalled the application, which is why it shows the repo as "adobe-linux-i386" and not "installed" When I run "acroread" as root, Adobe Reader starts up fine. When I run "acroread" as any other user (all other users use an NFS mounted home directory) Reader won't start. Doing an strace shows that the reader hits a segfault when run as any user other than root - and I can't tell why it's segfaulting. The strace doesn't actually tell me anything interesting beyond that, other than the fact that reader stats the local directory several times. I've managed to coax a "crash log" from adobe reader, but I get some simple list that doesn't tell me much of anything: ============== /usr/bin/acroread [0x8508e25] [@0x8048000] (__kernel_sigreturn+0x0) [0x110400] [@0x110000] /usr/bin/acroread [0x850c0ac] [@0x8048000] /usr/bin/acroread(main+0x87) [0x85705c5] [@0x8048000] /lib/libc.so.6(__libc_start_main+0xe6) [0x3e07ce6] [@0x3df1000] ============== Looking at the "acroread" command itself, it appears to be a complex script which then bootloads a bunch of library files and then loads reader from another directory. I've attempted to recreate this script minimally by setting the LD_LIBRARY_PATH as set in the script and then run the binary, but it then proceeds to complain at me that I am not starting it up via the script. Bananas, I tell you! Well, I spent the better part of an hour attempting to get it working, and will continue to attempt to get it working, but has anyone experienced this before? perhaps someone can shed some light on my predicament? Maybe an update to 6.1 is in order? Thanks! Christopher Tooley ctoo...@uvic.ca Systems, HEP/Astronomy UVic
