Bug 346984 - Ambiguous shortcut for Delete & Remove when switching applications (KF5-based Kontact)
Summary: Ambiguous shortcut for Delete & Remove when switching applications (KF5-based...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 326427 345749 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-04-30 21:32 UTC by Andreas Cord-Landwehr
Modified: 2018-02-01 09:51 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Cord-Landwehr 2015-04-30 21:32:51 UTC 
When starting Kontact with KMail as default/initial application, the delete key "Del" is an ambiguous shortcut for both Delete mail and Move mail to Trash (remarkably, this is not the case when only starting KMail as standalone). Fixing the ambiguous shortcut via the shortcut configuration menu and removing the Del shortcut for Delete message, only fixes the problem temporarily.
When switching to Akregator and then switching back to KMail, the Del shortcut is ambiguous again.

Reproducible: Always
Comment 1 Simon Persson 2015-09-01 03:26:50 UTC 
*** Bug 345749 has been marked as a duplicate of this bug. ***
Comment 2 Simon Persson 2015-09-01 03:30:25 UTC 
*** Bug 326427 has been marked as a duplicate of this bug. ***
Comment 3 Denis Kurz 2017-06-23 20:16:44 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 4 Denis Kurz 2018-02-01 09:51:34 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.