| Summary: | KGet crashes on saving images from Konqueror | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Marcus Harrison <marcus> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | frank78ac, kde2, kget, l.appelhans, mbj, Regnaron, zayed.alsaidi |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Valgrind log for kget crash | ||
Seems like a KIO-Bug to me... Lukas Confirming on KDE-4.1.1
Steps to reproduce:
1) Quit kget
2) Open konqueror and go to some site with images
3) Click on an image->save as
4) Set location and wait until kget fires up and crashes
Backtrace:
Application: KGet (kget), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb6232700 (LWP 12502)]
[KCrash handler]
#6 0xb75f5ca3 in QUrl::host (this=0x814a768) at io/qurl.cpp:4253
#7 0xb7ac487f in searchIdleList (idleSlaves=@0x82c8d3c, url=@0x814a768,
protocol=@0xbfdbebbc, exact=@0xbfdbec5b)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs-4.1.1/kio/kio/scheduler.cpp:609
#8 0xb7ac51bc in KIO::SchedulerPrivate::findIdleSlave (this=0x82c8ce8,
job=0x80b2ac0, exact=@0xbfdbec5b)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs-4.1.1/kio/kio/scheduler.cpp:683
#9 0xb7ac7286 in KIO::SchedulerPrivate::startJobDirect (this=0x82c8ce8)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs-4.1.1/kio/kio/scheduler.cpp:588
#10 0xb7ac7354 in KIO::SchedulerPrivate::startStep (this=0x82c8ce8)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs-4.1.1/kio/kio/scheduler.cpp:433
#11 0xb7ac74e9 in KIO::Scheduler::qt_metacall (this=0x814cff0,
_c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfdbed48)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs_build/kio/scheduler.moc:101
#12 0xb7652131 in QMetaObject::activate (sender=0x82c8cec,
from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0)
at kernel/qobject.cpp:3007
#13 0xb7654028 in QMetaObject::activate (sender=0x82c8cec, m=0xb77209c4,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3077
#14 0xb768af2d in QTimer::timeout (this=0x82c8cec)
at .moc/debug-shared/moc_qtimer.cpp:126
#15 0xb76581be in QTimer::timerEvent (this=0x82c8cec, e=0xbfdbf1fc)
at kernel/qtimer.cpp:263
#16 0xb764b5b9 in QObject::event (this=0x82c8cec, e=0xbfdbf1fc)
at kernel/qobject.cpp:1096
#17 0xb68a9f1b in QApplicationPrivate::notify_helper (this=0x80b2d98,
receiver=0x82c8cec, e=0xbfdbf1fc) at kernel/qapplication.cpp:3800
#18 0xb68b0a55 in QApplication::notify (this=0xbfdbf5c0, receiver=0x82c8cec,
e=0xbfdbf1fc) at kernel/qapplication.cpp:3392
#19 0xb7e4dce9 in KApplication::notify (this=0xbfdbf5c0, receiver=0x82c8cec,
event=0xbfdbf1fc)
at /var/tmp/portage/kde-base/kdelibs-4.1.1/work/kdelibs-4.1.1/kdeui/kernel/kapplication.cpp:311
#20 0xb763b771 in QCoreApplication::notifyInternal (this=0xbfdbf5c0,
receiver=0x82c8cec, event=0xbfdbf1fc) at kernel/qcoreapplication.cpp:591
#21 0xb7667ffe in QTimerInfoList::activateTimers (this=0x80b3ad4)
at kernel/qcoreapplication.h:215
#22 0xb76681c2 in QEventDispatcherUNIX::processEvents (this=0x80b2098, flags=
{i = -1076104036}) at kernel/qeventdispatcher_unix.cpp:899
#23 0xb693f03f in QEventDispatcherX11::processEvents (this=0x80b2098, flags=
{i = -1076103976}) at kernel/qeventdispatcher_x11.cpp:154
#24 0xb763a300 in QEventLoop::processEvents (this=0xbfdbf550, flags=
{i = -1076103912}) at kernel/qeventloop.cpp:149
#25 0xb763a4a2 in QEventLoop::exec (this=0xbfdbf550, flags={i = -1076103848})
at kernel/qeventloop.cpp:200
#26 0xb763c8bf in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#27 0xb68a9cb3 in QApplication::exec () at kernel/qapplication.cpp:3330
#28 0x080907fe in main (argc=3, argv=0xbfdbf7a4)
at /var/tmp/portage/kde-base/kget-4.1.1/work/kget-4.1.1/kget/main.cpp:153
#0 0xffffe424 in __kernel_vsyscall ()
*** Bug 171588 has been marked as a duplicate of this bug. *** Created attachment 27553 [details]
Valgrind log for kget crash
*** Bug 172256 has been marked as a duplicate of this bug. *** *** Bug 173032 has been marked as a duplicate of this bug. *** Probably a duplicate of bug 163171? I think so, yeah... Lukas *** This bug has been marked as a duplicate of bug 163171 *** |
Version: (using KDE 4.1.1) OS: Linux Installed from: Ubuntu Packages When KGet isn't already running and is used as Konqueror's default download manager, saving an image causes Konqueror to launch KGet. The KGet downloads window opens... then it crashes and closes with this backtrace: Application: KGet (kget), signal SIGSEGV (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb5fb0720 (LWP 17303)] [KCrash handler] #6 QUrl::host (this=0x60) at io/qurl.cpp:4253 #7 0xb7b0d321 in searchIdleList (idleSlaves=@0x8265f1c, url=@0x60, protocol=@0xbfede84c, exact=@0xbfede8eb) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/scheduler.cpp:609 #8 0xb7b0d8be in KIO::SchedulerPrivate::findIdleSlave (this=0x8265ec8, job=0x815d958, exact=@0xbfede8eb) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/scheduler.cpp:683 #9 0xb7b0fefa in KIO::SchedulerPrivate::startJobDirect (this=0x8265ec8) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/scheduler.cpp:588 #10 0xb7b0ffd8 in KIO::SchedulerPrivate::startStep (this=0x8265ec8) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/scheduler.cpp:433 #11 0xb7b10197 in KIO::Scheduler::qt_metacall (this=0x8113bf0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfede9c8) at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/kio/scheduler.moc:101 #12 0xb76e6f79 in QMetaObject::activate (sender=0x8265ecc, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3016 #13 0xb76e7642 in QMetaObject::activate (sender=0x8265ecc, m=0xb77c6ae4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3086 #14 0xb7724817 in QTimer::timeout (this=0x8265ecc) at .moc/release-shared/moc_qtimer.cpp:126 #15 0xb76ee0fe in QTimer::timerEvent (this=0x8265ecc, e=0xbfedeeb8) at kernel/qtimer.cpp:263 #16 0xb76e19fa in QObject::event (this=0x8265ecc, e=0xbfedeeb8) at kernel/qobject.cpp:1105 #17 0xb6c21f9c in QApplicationPrivate::notify_helper (this=0x80baaf0, receiver=0x8265ecc, e=0xbfedeeb8) at kernel/qapplication.cpp:3800 #18 0xb6c26bf9 in QApplication::notify (this=0xbfedf130, receiver=0x8265ecc, e=0xbfedeeb8) at kernel/qapplication.cpp:3392 #19 0xb7de51c3 in KApplication::notify (this=0xbfedf130, receiver=0x8265ecc, event=0xbfedeeb8) at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311 #20 0xb76d20b9 in QCoreApplication::notifyInternal (this=0xbfedf130, receiver=0x8265ecc, event=0xbfedeeb8) at kernel/qcoreapplication.cpp:591 #21 0xb76ffc01 in QTimerInfoList::activateTimers (this=0x80bd954) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 0xb76fd4a0 in timerSourceDispatch (source=0x80bd920) at kernel/qeventdispatcher_glib.cpp:166 #23 0xb635fdd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb6363193 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb636374e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb76fd9f8 in QEventDispatcherGlib::processEvents (this=0x80b8248, flags=@0xbfedf018) at kernel/qeventdispatcher_glib.cpp:325 #27 0xb6cb5a25 in QGuiEventDispatcherGlib::processEvents (this=0x80b8248, flags=@0xbfedf048) at kernel/qguieventdispatcher_glib.cpp:204 #28 0xb76d133d in QEventLoop::processEvents (this=0xbfedf0c0, flags=@0xbfedf084) at kernel/qeventloop.cpp:149 #29 0xb76d14cd in QEventLoop::exec (this=0xbfedf0c0, flags=@0xbfedf0c8) at kernel/qeventloop.cpp:200 #30 0xb76d374d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849 #31 0xb6c21897 in QApplication::exec () at kernel/qapplication.cpp:3330 #32 0x080934bb in ?? () #33 0xb6897450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #34 0x08061cc1 in _start () #0 0xb7f54410 in __kernel_vsyscall ()