Re: user cannot start acroread

[Kari Ruohonen <karruo@utu.fi>]

bob@proulx.com (Bob Proulx) writes:

> You could try running 'strace acroread'.  Be prepared for copious
> amounts of system trace information.  See if it indicates a filename
> near where the assertion failure occurs.

It looks like a problem with ATM-files: (some output from strace acroread
follows)
...
rt_sigaction(SIGINT, {0x8072648, [], 0x4000000}, {SIG_DFL}, 8) = 0
wait4(-1, acroread: ../../Source/ATM/Extra/Edge/FileCore.cpp:322: CTBool CTFile::Write(const void *, unsigned int): Assertion `nWritten == nCount' failed.
[WIFSIGNALED(s) && WTERMSIG(s) == SIGABRT], 0, NULL) = 3515
write(2, "/usr/bin/acroread: line 8:  3515"..., 93/usr/bin/acroread: line 8:  3515 Aborted                 /usr/lib/Acrobat4/bin/acroread "$@"
) = 93
...

I don't know what is the path that is referred to here
(../../Source/ATM/Extra/Edge/FileCore.cpp:322). Maybe it is this file
that has wrong permissions? But I cannot find it. When I ran strace
acroread as root, the line "wait4(-1," is where the program appears on
the screen. It waits there until killed.

> In the meantime until you get acroread running again I will recommend
> xpdf.  It is not perfect.  But the startup time is very fast.  I
> prefer it over acroread for my 99% case of reading pdf documents.

Thanks for suggestion. However, I use xpdf for most of my reading. I
only wanted to check some slides prepared by latex and supposed to be
shown with acroread on windows.

Regards, Kari

--