Created attachment 129216 [details] Video in a separate window (Everything KDE from git master on openSUSE Tumbleweed) I had this problem on my old laptop and was hoping it would go away with the new one, but it did not. When I open Kamoso, the main window displays nothing where the video should be, and instead the video appears in a second window! It's very weird. See the attached screenshot.
omg... -.- Can you try if you have the same problem with the flatpak version?
The Flatpak version from the kdeapps repo does not run due to what appears to be a packaging/runtime error: fpatpak run org.kde.kamoso If 'fpatpak' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf fpatpak nate@Liberator:~/kde/src/plasma-pa$ (work/ngraham/filter-out-useless-devices) flatpak run org.kde.kamoso (kamoso:2): GLib-GObject-CRITICAL **: 18:14:38.216: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed (kamoso:2): GLib-GObject-CRITICAL **: 18:14:38.216: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed new device "" "" "/dev/video2" Playing device changed "/dev/video2" (kamoso:2): GLib-GObject-CRITICAL **: 18:14:38.216: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed (kamoso:2): GLib-GObject-CRITICAL **: 18:14:38.216: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed new device "" "" "/dev/video0" qrc:/qml/Mode.qml:5:28: Invalid property assignment: string expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt. QQmlApplicationEngine failed to load component qrc:/qml/Main.qml:137:22: Type ImagesView unavailable qrc:/qml/ImagesView.qml:29:17: Type Kirigami.Heading unavailable file:///usr/lib/qml/org/kde/kirigami.2/Heading.qml:37:1: Type QQC2.Label unavailable file:///home/nate/kde/usr/lib64/qml/QtQuick/Controls.2/org.kde.desktop/Label.qml:11:1: module "QtQuick.Templates" version 2.15 is not installed
Can't reproduce ever since upgrading to Fedora. Since you can't reproduce it either, I guess there is no way to debug this, so I'll close it now.