Ubuntu
libreoffice package

LibreOffice Base Crash when i try to connect to mysql

Bug #1577316 reported by Kirino
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

When I try to connect to my mysql database via libreoffice base , this one closes it without providing crash report.

lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

apt-cache policy libreoffice-base
libreoffice-base:
  Installé : 1:5.1.2-0ubuntu1
  Candidat : 1:5.1.2-0ubuntu1

apt-cache policy libreoffice-mysql-connector
libreoffice-mysql-connector:
  Installé : 1.0.2+LibO5.1.2-0ubuntu1
  Candidat : 1.0.2+LibO5.1.2-0ubuntu1

Revision history for this message
penalvch (penalvch) wrote :

Kirino, thank you for reporting this and helping make Ubuntu better.

To clarify, after the crash, is there a crash file in /var/crash?

If not, could you please confirm apport is enabled as per https://help.ubuntu.com/community/ReportingBugs?

Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Kirino (lenormand-sbn) wrote :

Hello, no crash file in the /var/crash folder and apport is enabled.

I tried again after the verification of apport and still no crash file for libreoffice Base

Revision history for this message
Fred Saunier (fsaunier) wrote :

Hello, I am also affected by this bug since I upgraded to Xenial.

In my case, it is possible to connect through the MySQL JDBC driver (as a workaround).

However, the connection is way slower than what it was before the upgrade (I was then running LO 4.4 on Vivid), or than with my other desktop (still running Trusty).

Revision history for this message
Fred Saunier (fsaunier) wrote :

Complementary to comment #3, connections work fine on Trusty with LO 5.1.2.2 using native MySQL. It would appear the issue is with Xenial only.

Revision history for this message
penalvch (penalvch) wrote :

Björn Michaelsen, the original reporter can consistently reproduce a crash in LO but apport won't kick in despite being enabled. Has something changed in LO either upstream or for Ubuntu where apport will no longer catch crashes or crashes in certain circumstances? Or would this be something to chase up with apport developers?

tags: added: regression-release xenial
Changed in libreoffice (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libreoffice (Ubuntu):
status: New → Confirmed
Revision history for this message
Leo Gaggl (leogaggl) wrote :

Is there a work-around for this issue ?

Revision history for this message
Björn Michaelsen (bjoern-michaelsen) wrote :

@penalvch: No changes on that that Im aware of. Feel free to hint apport folks on this.

As an alternative:
 apt install libreoffice-dbg gdb

 gdb /usr/lib/libreoffice/program/soffice.bin
 type r

reproduce the crash:

 type bt

should provide a stacktrace too.

Revision history for this message
Fred Saunier (fsaunier) wrote :

On Xenial, the problem appears to be solved with LO 5.1.3 -- connection to database in native MySQL is now stable.

Revision history for this message
Martin Pitt (pitti) wrote :

Please attach /var/log/apport.log after a crash happens. If there is any entry about LibO and apport ignores it for some reason, please reassign to Apport.

Otherwise I suspect that LibO installs a signal handler for SIGSEGV, SIGABRT and friends, perhaps it has some kind of built crash feedback agent?

Revision history for this message
Kirino (lenormand-sbn) wrote :

libreoffice was update and all works for me!

Sebastien Bacher (seb128)
Changed in libreoffice (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.