Bug 287679

Summary:	sporadic startup crash in Konversation at qscopedpointer.h:113
Product:	[Applications] konversation	Reporter:	Tony Mechelynck <antoine.mechelynck>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	hein
Priority:	NOR
Version:	1.3.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Tony Mechelynck 2011-11-27 14:03:56 UTC

Version:           1.3.1 (using KDE 4.7.2) 
OS:                Linux

Stack trace follows. This couldn't be auto-reported because kded4 had crashed on logging in to X11.

Application: Konversation (konversation), signal: Segmentation fault
[KCrash Handler]
#6  operator-> (this=0xbabababa00000b5d) at
../../src/corelib/tools/qscopedpointer.h:113
#7  QSslError::operator== (this=0xbabababa00000b5d, other=...) at
ssl/qsslerror.cpp:181
#8  0x00007fcd155dab91 in contains (t=..., this=0xa7c488) at
../../src/corelib/tools/qlist.h:866
#9  QSslSocketBackendPrivate::startHandshake (this=0xa7c2a0) at
ssl/qsslsocket_openssl.cpp:1281
#10 0x00007fcd155dc4dd in QSslSocketBackendPrivate::transmit (this=0xa7c2a0) at
ssl/qsslsocket_openssl.cpp:1014
#11 0x00007fcd155d648d in QSslSocket::qt_metacall (this=0xcd1360,
_c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff01696510) at
.moc/release-shared/moc_qsslsocket.cpp:121
#12 0x00007fcd1444559a in QMetaObject::activate (sender=0xee1f10, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3287
#13 0x00007fcd155baf2f in QAbstractSocketPrivate::canReadNotification
(this=0xf98250) at socket/qabstractsocket.cpp:643
#14 0x00007fcd155a9b71 in event (this=<optimized out>, e=<optimized out>) at
socket/qnativesocketengine.cpp:1103
#15 QReadNotifier::event (this=<optimized out>, e=<optimized out>) at
socket/qnativesocketengine.cpp:1100
#16 0x00007fcd13589be4 in notify_helper (e=0x7fff01696a90, receiver=0xde7550,
this=0x89c6b0) at kernel/qapplication.cpp:4481
#17 QApplicationPrivate::notify_helper (this=0x89c6b0, receiver=0xde7550,
e=0x7fff01696a90) at kernel/qapplication.cpp:4453
#18 0x00007fcd1358ea71 in QApplication::notify (this=0x7fff01696d40,
receiver=0xde7550, e=0x7fff01696a90) at kernel/qapplication.cpp:4360
#19 0x00007fcd14e83e36 in KApplication::notify (this=0x7fff01696d40,
receiver=0xde7550, event=0x7fff01696a90) at
/usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311
#20 0x00007fcd1443281c in QCoreApplication::notifyInternal
(this=0x7fff01696d40, receiver=0xde7550, event=0x7fff01696a90) at
kernel/qcoreapplication.cpp:787
#21 0x00007fcd1445cc27 in sendEvent (event=0x7fff01696a90, receiver=<optimized
out>) at kernel/qcoreapplication.h:215
#22 socketNotifierSourceDispatch (source=0x8ab890) at
kernel/qeventdispatcher_glib.cpp:110
#23 0x00007fcd0ddcb58d in g_main_dispatch (context=0x89e5c0) at gmain.c:2425
#24 g_main_context_dispatch (context=0x89e5c0) at gmain.c:2995
#25 0x00007fcd0ddcbd88 in g_main_context_iterate (context=0x89e5c0,
block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073
#26 0x00007fcd0ddcbf59 in g_main_context_iteration (context=0x89e5c0,
may_block=1) at gmain.c:3136
#27 0x00007fcd1445d50f in QEventDispatcherGlib::processEvents (this=0x896d10,
flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#28 0x00007fcd1362cf2e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=<optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007fcd14431a22 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#30 0x00007fcd14431c1f in QEventLoop::exec (this=0x7fff01696cd0, flags=...) at
kernel/qeventloop.cpp:201
#31 0x00007fcd14435de7 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1064
#32 0x0000000000446e64 in main (argc=3, argv=0x7fff01697b18) at
/usr/src/debug/konversation-1.3.1/src/main.cpp:101

Reproducible: Couldn't Reproduce

Steps to Reproduce:
0. start Konversation


Actual Results:  
crash


Expected Results:  
no crash


Additional info: See also https://bugzilla.novell.com/show_bug.cgi?id=732730

Comment 1 Eike Hein 2011-11-28 19:40:50 UTC

Unfortunately there's no Konversation code in the backtrace and the steps to reproduce ("at startup") don't give us much to work with, so there's nothing we can do for the moment. However, there have been a fair amount of changes to the way Konversation interacts with KDE's and Qt's SSL code in 1.4-beta1, so with any luck perhaps things have improved for you there.

Comment 2 Tony Mechelynck 2011-11-29 08:02:10 UTC

(In reply to comment #1)
> Unfortunately there's no Konversation code in the backtrace and the steps to
> reproduce ("at startup") don't give us much to work with, so there's nothing we
> can do for the moment. However, there have been a fair amount of changes to the
> way Konversation interacts with KDE's and Qt's SSL code in 1.4-beta1, so with
> any luck perhaps things have improved for you there.

Well, this crash happened to me exactly once, apparently at or near the moment where the kres-migrator window gives way to the chat window proper. The kded4 crash seems gone, so if this happens again ($DEITY forbid) it'll be auto-reported. Will it be more informative though? Maybe not.

The version of Konversation in use at the time of the crash included a kde.org patch with a workaround for a Qt bug crashing Konversation at random times; this patch is still in the "testing" stage at openSUSE, it hasn't yet reached their production repos AFAIK. See https://bugzilla.novell.com/show_bug.cgi?id=731397#c8 for details of this particular point.

Comment 3 Eike Hein 2011-11-29 08:14:06 UTC

Yeah, I did follow the Novell link in the initial report and read about the patch, but concluded it's unrelated to your crash. The patch in question is to work around a Qt bug in the QTextDocument stack, which is far removed from any of the code in the backtrace.

Comment 4 Myriam Schweingruber 2013-04-13 22:51:51 UTC

Closing as this is for an outdated version, not reproducible. Please feel free to reopen if you can reproduce this with Konversation 1.5 RC1 or later and provide a new backtrace.

Comment 5 Tony Mechelynck 2013-04-14 00:14:52 UTC

Tere's been a ve-e-ery long time since Konversation last crashed on me. Maybe years. So AFAICT, either whatever caused this crash is a very rare occurrence (considering I run Konversation whenever my computer is online), or else it has been fixed somewhere somewhen.

Changing the resolution to WORKSFORME.