[imp] Blank Screen with Imp & wvHtml/wvWare

Richard H. Clayton rhclayto at loyno.edu
Sat Jan 17 18:43:50 PST 2004


Problem: attempting to use wvHtml within IMP to view msword documents, all
that is produced is a blank screen.  Recourse to the FAQs, the horde & imp
archives at MARC, & any number of exhausting (if not exhaustive) web
searches has given me some leads, but nothing that has allowed me to
scotch the problem, so I throw myself upon the mercy of the list for help.

Here's the setup:

OpenBSD 3.4
Apache 1.3.28
MySQL 3.23.57
PHP 4.3.3
Horde 2.2.4
IMP 3.2.2
wv 0.7.2

By default on OpenBSD, Apache is installed chrooted.  This caused me some
grief initially with IMP's finding wvWare, since I had wvWare installed
outside the server root.  So I brought it & all its necessary shared
objects & dependencies inside the server root.  I can use wvHtml/wvWare
from the command line from its location inside the server root, so I'm
pretty sure I've got it successfully transferred into the chrooted
environment.

However, now that IMP can actually *find* the wvHtml program, I am
encountering the problem described above: a separate browser window (under
both IE 5.5 & Mozilla 1.5) is brought up containing nothing but a blank
white screen.  I have seen several threads in the imp & horde list
archives which discuss similar problems, but I haven't been able to find a
solution there that seems to work.

The most promising idea for my situation, as far as I could tell, was the
suggestion that it might be an executable search path problem.  My httpd
on OpenBSD runs as the unprivileged user www, but it inherits its user
environment when it is started by root from root.

As a temporary testing measure, I added the directory wihin the chroot
that holds wvHtml & wvWare to root's environment path,
/var/www/usr/local/bin.  I checked httpd's environment:

#ps -wwaxe -p 21670

<snip>
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin:/var/www/usr/local/bin
<snip>

So the directory within chroot with wvWare *is* in the search path.

Yet still the problem persists.  Has anyone any idea what the problem
might be, & how it might be remedied?

Thanks a million.

Henry




More information about the imp mailing list