Ubuntu
kdebase package

konqueror crash in kubuntu 8.10 with signal SIGABRT

Bug #294174 reported by to6o
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Application: Konqueror (konqueror), signal SIGABRT
(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)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb60dc8d0 (LWP 6119)]
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb80d8430 in __kernel_vsyscall ()
#7 0xb7e93880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7e95248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb73ff795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb73ff872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb73ff915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7c50f50 in ?? () from /usr/lib/libkio.so.5
#13 0xb7c51c55 in ?? () from /usr/lib/libkio.so.5
#14 0xb7c5a6da in ?? () from /usr/lib/libkio.so.5
#15 0xb750ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb750d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb7c65083 in KDirWatch::dirty () from /usr/lib/libkio.so.5
#18 0xb7c658f2 in KDirWatch::setDirty () from /usr/lib/libkio.so.5
#19 0xb7c65e2b in ?? () from /usr/lib/libkio.so.5
#20 0xb7c6d826 in ?? () from /usr/lib/libkio.so.5
#21 0xb7c6eccb in ?? () from /usr/lib/libkio.so.5
#22 0xb750ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb750d7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb75477a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#25 0xb751340e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#26 0xb750753f in QObject::event () from /usr/lib/libQtCore.so.4
#27 0xb69fb8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#28 0xb6a0376e in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0xb79c772d in KApplication::notify () from /usr/lib/libkdeui.so.5
#30 0xb74f7e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#31 0xb7525d81 in ?? () from /usr/lib/libQtCore.so.4
#32 0xb7522520 in ?? () from /usr/lib/libQtCore.so.4
#33 0xb646e6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb6471da3 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb6471f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb7522478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#37 0xb6a95ee5 in ?? () from /usr/lib/libQtGui.so.4
#38 0xb74f652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0xb74f66ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0xb74f8da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0xb69fb767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#42 0xb808b95d in kdemain () from /usr/lib/libkdeinit4_konqueror.so
#43 0x080485b2 in _start ()
#0 0xb80d8430 in __kernel_vsyscall ()

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you install kdebase-dbg and re-obtain the backtrace? Thanks.
Also, if you know what you were doing when the crash occured that would be useful information too.

Changed in kdebase:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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