Bug 155771

Summary:	Konversation crashes randomly when sending messages under KDE 4.0
Product:	[Applications] konversation	Reporter:	Brian Vuyk <brian>
Component:	general	Assignee:	Konversation Developers <konversation-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Brian Vuyk 2008-01-14 18:36:23 UTC

Version:            (using KDE KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

Under KDE 4.0, Konversation crashes with no warning occasionally when sending messages. 

The application is not being used in any unexpected fashion, merely connection to IRC and chatting. Application behaves perfectly under KDE 3.5.8.

My OS is Ubuntu, the package is the most recent one in the Ubuntu repositories as of this date (Jan. 14 / 2008).

Backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233905984 (LWP 8535)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6ef5b8b in QTextFormat::removeRef () from /usr/lib/libqt-mt.so.3
#7  0xb6edb0f4 in QTextFormatterBreakWords::format ()
   from /usr/lib/libqt-mt.so.3
#8  0xb6ee49e4 in QTextParagraph::format () from /usr/lib/libqt-mt.so.3
#9  0xb6eec063 in QTextCursor::insert () from /usr/lib/libqt-mt.so.3
#10 0xb700c7ed in QTextEdit::insert () from /usr/lib/libqt-mt.so.3
#11 0xb700ccb4 in QTextEdit::insert () from /usr/lib/libqt-mt.so.3
#12 0xb7011662 in QTextEdit::keyPressEvent () from /usr/lib/libqt-mt.so.3
#13 0xb77a5745 in KTextEdit::keyPressEvent () from /usr/lib/libkdeui.so.4
#14 0x080b8a55 in ?? ()
#15 0x085b3580 in ?? ()
#16 0xbf8fb954 in ?? ()
#17 0xbf8fb954 in ?? ()
#18 0x00000000 in ?? ()

Comment 1 Eike Hein 2008-01-14 18:48:40 UTC

Please install the konversation-dbg and kdelibs-dbg packages and, well, "crash it again" - so we get a useful backtrace :-)

Comment 2 Brian Vuyk 2008-01-14 18:51:31 UTC

Your wish is my command, packages are installed, will follow up with another backtrace when konversation goes down again. Shouldn't take too long.

Comment 3 Eike Hein 2008-01-14 18:56:28 UTC

Thanks :)

Comment 4 argonel 2008-02-18 16:58:49 UTC

Ok, it has been 35 days. Has this occurred again?

Comment 5 argonel 2008-04-14 20:47:33 UTC

request for details ignored: closing.