https://bugs.kde.org/show_bug.cgi?id=363861
Andrew Crouthamel changed:
What|Removed |Added
Keywords||investigated, triaged
Status|NE
https://bugs.kde.org/show_bug.cgi?id=363861
RJVB changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363861
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=363861
--- Comment #4 from RJVB ---
(In reply to Kevin Funk from comment #3)
> FTR: I'm experiencing this a lot on Linux as well.
The next person to experience this should probably post a backtrace. I regret
not having done that; I didn't realise that the fun
https://bugs.kde.org/show_bug.cgi?id=363861
Kevin Funk changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |
https://bugs.kde.org/show_bug.cgi?id=363861
--- Comment #2 from RJVB ---
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
https://bugs.kde.org/show_bug.cgi?id=363861
--- Comment #1 from Milian Wolff ---
do you mean
while (currentIndex != index && currentIndex != previousIndex)
? does this fix the shutdown issue? could you recompile in debug mode to check
the state and whether this helps?
--
You are receiving thi
