https://bugs.kde.org/show_bug.cgi?id=510925
--- Comment #8 from Nicolas Fella <[email protected]> --- (In reply to Vangelis from comment #5) > > This isn't related to https://bugs.kde.org/show_bug.cgi?id=389441 > > It isn't, but also it is somehow. I'm fine with keeping it as an independent > bug though. > > What led two unrelated systems to get into this state after the upgrade to > KDE Neon with KDE 6.5.0 is potentially one issue. > > But once we got there, I think the main and even bigger issue is that > "kactivitymanagerd does not handle DB corruption properly". It shouldn't > render the system unusable, and if it did, it should happen in a more > graceful way with a pointer towards a resolution. The even bigger issue here > is that even a system re-installation wouldn't help as long as the user > doesn't start from a clean state and get rid of the corrupted DB.. What makes you think this issue has anything to do with database corruption? -- You are receiving this mail because: You are watching all bug changes.
