Red Hat Bugzilla – Bug 139677
OpenOffice.org crashes when trying to save table changes to MySQL using unixODBC/myODBC connector...
Last modified: 2007-11-30 17:10:54 EST
I was following the directions in the PDF titled: "OpenOffice 1.0,
ODBC, and MySQL 'How-to'" aviable from
www.unixodbc.org/doc/OOoMySQL9.pdf and got to page 9.
I created the sample table from the PDF in the Table Design
wizard/dialog/whatever, and when I went to save it, openoffice.org
crashed and the Bug Buddy popped up.
Did it twice in a row, I closed out, logged out, logged back in, and
did it again and it crashed once more.
Steps to reproduce the crash:
1. setup MySQL server to accept connections from OO.org and the ODBC
2. setup OO.org using the Data Source Administrator to use the ODBC to
access a test database in mysql
3. goto view --> datasources, select the mysql database, expand it,
right click on tables, select new table design.
4. create table with a few entries,
5. save table,
I expect it to save the table so that I can continue on with the howto.
I tried a few more times trying different things and it did exactly
the same thing over and over again. I could issue a SQL command from
OO.org and create a table manually, and I could open and edit it. But
when I would go to save it, it crashed.
I could make queries and save queries just fine though.
However I believe that I fixed it, at least sort of.
I went to MySQL's website and downloaded the current production MyODBC
connector RPM and installed that over the MyODBC package I installed
thru Apt-get from one of the Official Fedora Mirrors (no third party
Now I can edit, create, delete, and save tables just fine.
The one catch is that I now have no edit option from "Data Sources"
Window. In order to get to edit mode I have to go thru the
"Administrate Data Sources" window and select the tables tab and from
their I can right click and edit the tables and save them successfully.
So I am not sure if I should of posted this under "myODBC" or not. It
needs to be upgraded, I guess. Still doesn't quite seem right, I
should be able to edit it from Data Sources Window per instructions
from the howto PDF. Maybe OO.org needs to be upgraded to 1.1.3?
I am content with the workaround so far...
I went back to edit the table. It won't let me edit or change any
actual columns, but it'll let me add them. I can add them and save it
and it'll work.
But I can't do something like deleting them. If I do that I get a SQL
So I am now using all the newest versions of unixODBC, myODBC and now
OpenOffice.org (1.1.3) and it's still giving me a SQL error.
Maybe I just don't get it. Maybe the SQL stuff is fubared. I don't
know. I give up. Maybe I'll hit up the OO.org website and see if I can
get help from them.
So I suppose it's nothing you can do anything about. :(
what was your locale ? There was a bug in the odbc drivers where locales with
comma seperators instead of . for the decimal mark caused problems.
caolanm->tgl: Could you take a look at this, I haven't been able to reproduce
anything like it, except the old setlocale issue.
I am sorry. I am the guy that filed the bug report and it's been a while since I
stopped messing around with it. Hell, I don't even own the computer I was trying
All I figured is that this stuff is semi-hidden in OO.org for a reason. I
understand that they are pretty much redoing this stuff for the next release.
If you want me to I can try to setup a similar situation on this computer, but I
don't know how usefull that will be for you.
Hmm, seems this is still there in FC3 tip. I got a crash with
It's not the locale problem because I was using good 'ol C locale. I'm not
convinced it's very closely associated with the odbc code at all, in fact,
because the crash doesn't seem to be near there. ooffice printed out this:
sh: bug-buddy: command not found
Fatal exception: Signal 11
Let me know what I can/should do to gather more info for you.
Cute, rtl_convertTextToUnicode(). Any way to convince you to install all 500MB
[ checks disk space... ] Yeah, I can do that. Just install it and repeat the
test and I should get a better backtrace, right?
Yeah, it should show the file, line #, and arguments passed to each function on
each line of the stacktrace.
Well, since that report I've yum updated and now have
but the other packages are the same as before. I pulled the matching debuginfo
down, but no joy. What I find is that it still crashes immediately on hitting
"Save" in the Table Design dialog, but now the printout is just
sh: bug-buddy: command not found
no backtrace :-(. Setting "ulimit -c unlimited" didn't persuade it to drop a
core file either. Now what?
Hmm not sure if its related but i seem to be able to reproduce the crash on save
even without the odbc stuff installed. Start a new text document.. add a little
text...go to save get a bug buddy crash. However when using saveas instead
Should i open this as a new bug?
cvs diff -r1.30 -r1.31 connectivity/source/drivers/odbc/OConnection.cxx
"#117841 # the size given to external components is now reduced by 1 to avoid
that they corrupt our return address"