Crash on odbc traffic with MySQL server

[jph]

Binary package hint: openoffice.org-base

Kubuntu 8.04
openoffice.org-base:
  Installiert:1:2.4.0-3ubuntu5

I am trying to access with OOBase via ODBC a MySQL database.
Same scenario is working under gutsy.
ODBC is installed and seems functional.
OOBase opens file and when clicking on tables asks for MySQL password.
This is accepted and tables are shown. Therefore, the connection to MySQL database has been established successfully via ODBC and available tables are listed.
However, when trying to open a table OOBase crashes immediately without any additional comment.
I would expect the table to open and to see the data.
Using gnome (ubuntu-desktop) I see the same behavior.
This blocks use of company MySQL database completely, since all forms and queries used by company users are stored in an OOBase file.

[jph (jphorst)]

Problem can be solved by manually installing the correct 64bit ODBC driver from mysql.com.

Since I have a 64bit installation, the current hardy libmyodbc driver might not work correctly on 64bit systems.

[scananza (scananza)]

I confirm this, ubuntu hardy 64bit ODBC connector is buggy, OOo crashes as soon as it tries to connect to a mysql DB via ODBC. As jph suggests, installing "original" odbc connector from mysql.com fixes the problem, it is sufficient to convert rpm's with alien and then use them to replace ubuntu libmyodbc package.
I hope this will be fixed asap because it cut out all those office environments (like mine) that rely on OOo and mysql.

[Trond Thorbjørnsen (tthorb)]

I confirm this too.

I haven't managed to use the "original" odbc-connector successfully. After innstalling the rpm-package, what do I have to do so that oobase can find the "new" libmyodbc.so?

[cabay (cahyobayu-setiawan)]

Scananza, i have downloaded mysql-connector-odbc-5.1.4-0.x86_64.rpm for ubuntu hardy 64 bit to replace its native libmyodbc, i succeded convert it to deb package with alien (mysql-connector-odbc_5.1.4-1_amd64.deb) how do you configure the odbcinst.ini file to make a successfull connection? what's the path for the odbcinst.ini? do i have to replace the native unixODBC for hardy either?if so what is the replacement package/s and how to configure the odbc.ini file?and what's the path for it
thank you

[Chris Cheney (ccheney)]

Do you still have this problem with openoffice.org 1:2.4.1-1ubuntu2 in Ubuntu 8.04?

[jph (jphorst)]

On Thursday 24 July 2008 21:23:33 Chris Cheney wrote:
> Do you still have this problem with openoffice.org 1:2.4.1-1ubuntu2 in
> Ubuntu 8.04?
>
> ** Changed in: openoffice.org (Ubuntu)
> Status: New => Incomplete

I switched to Hardy 32bit just recently.
Before I used a workaround with the MySql 64bit version of the driver.
Therefore, I am sorry that I cannot tell you if this bug changed with
OpenOffice upgrades.

[sgnaus (sgnaus01)]

Io ho risolto il problema eseguendo la seguente procedura:

- Scaricare il pacchetto dal sito MySQL http://dev.mysql.com/downloads/connector/odbc/5.1.html
- Convertire il file da rpm a deb con alien: sudo alien -d nome_del_file.rpm
- Installare con Synaptic i seguenti pacchetti: mysql-connector-odbc e libmyodbc

Configurare il file /etc/odbcinst.ini nel seguente modo:

[MySQL]
Description = MySQL ODBC 5.1 Driver
Driver = /usr/lib64/libmyodbc5-5.1.4.so
Setup = /usr/lib64/libmyodbc5.so
FileUsage = 1
CPTimeout =
CPReuse =

Configurare il file /etc/odbc.ini nel seguente modo:

[nome_db]
Description = TLP Connection
Driver = MySQL
Server = localhost
Database = nome_db
Port = 3306
Socket =/var/run/mysqld/mysqld.sock
Option =
Stmt =

[Emmanuel Charpentier (charpent)]

I have a problem similar to wht has been reported with mysql ODBC
access : immediate crash of OpenOffice Base when trying to query a
PostgreSQL ODBC database.

Setup : Hardy (8.04) amd64 + updates from hardy-updates and
hardy-backports. OpenOffice-base is 1:2.4.1-1ubuntu2, PostgreSQL is
8.3.3-0ubuntu0.8.04 (sic... that's what dpkg - reports) and
odbc-postgresql is 1:08.01.0200-2.1. unixodbc is 1:08.01.0200-2.1. All
of this comes clean from Ubuntu repositories.

Way to reproduce : create test database (with psql or with OOo and the
the SDBC driver), crete a test table. Check it with various tools (OOo +
SDBC in my case), check the ODBC connection (I tested with isql and R +
RODBC) : works like a charm.
In OOo, create a new database file accessing the test database via the
ODBC driver. runs OK, asking (correctly) for the database's password.
The "Tables" views shows the "public" schema and the test table. Click
on the table's name (or icon) : immediate crash. Relaunching OOo-Base
leads to the "restoration of an unsaved document", which runs OK. An
you're back where you started.
Other symptoms : trying to create a query crashes as soon as you are
trying to click on the table's name or icon. You can create a query in
SQL mode, but trying to execute it crashes immediately.

In short, the &#@! OOo-base crashes as soon as it tries to get
information about a table.

I have had similar symptoms with a sqlite3 database, but I concluded
(erroneously ?) that this might be an ODBC driver problem (the
libsqlite-odbc package seems to be a bit ancient when compared to
upstream...). Now, it seems to me that the problem might lie with
OOo-base (amd64) trying to access a table in the "public" schema.

Attached is an ODBC trace coresponding to the following operations :
- open OOo-base
- connect to the database,
- clicking (once) on the table name in the "tables" view.
[ Crash ]

Sincerely yours,

                                        Emmanuel Charpentier

[resplin (resplin)]

I see the same behavior when accessing SQLite3 (3.4.2-2) via libsqliteodbc (0.70-3), unixodbc (2.2.11-16build1), and odbcinst1debian1 (2.2.11-16build1). I can see the list of tables inside the database, but if I do anything that tries to read a database table, Base disappears. I have tried this with near-empty databases.

I am using Kubuntu 10.04 Hardy 64 bit Intel.

I loaded OpenOffice3 rc1 and saw the similar crash with a large sqlite database. Perhaps the problem is in the ODBC libraries?

[resplin (resplin)]

I linked this to upstream bug:
http://qa.openoffice.org/issues/show_bug.cgi?id=85094

I'm not certain it is the same, but it looks pretty close.

[penalvch (penalvch)]

jph, thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[penalvch (penalvch)]

As per upstream, suspect build issue and no detailed reproduction steps. Unlinking.