Bug 313295 - Activity performed, although whole part was cancelled
Summary: Activity performed, although whole part was cancelled
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: shortcuts (show other bugs)
Version: 4.9.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-15 13:32 UTC by Axel Braun
Modified: 2023-01-08 16:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2013-01-15 13:32:35 UTC
Please have a look at https://bugs.kde.org/show_bug.cgi?id=313231

In the configuration dialog for keyboard shortcuts, one key was assigned twice after a system upgrade.
For both keys it says it is the Standard-Assignment. So go to settings -> keyboard shortcuts First problem: the assignment cant be deleted (as it is the standard scheme). So I have chosen to delete the standard assignment. This was unfortunately not only done for the selected shortcuts ('del' in the selection bar on top), but for all shortcuts. Second problem: When cancelling the whole activity ('Cancel' in the menu bar) the activity is not reverted - all keyboard shortcuts are removed. 

According to the KMail developer this is an issue of the KDE-libs

Reproducible: Always

Steps to Reproduce:
1. delete keyboard shortcuts
2. 'Cancel' the whole activity
3. Shortcuts removed anyway
Actual Results:  
See above

Expected Results:  
The whole transaction / activity is cancelled and in the state as before.
Comment 1 Andrew Crouthamel 2018-11-09 00:53:26 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-18 03:31:40 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Axel Braun 2018-11-18 10:05:27 UTC
Checked this on KMail 5.7.3 (openSUSE Leap 15), issue is still persistent.
Comment 4 Justin Zobel 2022-12-23 00:28:32 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Axel Braun 2022-12-23 14:48:25 UTC
Can I wait with the reply to the 10 years anniversary of this bug?
Comment 6 Bug Janitor Service 2023-01-07 05:22:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Axel Braun 2023-01-08 16:44:52 UTC
Tested on Operating System: openSUSE Tumbleweed 20230106
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7

and......bug seems to be gone! when I change a shortcut and cancel the activity, the shortcut is *not* activated. Thats expected behaviour.

After nearly 10 years, I set this to WFM