Konversation crashed while typing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qt-x11-free (Ubuntu) |
Won't Fix
|
Low
|
Unassigned |
Bug Description
Binary package hint: konversation
I was typing/editing a message in Konversation, when it suddenly crashed.
[Thread debugging using libthread_db enabled]
[New Thread 0xb67b8960 (LWP 11766)]
[KCrash handler]
#6 0xb6f7ccab in QTextStringChar
at widgets/
#7 0xb6f624b6 in QTextFormatterB
doc=0x8565ac0, parag=0x8efb680, start=0) at kernel/
#8 0xb6f6b962 in QTextParagraph:
doMove=true) at kernel/
#9 0xb6f72f3e in QTextCursor::insert (this=0x8eee048, str=@0xbfad3844,
checkNewLin
#10 0xb7092fb9 in QTextEdit::insert (this=0x8564628, text=@0xbfad395c,
insertionFl
#11 0xb709346c in QTextEdit::insert (this=0x8564628, text=@0xbfad395c,
indent=true, checkNewLine=false, removeSelected=
at widgets/
#12 0xb7097cf0 in QTextEdit:
at widgets/
#13 0xb780e1df in KTextEdit:
at /build/
#14 0x080b79bb in IRCInput:
at /build/
#15 0xb6f38055 in QWidget::event (this=0x8564628, e=0xbfad3e18)
at kernel/
#16 0xb708fec7 in QTextEdit::event (this=0x8564628, e=0xbfad3e18)
at widgets/
#17 0xb6e95c36 in QApplication:
receiver=
#18 0xb6e97c00 in QApplication:
e=0xbfad3e18) at kernel/
#19 0xb75cf672 in KApplication:
event=
at /build/
#20 0xb6e26301 in QApplication:
event=
#21 0xb6e17065 in QETWidget:
event=
#22 0xb6e231a9 in QApplication:
event=
#23 0xb6e3a943 in QEventLoop:
at kernel/
#24 0xb6eb0f90 in QEventLoop:
at kernel/
#25 0xb6eb0c8e in QEventLoop::exec (this=0x82b2730)
at kernel/
#26 0xb6e977df in QApplication::exec (this=0xbfad4474)
at kernel/
#27 0x0812a36e in main (argc=1, argv=0x1)
at /build/
ProblemType: Bug
Architecture: i386
Date: Tue May 6 02:07:03 2008
DistroRelease: Ubuntu 8.04
NonfreeKernelMo
Package: konversation 1.0.1-4ubuntu6
PackageArchitec
ProcEnviron:
PATH=/
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: konversation
Uname: Linux 2.6.24-16-generic i686
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.