Active Topics
-
Is there a section to talk about Java ME? Apps, etc. (5)
to General by teroyk - 4 days, 1 hr ago -
Extra softwares in Sailfish using CLI, repositories, etc (118)
to SailfishOS by nieldk - 4 days, 6 hrs ago -
Paths (0)
to Maemo 7 / Leste by teroyk - 5 days, 4 hrs ago - more...
rinigus |
2020-07-11
, 11:51
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#371
|
Turned out that it was due to ffmpeg update. To get it back
Reference: https://github.com/flatpak/flatpak/issues/3097
Code:
|
|
2020-07-11
, 13:18
|
|
Posts: 19 |
Thanked: 48 times |
Joined on Apr 2020
@ Spain
|
#372
|
Originally Posted by rinigus
Great!! It works again, thank you!
Turned out that it was due to ffmpeg update. To get it back
Reference: https://github.com/flatpak/flatpak/issues/3097Code:flatpak update --commit=6cc32e9f41c440fd05c2bbfcf0eeafee974c95a2d89f8f738492966d68ab8a8d org.freedesktop.Platform.ffmpeg-full
|
|
2020-07-19
, 17:00
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#373
|
Flatpak has been bumped to 1.6.5. Update as usual via zypper or some other tool.
 |
|
2020-08-07
, 01:01
|
|
Posts: 592 |
Thanked: 706 times |
Joined on Jul 2019
@ UK
|
#374
|
I am trying to install angelfish but my device always gets rebooted right after the installation starts. After the reboot, it looks like the app is installed but in reality, it is not the case. When I try to remove it with 'flatpak remove --user angelfish', the device also instantly gets rebooted.
I am following the instructions from here. (Flatpak version is 1.6.5)
Is it just I, or somebody else is having similar issues? Thanks.
I am following the instructions from here. (Flatpak version is 1.6.5)
Is it just I, or somebody else is having similar issues? Thanks.
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
|
|
2020-08-07
, 07:28
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#375
|
Originally Posted by edp17
Have you tried to remove setuid from flatpak-bwrap?
I am trying to install angelfish but my device always gets rebooted right after the installation starts. After the reboot, it looks like the app is installed but in reality, it is not the case. When I try to remove it with 'flatpak remove --user angelfish', the device also instantly gets rebooted.
I am following the instructions from here. (Flatpak version is 1.6.5)
Is it just I, or somebody else is having similar issues? Thanks.
|
|
2020-08-07
, 08:25
|
|
Posts: 592 |
Thanked: 706 times |
Joined on Jul 2019
@ UK
|
#376
|
Originally Posted by rinigus
Thank you this helped with the install/uninstall.
Have you tried to remove setuid from flatpak-bwrap?
However, once I successfully installed the angelfish, when I start it with 'flatpak-runner org.kde.mobile.angelfish' while the setuid is removed from flatpak-bwrap, I get this:
Code:
[nemo@GalaxyNote4 ~]$ flatpak-runner org.kde.mobile.angelfish Starting: org.kde.mobile.angelfish [D] unknown:0 - Using Wayland-EGL library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it Wayland socket: ../../display/wayland-1 WAYLAND_DISPLAY="../../display/wayland-1" FLATPAK_MALIIT_CONTAINER_DBUS="unix:abstract=/tmp/dbus-2jgsVazrhw,guid=6dbb0b460b76ace39f6f63685f2d0ab1" flatpak run --env=QT_WAYLAND_FORCE_DPI=517 --filesystem=/system:ro --filesystem=/vendor: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_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.kde.mobile.angelfish [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 bwrap: Creating new namespace failed, likely because the kernel does not support user namespaces. bwrap must be installed setuid on such systems.
If I put the setguid back to the flatpak-bwrap, upon starting angelfish I get a screen whith the circle animation and the following in the console:
Code:
[nemo@GalaxyNote4 ~]$ flatpak-runner org.kde.mobile.angelfish Starting: org.kde.mobile.angelfish [D] unknown:0 - Using Wayland-EGL library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it Wayland socket: ../../display/wayland-2 WAYLAND_DISPLAY="../../display/wayland-2" FLATPAK_MALIIT_CONTAINER_DBUS="unix:abstract=/tmp/dbus-1MAKn0UhdE,guid=ff1e7aa17d091e23d6b5f2775f2d0bb5" flatpak run --env=QT_WAYLAND_FORCE_DPI=517 --filesystem=/system:ro --filesystem=/vendor: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_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.kde.mobile.angelfish [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 bwrap: execvp xdg-dbus-proxy: No such file or directory
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
| The Following User Says Thank You to edp17 For This Useful Post: | ||
|
|
2020-08-07
, 12:10
|
|
Posts: 592 |
Thanked: 706 times |
Joined on Jul 2019
@ UK
|
#378
|
Originally Posted by rinigus
Yes, that is installed:
xdg-dbus-proxy: do you have it installed? maybe try to install again flatpak-runner, that should pull all dependencies...
Code:
[nemo@GalaxyNote4 ~]$ sudo zypper se xdg-dbus-proxy Loading repository data... Reading installed packages... S | Name | Summary --+----------------------------+------------------------------------------- i | xdg-dbus-proxy | Filtering proxy for D-Bus connections | xdg-dbus-proxy-debuginfo | Debug information for package xdg-dbus-proxy | xdg-dbus-proxy-debugsource | Debug sources for package xdg-dbus-proxy
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
| The Following User Says Thank You to edp17 For This Useful Post: | ||
|
|
2020-08-07
, 13:46
|
|
Posts: 1,414 |
Thanked: 7,547 times |
Joined on Aug 2016
@ Estonia
|
#379
|
Originally Posted by edp17
Beats me. Maybe try to reinstall it. Don't remember seeing this error...
Yes, that is installed:
Code:[nemo@GalaxyNote4 ~]$ sudo zypper se xdg-dbus-proxy Loading repository data... Reading installed packages... S | Name | Summary --+----------------------------+------------------------------------------- i | xdg-dbus-proxy | Filtering proxy for D-Bus connections | xdg-dbus-proxy-debuginfo | Debug information for package xdg-dbus-proxy | xdg-dbus-proxy-debugsource | Debug sources for package xdg-dbus-proxy
|
|
2020-08-07
, 14:50
|
|
Posts: 592 |
Thanked: 706 times |
Joined on Jul 2019
@ UK
|
#380
|
Originally Posted by rinigus
No, I wouldn't do that! Ever.
Beats me. Maybe try to reinstall it. Don't remember seeing this error...
Instead, I'll go and double-check the requirements and try to reinstall everything.
I wouldn't be surprised if this was a limitation/bug of my port for this device. I'll let you know the outcome here anyway. Thank you.
__________________
Porting SailfishOS to some devices:
Porting SailfishOS to some devices:
