Summary: | KTorrent crashed when I wanted to change the download directory for a new torrent | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Daniel Hahler <kde-bugzilla> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | justin.zobel, kde-bugzilla |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Daniel Hahler
2010-03-02 18:13:23 UTC
> #25 0x00f89b2a in KApplication::xErrhandler
I have no idea why this one appears in the backtrace. Why does this function call QApplication::notify() ?
Created attachment 53136 [details]
New crash information added by DrKonqi
ktorrent (4.0.3) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0
I right-clicked "Move data" this time, and KTorrent (4.0.3 from Ubuntu) crashed like before in a similar situation (when setting the download directory).
-- Backtrace (Reduced):
#7 0xb7423cce in readCheck<bool> (directory=...) at ../../kdecore/config/kconfiggroup.h:720
#8 readEntry<bool> (directory=...) at ../../kdecore/config/kconfiggroup.h:249
#9 isNative (directory=...) at ../../kio/kfile/kfiledialog.cpp:221
#10 KFileDialog::setStartDir (directory=...) at ../../kio/kfile/kfiledialog.cpp:952
#11 0x080d048b in kt::View::moveData (this=0xee85e20) at ../../ktorrent/view/view.cpp:340
> > #25 0x00f89b2a in KApplication::xErrhandler
> I have no idea why this one appears in the backtrace. Why does this function
> call QApplication::notify() ?
I do not know, maybe this is caused by some Ubuntu patch? I have submitted another crash (see above).
Now I will be using 4.0.4 backported from Debian.
Daniel, please report a new bug for KTorrent for comment #2. The backtrace is completely different from this bug. Thank you for the report, Daniel. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |