Bug 171588 - Kget crashes with "Save link as" in Konqueror
Summary: Kget crashes with "Save link as" in Konqueror
Status: RESOLVED DUPLICATE of bug 170869
Alias: None
Product: kio
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-24 13:40 UTC by Morten Bo Johansen
Modified: 2008-09-24 19:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Morten Bo Johansen 2008-09-24 13:40:37 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

In Konqueror I right clicked on this url http://hamrick.com/files/vuesca84.tgz and chose "Save link as" and then save to location and then kget crashed. It is reproducible right now. KDE 4:4.1 packages are from Debian's experimental repository and plugins are disabled in Konqueror. Backtrace follows:

Application: KGet (kget), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f7cb70 (LWP 5918)]
[KCrash handler]
#6  QUrl::host (this=0x70) at io/qurl.cpp:4247
#7  0xb7a22dab in searchIdleList (idleSlaves=@0x9392b34, url=@0x70, 
    protocol=@0xbf9f9a64, exact=@0xbf9f9b1f)
    at /tmp/buildd/kde4libs-4.1.1/kio/kio/scheduler.cpp:609
#8  0xb7a265e4 in KIO::SchedulerPrivate::findIdleSlave (this=0x9392ae0, 
    job=0x947d840, exact=@0xbf9f9b1f)
    at /tmp/buildd/kde4libs-4.1.1/kio/kio/scheduler.cpp:683
#9  0xb7a273cf in KIO::SchedulerPrivate::startJobDirect (this=0x9392ae0)
    at /tmp/buildd/kde4libs-4.1.1/kio/kio/scheduler.cpp:588
#10 0xb7a27660 in KIO::SchedulerPrivate::startStep (this=0x9392ae0)
    at /tmp/buildd/kde4libs-4.1.1/kio/kio/scheduler.cpp:433
#11 0xb7a284e6 in KIO::Scheduler::qt_metacall (this=0x9463240, 
    _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf9f9c18)
    at /tmp/buildd/kde4libs-4.1.1/obj-i486-linux-gnu/kio/scheduler.moc:101
#12 0xb6c5d0c0 in QMetaObject::activate (sender=0x9392ae4, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#13 0xb6c5de42 in QMetaObject::activate (sender=0x9392ae4, m=0xb6d2aae4, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#14 0xb6c97f37 in QTimer::timeout (this=0x9392ae4)
    at .moc/release-shared/moc_qtimer.cpp:126
#15 0xb6c63aee in QTimer::timerEvent (this=0x9392ae4, e=0xbf9fa0bc)
    at kernel/qtimer.cpp:263
#16 0xb6c57baf in QObject::event (this=0x9392ae4, e=0xbf9fa0bc)
    at kernel/qobject.cpp:1105
#17 0xb6ed666c in QApplicationPrivate::notify_helper (this=0x92e2e88, 
    receiver=0x9392ae4, e=0xbf9fa0bc) at kernel/qapplication.cpp:3772
#18 0xb6ede43e in QApplication::notify (this=0xbf9fa348, receiver=0x9392ae4, 
    e=0xbf9fa0bc) at kernel/qapplication.cpp:3366
#19 0xb7e4497d in KApplication::notify (this=0xbf9fa348, receiver=0x9392ae4, 
    event=0xbf9fa0bc)
    at /tmp/buildd/kde4libs-4.1.1/kdeui/kernel/kapplication.cpp:311
#20 0xb6c48571 in QCoreApplication::notifyInternal (this=0xbf9fa348, 
    receiver=0x9392ae4, event=0xbf9fa0bc) at kernel/qcoreapplication.cpp:587
#21 0xb6c765e1 in QTimerInfoList::activateTimers (this=0x92e5c04)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 0xb6c72c20 in timerSourceDispatch (source=0x92e5bd0)
    at kernel/qeventdispatcher_glib.cpp:166
#23 0xb63052e1 in IA__g_main_context_dispatch (context=0x92e4c98)
    at /tmp/buildd/glib2.0-2.16.5/glib/gmain.c:2012
#24 0xb6308973 in g_main_context_iterate (context=0x92e4c98, block=1, 
    dispatch=1, self=0x92dc008)
    at /tmp/buildd/glib2.0-2.16.5/glib/gmain.c:2645
#25 0xb6308b31 in IA__g_main_context_iteration (context=0x92e4c98, 
    may_block=1) at /tmp/buildd/glib2.0-2.16.5/glib/gmain.c:2708
#26 0xb6c72b78 in QEventDispatcherGlib::processEvents (this=0x92e2558, flags=
      {i = -1080057288}) at kernel/qeventdispatcher_glib.cpp:325
#27 0xb6f6f415 in QGuiEventDispatcherGlib::processEvents (this=0x92e2558, 
    flags={i = -1080057240}) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb6c46c5a in QEventLoop::processEvents (this=0xbf9fa2e0, flags=
      {i = -1080057176}) at kernel/qeventloop.cpp:149
#29 0xb6c46e1a in QEventLoop::exec (this=0xbf9fa2e0, flags={i = -1080057112})
    at kernel/qeventloop.cpp:200
#30 0xb6c494c5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#31 0xb6ed64e7 in QApplication::exec () at kernel/qapplication.cpp:3304
#32 0x08098f5a in main (argc=3, argv=0xbf9fa534)
    at /tmp/buildd/kdenetwork-4.1.1/kget/main.cpp:153
#0  0xffffe424 in __kernel_vsyscall ()
Comment 1 Lukas Appelhans 2008-09-24 13:44:14 UTC
Looks like a KIO-crash, reassigning...
Comment 2 Morten Bo Johansen 2008-09-24 13:51:23 UTC
If instead I choose "Actions" -> "Download with Kget" from the right click menu in Konqueror there is no problem. There is no problem either if Kget is already running and I choose "Save link as". Ie. the crash only seems to happen if Kget one chooses "Save link as" and Kget is not already running.
Comment 3 David Faure 2008-09-24 15:15:35 UTC
Looks like a KUrl (or something containing it) gets deleted before it gets to the scheduler.
Any chance for a valgrind log?
Comment 4 Urs Wolfer 2008-09-24 19:29:22 UTC

*** This bug has been marked as a duplicate of bug 170869 ***