Updated OS and Priority flags.

Marc, any notes on the Debian mailing lists about your problem?

I'd also check the basics to make sure your MySQL server is running
and you are able to connect to it using the settings that OOo uses.

MySQL works well. And I can run isql to connect through ODBC, too. But
I haven't checked the Debian side, yet. Will do that next.

My problem is fixed, but not really solved. Through Debian, I found 
they had an apt-get installation for OpenOffice 1.0.1. I deleted my 
OO installation and re-installed, using theirs. So far, no crashing 
and the database access seems to be working. I was able to create a 
table, exit OO, go back in and play with the new table.

The underlying problem is still unknown, but things are working.

sorry, what is "apt-get"?
Do I understand this correctly that the bug vanished for you by
installing _another_ 1.0.1? With "not solved", do you mean that it
vanished "magically", or is there another problem?

Hello Frank and user ( sorry no name I can easily figure out ).

"apt-get" is a package management system for Debian.  It's pretty 
slick for upgrading and maintaining packages on the Debian distro.

I've seen similiar comments about stock OOo having problems on Debian 
distros.  I should have realized that asking the user to install 
using the Debian"ized" version of OOo might resolve the problem.

Good to hear the problem is resolved.

Apt-get is a list-based application installer that comes with Debian 
Linux. Debian has a large list of "approved" applications. These 
applications are built and tested fully on Debian, then it's added to 
the list, along with the binaries.  apt-get uses the list and 
resolves all dependancies. Works much nicer than rpm, at least it has 
for me so far.

And, yes, by "fixed, but not solved", the problem has been magically 
fixed. It's possible I did something different with the new install 
that made it work, but I don't see how. I really was following the 
document to the letter both times. Personally, I would like to know 
the root cause, but I feel that finding this may be out of my league.

So no new, nor old, problems, but no solution to the root cause.

Hi Gordon and user,

(sorry, too. BTW: the issue where I complained about missing real
names is issue 8945 :)

thanks for the explanations. I agree that it is unsatisfying to not
know the root cause for such a problem. Would be interesting if the
crash is really a problem of the "no approved" version, i.e. if it can
be reproduced for subsequent installations, or if it was a problem of
the particular installation only ....

I don't want to turn this issue into a "newsgroup", but the Debian
maintainers usually do a lot of customization to their version of OOo.

It could simply be a library version/dependancy issue that OOo was
never built to handle.

Same goes for RH 8.0, Mandrake 9, etc.

I should have added:

Ideally, there should be a list of changes that the Debian maintainer
for this package made.  The answer probably lies there.

I'll take a look for that Debian list and see if there's anything 
mentioned, or any clues.

--Marc Godbout (aka "user" - and I'll look to see how to get a real 
name)

No reporter-activity for 8 months
No votes
No other one who confirmed the problem

I think we should close that issue.
If someone still sees the problem, the issue can be reopened

If I will not see any further action as votes, attachments or
confirmations, I will have to close this issue 2003-09-30 as WFM.

Rainer

Closing issue due to reporter's inactivity as WFM.

If you find out that the problem still is actual, please open a new issue!

Rainer

.

change subcomponent to 'none'