Summary: | Kget crashed once when I tried to download googleearth, cannot reproduce | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | auxsvr |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kget, rasasi78 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
auxsvr
2008-07-13 12:03:45 UTC
Looks like a crash in KIO. Hello: I've found this working on 4.1.1, please retest and close if convenient. Regards, Bug #170869 looks like a duplicate of this. I had another crash with KDE 4.1.2 today that is similar: Application: KGet (kget), signal SIGSEGV [?1034h(no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5fed700 (LWP 3265)] [KCrash handler] #6 QUrl::host (this=0x72) at io/qurl.cpp:4247 #7 0xb7a8d7fb in searchIdleList (idleSlaves=@0x826ff24, url=@0x72, protocol=@0xbfde7cc4, exact=@0xbfde7d5f) at /usr/src/debug/kdelibs-4.1.2/kio/kio/scheduler.cpp:609 #8 0xb7a91374 in KIO::SchedulerPrivate::findIdleSlave (this=0x826fed0, job=0x825f068, exact=@0xbfde7d5f) at /usr/src/debug/kdelibs-4.1.2/kio/kio/scheduler.cpp:683 #9 0xb7a91c6f in KIO::SchedulerPrivate::startJobDirect (this=0x826fed0) at /usr/src/debug/kdelibs-4.1.2/kio/kio/scheduler.cpp:588 #10 0xb7a91e10 in KIO::SchedulerPrivate::startStep (this=0x826fed0) at /usr/src/debug/kdelibs-4.1.2/kio/kio/scheduler.cpp:433 #11 0xb7a92076 in KIO::Scheduler::qt_metacall (this=0x826ff60, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfde7e48) at /usr/src/debug/kdelibs-4.1.2/build/kio/scheduler.moc:101 #12 0xb75bd730 in QMetaObject::activate (sender=0x826fed4, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031 #13 0xb75be4b2 in QMetaObject::activate (sender=0x826fed4, m=0xb768c904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101 #14 0xb75f8bb7 in QTimer::timeout (this=0x826fed4) at .moc/release-shared/moc_qtimer.cpp:126 #15 0xb75c41ce in QTimer::timerEvent (this=0x826fed4, e=0xbfde8310) at kernel/qtimer.cpp:257 #16 0xb75b81ef in QObject::event (this=0x826fed4, e=0xbfde8310) at kernel/qobject.cpp:1120 #17 0xb678b82c in QApplicationPrivate::notify_helper (this=0x80bb8a8, receiver=0x826fed4, e=0xbfde8310) at kernel/qapplication.cpp:3803 #18 0xb67936ce in QApplication::notify (this=0xbfde85c8, receiver=0x826fed4, e=0xbfde8310) at kernel/qapplication.cpp:3393 #19 0xb7e0ce0d in KApplication::notify (this=0xbfde85c8, receiver=0x826fed4, event=0xbfde8310) at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311 #20 0xb75a8a61 in QCoreApplication::notifyInternal (this=0xbfde85c8, receiver=0x826fed4, event=0xbfde8310) at kernel/qcoreapplication.cpp:587 #21 0xb75d6dd6 in QTimerInfoList::activateTimers (this=0x80be6c4) at kernel/qcoreapplication.h:209 #22 0xb75d32a0 in timerSourceDispatch (source=0x80be690) at kernel/qeventdispatcher_glib.cpp:160 #23 0xb61112d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb611485b in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb61149d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb75d31f8 in QEventDispatcherGlib::processEvents (this=0x80bb978, flags= {i = -1075936072}) at kernel/qeventdispatcher_glib.cpp:319 #27 0xb6824885 in QGuiEventDispatcherGlib::processEvents (this=0x80bb978, flags={i = -1075936024}) at kernel/qguieventdispatcher_glib.cpp:198 #28 0xb75a713a in QEventLoop::processEvents (this=0xbfde8560, flags= {i = -1075935960}) at kernel/qeventloop.cpp:143 #29 0xb75a72fa in QEventLoop::exec (this=0xbfde8560, flags={i = -1075935896}) at kernel/qeventloop.cpp:194 #30 0xb75a9995 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #31 0xb678b6a7 in QApplication::exec () at kernel/qapplication.cpp:3331 #32 0x0809616a in _start () #0 0xffffe430 in __kernel_vsyscall () This also looks similar to bug #170115 and bug #163171. It must be a kdelibs issue. This is a duplicate of bug #163171. *** This bug has been marked as a duplicate of bug 163171 *** |