I had been installing the StarOffice3.1 deb package as root, so I tried to
redoo it as a regular user, but dpkg said I needed superuser priviliges.So,
I tried untarring the tarballs manually according to the mini-howto, but I ran
into the same Server Crash no 11 problem when I tried to do the setup script.
I was wondering if it could be my libc5 or xpm, ( I have libc 5.4.38 (the newest
on debian.org, unstable/base) and xpm4.7 3.4j-0.5), but the FAQsaid that you
get a
specific error message if your libc5 isn't good enough; which I didn't get, so I
doubt it.
Did you have to do anything special to get your manually untarred 3.1 to
work?
Timothy
PS - This is very depressing, this is the first thing i've been trying to do
under
linux that hasn't worked.
I think I'll go get version 4 just to see if it works. :).
> Error no. 11 is a subject for a thesis, but the jist of it is that
> memory is trying to be accessed which is not properly provided for.
> This can be the result of a number of things such as bad code,
> overclocked processors, and it may even be intentional. (Because I
> doubt you want to become a developer right now, I'll skip the debugging
> hoopla, although ideally that would be a Good Thing.) One reason it
> may be intentional is that one cannot install staroffice as root--any
> attempt to do so will intentionally dump core. The reason is that like
> some other programs which are intended to be networked, it is
> considered insecure to give superuser status to apps which could be
> heisted by a hacker. There are several ways this can occur, I believe
> one such type of attack is called buffer flow overrun, which is
> essentially what it sounds like. Anyway, make sure you're NOT root and
> see if that helps.
>
> > This time I ran the script, and it crashed the X-Server again with the same
> > error, but the script didn't give any error messages.
> >
> > Any ideas?
> > Thanks!
> > Timothy
>
> Remember that while I do have a functional staroffice3.1 installation,
> I haven't used the .deb myself. Before you criticize me for
> recommending that, let me explain: I spent FIVE MONTHS (no joke) trying
> to get staroffice to install using manual tarball and rpm methods, and
> finally I got a working installation. Then I installed Debian, and at
> about the same time I started hearing reports that the .deb script
> worked very well. Since that time (several months) I've not heard a
> single report of any difficulty, thus my recommendation. Meanwhile, my
> StarOffice installation is on /opt which I merely set in /etc/fstab to
> be booted automatically, so I just copied some user configuration files
> with filerunner from my old installation, and I was ready to go.
>
> Also remember that any large application with static motif libraries
> will likely have a performance impediment--it's not terrible with
> staroffice, but is noticeable. Version 4.0 is not linked against motif,
> and the performance is much improved. Also, the 4.0 installation is
> wizardly simple, fast, smooth, and flexible. Also, version 4.0 has
> nicer appearing fonts. In my opinion, version 4.0 is worth waiting
> three weeks for.
>
> I suspect that any further questions regarding this particular case
> will exceed by ability to knowledgably respond, so my recommendation
> would be to accomplish what you can with what I've given you and then
> post the list for soem more qualified help. But if I can be of any
> real help, don't hesitate to ask.
>
> --
> David Stern
>
> [EMAIL PROTECTED]
> http://weber.u.washington.edu/~kotsya/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
