Bug 426525

Summary:	Key sequences ambiguous by default
Product:	[Applications] kdevelop	Reporter:	ypugach <pugach.yaroslav2>
Component:	UI: general	Assignee:	kdevelop-bugs-null
Status:	REPORTED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	5.6.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Error message

Description ypugach 2020-09-14 15:12:30 UTC

Created attachment 131641 [details]
Error message

SUMMARY

KDevelop AppImage reports a lot of ambiguous key sequences when installed as is.


STEPS TO REPRODUCE
1. Follow the official guide to download and run KDevelop:

{{Output|1=<nowiki>
wget -O KDevelop.AppImage https://download.kde.org/stable/kdevelop/5.6.0/bin/linux/KDevelop-5.6.0-x86_64.AppImage
chmod +x KDevelop.AppImage
./KDevelop.AppImage
</nowiki>}}

2. Open a project, set a breakpoint, and run debug launch.

3. Hit F10 to step over. 


OBSERVED RESULT

The message pops up saying
<blockquote>
The key sequence 'F10' is ambiguous. Use 'Configure Shortcuts'
from the 'Settings' menu to solve the ambiguity.
No action will be triggered.
</blockquote>

See the screenshot attached.

EXPECTED RESULT

The instruction pointer moving to the next code line.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Going to keyboard shortcut configuration and searching for F10 key proves that the key is indeed ambiguous. By default it has been assigned to Dynamic Word Wrap (Kate Part) and Step Over (Debugger). Sure, I can change the key, but isn't it supposed to work right out of the box? Moreover, there are many other keys which bring about the same issue.