Bug 122587

Description of the crash? How to reproduce? Any additional info than a 
backtrace?

kget 0.8.5, latest ubuntu version i am downloading 4 files:
http://www.gentoo-es.org/~ferdy/bash1.avi
http://www.gentoo-es.org/~ferdy/bash2.avi
http://mirror.espri.arizona.edu/gentoo//releases/x86/2005.1/installcd/install-x86-universal-2005.1.iso
http://gentoo.ussg.indiana.edu//releases/x86/2005.1/packagecd/packages-x86-2005.1.iso
I just put the four to download and then start/stop/resume then randomly and the after some seconds doing that crashes, since I am not a developer I cannot provide you more technical info. Maybe KDE should improve their backtrace-management in order not to use the users as co-developers.

With the newer version I did not have any problems, now seems to work.

Closed.

I can still reproduce this bug (using current KDE 3.5.5/KGet 0.8.5 packages in Debian Sid) doing the steps given in comment 2. Reopening and confirming.

Here's a more complete backtrace with line numbers:

(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 -1209104704 (LWP 7442)]
[New Thread -1223320656 (LWP 29499)]
[New Thread -1214927952 (LWP 29303)]
[KCrash handler]
#9  0x4364162b in KIO::Slave::resume (this=0x825cb30)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slave.cpp:266
#10 0x4364189b in KIO::TransferJob::resume (this=0x827f318)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:1099
#11 0x436a0740 in KIO::FileCopyJob::slotData (this=0x8258340, 
    data=@0xbff33900)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:1812
#12 0x436b6363 in KIO::FileCopyJob::qt_invoke (this=0x8258340, _id=7, 
    _o=0xbff33600) at ./jobclasses.moc:1556
#13 0x42b01253 in QObject::activate_signal (this=0x82badc8, clist=0x82d4eb8, 
    o=0xbff33600) at kernel/qobject.cpp:2356
#14 0x4364f73d in KIO::TransferJob::data (this=0x82badc8, t0=0x82badc8, 
    t1=@0xbff33900) at ./jobclasses.moc:993
#15 0x4364f7c8 in KIO::TransferJob::slotData (this=0x82badc8, 
    _data=@0xbff33900)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/job.cpp:906
#16 0x4368ce19 in KIO::TransferJob::qt_invoke (this=0x82badc8, _id=18, 
    _o=0xbff336f4) at ./jobclasses.moc:1072
#17 0x42b01253 in QObject::activate_signal (this=0x82c53a0, clist=0x825ccf0, 
    o=0xbff336f4) at kernel/qobject.cpp:2356
#18 0x4364be7e in KIO::SlaveInterface::data (this=0x82c53a0, t0=@0xbff33900)
    at ./slaveinterface.moc:194
#19 0x436acb42 in KIO::SlaveInterface::dispatch (this=0x82c53a0, _cmd=100, 
    rawdata=@0xbff33900)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slaveinterface.cpp:234
#20 0x436aaed8 in KIO::SlaveInterface::dispatch (this=0x82c53a0)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slaveinterface.cpp:173
#21 0x4365bfab in KIO::Slave::gotInput (this=0x82c53a0)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kio/kio/slave.cpp:300
#22 0x4369aa60 in KIO::Slave::qt_invoke (this=0x82c53a0, _id=4, _o=0xbff33a28)
    at ./slave.moc:113
#23 0x42b01253 in QObject::activate_signal (this=0x82bea60, clist=0x82a7e20, 
    o=0xbff33a28) at kernel/qobject.cpp:2356
#24 0x42b01b5a in QObject::activate_signal (this=0x82bea60, signal=2, 
    param=18) at kernel/qobject.cpp:2449
#25 0x42e8b027 in QSocketNotifier::activated (this=0x82bea60, t0=18)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#26 0x42b239fe in QSocketNotifier::event (this=0x82bea60, e=0xbff33d80)
    at kernel/qsocketnotifier.cpp:258
#27 0x42a99176 in QApplication::internalNotify (this=0xbff34000, 
    receiver=0x82bea60, e=0xbff33d80) at kernel/qapplication.cpp:2635
#28 0x42a9af93 in QApplication::notify (this=0xbff34000, receiver=0x82bea60, 
    e=0xbff33d80) at kernel/qapplication.cpp:2358
#29 0x4319af8e in KApplication::notify (this=0xbff34000, receiver=0x82bea60, 
    event=0xbff33d80)
    at /home/ana/Debian/kdelibs/kdelibs-3.5.5a.dfsg.1/./kdecore/kapplication.cpp:550
#30 0x42a2c971 in QApplication::sendEvent (receiver=0x82bea60, 
    event=0xbff33d80) at ../include/qapplication.h:520
#31 0x42a8b529 in QEventLoop::activateSocketNotifiers (this=0x8169c88)
    at kernel/qeventloop_unix.cpp:578
#32 0x42a40ca4 in QEventLoop::processEvents (this=0x8169c88, flags=4)
    at kernel/qeventloop_x11.cpp:383
#33 0x42ab36c9 in QEventLoop::enterLoop (this=0x8169c88)
    at kernel/qeventloop.cpp:198
#34 0x42ab34ea in QEventLoop::exec (this=0x8169c88)
    at kernel/qeventloop.cpp:145
#35 0x42a9ad0f in QApplication::exec (this=0xbff34000)
    at kernel/qapplication.cpp:2758
#36 0x08062908 in ?? ()
#37 0xbff34000 in ?? ()
#38 0x00000001 in ?? ()
#39 0x00000001 in ?? ()
#40 0x00000000 in ?? ()

*** Bug 134598 has been marked as a duplicate of this bug. ***

*** Bug 137885 has been marked as a duplicate of this bug. ***

*** Bug 138258 has been marked as a duplicate of this bug. ***

Created attachment 19107 [details]
kget backtrace after pausing some files

It happens nearly every time I pause more than one download. Sometimes it
happens with one download or with the delay function too.
I am using Kubuntu Edgy but same happens in Dapper too.

*** Bug 137879 has been marked as a duplicate of this bug. ***

*** Bug 134592 has been marked as a duplicate of this bug. ***

Due to the move from the make_kget_cool branch back into kdenetwork, this issue has been resolved.

For more details about the new KGet please have a look at this page (1st article):
http://commit-digest.org/issues/2007-02-25/

The article listed above as the "resolution" does not link any type of fix for this problem that I can see at the present time. It discusses a future release of kget with KDE 4.

Is there an actual fix for this problem in KDE 3.5.5? If so, then kindly post a link to the files so that we can download the fix? Any updates I've done on opensuse 10.2 have NOT resolved this problem. Is there source code or a package that actually fixes this problem now?

Thanks.

It will be fixed with KDE 4.0. There is no fix for the KDE 3.5.x. available.
Please be patience! ;)

*** Bug 150919 has been marked as a duplicate of this bug. ***

I can confirm this bug too.

KDE Version  v0.8.5 (KDE 3.5.9, Debian Package 4:3.5.9.dfsg.1-4 (lenny/sid))

[KCrash handler]
#6  0x4d18baab in KIO::Slave::resume () from /usr/lib/libkio.so.4
#7  0x4d18bd5b in KIO::TransferJob::resume () from /usr/lib/libkio.so.4
#8  0x4d1dbc60 in KIO::FileCopyJob::slotData () from /usr/lib/libkio.so.4
#9  0x4d1f4101 in KIO::FileCopyJob::qt_invoke () from /usr/lib/libkio.so.4
#10 0x4e60c4cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x4d197fdd in KIO::TransferJob::data () from /usr/lib/libkio.so.4
#12 0x4d198048 in KIO::TransferJob::slotData () from /usr/lib/libkio.so.4
#13 0x4d1df619 in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4
#14 0x4e60c4cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0x4d1963be in KIO::SlaveInterface::data () from /usr/lib/libkio.so.4
#16 0x4d1dee49 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#17 0x4d200dba in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#18 0x4d1a7e7c in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#19 0x4d1d6238 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#20 0x4e60c4cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0x4e60cf50 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#22 0x4e9373b0 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#23 0x4e629f60 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#24 0x4e5ae6ea in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#25 0x4e5af4d6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#26 0x4c8bf062 in KApplication::notify () from /usr/lib/libkdecore.so.4
#27 0x4e5a2fa7 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#28 0x4e55d730 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#29 0x4e5c50e0 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#30 0x4e5c4f76 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#31 0x4e5ae25f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#32 0x08063fa0 in ?? ()
#33 0xbff18f70 in ?? ()
#34 0x00000001 in ?? ()
#35 0x00000001 in ?? ()
#36 0x00000000 in ?? ()

On Monday 05 May 2008 9:11:02 pm Oleg Atamanenko wrote:
[bugs.kde.org quoted mail]

Hi
note that your enviroment are mixing qt3 and qt4 libraries

>#9  0x4d1f4101 in KIO::FileCopyJob::qt_invoke () from /usr/lib/libkio.so.4
> #10 0x4e60c4cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #11 0x4d197fdd in KIO::TransferJob::data () from /usr/lib/libkio.so.4
> #12 0x4d198048 in KIO::TransferJob::slotData () from /usr/lib/libkio.so.4
> #13 0x4d1df619 in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4
> #14 0x4e60c4cd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> 


please fix that and let us know

cheers
Manolito

> _______________________________________________
> Kget mailing list
> Kget@kde.org
> https://mail.kde.org/mailman/listinfo/kget

On Thursday 08 May 2008 3:48:13 pm Manolo Valdes wrote:
[bugs.kde.org quoted mail]

sorry i guess you are using kde3 and the old kget implementation

just forget the noise

cheers
Manolito

On Thursday 08 May 2008 22:48:14 Manolo Valdes wrote:
[bugs.kde.org quoted mail]

This one has been around a while. When I first reported it, there might not 
have been a qt4?

Kget for kde3 has been working reliably. The crash was occasional and not 
recently frequent. Kget for kde4 crashes on startup and is unusable.

Since both library sets reside on /usr/lib, it would seem quite difficult to 
sort the above load library out.

I have the following (Debian Sid):
~$ ls -l /usr/lib/libqt-mt.so*
lrwxrwxrwx 1 root root      17 2008-03-24 18:30 /usr/lib/libqt-mt.so -> 
libqt-mt.so.3.3.8
lrwxrwxrwx 1 root root      17 2008-03-24 18:30 /usr/lib/libqt-mt.so.3 -> 
libqt-mt.so.3.3.8
lrwxrwxrwx 1 root root      17 2008-03-24 18:30 /usr/lib/libqt-mt.so.3.3 
->libqt-mt.so.3.3.8
-rw-r--r-- 1 root root 7291708 2008-03-11 00:07 /usr/lib/libqt-mt.so.3.3.8

This I assume is qt3 since I have similar sos on a konstructed $KDEDIR/lib

~$ ls -l /usr/lib/libkio.so*
lrwxrwxrwx 1 root root      11 2008-05-01 17:17 /usr/lib/libkio.so -> 
libkio.so.5
lrwxrwxrwx 1 root root      15 2008-05-01 17:18 /usr/lib/libkio.so.5 -> 
libkio.so.5.1.0
-rw-r--r-- 1 root root 2563004 2008-04-30 21:18 /usr/lib/libkio.so.5.1.0

These, I might assume are qt4 but may not be. I have ones with so.4 suffixes 
on the konstructed $KDEDIR/lib. There is apparently NO libqt4-mt. This all 
would seem to indicate the the above traceback is NOT mixing qt3 and qt4! 

When I run kde3, the LD_LIBRARY_PATH checks the konstructed $KDEDIR/lib 
FIRST--has to use these because of something in kde3.* dealing with version 
numbers.
When I run kde4, this  library path would be at the END.
Looks like the qt4 libs are stored and accessed differently, at least in 
Debian installations, with no explicit sos in /usr/lib at all.

l