Bug 288202 - Components under Kontact forget custom keyboard shortcuts when switching between components
Summary: Components under Kontact forget custom keyboard shortcuts when switching betw...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: Gentoo Packages Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-04 14:08 UTC by Thomas Fischer
Modified: 2017-01-07 22:25 UTC (History)
0 users

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 Thomas Fischer 2011-12-04 14:08:15 UTC
Version:           4.7.2 (using KDE 4.7.3) 
OS:                Linux

Most components (KMail, Contacts, ...) allow to configure keyboard shortcuts via Settings -> Configure Shortcuts. Settings made there, however, seem only last as long as one does not switch to another component, e.g. from KMail to Contacts.
For example, take an action that has no shortcut yet, such as "Mark Mail as Read", and assign Ctrl+R to it. Close dialog with "OK" and onfirm that the keyboard shortcut is working on a real email. Switch to Feeds (aKregator) or Contacts and switch immediately back to Mail. Go to the keyboard settings dialog: the configured shortcut is gone.
The same problem exist for keyboard shortcuts configured in other components as well, such as Contacts. It looks like a problem more general to Kontact and how components are handled than a KMail-specific problem.

Reproducible: Always

Steps to Reproduce:
Steps to Reproduce: see above description

Actual Results:  
Actual Results: see above description

Expected Results:  
Actual Results: see above description

Kontact 4.7.3, which wasn't in the list of available versions to choose from.
Comment 1 Denis Kurz 2016-09-24 19:34:26 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:25:28 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.