Bug 362281

Summary: Kontact and kmail share New mail shortcut
Product: [Applications] kontact Reporter: Martin van Es <bugs>
Component: mailAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: kdenis, woebbeking
Priority: NOR    
Version: 5.5.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: https://commits.kde.org/kmail/3033e8b58fe41d5911320599710b05e124e23cf6 Version Fixed In: 5.6.1
Sentry Crash Report:

Description Martin van Es 2016-04-26 08:31:46 UTC 
On a fresh Xenial installation, kmail (as part of kontact) complains about Ctrl+N being ambiguous and needs to be resolved. After long search, it turns out the ambiguity arrises from both kontact and kmail sharing Ctrl+N for "New message". This can be checked when kmail is started as separate application (Ctrl+N works). I then assigned "None" to "New message" in kontact and Ctrl+N now works like a charm in kmail (as part of kontact).

Reproducible: Always

Steps to Reproduce:
1. Fresh install of kontact
2. Open Kmail (as part of kontact)
3. Press Ctrl+N

Actual Results:  
Abiguity warning about Ctrl+N assigment

Expected Results:  
New message

Remove Ctrl+N shortcut from New message in kontact (unintuitively) resolves the problem.
Comment 1 Denis Kurz 2017-06-23 22:39:57 UTC 
This is still an issue in 5.5.2. Although I cannot test with a completely fresh configuration right now, I also get the ambiguity warning. However, the "Configure shortcuts" dialog does not show any Ctrl+N shortcuts for the Kontact. Only the KMail2 component contains the "New Mail" -> Ctrl+N shortcut. So the only way for me to resolve the conflict is to remove the shortcut from KMail, but then it wouldn't work any more in standalone KMail.
Comment 2 Daniel Vrátil 2017-08-21 17:38:03 UTC 
Git commit 3033e8b58fe41d5911320599710b05e124e23cf6 by Daniel Vrátil.
Committed on 21/08/2017 at 17:37.
Pushed by dvratil into branch 'Applications/17.08'.

Don't set KMKernel::xmlGuiInstanceName() by default

This is a porting regression - KMKernel by default should have an
invalid xmlGuiInstance, which implies that KMail is not running as
a component. When xmlGuiInstance is set, like from KMail::Part, then
we know we are running inside Kontact or similar. Before this change
xmlGuiInstance was always set by the Kernel, so code that was using
this to check if it's running inside Kontact or not did not work.

Together with a porting typo fix, this fixes the ambiguous Ctrl+N
shortcut in KMail inside Kontact.
FIXED-IN: 5.6.1

M  +0    -1    src/kmkernel.cpp
M  +1    -1    src/kmmainwidget.cpp

https://commits.kde.org/kmail/3033e8b58fe41d5911320599710b05e124e23cf6
Comment 3 Andre Woebbeking 2017-08-21 18:38:47 UTC 
Daniel you made my day :-)