Bug 142776 - Calc 7.1.4 crashes when I try to open external Firebird3 database (jdbc) in Beamer
Summary: Calc 7.1.4 crashes when I try to open external Firebird3 database (jdbc) in B...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.1.4.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: possibleRegression
Depends on:
Blocks: Crash
  Show dependency treegraph
 
Reported: 2021-06-10 20:53 UTC by sasakelecevic
Modified: 2023-11-28 03:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature: ["mergedlo.dll"]


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sasakelecevic 2021-06-10 20:53:55 UTC
This bug was filed from the crash reporting server and is br-744e885d-b9fd-4edc-b0e4-109353c1adf7.
=========================================

Calc 7.1.4 crashes when I try to open external Firebird3 database (jdbc) in Data Beamer.
Note - LO 7.0.5 works as expected.

Best
Comment 1 Alex Thurgood 2021-06-11 12:51:05 UTC
Which version of Firebird3 server are you using ? and what is the engine version for the FDB file ?

Currently, support appears to be limited to the 12.0 version or lower of the firebird engine, which means that anything later fails to load (cf. bug 141846). Perhaps this failure to load is translating as a crash for you on Windows ?

Unfortunately, the crash report doesn't appear to be of much use, as it would relies in this instance on being able to debug the JVM instance for which it isn't set up.
Comment 2 sasakelecevic 2021-06-12 14:02:45 UTC
Hi,

thanks for the reply.

Im using Firebird 3 server on Windows 10.0 Build 19042:

RDB$GET_CONTEXT = 3.0.5

MON$ODS_MAJOR = 12	

MON$ODS_MINOR = 0

LibreOffice 7.1.4:

Version: 7.1.4.2 (x64) / LibreOffice Community
Build ID: a529a4fab45b75fefc5b6226684193eb000654f6
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: sr-Latn-RS (en_US); UI: en-US
Calc: threaded

Connection type: - JDBC - jaybird-full-4.0.3.java11.jar

Best
Comment 3 sasakelecevic 2021-06-12 14:20:40 UTC
Hi,

I had tried uninstall new LibreOffice and then install "old" version.

1. uninstall LibreOffice 7.1.4, user profile unchanged

2. install LibreOffice 7.0.6
Version: 7.0.6.2 (x64)
Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b
CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: sr-Latn-RS (en_US); UI: en-US
Calc: threaded

3. Start Calc -> View - Data Sourses -> enter password for my database

Result -> No crash
Comment 4 Roman Kuznetsov 2022-10-25 18:01:30 UTC
Could you please retest it in 7.3.6 or in 7.4.2 LibreOffice version?
Comment 5 QA Administrators 2023-04-24 03:24:49 UTC Comment hidden (obsolete)
Comment 6 Julien Nabet 2023-04-30 06:22:21 UTC
You may also try Jaybird 4.0.9 or try Jaybird
Comment 7 QA Administrators 2023-10-28 03:13:27 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2023-11-28 03:13:15 UTC
Dear sasakelecevic,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp