From: forkosh@panix.com   
      
   Henrik Carlqvist  wrote:   
   > John Forkosh wrote:   
   >> Henrik Carlqvist  wrote:   
   >>> John Forkosh wrote:   
   >>>> 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   
   >>   
   >> 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.   
      
   > 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   
      
   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:  j@f.com  where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)