Bug 54158 - : Segmentation fault (11)
Summary: : Segmentation fault (11)
Status: RESOLVED DUPLICATE of bug 53557
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.6.0.1 rc
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-28 13:38 UTC by Vince Radice
Modified: 2012-08-28 20:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Database in question (553.05 KB, application/vnd.oasis.opendocument.database)
2012-08-28 13:38 UTC, Vince Radice
Details
bt on 3.6 (4.92 KB, text/plain)
2012-08-28 20:51 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Radice 2012-08-28 13:38:11 UTC
Created attachment 66224 [details]
Database in question

Problem description: 

Steps to reproduce:
1.Open database
2.Go to Forms section
3.Try to open Earnpserv, Search Cooktime Earning per share, or Search Cooktime XPs Descending

Current behavior:

Executable: soffice.bin PID: 29357 Signal: Segmentation fault (11)

Expected behavior:

Form opens properly

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1

I upgraded from 3.4 to 3.6.  I have several forms that worked properly under 3.4 but now I get a segmentation fault when opening several of them.  I have attached the database in question,  The forms that fail are Earnpserv, Search Cooktime Earning per share, and Search Cooktime XPs Descending.

When the segmentation fault occurs, I get the wizard that wants to submit a bug report.  As I follow through it, I get to the point of creating a back trace.  In order to do that, I need to install the debug symbols.  I try but yum is unable to find them.
Comment 1 Julien Nabet 2012-08-28 20:51:21 UTC
Created attachment 66248 [details]
bt on 3.6

On pc Debian x86-64 with 3.6 sources updated today, I reproduce the problem.
I attached console logs + bt
Comment 2 Julien Nabet 2012-08-28 20:53:30 UTC
According to the bt, it's perhaps a dup of fdo#53557.

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