| Summary: | Cannot create activity while editing other configuration in systemsettings | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Alexander Potashev <aspotashev> |
| Component: | kcm_activities | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | ivan.cukic, kdedev |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Alexander Potashev
2025-05-04 17:39:46 UTC
Thanks for the report. I verified this behavior on git-master and it looks intentional This happens any time you have unsaved changes in one settings page and try to navigate to another setting page. There may be complications in allowing changes to one settings module while there are other changes in another module. Would it be enough to discard or save your changes to the shortcut (for example) before making other settings changes? If there is a real need for this, can you please describe the use case? Thanks. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. > Would it be enough to discard or save your changes to the shortcut (for example) before making other settings changes? Ideally, this shouldn't be required because it interrupts my workflow. One of the settings changes may be more urgent than another, for example I can imagine doing something urgently in a new activity and not wanting to spend time on finalizing shortcut settings changes that are non-urgent. There's also the aspect of human context switching which is expensive: If Plasma asks me about shortcuts, * I need to stop thinking about activities and start thinking about shortcuts * Once I'm done reviewing the shortcuts, I need to start thinking about activities and recall what I wanted to do with activities. There was probably a chain (rabbit hole) of things I was doing as "dependencies" of the original goal, creating an activity being one of them. Having to discard/save shortcuts increases the depth of the rabbit hole by one. Of course I can strictly sequence every configuration change, but that requires additional effort / brainpower / time, and may be inappropriate in situations where there's urgency. Filed https://bugs.kde.org/show_bug.cgi?id=508972 which would fix the current issue. Although the current issue can be fixed without https://bugs.kde.org/show_bug.cgi?id=508972 by providing a separate UI to an create activity that doesn't involve running System Settings. Thanks for the context. I'm going to close this out in favor of bug 508972, which captures the overall need better, in my opinion. There's no need to have two reports open to address the same thing. *** This bug has been marked as a duplicate of bug 508972 *** Like suggested in https://bugs.kde.org/show_bug.cgi?id=508972#c3, a workaround is "kcmshell6 kcm_activities". |