Bug 1886368 - kdenlive application provokes machine freeze
Summary: kdenlive application provokes machine freeze
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 32
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-08 09:49 UTC by Ken Smith
Modified: 2021-05-25 17:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2021-05-25 17:29:45 UTC
Type: Bug

Attachments (Terms of Use)

Description Ken Smith 2020-10-08 09:49:54 UTC
Description of problem:

Open application. Click on GUI. Machine freezes - power off required

Version-Release number of selected component (if applicable):

kdenlive 20.08.01


Linux localhost.localdomain 5.8.12-200.fc32.x86_64 #1 SMP Mon Sep 28 12:17:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Qt Version: 5.14 (qt5-qtbase-common-5.14.2-5.fc32.noarch)

System is i7/nVidia;  Fedora/Gnome/Wayland/Nouveau

How reproducible:

1. Open Kdenlive 20.08.1
2. Click on the Logging, Editing, Audio, Effects, Color items in the top right of the GUI
3. Wait a couple of moments 

Actual results:

Mouse movement ceases, keyboard unresponsive. Last resort - pull power

This happens of 3 different Fedora 32 installations. One on a i7/nVidia/nouveau another Core 2 Duo/Intel VGA and another on i5/Intel VGA

Expected results:

Application continues running, does not reduce the machine to inoperable state

Additional info:

This has been reported to the RPMFusion Bugzilla who determined that this looks like a Wayland issue. Starting the application under X.org is successful confirming this suspicion. (https://bugzilla.rpmfusion.org/show_bug.cgi?id=5783) 

journalctl has these kinds of messages

Oct 06 14:17:30 localhost.localdomain kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 00200000 [ILLEGAL_MTHD] ch 12 [004f042000 kdenlive[7106]] subc 0 mthd 0004 data 00000040

Oct 06 15:18:54 localhost.localdomain kdenlive[48817]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Whatever happens the machine gets eaten alive such that the mouse and keyboard cease working. In 20 years using linux I've never had a situation where the only option is to pull the power.

Comment 1 Fedora Program Management 2021-04-29 16:57:22 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 17:29:45 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.