Bug 312860 - Tag key sequences 'ambiguous', must be un-set, saved, re-set to work
Summary: Tag key sequences 'ambiguous', must be un-set, saved, re-set to work
Status: REPORTED
Alias: None
Product: basket
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kelvie Wong
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-08 07:58 UTC by C. Andrew Warren
Modified: 2021-03-09 01:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description C. Andrew Warren 2013-01-08 07:58:29 UTC
Baskets Version 1.81
KDE Platform Version 4.9.2
Ubuntu Version 12.10

When a note is highlighted, using any Tag keyboard shortcut (Ctrl+0 through Ctrl+9) results in the following pop-up error dialog:

"The key sequence 'Ctrl+9' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered."

However, when visiting 'Configure Shortcuts' from the 'Settings' menu, no shortcuts appear with that key combination (much less more than one).

Workaround:
- Select a message with a tag (assigned via mouseclick instead of keyboard shortcut).
- Click the Tags menu -> Customize -> Select the tag you tried to use
- Delete the tag's main keyboard shortcut, then click 'OK' to save it
- Click the Tags menu -> Customize -> Select the tag you tried to use
- Set the keyboard shortcut back to what it was originally (e.g., Ctrl+3), then click 'OK' to save it
- Repeat for all tags with keyboard shortcuts (optional)
Comment 1 OmegaPhil 2015-02-20 17:26:24 UTC
I also get this fairly often, typically now I've reached investigating it, its not recreatable. When it happens again I'll see if there is a way to reproduce it.
Comment 2 Justin Zobel 2021-03-09 01:02:54 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.