https://bugs.kde.org/show_bug.cgi?id=397724
Bug ID: 397724
Summary: Wayland is not used, even if available
Product: flatpak-platform-plugin
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: m...@rainer-finke.de
Target Milestone: ---
Today I installed via the KDE flatpak testing repository Falkon (master).
Falkon does start on Plasma Wayland only via XWayland. I've tested the normal
Falkon package in ArchLinux on Wayland and it works great. Is Wayland support
missing in the flatpak backend? Flatpak wants to offer additional security via
sandboxing, but this doesn't make sense to me if then xcb is used anyway.
flatpak run org.kde.falkon --platform=wayland
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even
though it was found.
[3:3:0821/232145.470805:INFO:zygote_host_impl_linux.cc(126)] No usable sandbox!
Update your kernel or see
https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md
for more information on developing with the SUID sandbox. If you want to live
dangerously and need an immediate workaround, you can try using --no-sandbox.
Falkon: 2 extensions loaded
Couldn't start kwalletd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown",
"org.freedesktop.DBus.Error.ServiceUnknown")
--
You are receiving this mail because:
You are watching all bug changes.
