Bug 332474 - Changing the shortcut from one application to another claims it would still be assigned
Summary: Changing the shortcut from one application to another claims it would still b...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-23 13:51 UTC by Ralf Jung
Modified: 2023-02-17 03:48 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 Ralf Jung 2014-03-23 13:51:45 UTC
When changing the shortcut used for one application, to be used for another application, the hot key management complains a shortcut would be assigned twice, which is wrong of course.

Reproducible: Always

Steps to Reproduce:
1. Assign Amarok the shortcut Win-Shift-A
2. Click "Save", restart KMenuEdit
3. In Amarok, delete the shortcut (with the X)
4. Assign Kopete the shortcut Win-Shift-A
5. Click "Save"
Actual Results:  
The hot key daemon (or its configuration library or something like that) complains that the shortcut would be assigned to Amarok.

Expected Results:  
It shouldn't complain.

The issue arises even if I hit "Save" between steps 3 and 4.

This is with KMenuEdit 0.9 as shipped with KDE 4.11.5.
Comment 1 Andrew Crouthamel 2018-11-11 04:35:14 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-21 04:49:28 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 Justin Zobel 2023-01-18 02:41:13 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 4 Bug Janitor Service 2023-02-02 05:01:02 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 5 Bug Janitor Service 2023-02-17 03:48:43 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!