https://bugs.kde.org/show_bug.cgi?id=459108
--- Comment #5 from Oded Arbel <o...@geek.co.il> --- The problem appears to me to have been introduced in this commit: https://invent.kde.org/utilities/kate/-/commit/1b93ede0e09fcc5ef069cf5c3be33e914c660162#1d89091b7718b0df550ed065e31436f1fab5217c_1112_1123 where the new code for KateMDI::Sidebar::saveSession assumes (without checking) that all items in the tab bar are already initialized tool views, but the problem is that the KateFileBrowser tool view - when it can't immediately identify the location from its configuration as a valid folder - starts a KIO stat job, which takes time to complete - and calls into the QEventLoop. The event loop may cause the SMC save_yourself API to be called to save the current session state - calling on KateMDI::Sidebar::saveSession to save the state of a partially initialized sidebar. I believe more error checking all around would be useful, but maybe the correct fix here would be for KateFileBrowser to not set the KUrlNavigator to the configured location until a later time, as that operation has a lot of side effects that should not delay the plugin loading. -- You are receiving this mail because: You are watching all bug changes.
