Bug 83028 - VIEWING: Displaying mysql database
Summary: VIEWING: Displaying mysql database
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Keywords: regression
Depends on:
Reported: 2014-08-25 01:30 UTC by Peter
Modified: 2015-05-14 09:23 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

I have opened a mysql database that resides on another system that has not been updated for weeks. The line with the error should just have - Discruption in it - (76.72 KB, image/png)
2014-08-25 01:30 UTC, Peter
gdbtrace 1 (15.30 KB, text/x-log)
2014-09-05 10:56 UTC, MAG4
gdbtrace 2 (18.49 KB, text/x-log)
2014-09-05 10:57 UTC, MAG4

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2014-08-25 01:30:02 UTC
Created attachment 105207 [details]
I have opened a mysql database that resides on another system that has not been updated for weeks. The line with the error should just have  - Discruption in it -

Problem description: After updating on 25aug14 on Debian jessie 
3.14.15-2 one of the fields in my datadase starts out displaying the correct information then changes to the longest line of text on the screen finishing in square zeros.
Steps to reproduce:
1. ....
2. ....
3. ....

Current behavior:

Expected behavior:

Operating System: Debian
Version: release
Comment 1 Robert Großkopf 2014-08-25 18:40:38 UTC
What has been changed by the update from Debian? Did you change version from LO? Did you change the installation of MySQL? Dud you change the type of connection to MySQL?

I saw XEventListener in the text. Does anything in the database run with macros?
Comment 2 Peter 2014-08-26 02:33:14 UTC
The system that has the mysql is called crystal and is running Debian squeeze and because it is being retired it has not been updated for about 2 months.
To the best of my knowledge the MySQL is not running macros, but it is also used for mythtv that has not been changed for over a year.
The system that I am connecting from is a Debian Jessie system.
This is the first time I have used this bug reporting system and can not see how to do another attachment so I will send the garadge.odb file to the email address robert@familiegrosskopf.de
When I updated the  Debian Jessie system it put about 100 updates on it including Libreoffice, prior to the update I had been using the garadge.odb on the new system for a couple of months, the Log updates I have put in a file called dpkgLog
and will send that to your E-Mail address.
I don't know what you mean by "Did you change version from LO?"
The garadge.odb has not been changed for years.
Comment 3 Robert Großkopf 2014-08-26 17:40:37 UTC
Hi Peter,

seem you have updated LO and the mysql-connector to LO version (see this in the log-file you send to me). You are using the direct connection.
You could try to change to a JDBC-connection. The connector is an extension and it could be there are problems inside the connector ...
The updates you made were updates of your system, right? is a very new version. I thought debian is specialist for stable working version, so I wonder that there is a for download, not a 4.2.* with more bugfixes ...

I cant get any connection with the database-file you send directly to my mailaddress. It's because I have no dump of your MySQL-Database. So I could only see you haven't used any macros inside the document.

You could send me a dump of your mysql-database so I could see, if I am able to reproduce the buggy behavior.

You could get such a dump with a command like this in the terminal:
mysqldump -u <mysqlusername> -l <databasename> > /home/user/database.sql;


Comment 4 Peter 2014-08-28 03:20:54 UTC
Robert, I have now removed the mysql-connector, rebooted and tested, and the problem is still the same. Then I noticed that there was a upgrade for the libmysql-java so I did another update and retried my garadge.odb but it is still getting the same errors.To the best of my knowledge the garadge.odb uses JDBC although it is a long time since I set it up and my database skills are minimual.
For security reasons I will send you the data base file directly, plus some others directly.
Comment 5 Robert Großkopf 2014-08-28 06:07:52 UTC
Hi Peter,

I could confirm the behavior for every 4.3-version installed here. Doesn't appear in LO

When I open the form in 4.3 it hangs for some seconds, showing a readable entry in the field. Then it switched to such things like showing which fonts are installed or only squares.

Could you add the database and the *.sql-file as a *.zip as attachment to this bug so other people could have a look at it? Should I do it? Or should I delete the data and rewrite with some nonsense-content, which will show the same buggy behavior.

Try to switch to LO - there it will work.

Set this bug as New, regression and the version to the first LO 4.3, because I could also notice it with LO
Comment 6 MAG4 2014-09-05 10:56:53 UTC
Created attachment 105794 [details]
gdbtrace 1
Comment 7 MAG4 2014-09-05 10:57:18 UTC
Created attachment 105795 [details]
gdbtrace 2
Comment 8 MAG4 2014-09-05 10:59:24 UTC
Hi, we also confirm the regression (with version 4.3.0-3 now in Debian Testing).
Downgrading to version 4.2.6 the problem disappear.
We attach two gdbtrace ...

Comment 9 MAG4 2014-09-16 08:45:35 UTC
Hi, we confirm the regression also with version 4.3.1-1 now in Debian Testing.

Comment 10 Joel Madero 2014-11-07 02:21:57 UTC
Would be fantastic if someone could bibisect this: https://wiki.documentfoundation.org/QA/HowToBibisect

Feel free to jump into the QA channel for guidance.
Comment 11 MAG4 2014-11-18 12:03:29 UTC
Hi, upgrading to version 4.3.3-1 now in Debian Testing solve the regression ...

Comment 12 Matthew Francis 2014-12-19 09:29:49 UTC
According to comment 11, the issue has already been resolved in 4.3

-> Removing Whiteboard: bibisectRequest
-> Setting status to RESOLVED - WORKSFORME (as the precise commit isn't known)