Bug 97695 - No SDBC driver was found for the URL 'sdbc:embedded:firebird'
Summary: No SDBC driver was found for the URL 'sdbc:embedded:firebird'
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, regression
Depends on:
Blocks:
 
Reported: 2016-02-09 17:25 UTC by Terrence Enger
Modified: 2016-02-12 19:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
example database (42.25 KB, application/vnd.oasis.opendocument.database)
2016-02-09 17:25 UTC, Terrence Enger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Terrence Enger 2016-02-09 17:25:22 UTC 
Created attachment 122488 [details]
example database

STR
(1) Download and open the attached example_fb.odb.  Program presents
    Base window.
(2) In pane Database, click <Queries>.
(3) In pane Queries, double-click <Query2>.
    Expected :  A data grid with one row.
    Observed :  Program displays message box ...

        LibreOfficeDev Base

        The connection to the data source "example_fb" could not be
        established.

        The connection to the external data source could not be
        extablished.  No SDBC driver was found for the URL
        'sdbc:embedded:firebird'.
Comment 1 Terrence Enger 2016-02-09 17:28:24 UTC 
Working in the daily linux dbgutil repository, I see (whitespace
added) from `git bisect good` ...

    f10dd63f9742a7f653071feb08c847099d251d5e is the first bad commit
    commit f10dd63f9742a7f653071feb08c847099d251d5e
    Author: Miklos Vajna <vmiklos@collabora.co.uk>
    Date:   Sat Feb 6 05:36:03 2016 +0100

        2016-02-06: source-hash-5e971b274922f9713aefcd5f612459ffced84845

    :100644 100644 e32ab6bbaf618ddc1f320bb89466b3f9eb529703
        4c5f39a85b54122e70e4acc430d810941a40ef7c M	build-info.txt
    :040000 040000 025fda40d167603a046418134d267b30837031fd
        12223e41c1c1d9574338b1c46d73df8ee50c725d M	opt

and from `git bisect log` ...

    # bad: [48055178fe3433f31269d7f1c8be8707b43114bf] 2016-02-09:
        source-hash-76ec54e8c9f3580450bca85236a4f5af0c328588
    # good: [aae1af85a5606ec45ac8d7371f71b82d0dd4228a] 2015-12-29:
        source-hash-e413549dc8b5669a806eeabc30c7d6f92723a882
    git bisect start '4805517' 'aae1af8'
    # good: [51541618133d0694b7bf06ce99b2896e180e35af]
        2016-01-19: source-hash-d95d9d7f908419f397941ef60ac6ced3261c9b87
    git bisect good 51541618133d0694b7bf06ce99b2896e180e35af
    # good: [4c0559392909c93c97e9b07c392d0e1ada9e6500] 2016-01-29:
        source-hash-182505aff18e1241ac88f791b419e6c856bf7ee5
    git bisect good 4c0559392909c93c97e9b07c392d0e1ada9e6500
    # good: [ad7be19d77481de0f03123ada4856c11d883135a] 2016-02-03:
        source-hash-e9089b4f53c0fef5d0bdcc76add9a43a8c6d81bd
    git bisect good ad7be19d77481de0f03123ada4856c11d883135a
    # bad: [f10dd63f9742a7f653071feb08c847099d251d5e] 2016-02-06:
        source-hash-5e971b274922f9713aefcd5f612459ffced84845
    git bisect bad f10dd63f9742a7f653071feb08c847099d251d5e
    # good: [8dea1e7c23dd057a83be1b08104569ba5a89fc09] 2016-02-05:
        source-hash-40322a77af79420d0b30d32b3ec53c9a4fa00428
    git bisect good 8dea1e7c23dd057a83be1b08104569ba5a89fc09
    # first bad commit: [f10dd63f9742a7f653071feb08c847099d251d5e]
        2016-02-06: source-hash-5e971b274922f9713aefcd5f612459ffced84845

I am setting keywords regression, bibisected.
Comment 2 Julien Nabet 2016-02-11 19:41:57 UTC 
On pc Debian x86-64 with master sources updated today, I could reproduce this only when experimental features weren't enabled.
However, as soon as I enabled them (and after having restarted LO), it was ok.
Comment 3 Terrence Enger 2016-02-12 19:07:50 UTC 
Thank you, Julien, for the attention.

Again in the linux daily dbgutil bibisect repository, I see that the
problem went away between versions 2016-02-09and 2016-02-12.  I am
setting status RESOLVED WORKSFORME.