https://bugs.kde.org/show_bug.cgi?id=410103
--- Comment #1 from RJVB <[email protected]> --- I'm beginning to think that what happens here is that the registry/itemrepository somehow tries to write 2 different version formats to file, which leads to an open failure if there's a runtime version mismatch. The reason I think that is that I see the timestamps change on both version files (and curiously this session is the only one where that happens). ``` > CD ~/.cache/kdevduchain/ ls -l -htr kdevelop-*/{version_*,"Persistent > Declaration Table"} [...] -rw-rw-r-- 1 bertin bertin 0 Jul 22 15:43 kdevelop-{c241ebeb-91a8-4054-a7f4-ef33efe8fd99}/version_84083201 -rw-rw-r-- 1 bertin bertin 2.3M Jul 22 15:46 kdevelop-{c241ebeb-91a8-4054-a7f4-ef33efe8fd99}/Persistent Declaration Table -rw-rw-r-- 1 bertin bertin 0 Jul 22 15:46 kdevelop-{c241ebeb-91a8-4054-a7f4-ef33efe8fd99}/version_84083457 ``` It would seem that the older tag file came from the kdev-python plugin which I had NOT updated to 5.3.3 . It never occurred to me that this might be necessary, and I think users (even) less involved with KDevelop development than I will think of it even less. Would it be an idea to let the plugin disable itself if it detects that the current DUChain version is not the same as the one it was built against? Anyway, updating the plugin did NOT solve my crashing issue. -- You are receiving this mail because: You are watching all bug changes.
