[Gutsy] Crash when opening with 4 error messages

Bug #151972 reported by Rich Johnson
2
Affects Status Importance Assigned to Milestone
konversation (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: konversation

## BACKTRACE ##
--------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233783104 (LWP 21972)]
[KCrash handler]
#6 0x0000000a in ?? ()
#7 0xb7d98df3 in KIO::Scheduler::createSlave (this=0x83fdcb0,
    protInfo=0x83ffd88, job=0x8467010, url=@0x8467088)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/scheduler.cpp:561
#8 0xb7da80f6 in KIO::Scheduler::startJobDirect (this=0x83fdcb0)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/scheduler.cpp:436
#9 0xb7da8479 in KIO::Scheduler::startStep (this=0x83fdcb0)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/scheduler.cpp:273
#10 0xb7da85dc in KIO::Scheduler::qt_invoke (this=0x83fdcb0, _id=4,
    _o=0xbfe3c81c) at ./scheduler.moc:161
#11 0xb6e97893 in QObject::activate_signal (this=0x83fdcd8, clist=0x83feb00,
    o=0xbfe3c81c) at kernel/qobject.cpp:2356
#12 0xb6e98338 in QObject::activate_signal (this=0x83fdcd8, signal=2)
    at kernel/qobject.cpp:2325
#13 0xb72259b2 in QTimer::timeout (this=0x83fdcd8)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#14 0xb6ebf5ba in QTimer::event (this=0x83fdcd8, e=0xbfe3cb48)
    at kernel/qtimer.cpp:219
#15 0xb6e2eaf0 in QApplication::internalNotify (this=0xbfe3ce44,
    receiver=0x83fdcd8, e=0xbfe3cb48) at kernel/qapplication.cpp:2635
#16 0xb6e3091f in QApplication::notify (this=0xbfe3ce44, receiver=0x83fdcd8,
    e=0xbfe3cb48) at kernel/qapplication.cpp:2358
#17 0xb7552212 in KApplication::notify (this=0xbfe3ce44, receiver=0x83fdcd8,
    event=0xbfe3cb48)
    at /build/buildd/kdelibs-3.5.7/./kdecore/kapplication.cpp:550
#18 0xb6dc1209 in QApplication::sendEvent (receiver=0x83fdcd8,
    event=0xbfe3cb48) at ../include/qapplication.h:520
#19 0xb6e2153b in QEventLoop::activateTimers (this=0x82a0a80)
    at kernel/qeventloop_unix.cpp:556
#20 0xb6dd5d49 in QEventLoop::processEvents (this=0x82a0a80, flags=4)
    at kernel/qeventloop_x11.cpp:389
#21 0xb6e491ce in QEventLoop::enterLoop (this=0x82a0a80)
    at kernel/qeventloop.cpp:198
#22 0xb6e48fde in QEventLoop::exec (this=0x82a0a80)
    at kernel/qeventloop.cpp:145
#23 0xb6e30699 in QApplication::exec (this=0xbfe3ce44)
    at kernel/qapplication.cpp:2758
#24 0x0812d13e in ?? ()
#25 0xbfe3ce44 in ?? ()
#26 0x0822a908 in ?? ()
#27 0x00000000 in ?? ()

Revision history for this message
Rich Johnson (nixternal) wrote :

Here is a screenshot of the 4 error dialogs.

Rich Johnson (nixternal)
Changed in konversation:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.