Summary: | hang in function Konversation::DCC::TransferRecv::createDirs 396 KIO Job exec | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | Zhang Jingqiang <zh_jq> |
Component: | dcc | Assignee: | Bernd Buschinski <b.buschinski> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andrew.crouthamel, konversation-devel |
Priority: | NOR | ||
Version: | 1.6 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Zhang Jingqiang
2016-10-22 03:18:24 UTC
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! (In reply to Andrew Crouthamel from comment #1) > 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! Yes, but it's not a 100% loop, sorry for the privious (maybe) wrong info. It is reproducible by adding 5 downloadings, then adding another one, then konversation GUI freeze. After anyone of the 5 downloading ends, then the new one will be started to save to disk (through kio, I guess), but the connection is already timeout. The freeze seems to be happening during adding kio jobs, which seems to be blocked. I guess there is some limit on number of KIO jobs for each application. And after anyone of the 5 downloading jobs finish, there will be 3 job finish notifications, which seems to be: 1. stat for /home 2. stat for /home 3. stat for /home/<username> So where is blocked is inside KIO stat function. Thanks for the update! Thank you for the crash report. 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! |