Bug 173961 - crash if cancelling the "similar file exists" dialog
Summary: crash if cancelling the "similar file exists" dialog
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: SVN
Platform: Compiled Sources Unspecified
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-31 11:34 UTC by Frederik Schwarzer
Modified: 2009-01-26 00:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frederik Schwarzer 2008-10-31 11:34:43 UTC
Version:            (using Devel)
Installed from:    Compiled sources

I tried downloading a file which was already downloading (there were two links to the same file in a feed).
I then cancelled the dialog that said there would be a "similar file"
with that name already.
The app crashed with the followin backtrace:
Application: Akregator (akregator), signal SIGSEGV

Thread 1 (Thread 0xb49de740 (LWP 2362)):
[KCrash Handler]
#6  0x08c61363 in ?? ()
#7  0xb70a55fe in ~KCompositeJobPrivate (this=0x8672930) at /usr/include/qt4/QtCore/qalgorithms.h:346
#8  0xb7662203 in ~FileCopyJobPrivate (this=0x8672930) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job_p.h:35
#9  0xb70a65a4 in ~KJob (this=0x8973098) at /home/compiler/kde/src/KDE/kdelibs/kdecore/jobs/kjob.cpp:69
#10 0xb70a53b8 in ~KCompositeJob (this=0x8973098) at /home/compiler/kde/src/KDE/kdelibs/kdecore/jobs/kcompositejob.cpp:44
#11 0xb7651798 in ~Job (this=0x8973098) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job.cpp:97
#12 0xb76517cd in ~FileCopyJob (this=0x8973098) at /home/compiler/kde/src/KDE/kdelibs/kio/kio/job.cpp:1820
#13 0xb6e70f5c in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4
#14 0xb6e72913 in QObject::event () from /usr/lib/libQtCore.so.4
#15 0xb63af79c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb63b761e in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb73d7c9d in KApplication::notify (this=0xbf98e640, receiver=0x8973098, event=0x8bc6c98) at /home/compiler/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#18 0xb6e630d1 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#19 0xb6e63d55 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#20 0xb6e63f4d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#21 0xb6449e3f in ?? () from /usr/lib/libQtGui.so.4
#22 0xb6e6179a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#23 0xb6e6195a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#24 0xb6e64015 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#25 0xb63af617 in QApplication::exec () from /usr/lib/libQtGui.so.4
#26 0x0804ed21 in main (argc=) at /home/compiler/kde/src/KDE/kdepim/akregator/src/main.cpp:115
Comment 1 Frank Osterfeld 2008-10-31 11:47:57 UTC
Is that reproducible in Konqueror, too?
Comment 2 Frederik Schwarzer 2008-10-31 12:04:20 UTC
No.
The problem only occured with the "similar file exists" message. If I try to
repeat it in Akregator with the file already completely downloaded ("older file exists"), it does not crash. The "similar file exists" crash however is reproducable for me every time.
If I try to download the same file twice while still downloading the first instance, konqueror just dowanloads the file twice without saying anything.
Only if the second instance is finished there is an error message:
"Could not rename partial file %filename. Please check permissions."

So the two apps seem to handle this thing differently.
Comment 3 Dario Andres 2009-01-24 18:57:17 UTC
What KDE version (SVN revision) were you using?
The backtrace looks like the one in bug 162285 , but it should be fixed a while ago.
Comment 4 Frederik Schwarzer 2009-01-24 23:04:20 UTC
Hmm... now in r915510 from 4.2 branch the bahviour seems to be more like in Konqueror. The file is just downloaded twice and the download that finishes second gives an error.
No idea where the "Similar File Exists" dialog came from and where it is used now.
Comment 5 Frank Osterfeld 2009-01-26 00:13:49 UTC
So can we close this report?
Comment 6 Dario Andres 2009-01-26 00:40:42 UTC
As the original bug (crash) is no longer there, we can close the report. However the report may want to file a new bug report for the current behaviour