https://bugs.kde.org/show_bug.cgi?id=363861
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Yes, I meant something like that. I added a patch at the end of the loop that's
a bit more of a hack
if(currentIndex == previousIndex){
currentIndex = index;
}
That did not immediately resolve the hang, so I added a qDebug statement to
follow index and currentIndex.
Believe it or not, after that the session has been exiting correctly, without
currentIndex ever getting stuck on a fixed value.
Don't you just love Heisenbugs ...
I'm leaving in that print-out, in case the issue ever returns.
Can this have been related to a corrupt cache? Or is whatever this class does
in any way related to data returned from KIO's ioslaves or other components?
--
You are receiving this mail because:
You are watching all bug changes.
