View Single Post
Posts: 53 | Thanked: 146 times | Joined on Apr 2012 @ Australia
#221
Hi Rinigus,
Stripping setuid certainly seems to have worked.
No reboots on installation. Install completes, and angelfish shows up in flatpak-runner, as does the angelfish desktop icon.
Every flatpak install (or uninstall) command issued the following warning between 1 and 3 times:
Code:
bwrap: Can’t mount devpts on /newroot/dev/pts: Operation not permitted
Despite this, the command reports completion and everything seems to work.
On a side note, telegram doesn’t start. The GUI window reports “Application finished with exit code 134” and the terminal looks like this:
Code:
 Last login: Tue Apr  7 13:27:43 2020 from 172.20.10.1
,---
| Sailfish OS 3.3.0.14 (Rokua)
'---
[nemo@Sailfish ~]$ flatpak list --user
Name                                  Application ID                                          Version         Branch         Origin
default                               org.freedesktop.Platform.GL.default                                     19.08          flathub
ffmpeg-full                           org.freedesktop.Platform.ffmpeg-full                                    19.08          flathub
KDE Application Platform              org.kde.Platform                                                        5.14           flathub
Maliit plugin for SailfishOS          org.kde.PlatformInputContexts.MaliitSailfishOS                          5.14           flathub
Angelfish Webbrowser                  org.kde.mobile.angelfish                                                master         kdeapps
Telegram Desktop                      org.telegram.desktop                                    2.0.1           stable         flathub
[nemo@Sailfish ~]$ flatpak-runner org.telegram.desktop
Starting: org.telegram.desktop
[D] unknown:0 - Using Wayland-EGL
Wayland socket: ../../display/wayland-1
WAYLAND_DISPLAY="../../display/wayland-1" FLATPAK_MALIIT_CONTAINER_DBUS="unix:abstract=/tmp/dbus-SNrqq3t4Q8,guid=f6b4913f7c0ddd07f11975ae5e8bf82d" flatpak run --env=QT_WAYLAND_FORCE_DPI=446 --filesystem=/system:ro --filesystem=/vendor:ro --filesystem=/odm:ro --device=all --talk-name=org.maliit.server --env=QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu-compositing --num-raster-threads=1 --enable-viewport --disable-composited-antialiasing --env=QTWEBENGINE_DISABLE_GPU_THREAD=1 --env=QT_QPA_PLATFORM=wayland= --env=QT_QUICK_CONTROLS_MOBILE=1 --env=QT_QUICK_CONTROLS_STYLE=Plasma --env=HYBRIS_EGLPLATFORM_DIR=/usr/lib/arm-linux-gnueabihf/GL/host/lib/libhybris --env=HYBRIS_LINKER_DIR=/usr/lib/arm-linux-gnueabihf/GL/host/lib/libhybris/linker --env=HYBRIS_LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/GL/host/libexec/droid-hybris/system/lib:/usr/libexec/droid-hybris/system/lib:/vendor/lib:/system/lib --env=LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/GL/host/lib org.telegram.desktop
[D] onCompleted:424 - Warning: specifying an object instance for initialPage is sub-optimal - prefer to use a Component
[W] unknown:53 - file:///usr/share/flatpak-runner/qml/main.qml:53:26: Unable to assign [undefined] to bool
[W] unknown:0 - Could not find the Qt platform plugin "wayland=" in ""
[F] unknown:0 - This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, xcb.

[D] expression for onExit:59 - Skipping quit as it will hang the window. Proper exit is needed
Note that setuid was readded, and angelfish runs well. Also note that the environmental variable QT_QPA_PLATFORM=wayland was added.

Thanks again for all your help,
 

The Following 2 Users Say Thank You to juz For This Useful Post: