Bug 751462
Summary: | OpenLP crashes when starting LibraOffice in Fedora 16 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | TR Bentley <home> | ||||
Component: | PyQt4 | Assignee: | Rex Dieter <rdieter> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 16 | CC: | caolanm, dmalcolm, dtardon, erack, ltinkl, mstahl, rdieter, sbergman, than | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-11-08 14:56:30 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
TR Bentley
2011-11-04 19:46:44 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. 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. Created attachment 532102 [details]
Trace file when run with first time wizard
Yeah, just what I thought: this is the same trace I have got. And it has nothing to do with libreoffice. *** This bug has been marked as a duplicate of bug 752101 *** |