Transparent Flatpak applications |KDEnlive | UI

Hello there! I’ve been a Fedora Workstation user for 2 years now. After tons of issues with Ubuntu, Fedora is like a home for me. I’ve never had any major issues (or there was an easy fix), until today.
I love editing videos in my free time. Also, I often make them for my best friend for his YouTube channel, as I don’t run my own. On Fedora, I made about 300 of them on 2 versions - 38 and 39. It was an amazig experience: I even made a use of my Intel HD Graphics 5500 chip, which made video rendering time 2 times shorter!
So, this morning, I was making a huge project in Kdenlive 24.05.2 (it automatically updates to latest stable version of Flatpak - default Fedora behaviour). Everything went well, until some bug appeared: the video timeline had a non-existing video clip (I could see it with a marker), which blocked moving of a clip before it, see an example:


I saved the project and closed the app. After that, opened it again from Activities, and it’s now… transparent. Just an empty window, which doesn’t even had a titlebar, and I could close it only from Activities. It responds as usual to this call (see GIF attachments below). Tried restarting the machine - nothing changed:

(sorry if I posted the wrong way. I’m afraid GIFs won’t play just in post, correct me if they do)
Don’t know what to do now. It only happens with KDE Qt apps, others are unaffected: flatpak list - PrivateBin
Switching to X.org is not a solution for me: most useful functions of Fedora I normally use are unavailable there, and I remember some new apps were broken.
I think the following details might clarify the issue more. The system is an HP 840 G2 laptop I’ve bought 3 years ago:

# System Details Report
---

## Report details
- **Date generated:**                              2024-07-10 12:11:21

## Hardware Information:
- **Hardware Model:**                              Hewlett-Packard HP EliteBook 840 G2
- **Memory:**                                      8.0 GiB
- **Processor:**                                   Intel® Core™ i5-5300U × 4
- **Graphics:**                                    Intel® HD Graphics 5500 (BDW GT2)
- **Disk Capacity:**                               500.1 GB

## Software Information:
- **Firmware Version:**                            M71 Ver. 01.09
- **OS Name:**                                     Fedora Linux 39 (Workstation Edition)
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               45.7
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.9.7-100.fc39.x86_64

My GNOME Tweaks window (I only changed the scaling factor to 1.25 a while back):

As I mentioned before, I initially had almost stock F38 with 3 extensions:


Never had any troubles with apps at all.
In May, I upgraded to F39 from command line using official method from Docs. The system seems to be OK.
I must also note that this isn’t the first time I encounter this annoying bug. It also happened with Falkon some time ago after the upgrade to F39. Clearing application’s settings didn’t help. How did I fix it? Just installed the RPM variant from Software, and it’s back now…
Maybe I should also mention that some person on Reddit also experienced this bug on F37 in 2022? But he had NVidia, and the window looked different: Reddit - Dive into anything
P.S. Of course I’ll try X.Org later (I’m busy RN) and will tell how it’s going there. Thanks in advance.

The error occurs when the window is maximized. Log in to the xorg session for a moment change the window so it is not full screen and close the program. Then return to wayland. Unfortunately I also have this unpleasant problem since yesterday. I don’t know what happened because I don’t think I did any update. I hope it will be fixed soon. Remember not to leave the window maximized before shutting down Kdenlive.

1 Like

Removed f37, f38, Site Help & Feedback, intel, nvidia

Hi @mikosenigma , thanks for your reply! :bluethumb:
As you saw in my post, I always use Kdenlive maximized 'cause my laptop has 14" screen, which barely fits all control buttons(
Let me clarify the steps:

  1. Log out from Wayland
  2. Log in to “GNOME on Xorg” from a menu at bottom right corner
  3. Open Kdenlive
  4. Make the window non-maximized by double clicking on the titlebar
  5. Close it
  6. Log out from Xorg
  7. Log in to Wayland again
  8. Open Kdenlive from there and it should start normally
    Is it correct? I’ve tried these steps in the ascending order, but the issue persists…
    I think I shuld make a backup of my preferences and reset the app to make it non-maximized. AS per resetting, it’s pretty straightforward - moving everything from ~/.var/<app name> folder, but what about window settings? :no_mouth:
    Anyway, will try what my intuition tells me ^^^^^^^^

I investigated the issue a bit more. As I said, I found the configuration directory. I opened a file ~/.var/app/org.kde.kdenlive/config/kdenlive-flatpakrc. There were 6 lines with Window-Maximized=true parameter. I changed each to false. After logging out and in, rebooting, it still made no change :monkey: :-1:
Even removing this file didn’t fix the error. I see it only resets window parametres, but that is seen only in Xorg…
Yesterday, I came up with idea in fully removing Flatpak version of Kdenlive and using official AppImage. I’ve tried it today - it’s practically unusable: nothing fits on my screen! I only see the project and clip monitor, library, and 1.5 tracks in timeline, not to mention the bottom panel I always use is somewhere out of vidible area…
If I run from terminal, I get nothing useful:

flatpak run org.kde.kdenlive

kf.config.core: Watching absolute paths is not supported “/usr/share/color-schemes/BreezeDark.colors”
profilePath from KdenliveSetting::mltPath: “/app/share/mlt-7/profiles”
meltPath from KdenliveSetting::meltPath: “/app/bin/melt”
plugin not available: “region”
Empty metadata for “telecide”
plugin not available: “avfilter.acompressor”
plugin not available: “avfilter.aecho”
plugin not available: “avfilter.agate”
plugin not available: “avfilter.atadenoise”
plugin not available: “avfilter.bs2b”
plugin not available: “avfilter.bwdif”
plugin not available: “avfilter.deblock”
plugin not available: “avfilter.dedot”
plugin not available: “avfilter.deflate”
plugin not available: “avfilter.derain”
plugin not available: “avfilter.doubleweave”
plugin not available: “avfilter.field”
plugin not available: “avfilter.framestep”
plugin not available: “avfilter.fspp”
plugin not available: “avfilter.graphmonitor”
plugin not available: “avfilter.hqdn3d”
plugin not available: “avfilter.inflate”
plugin not available: “avfilter.lagfun”
plugin not available: “avfilter.loudnorm”
plugin not available: “avfilter.random”
plugin not available: “avfilter.removegrain”
plugin not available: “avfilter.separatefields”
plugin not available: “avfilter.shuffleplanes”
plugin not available: “avfilter.sofalizer”
plugin not available: “avfilter.sr”
plugin not available: “avfilter.tmix”
plugin not available: “avfilter.w3fdif”
plugin not available: “avfilter.weave”
plugin not available: “avfilter.yadif”
plugin not available: “frei0r.baltan”
plugin not available: “frei0r.bgsubtract0r”
plugin not available: “frei0r.delay0r”
plugin not available: “frei0r.delaygrab”
plugin not available: “frei0r.facebl0r”
plugin not available: “frei0r.facedetect”
plugin not available: “frei0r.lightgraffiti”
plugin not available: “frei0r.lightgraffiti”
plugin not available: “frei0r.tehRoxx0r”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “ladspa”
plugin not available: “movit.blur”
plugin not available: “movit.sharpen”
plugin not available: “movit.diffusion”
plugin not available: “movit.flip”
plugin not available: “movit.glow”
plugin not available: “movit.lift_gamma_gain”
plugin not available: “movit.mirror”
plugin not available: “movit.opacity”
plugin not available: “movit.rect”
plugin not available: “movit.saturation”
plugin not available: “movit.unsharp_mask”
plugin not available: “movit.vignette”
plugin not available: “movit.white_balance”
plugin not available: “timewarp”
=== /// CANNOT ACCESS SPEECH DICTIONARIES FOLDER
begin
OpenGL vendor “Intel”
OpenGL renderer “Mesa Intel(R) HD Graphics 5500 (BDW GT2)”
OpenGL threaded? true
OpenGL ES? false
OpenGL maximum texture size = 16384
OpenGL maximum viewport size = 16384 x 16384
end
begin
OpenGL vendor “Intel”
OpenGL renderer “Mesa Intel(R) HD Graphics 5500 (BDW GT2)”
OpenGL threaded? true
OpenGL ES? false
OpenGL maximum texture size = 16384
OpenGL maximum viewport size = 16384 x 16384
end
:::: USING TRACK COMPOSITING: “frei0r.cairoblend”
:::: NOT FOUND DOCUMENT GUIDES !!!
!!!
qrc:/qml/timeline.qml:509: ReferenceError: proxy is not defined
qrc:/qml/timeline.qml:489: ReferenceError: proxy is not defined
==== NO PREVIOUS TIMELINE
::::::::::: connecting timeline: QUuid(“{0a9661f1-5256-468e-9b34-207b3b14049c}”) , DUR: 0
root context get sub model new function
HHHHHHHHHHHH
INVALID BIN PLAYLIST…
++++++++++ ININT VIEW WITH TYPE: 0
=== OPENING FILE WITH TRACKS: 5
:::: FOUND TRACTOR WITH TRACKS: 2


=== MODEL DATA CHANGED: MUTE DONE TRACK NOT FOUND!!!
:::: FOUND TRACTOR WITH TRACKS: 2


=== MODEL DATA CHANGED: MUTE DONE TRACK NOT FOUND!!!
:::: FOUND TRACTOR WITH TRACKS: 2


=== MODEL DATA CHANGED: MUTE DONE TRACK NOT FOUND!!!
:::: FOUND TRACTOR WITH TRACKS: 2


=== MODEL DATA CHANGED: MUTE DONE TRACK NOT FOUND!!!
:::: USING TRACK COMPOSITING: “frei0r.cairoblend”
===== ACTIVATING DOCUMENT: QUuid(“{0a9661f1-5256-468e-9b34-207b3b14049c}”)
::::::::::::::::::::::

For now, I see no fix in my case. It could be AppImage, but you already know what’s wrong with it for me. As per bug request, I don’t even know what I can take from my “research” to file a bug - too few information…