Bug 435264 - Nie działa edycja jpg i wav
Summary: Nie działa edycja jpg i wav
Status: RESOLVED NOT A BUG
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 20.04.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-02 13:02 UTC by jarek
Modified: 2021-04-06 12:21 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jarek 2021-04-02 13:02:06 UTC 
SUMMARY
w "ustawienia>ustawienia kdenlive > środowisko > domyślne programy > edytowanie obrazów > digikam" -nie otwiera digikam
To samo jest w "ustawienia>ustawienia kdenlive > środowisko > domyślne programy > edytowanie dźwięku > Audacity" -nie otwiera Audacity
Nie działa też edycja wycinków *.jpg i *.wav

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS 
Linux 5.4.0-71 64bit/Kubuntu20.04.2LTS/KDE Plasma
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version:5.68.0 
Qt Version: 5.12.8

ADDITIONAL INFORMATION
w wersji kdenlive 19.12 szystko OK. Wersja 19 usunięta z systemu przed instalacją kdenlive 20.04
Comment 1 Julius Künzel 2021-04-04 13:27:36 UTC 
Thanks for your report! Is it possible for you to translate to English?
Comment 2 jarek 2021-04-06 10:26:06 UTC 
In "settings> kdenlive settings> environment> default programs> image editing> digikam" -not open digikam
The same is in "settings> kdenlive settings> environment> default programs> audio editing> Audacity" - does not open Audacity
Editing of * .jpg and * .wav clippings also does not work
Comment 3 jarek 2021-04-06 11:12:49 UTC 
Everything cleared up. You had to enter the appropriate paths.
I'm sorry to take your time.
Comment 4 jarek 2021-04-06 11:24:47 UTC 
Please close bug
Comment 5 Julius Künzel 2021-04-06 12:21:19 UTC 
Thanks for your response! You closed the bug already yourself by setting it to RESOLVED > NOT A BUG

(In reply to jarek from comment #3)
> Everything cleared up. You had to enter the appropriate paths.
> I'm sorry to take your time.

Personally I like it much more if you report a "wrong bug" but feel in general responsible to report bugs, than not reporting any bugs :-)