https://bugs.kde.org/show_bug.cgi?id=525398
Bug ID: 525398
Summary: KDevelop keeps forgetting modules (and other)
configuration
Classification: Applications
Product: kdevelop
Version First unspecified
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Session support
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
DESCRIPTION
Almost after each KDevelop crash, or sometimes even without it, KDevelop
forgets its settings. Typically the modules settings. But I know that there are
more setting options forgotten (like re-enabled previously disabled memory
draining "Schedule all project files for parsing" in Projects tab).
STEPS TO REPRODUCE
1. Store your favorite carefully selected module configuration.
2. Forget to do rm /usr/bin/kaccess after updating plasma-desktop package, or
to type systemctl stop --user plasma-kaccess after each reboot.
3. Do that unlucky mouse move/click which crashes KDevelop
(QAccessibleEvent::accessibleInterface() const () from /usr/lib/libQt6Gui.so.6
).
4. Start KDevelop, open the module configuration window with modules tab, and
observe that all the configuration module "ballast" is enabled again.
OBSERVED RESULT
All previously disabled modules, which maybe should not be enabled by default
(like almost all of VCS modules, flatpak, docker, android support, ...), are
enabled again. And it seems that there is a new feature that uses (after a
crash automatically re-enabled) meson/ninja to build my CMake projects now.
EXPECTED RESULT
Even after a KDevelop crash, or sometimes just only after a reboot, the
configuration should be set as I left it.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.2
(The current configuration - but this behavior is there for years...)
ADDITIONAL INFORMATION
The concrete (and maybe little funny - for someone) case from today: I noticed
that my KDevelop settings are forgotten (Due to this bug I do settings checks
after each KDevelop start). Then I spent some time with setting optimizations.
Few minutes after I had to do reboot due to not loaded and missing kernel
wireguard module after system updating. So, I closed KDevelop regularly (there
was not a crash), and did the reboot. After the reboot, login, and KDevelop
starting, I did the usual configuration check. Damn! The configuration is back
to default! Then I spent some time with setting optimizations, again. First
click to the opened file and crash! Damn!!! I forgot to kill and remove
/usr/bin/kaccess!!! Why cannot it be disabled permanently?! After starting
KDevelop, again, and its configuration check, the configuration was restored to
default, again!!! After years there is finally THE time to report this bug!
--
You are receiving this mail because:
You are watching all bug changes.
