Re: acroread9 crashing
On Sat, 23 Oct 2010 20:35:37 + Alexander Best articulated: > On Sat Oct 23 10, Jerry wrote: > > FreeBSD 8.1-STABLE /amd64 > > > > I continue to have a problem getting acroread9 to run. > > > > 1) It will not create its directory in my home directory. > > > > :1: error: unexpected character `\1', expected keyword - e.g. > > `style' Acroread was unable to create the directory .adobe in your > > home directory. There may be a permission problem with the parent > > directory. Acroread was unable to create the > > directory /home/gerard/.adobe/Acrobat in your home directory. There > > may be a permission problem with the parent directory. Acroread was > > unable to create the directory /home/gerard/.adobe/Acrobat in your > > home directory. There may be a permission problem with the parent > > directory. Acroread was unable to create the > > directory /home/gerard/.adobe/Acrobat in your home directory. There > > may be a permission problem with the parent directory. Acroread was > > unable to create the directory /home/gerard/.adobe/Acrobat in your > > home directory. There may be a permission problem with the parent > > directory. Acroread was unable to create the > > directory /home/gerard/.adobe/Acrobat in your home directory. There > > may be a permission problem with the parent directory. Acroread was > > unable to create the directory /home/gerard/.adobe/Acrobat in your > > home directory. There may be a permission problem with the parent > > directory. > > > > The directory permissions are normal and no other program has ever > > complained about it. I even tried giving it 0777 permissions without > > success. So, I manually create the directory structure it appears to > > want. > > > > 2) Now I manually start acroread9 again: > > > > Error message: > > > > :1: error: unexpected character `\1', expected keyword - e.g. > > `style' > > > > Next License agreement displays and I choose > > > > Main program windows pops up for 1 second and then disappears > > > > This is now displayed: > > > > terminate called after throwing an instance of 'RSException' > > > > 3) From the "Security Run Output" received every morning, this > > excerpt: > > > > +linux: pid 17352 (acroread): syscall inotify_init not implemented > > > > I have tried doing a complete 'pkg_delete" of the program and then > > reinstalling it without any success. > > > > I wanted to use 'gdb' to try to debug the program; however, it > > throws an error message also: > > > > gdb acroread9 > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, > > and you are welcome to change it and/or distribute copies of it > > under certain conditions. Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for > > details. This GDB was configured as > > "amd64-marcel-freebsd"..."/usr/local/bin/acroread9": not in > > executable format: File format not recognized > > > > (gdb) run > > Starting program: > > No executable file specified. > > Use the "file" or "exec-file" command. > > > > I tried using the "file" command; however, that also throws an > > error, probably because I am using the wrong syntax. > > > > I am open to any suggestions. I tried Googling without any great > > success. Evidently, many others have experienced this problem also. > > I have not seen a concrete solution posted for it. This problem was > > reported over a year ago, and perhaps more from what I have been > > able to discover. If it is a universal problem in FreeBSD, then > > perhaps the port should be marked "Broken". If not, then why does > > it work on some systems and not others? From what I have been able > > to ascertain, many users have never gotten it to work and have just > > given up on it. > > > > I have used truss to capture the output if anyone wants to view it. > > the freebsd linux emulator is missing support for the inotify_init > syscall. you won't be able to use acroread9, until it gets > implemented. > > right now i guess it returns ENOSYS to any linux app making use of > it. you might be able to work around this problem by replacing ENOSYS > with 0. however since no actual work is being done i suspect this > won't make acroread9 run properly. > > you might want to drop Roman Divacky (rdivacky@) a note. he may have > some experimental patches at hand. Thanks Alex, I was beginning to think that, that might be the problem. What I do not understand is why the port is not marked "broken". That would certainly make more sense than having users waste their time attempting to get a port to run when it cannot be made to do so. Perhaps the port maintainer would care to comment on this. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Old
Re: acroread9 crashing
On Sat, Oct 23, 2010 at 07:25:27AM -0400, Jerry wrote: > FreeBSD 8.1-STABLE /amd64 > > I continue to have a problem getting acroread9 to run. > > 1) It will not create its directory in my home directory. I have not been able to get acroread to work. I gave up and use XPDF which does what I need, though minimally. jerry > > :1: error: unexpected character `\1', expected keyword - e.g. `style' > Acroread was unable to create the directory .adobe in your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > > The directory permissions are normal and no other program has ever > complained about it. I even tried giving it 0777 permissions without > success. So, I manually create the directory structure it appears to > want. > > 2) Now I manually start acroread9 again: > > Error message: > > :1: error: unexpected character `\1', expected keyword - e.g. `style' > > Next License agreement displays and I choose > > Main program windows pops up for 1 second and then disappears > > This is now displayed: > > terminate called after throwing an instance of 'RSException' > > 3) From the "Security Run Output" received every morning, this excerpt: > > +linux: pid 17352 (acroread): syscall inotify_init not implemented > > I have tried doing a complete 'pkg_delete" of the program and then > reinstalling it without any success. > > I wanted to use 'gdb' to try to debug the program; however, it throws an > error message also: > > gdb acroread9 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as > "amd64-marcel-freebsd"..."/usr/local/bin/acroread9": not in executable > format: File format not recognized > > (gdb) run > Starting program: > No executable file specified. > Use the "file" or "exec-file" command. > > I tried using the "file" command; however, that also throws an error, > probably because I am using the wrong syntax. > > I am open to any suggestions. I tried Googling without any great > success. Evidently, many others have experienced this problem also. I > have not seen a concrete solution posted for it. This problem was > reported over a year ago, and perhaps more from what I have been able > to discover. If it is a universal problem in FreeBSD, then perhaps the > port should be marked "Broken". If not, then why does it work on some > systems and not others? From what I have been able to ascertain, many > users have never gotten it to work and have just given up on it. > > I have used truss to capture the output if anyone wants to view it. > > -- > Jerry ??? > freebsd.u...@seibercom.net > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __ > > "We're going to have the best educated American people in the world." > > George W. Bush > September 21, 1997 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: acroread9 crashing
the freebsd linux emulator is missing support for the inotify_init syscall. you won't be able to use acroread9, until it gets implemented. right now i guess it returns ENOSYS to any linux app making use of it. you might be able to work around this problem by replacing ENOSYS with 0. however since no actual work is being done i suspect this won't make acroread9 run properly. you might want to drop Roman Divacky (rdivacky@) a note. he may have some experimental patches at hand. cheers. alex On Sat Oct 23 10, Jerry wrote: > FreeBSD 8.1-STABLE /amd64 > > I continue to have a problem getting acroread9 to run. > > 1) It will not create its directory in my home directory. > > :1: error: unexpected character `\1', expected keyword - e.g. `style' > Acroread was unable to create the directory .adobe in your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > Acroread was unable to create the directory /home/gerard/.adobe/Acrobat in > your home directory. > There may be a permission problem with the parent directory. > > The directory permissions are normal and no other program has ever > complained about it. I even tried giving it 0777 permissions without > success. So, I manually create the directory structure it appears to > want. > > 2) Now I manually start acroread9 again: > > Error message: > > :1: error: unexpected character `\1', expected keyword - e.g. `style' > > Next License agreement displays and I choose > > Main program windows pops up for 1 second and then disappears > > This is now displayed: > > terminate called after throwing an instance of 'RSException' > > 3) From the "Security Run Output" received every morning, this excerpt: > > +linux: pid 17352 (acroread): syscall inotify_init not implemented > > I have tried doing a complete 'pkg_delete" of the program and then > reinstalling it without any success. > > I wanted to use 'gdb' to try to debug the program; however, it throws an > error message also: > > gdb acroread9 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as > "amd64-marcel-freebsd"..."/usr/local/bin/acroread9": not in executable > format: File format not recognized > > (gdb) run > Starting program: > No executable file specified. > Use the "file" or "exec-file" command. > > I tried using the "file" command; however, that also throws an error, > probably because I am using the wrong syntax. > > I am open to any suggestions. I tried Googling without any great > success. Evidently, many others have experienced this problem also. I > have not seen a concrete solution posted for it. This problem was > reported over a year ago, and perhaps more from what I have been able > to discover. If it is a universal problem in FreeBSD, then perhaps the > port should be marked "Broken". If not, then why does it work on some > systems and not others? From what I have been able to ascertain, many > users have never gotten it to work and have just given up on it. > > I have used truss to capture the output if anyone wants to view it. > > -- > Jerry ??? > freebsd.u...@seibercom.net > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __ > > "We're going to have the best educated American people in the world." > > George W. Bush > September 21, 1997 -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
