Bug 397724 - Wayland is not used, even if available
Summary: Wayland is not used, even if available
Status: RESOLVED NOT A BUG
Alias: None
Product: flatpak-platform-plugin
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-21 21:33 UTC by Rainer Finke
Modified: 2021-06-22 19:16 UTC (History)
4 users (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 Rainer Finke 2018-08-21 21:33:19 UTC
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")
Comment 1 Alexander Mentyu 2018-08-22 11:43:08 UTC
Can reproduce

Distribution: KDE neon Developer Edition
Kernel: 4.15.0-29-generic
Plasma: 5.13.80
Apps: 18.11.70
Qt: 5.11.1
Frameworks: 5.48.0
Graphics:  Card-1: Intel driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 
Card-2: NVIDIA GM108M [GeForce 940MX] driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:134d 
Display: wayland server: X.Org 1.19.6 driver: modesetting,nouveau 
unloaded: fbdev,vesa alternate: nvidia compositor: kwin wayland 
resolution: 1920x1080~57Hz 
OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.0.5 
compat-v: 3.0 direct render: Yes
Comment 2 Jan Grulich 2018-08-27 07:01:56 UTC
Falkon doesn't seem to have enabled "--socket=wayland" in its manifest. Can you try using "flatpak run --socket=wayland org.kde.falkon -platform wayland"?
Comment 3 Christoph Feck 2018-09-13 16:06:36 UTC
If you can provide the information requested in comment #2, please add it.
Comment 4 Alexander Mentyu 2018-09-16 15:29:21 UTC
(In reply to Jan Grulich from comment #2)
> Falkon doesn't seem to have enabled "--socket=wayland" in its manifest. Can
> you try using "flatpak run --socket=wayland org.kde.falkon -platform
> wayland"?

Launched Falkon with this options - xwininfo command doesn't indicates that this is an XWayland window
Comment 5 Jan Grulich 2021-06-22 19:16:47 UTC
Closing.

1) This is a bug in the package itself
2) We don't have a KDE flatpak platform plugin anymore