Bug 751462 - OpenLP crashes when starting LibraOffice in Fedora 16
Summary: OpenLP crashes when starting LibraOffice in Fedora 16
Keywords:
Status: CLOSED DUPLICATE of bug 752101
Alias: None
Product: Fedora
Classification: Fedora
Component: PyQt4
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 19:46 UTC by TR Bentley
Modified: 2011-11-08 14:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-08 14:56:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Trace file when run with first time wizard (106.38 KB, text/plain)
2011-11-07 17:47 UTC, TR Bentley
no flags Details

Description TR Bentley 2011-11-04 19:46:44 UTC
Description of problem:
OpenLP (packaged in fedora) tries to start Impress using the sockets interface. This has worked fine for the last few Fedora releases.  Having just upgraded to Fedora16 OpenLP now crashes if it is asked to use Impress.


Version-Release number of selected component (if applicable):
OpenLP 1.9.8 (or any version)
Impress - Current Fedora release version (Updates)

How reproducible:
Every time.

Steps to Reproduce:
1. Install OpenLP from Fedora repository and start it.
2. When the first time wizard runs make sure "Presentations" is selected.  
3. Wait for the "bang"
  
Actual results:
OpenLP fails to start and gives you a stack trace.

Expected results:
OpenLP starts and give you a display to use

Additional info:
Attached file is a stack trace

Comment 1 TR Bentley 2011-11-06 09:25:20 UTC
Following testing on other platforms by the rest of the team it seems like it only happens on Fedora 16 when it tries to access LibreOffice.

Comment 2 David Tardon 2011-11-07 13:45:09 UTC
It crashes here during start with

*** buffer overflow detected ***: /usr/bin/python terminated
======= Backtrace: =========
/lib64/libc.so.6(__fortify_fail+0x37)[0x30c9d06977]
/lib64/libc.so.6[0x30c9d048f0]
/lib64/libc.so.6[0x30c9d0692e]
/usr/lib64/libQtCore.so.4[0x30d55525d4]
/usr/lib64/python2.7/site-packages/PyQt4/QtCore.so(+0x101a63)[0x7f7f322b0a63]
/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x557b)[0x30cd0dffbb]

, so I do not even get as far as the first time wizard ;) If you have stack trace, please attach it here.

Comment 3 TR Bentley 2011-11-07 17:47:17 UTC
Created attachment 532102 [details]
Trace file when run with first time wizard

Comment 4 David Tardon 2011-11-08 08:56:18 UTC
Yeah, just what I thought: this is the same trace I have got. And it has nothing to do with libreoffice.

Comment 5 Rex Dieter 2011-11-08 14:56:30 UTC

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


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