View Issue Details

IDProjectCategoryView StatusLast Update
0014843ScribusOS-Haikupublic2017-06-07 18:29
Reporterrobertocmcosta Assigned Tojghali  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionno change required 
Platformx86_64OSHaikuOS Versionhrev51192
Product Version1.5.3 
Summary0014843: Scribus crashes when trying to use any tool (text frame, image placeholder...) and moving objects
DescriptionScribus 1.5.3 (also 1.5.2) successfully builds and runs in 64bit Haiku-OS with Qt 5.8.
The application is snappy, loads files correctly, floating palettes work as expected (except they can't be docked like in other OSs), preferences dialogue ok.
But when I try to select and move any object on the page or when I try to use any tool from the toolbar the application crashes immediately with no bug report.
Running it from the terminal and crashing it gives this final message:

QObject::˜QObject: Timers cannot be stopped from another thread

Steps To ReproduceOpen the application, new document, click on text frame tool on the toolbar, click on the page to create a text frame.
Or open a document, select an object on the page and try to move it or double-click on a text frame to edit the text.

Both operations crash the application.
TagsNo tags attached.
PatchNo

Activities

robertocmcosta

2017-06-02 19:23

reporter  

scribus 1.5.3 crash.png (11,660 bytes)   
scribus 1.5.3 crash.png (11,660 bytes)   

cbradney

2017-06-02 20:51

administrator   ~0043985

This is likely related to Qt on Haiku and in that case would be something we cannot fix. Now, we might be able to though if its a bug in our code that only Haiku surfaces. Can you get a backtrace?

robertocmcosta

2017-06-03 12:36

reporter   ~0043987

I don't know if this is exactly what you're asking for, but I ran Scribus through Haiku debugger, reproduced the bug then saved this report.
Please let me know if this is all what you want or if there's anything else I can do to assist you.

jghali

2017-06-03 23:28

administrator   ~0043991

Last edited: 2017-06-03 23:29

Unfortunately this report does not tell us anything about the crash. If Haiku debugger looks like the one shown on https://www.haiku-os.org/node/5004/, what interest us is what display in the top right list, the one displaying "Frame", "IP", "Function" in header. But for this list to display anything useful, you will need a Scribus built with debug information.

robertocmcosta

2017-06-04 15:52

reporter   ~0043994

Yes it is. But it's only filled with data before crashing Scribus. I saved these reports so you can check. But as you mentioned I would need a debug build of Scribus which I dont have. Would you guide me to do it?

jghali

2017-06-05 00:34

administrator   ~0043996

Thanks for those new reports. The crash data appearing in those reports involves only Qt code. But without a debug build the crash data is likely incomplete. Unfortunately nobody in the team is using Haiku. So you cannot provide much help. You'd better contact the Scribus maintainer for Haiku directly. As of now the crash data you provided has only involved Qt, so the root cause of the issue is likely the Qt port for Haiku. In the end, this will probably have to get fixed directly in the Qt port for Haiku.

robertocmcosta

2017-06-06 17:12

reporter   ~0044005

Hi Jean,

With the help of a Haiku developer I could build a debug version of Scribus 1.5.3. Then I ran it through Haiku debugger and here I have the complete debug report. This is what led to the program crash: I created a new default document, selected the text frame tool and clicked on the canvas. Crash!
I hope this new information helps you find out whether it's bug in Scribus code or as you said, in Qt code.
Scribus is shaping up to become a mainstream competitor. A few more interface adjustments, speed improvement and it will get there. Thank you.

jghali

2017-06-07 18:29

administrator   ~0044009

Thanks for the new report. The report confirms the crash occurs inside the Qt port for Haiku:

0x7fff447bc480 0x7ff83340923b commpage_signal_handler + 0x2b
0x7fff447bc890 0x103e9220940 QWidget::windowHandle() const + 0
0x7fff447bc930 0x103e922d654 QWidgetPrivate::create_sys(unsigned long long, bool, bool) + 0x2e4
0x7fff447bc9a0 0x103e922dbb4 QWidget::create(unsigned long long, bool, bool) + 0x114
0x7fff447bca00 0x103e92384e9 QWidget::setVisible(bool) + 0x89
0x7fff447bca50 0x103e921cb5e QToolTip::showText(QPoint const&, QString const&, QWidget*, QRect const&, int) + 0x11e
0x7fff447bca70 0x103e921cca8 QToolTip::showText(QPoint const&, QString const&, QWidget*) + 0x28

As a consequence, this issue should be seen directly with Qt port for Haiku maintainers.

Issue History

Date Modified Username Field Change
2017-06-02 19:23 robertocmcosta New Issue
2017-06-02 19:23 robertocmcosta File Added: scribus 1.5.3 crash.png
2017-06-02 20:51 cbradney Note Added: 0043985
2017-06-03 12:36 robertocmcosta File Added: Scribus-373-debug-03-06-2017-09-30-59.report
2017-06-03 12:36 robertocmcosta Note Added: 0043987
2017-06-03 23:28 jghali Note Added: 0043991
2017-06-03 23:29 jghali Note Edited: 0043991
2017-06-04 15:52 robertocmcosta File Added: Scribus-741-debug-04-06-2017-11-51-47.report
2017-06-04 15:52 robertocmcosta File Added: Scribus-741-debug-04-06-2017-11-52-07.report
2017-06-04 15:52 robertocmcosta Note Added: 0043994
2017-06-05 00:34 jghali Note Added: 0043996
2017-06-06 17:12 robertocmcosta File Added: Scribus-381-debug-06-06-2017-14-00-07.report
2017-06-06 17:12 robertocmcosta Note Added: 0044005
2017-06-07 18:29 jghali Assigned To => jghali
2017-06-07 18:29 jghali Status new => resolved
2017-06-07 18:29 jghali Resolution open => no change required
2017-06-07 18:29 jghali Note Added: 0044009
2017-06-07 18:29 jghali Status resolved => closed