Bug 1497523 - Libreoffice Base crashes
Summary: Libreoffice Base crashes
Keywords:
Status: CLOSED DUPLICATE of bug 1468436
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 26
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-01 12:02 UTC by Th. Siraut
Modified: 2017-10-09 12:32 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-10-09 12:32:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
demo odb (2.94 KB, application/zip)
2017-10-02 09:00 UTC, Caolan McNamara
no flags Details

Description Th. Siraut 2017-10-01 12:02:48 UTC
Description of problem: When I click on the Tables button, libreoffice Base crashes and closes without error messages.


Version-Release number of selected component (if applicable): LibreOffice v5.3.6.1


How reproducible:
- Click on the Tables button after open the .odb file


Steps to Reproduce:
1. Run the .odb file with Libreoffice Base
2. Click on the Tables button
3. Base closes without error messages
4. F26 display "Oups! We are sorry. It seems that he had an incident ... 

Actual results: Crash


Expected results: Access to tables ...


Additional info:

Comment 1 Th. Siraut 2017-10-01 12:06:18 UTC
Since the last updates of F26, I get to the login the message "Oups! We are sorry. It seems that he had an incident ..."
Bug of F26 or Libreoffice Base ???

Comment 2 Caolan McNamara 2017-10-02 09:00:16 UTC
Created attachment 1333148 [details]
demo odb

Comment 3 Caolan McNamara 2017-10-02 09:00:44 UTC
with attached odb and libreoffice-base-5.3.6.1-6.fc26.x86_64 I have no error locally

Comment 4 Th. Siraut 2017-10-05 19:21:36 UTC
(In reply to Caolan McNamara from comment #3)
> with attached odb and libreoffice-base-5.3.6.1-6.fc26.x86_64 I have no error
> locally

Thank you for demo .odb....
After test, Base crashes also :(

Comment 5 Caolan McNamara 2017-10-06 16:05:06 UTC
oh wait, i686 right, not x86_64 like me. I bet this is an incarnation of the java + recent linux kernels crasher bug

Comment 6 Th. Siraut 2017-10-06 19:00:38 UTC
(In reply to Caolan McNamara from comment #5)
> oh wait, i686 right, not x86_64 like me. I bet this is an incarnation of the
> java + recent linux kernels crasher bug

It is possible, indeed ... but I have not found anything as a solution
for information:
the kernel version is : uname -r --> 4.12.14-300.fc26.i686
the java version is : java -version --> 1.8.0_144

Can this help you ?

Comment 7 Caolan McNamara 2017-10-09 12:32:22 UTC
There's a reported workaround for the bug I've just made this a duplicate of, see if that's any use

*** This bug has been marked as a duplicate of bug 1468436 ***


Note You need to log in before you can comment on or make changes to this bug.