https://bugs.kde.org/show_bug.cgi?id=505199
--- Comment #2 from Roland <carbonwer...@hotmail.com> --- I have not seen it repeat, but I will keep an eye on it. As I said- I dont think this is something that is easy to reproduce. Could speculate all day- but I put this out here just in case others have seen it. If it exists, Ill keep a closer eye on context. I realize the process not ending was a prior bug, and I dont want to convolute this report, but is the issue with the digikam process remaining active active again? If not, I can reopen it or post it again- though it is trivial to reproduce at present (i.e. close the app). Aside from the potential for contested db access etc, it prevents a simple update- since the updated stub thinks the app is still running (well, it is still running, just not with a GUI) -- You are receiving this mail because: You are watching all bug changes.
