I have a bug with the flatpak version of shotcut. When I try to type something in the text input field in the text:filter, the text is not entered and different key combinations work instead. But if I hold the ALT key, everything works as expected. This bug is only in this text input window. In any other windows, such as the filter search window or track renaming, text input works fine. I can’t figure out what this anomaly is related to. I reinstalled shotcut. AppImage version works fine.
I have not reproduced it on Ubuntu 24.04 when another user reported it recently. You can see if not using Wayland makes a difference. There is nothing in our code that can be changed to address this; it is Linux integration issue.
I use X11, I can’t use wayland properly in my linuxmint, because its support is only experimental there. I’ll check tomorrow how it works in a wayland session, unfortunately I didn’t think to do it today. I suspect it happened after another system update. I tried to roll back the shotcut version to an older one, it also has this bug. But I did not encounter it a week ago. Apart from shotcut, the keyboard works fine in other flatpak applications.
Rolling back to an earlier version of the KDE platform helped me.
I just entered this command sudo flatpak update --commit=25f4e90265bbf21753ddf9b5926061cd3f5c40e9298bffbc7121d041e2457d10 org.kde.Platform/x86_64/6.9
and now everything works fine for me. I’ll have to disable auto-updates and ignore KDE platform updates.
Yup, having the same issue on Fedora. Just chiming in to share another workaround: trying to ctrl+v text into the text fields doesn’t work, but if you type whatever it is you want to type in a text editor and then use ctrl+shift+v the text will paste in as expected.
I have same problem. If with cursor in the filter:simple, try to delete a letter (backspace or delete) it deletes the video itself. With submenu works fine.
Regarding Ar_D’s question: The S key in Shotcut typically splits a segment/clip in the timeline. This behavior happening unexpectedly is indeed considered a bug, as it interrupts user workflow when trying to type in the text filter.
The development team seems aware of the issue, but a definitive fix has not been implemented yet.
Let me help you find more information about this issue by searching the forum.
Search
Found 1 result for 'S key split segment bug linux category:Bug'
Regarding the S key behavior, in Shotcut, the S key is a standard keyboard shortcut for splitting a segment/clip in the timeline. This is a normal feature, not typically considered a bug. However, in this specific context, it becomes problematic because:
The keyboard shortcut is being triggered unexpectedly when users are trying to type in the text filter input field
This indicates a focus/input handling issue in the application
It’s interrupting the user’s workflow by inadvertently splitting timeline segments
The bug appears to be related to:
Keyboard input focus management
Possibly an issue with Flatpak or Linux desktop environment integration
Specifically affecting text input in the filter field
Recommended actions for the user:
Continue using the provided workarounds (ALT key, ctrl+shift+v)
Report the detailed steps to reproduce the issue on the Shotcut GitHub repository
If possible, test on different Linux distributions and desktop environments to help isolate the problem
For the most up-to-date information, users should check the Shotcut GitHub Issues page for any updates on this specific bug.
Would you like me to elaborate on any part of this explanation?
This error isn’t in Shotcut’s code, but in the QT graphical shell that Shotcut runs on. We need to wait for either the QT developer to fix the issue, or for the Shotcut developer to find a workaround. Currently, there’s only one working solution, which I described above.
Indeed, in exactly 2 years I celebrate my 50th year working almost daily with computers. But that wouldn’t have helped me with the problem at hand. If they had locked me into a prison cell with the instruction “You’ll only get out of here if you can fix the Shotcut-bug yourself,” I would have died miserably in that prison cell, despite my 50 years of computer experience. What a pity, what a shame. Especially given the fact that in my age every day has to be lived consciously in view of the possible arrival of that Grim Reaper at any time. - Many thanks for this bloody, bloody complicated one-liner debugging my problem on the top of this message.
But every remedy comes with (in this case minor) disadvantages. The "automated (preprogrammed) functions for the text-manipulation stopped now working. They are positioned above the text-input field and they hold dozens of prefabricated functions like “zoom in slowly, then move to the upper left”. If one uses these under the new (old) KDE the result is that size and color of the Font are abruptly changed and the (in my case) gigantic sized white text sticks suddenly in the upper left side of the video. But I do not use these prefabricated functions. I do not know why I checked them intuitively. There may be more aberrations to follow. But so far the main thing works again. Who is to blame for this? KDE (german developers) or the general overcomplexity of our systems? Downloading just the earlier KDE Applications Platform took mind whopping 382 Megabyte.
Once you start the system fresh, the Linux Update Manager greets you with the request to download the KDE Platform 6.9. There are certain possibilities to deal with this problem and I use more and more the chat-gpt under google to deal with this kind of problems.
Thanks to you all, especially to the Redhead Dan Demmedy, who helped me here once more in the most kind and most unburocratic way possible. Great site, this Shotcut Forum, Dan is last man standing, before everyone else will act like your terrible US-administration these days.
Humble I remain - with high respect and grateful for your help.
The problem returned. I’m at a loss. I started using Shotcut again today and it’s gone back to preventing text editing and instead is treating key strokes as commands.
I fixed the Flatpak by downgrading the runtime to use Qt 6.8.3. The Shotcut version is the same, but one can confirm the change by checking Help > About Qt.
Bug Details:
Potential Cause:
Temporary Solutions: