libreoffice 4.1.3 base connection to mdb via odbc crashes on saving odb file

Bug #1254420 reported by magowiz
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I was trying to connect to an existing mdb (MS Access) database file using unixodbc and libreoffice-base,
I've got unixodbc , undixodbc-bin and libmdbodbc1 packages installed
I set the odbc as following :

/etc/odbc.ini
[Pippo]
Description = mine database
Driver = /usr/lib/x86_64-linux-gnu/odbc/libmdbodbc.so.1
Database = /home/magowiz/pippo.mdb

/etc/odbcinst.ini
[MDBTools]
Description = MDBTools Driver
Driver = libmdbodbc.so.1
Setup = libmdbodbc.so.1
FileUsage = 1
UsageCount = 2

I use the connection wizard into libreoffice base : I can successfully test mine connection but while I'm saving the odb file the whole program crashes and close itself

It follows distro and software versions :

$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

apt-cache policy libreoffice-base
libreoffice-base:
  Installed: 1:4.1.3-0ubuntu1
  Candidate: 1:4.1.3-0ubuntu1

apt-cache policy unixodbc
unixodbc:
  Installed: 2.2.14p2-5ubuntu4
  Candidate: 2.2.14p2-5ubuntu4

apt-cache policy libmdbodbc1
libmdbodbc1:
  Installed: 0.7-3
  Candidate: 0.7-3

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: libreoffice-core 1:4.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sun Nov 24 10:34:00 2013
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
ExecutableTimestamp: 1385081753
MarkForUpload: True
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
ProcCwd: /home/magowiz
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
 LD_LIBRARY_PATH=<set>
SegvAnalysis: Failure: invalid literal for int() with base 16: 'symbol'
Signal: 11
SourcePackage: libreoffice
StacktraceTop:

Title: soffice.bin crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-10-17 (37 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
magowiz (magowiz) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 extract_sql_error_rec (head=head@entry=0x30d90a0, sqlstate=sqlstate@entry=0x7fff435e3ca0 "00000", rec_number=<optimized out>, rec_number@entry=1, native_error=native_error@entry=0x7fff435e3c5c, message_text=message_text@entry=0x7fff435e3cb0 "", buffer_length=<optimized out>, text_length=text_length@entry=0x7fff435e3c5a) at SQLGetDiagRec.c:444
 SQLGetDiagRec (handle_type=<optimized out>, handle=0x30d8c60, rec_number=<optimized out>, sqlstate=0x7fff435e3ca0 "00000", native=0x7fff435e3c5c, message_text=0x7fff435e3cb0 "", buffer_length=511, text_length_ptr=0x7fff435e3c5a) at SQLGetDiagRec.c:745
 ?? () from /tmp/apport_sandbox_ZXdRys/usr/lib/libreoffice/program/../program/libodbcbaselo.so
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libudev1: package version 204-0ubuntu19 dbgsym version 204-0ubuntu18
outdated debug symbol package for libp11-kit-gnome-keyring: package version 3.8.2-0ubuntu3.1 dbgsym version 3.8.2-0ubuntu3

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
penalvch (penalvch) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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