Bug 407193 - Cursor stops working after setting render threads higher than one
Summary: Cursor stops working after setting render threads higher than one
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 19.04.0
Platform: Mint (Ubuntu based) Linux
: NOR critical
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-03 19:56 UTC by matteo.magnoni.majo
Modified: 2019-06-03 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: Translation_missing+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matteo.magnoni.majo 2019-05-03 19:56:22 UTC
After setting the render threads to six(I have an i5-8400), the cursor stopped working. After hours of trail and error I stumbled on a forum where a guy discovered that the problem lied with the render threads. After setting them back to one the cursor started working again(the problem and the fix got reproduced on a laptop with the latest version of Manjaro)

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Linux Mint 19.1 Cinnamon(kernel version: 5.0)
Comment 1 emohr 2019-05-04 18:12:12 UTC
Environment settings: set processing threads to 1. Multithreading is not possible at the moment. 

Render -> tick “parallel processing” -> tick “more options” -> on the right side set threads to “0”. This is the fastest render setting.

If you have problem with the rendered video untick “parallel processing”.
Comment 2 Bug Janitor Service 2019-05-19 04:33:07 UTC
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!
Comment 3 Bug Janitor Service 2019-06-03 04:33:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!