Bug 497911 - Unable to install speech recognition tools
Summary: Unable to install speech recognition tools
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Setup & Installation (show other bugs)
Version: 24.12.0
Platform: Flatpak Linux
: HI normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2024-12-26 16:01 UTC by Cédric BRINER
Modified: 2025-01-12 14:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cédric BRINER 2024-12-26 16:01:37 UTC
Hi,

I've been trying to use flatpak (user install) for kdenlive without success. The tool keeps on telling me that it cannot access to pip3.


In Tool > Speech Recognition > Configure, I get a :
```
Cannot find pip3, please install it on your system.
If already installed, check it is installed in a directory listed in PATH environment variable
```

And when I clic on `Check Configuration`, I get this message:
```
No version information available.
```

I was not able to understand what to do to get a backtrace for it. So.. I launched it in command line with: 
`LC_ALL=C flatpak run org.kde.kdenlive`

And get a 
```
::::: CHECKING PYTHON, RQST VENV:  false
::::: CHECKING PYTHON, RQST VENV:  false
::: CHECKING DEPENDENCIES... NO VERSION INFO AVAILABLE
```
Comment 1 emohr 2025-01-09 10:53:08 UTC
We jsut updated the Flatpak recently to correct some of the
Comment 2 emohr 2025-01-09 10:55:38 UTC
We just updated the flatpak recently to correct some of the speech recognition issues.
Please try with the nightly flatpak from the download page to see if your issue is fixed: https://kdenlive.org/en/download/ (scroll down to the bottom)
Comment 3 Cédric BRINER 2025-01-12 14:15:13 UTC
Yeah, it worked !

Many thanks, from Geneva Switzerland.

Cédric BRINER
Comment 4 emohr 2025-01-12 14:47:24 UTC
Thank you for your feedback. Glad to here it works.

I close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.