pkg/29025: suse91_base oddity with openoffice

[jschauma%netmeister.org@localhost]

>Number:         29025
>Category:       pkg
>Synopsis:       suse91_base prevents openoffice from setup
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 20 20:39:00 +0000 2005
>Originator:     Jan Schaumann
>Release:        NetBSD 2.0
>Organization:
        
>Environment:
        
        
System: NetBSD dogfish-head.cs.stevens.edu 2.0 NetBSD 2.0 (BOCK) #2: Thu Jan 20 
12:39:01 EST 2005 
jschauma%doppelbock.hpcf.cs.stevens-tech.edu@localhost:/usr/2.0/src/sys/arch/i386/compile/obj/BOCK
 i386
Architecture: i386
Machine: i386
>Description:

Many commercial linux software packages nowadays require a linux emulation
layer newer than the one provided in the suse-packages base on suse 7.x.

suse packages based on 9.x are in pkgsrc, and even though they do not claim
to be stable, they are the only choice a pkgsrc-user has.

openoffice-linux works well with suse 7.x.

openoffice-linux works well with suse 9.x *iff* it has been setup previously.
That is, if you initially start openoffice-linux with suse 7.x packages, it
will run the setup program successfully.  If, on the other hand, you run
openoffice-linux with suse 9.x packages, the setup program will segfault
and fail.

Note, however, that once you have run the setup program with the suse 7.x
packages, you can upgrade the suse packages to 9.x and subsequently run
openoffice-linux and it will work fine.

If started as 'root', the setup appears to finish correctly, but the
subsequent invocation of 'soffice' fails, b/c the setup installs the necessary
files in the linux emulation's root directory (ie /usr/pkg/emul/linux/root),
but the program looks in /root.  Nuking '/usr/pkg/emul/linux/root' entirely
allows root to run openoffice-linux successfully (note: *both* setup *and*
regular).

While suse 9.x is not stable, this PR should still be considered somewhat
important since, as I said above, our current linux emulation layer is
outdated and no longer sufficient for various commercial linux applications.


>How-To-Repeat:

cd /usr/pkgsrc/emulators/suse91_base
make install
cd /usr/pkgsrc/emulators/suse91_x11
make install
cd /usr/pkgsrc/misc/openoffice-linux
make install
soffice

>Fix:

unknown
Note, however, that the fact that it runs fine for 'root' seems to indicate
that this is a permission problem, and not a kernel problem with the linux
emulation.  The question is just, where and when does the setup program try to
access a file that normal users can't?

I've stared at the (rather large) output of

ktrace -i soffice
kdump -e linux

for a while but haven't found anything clearly indicating the problem.

>Unformatted: