[Kst] Mysterious crash, please help!

Barth Netterfield barth.netterfield at utoronto.ca
Tue Nov 12 19:09:00 UTC 2013

I'm going to start looking at... right now.

On November 12, 2013 8:06:28 PM Nicolas Brisset wrote:

> Hi Peter,
> I tried your suggestion below, but it does not work. I don't get messages,
> and it still crashes. Also tried Qt::BlockingQueuedConnection, which raises
> the following message: Qt: Dead lock detected while activating a
> BlockingQueuedConnection: Sender is AsciiSource(0x7f3864c72010), receiver
> is Kst::MainWindow(0x13b2680)
> The other problem is that the other places which trigger messages don't do
> it with signals but by calling setMessage() directly. What I don't get is
> why it works to call setText() on a QLabel and not showMessage on the
> QStatusBar object.
> Looks like I'm still stuck.
> Nicolas
> > You could try to connect all signals to setMessage() with
> > Qt::QueuedConnection.
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst

Barth Netterfield
University of Toronto

More information about the Kst mailing list