Bug 250296 - On pressing "J" KMail claims "ambiguous keyboard shortcut sequence detected"
Summary: On pressing "J" KMail claims "ambiguous keyboard shortcut sequence detected"
Status: RESOLVED DUPLICATE of bug 272155
Alias: None
Product: kmail
Classification: Unmaintained
Component: folder list (show other bugs)
Version: 1.13.5
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-05 18:36 UTC by Christoph Lange
Modified: 2011-05-01 15:13 UTC (History)
1 user (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 Christoph Lange 2010-09-05 18:36:21 UTC 
Version:           1.13.5 (using KDE 4.4.5) 
OS:                Linux

I don't recall the exact wording, but IIRC it is "ambiguous keyboard shortcut sequence detected", you will know what I mean.  So I had the keyboard focus on the list of messages in some folder, and I wanted to jump to a different folder using J.  Well, KMail claimed all of a sudden that that shortcut was ambiguous.  When I went to the "configure shortcuts" dialog, I couldn't find a duplicate, and I haven't changed anything in the configuration recently.  The only change I had made was changing to the layout "message preview right of message list" instead of "message preview below message list".  Switching back did not solve the shortcut problem.  Restarting KMail did.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
Was fixed after a restart, hasn't occurred again so far.



OS: Linux (x86_64) release 2.6.31-thinkpad
Compiler: x86_64-pc-linux-gnu-gcc
Comment 1 Davor Cubranic 2011-01-28 06:58:49 UTC 
I had a similar problem with Ctrl+C (reported in bug 264582), except that for me it happened after I changed setting for the preferred viewing format. For me restarting also fixed the error message.
Comment 2 Christophe Marin 2011-05-01 15:13:07 UTC 

*** This bug has been marked as a duplicate of bug 272155 ***