SUMMARY On the Russian keyboard shortcuts do not work. This greatly slows down the workflow when placing markers to which meaningful names should be given. You have to switch to the English layout to make a marker, then to Russian to enter a name, then again to English. SOFTWARE/OS VERSIONS Ubuntu Studio 19.10 x64 Kdenlive from appimage 20.04.0b KDE Frameworks 5.68.0 Qt 5.14.1 (built against 5.14.1) The xcb windowing system
Today it works fine on both layouts - in Russian and in English ... I didn’t do any settings, neither in kdenlive nor in the OS. I will observe further behavior.
It seems the following pattern: if I launch kdenlive on two monitors and open the clip monitor window on a separate monitor in full screen, then with the active clip monitor window Shift + M does not work on the Russian layout but works on the English one. If you click once on the main window of the kdenlive, that is, make it active and not the clip monitor, then the hot keys on both layouts will work. If you do not initially use a second monitor, it works on both layouts. (Shift + M is adding marker. I don’t remember - this is a standard key or I assigned it myself.)
Shift + M is not a standard shortkey. The standard shortkey to add markers and guides s is “*” on the numpad. Please try again with this shortcut to check if it is working.
I don't know whether it is the same bug or not, but the Ctrl+S shortcut works only when in English on Windows 10.
Which keyboard layout is your normal one?
(In reply to emohr from comment #5) > Which keyboard layout is your normal one? My keyboard layouts are English QWERTY and Hebrew.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Hi and thank you for your patience. Can you please check whether this issue still exists in the latest version 24.12.0? If yes, please update this report to reflect the new version. If it works now like you expect it would, you may change the status of this report to RESOLVED - FIXED. At any rate, this report will be closed if there is no activity for the next 30 days.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.