https://bugs.kde.org/show_bug.cgi?id=410103
RJVB <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from RJVB <[email protected]> --- Turns out this was a false alarm, it just took me way too long to get the idea to check who was using libKDevPlatformSerialisation. Sure enough I had a not-so-zombie KDevelop 5.3.2 process running which I thought I had quit before logging off (the 1st time after upgrading to 5.60.0). My issues started after logging in. Two things would probably have helped me think of this sooner: - using the hex version number in the version file, so I'd have seen an unexpected version_5030201 file. - storing the application PID in the file instead of keeping it empty. It's been a (potentially) interesting "experiment" though that has shown that the session can survive unexpected "failed to open registry" errors, i.e. that an immediate abort isn't required. -- You are receiving this mail because: You are watching all bug changes.
