https://bugs.kde.org/show_bug.cgi?id=463497
Igor Kushnir <igor...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|NOT A BUG |---
Status|NEEDSINFO |CONFIRMED
--- Comment #3 from Igor Kushnir <igor...@gmail.com> ---
Your reply is too verbose and poorly formatted. Please reply on the bug
tracker, not via email.
(In reply to hong from comment #2)
> shutting down immediately with no warning of any kind should not be
> considered proper behavior.
That depends on your desktop environment or window manager. I see from the bug
report that you are using KDE Plasma. Plasma implements session management.
Just checked: indeed KDevelop does not support it. Such support should be added
as described here: https://doc.qt.io/qt-5/session.html. With session management
support implemented, the desktop environment will wait for KDevelop to exit
before shutting down, or ask the user whether to wait for KDevelop to exit. A
merge request that implements session management support at
https://invent.kde.org/kdevelop/kdevelop/-/merge_requests is welcome.
> why is it that only upon second attempt at starting does it offer the option
> to clear cache?
Because the dialog appears after any crash before attempting to read possibly
corrupt cache data, which may cause a crash. Without a recent crash KDevelop
doesn't expect the cache to be corrupted. Offering the option to clear the
cache at every KDevelop start would be much worse than the current behavior.
--
You are receiving this mail because:
You are watching all bug changes.
