Summary: | Kget crashed when changing a download's destination folder (folder is mounted on windows 7 dual boot partition) | ||
---|---|---|---|
Product: | [Applications] kget | Reporter: | Juan <juan.seo> |
Component: | general | Assignee: | KGet authors <kget> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | joris.guisson, ponchorat1968 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Juan
2012-06-12 06:24:19 UTC
This looks like a crash in libktorrent. Joris, can you look at this? Lukas The torrent pointer of the BTTransfer object is most likely 0, judging by the address of the string object in the isEmpty call. Created attachment 97037 [details]
New crash information added by DrKonqi
kget (2.14.13) on KDE Platform 4.14.13 using Qt 4.8.6
- What I was doing when the application crashed:
Selected some downloads that had stopped and was reporting themselves to not be able to be downloaded due to no torrent being found.
I had previously changed the download location and then rebooted.
I selected a new location and then KGet crashed.
-- Backtrace (Reduced):
#6 isEmpty (this=0x90) at /usr/include/qt4/QtCore/qstring.h:705
#7 KUrl::addPath (this=0x7ffdf01e4340, _txt=...) at ../../kdecore/io/kurl.cpp:1357
[...]
#11 0x00007fd6314e6d0d in KDialog::slotButtonClicked (this=0x2a96290, button=4) at ../../kdeui/dialogs/kdialog.cpp:885
#12 0x00007fd6314e857f in KDialog::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kdialog.moc:166
[...]
#14 0x00007fd62f266fbe in QSignalMapper::mapped (this=this@entry=0x2b0dd70, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:114
Created attachment 97038 [details]
New crash information added by DrKonqi
kget (2.14.13) on KDE Platform 4.14.13 using Qt 4.8.6
- What I was doing when the application crashed:
Selected some downloads that had stopped and was reporting themselves to not be able to be downloaded due to no torrent being found.
I had previously changed the download location and then rebooted.
I selected a new location and then KGet crashed.
-- Backtrace (Reduced):
#6 isEmpty (this=0x90) at /usr/include/qt4/QtCore/qstring.h:705
#7 KUrl::addPath (this=0x7ffdf01e4340, _txt=...) at ../../kdecore/io/kurl.cpp:1357
[...]
#11 0x00007fd6314e6d0d in KDialog::slotButtonClicked (this=0x2a96290, button=4) at ../../kdeui/dialogs/kdialog.cpp:885
#12 0x00007fd6314e857f in KDialog::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at ./kdialog.moc:166
[...]
#14 0x00007fd62f266fbe in QSignalMapper::mapped (this=this@entry=0x2b0dd70, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:114
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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! |