levone1 | # 201 | 2021-10-20, 15:02 | Report

For example - if I open telegram desktop from within Debian desktop, a new card opens in Sailfish, with telegram desktop app open.
This is the terminal output :

(kdeconnect-app:5194): Gdk-WARNING **: 14:55:50.385: The Wayland compositor does not provide any supported shell interface, not using Wayland display
Could not create scene graph context for backend 'customcontext' - check that plugins are installed correctly in /usr/lib/aarch64-linux-gnu/qt5/plugins
kf.kirigami: Warning: Theme implementations should use Kirigami.BasicThemeDefinition for its root item
kf.kirigami: Failed to find a Kirigami platform plugin
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86 ): This returns 1 when using Qt HiDPI scaling.
qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell-v6" or "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
qt.qpa.wayland: Minimizing is not supported on wl-shell. Consider using xdg-shell instead.

But when the start_desktop sh script used to work, that app would open in the same desktop. I can't figure out the difference ...

edp17 | # 202 | 2021-10-21, 07:10 | Report

Hm, on my treltexx, it opens up the apps within the desktop screen. I use sfos4.1 on there. Could it be the reason?
How do you start the desktop distro, using multiple Fingerterm sessions and command line, or with one script from Shellex/command line, or with an icon on your desktop? (I've used to use Shellex, but then created an icon in sfos for it.)

levone1 | # 203 | 2021-10-21, 14:59 | Report

- open Containers app
- start container, (works), tap "start xsession", (doesn't open window, but something happens - it won't work if I don't do it), then tap "attach", (works, and terminal opens with shell)
- in shell, enter some of the commands from 'start_desktop' script, (e.g. "export $(dbus-launch)", "export XDG_RUNTIME_DIR", etc), finishing with "su user -c startx".

Then window opens with debian desktop. All functions normally, except that some user-installed apps open in a separate window, and won't stay open if a different window is opened.

One thing I discovered is that all of the commands from start_desktop script run successfully when entered individually, except for export $(dbuslaunch). That one gives error about how xdg runtime is owned by uid 100000. The only way I can get it to work is to mkdir /run/user/1001, then set 1001 as runtime dir.

I did try to chown on xdg runtime dir, and then dbus launch command worked without error, but startx fails with "cannot open display server refused..."

edp17 | # 204 | 2021-11-03, 15:55 | Report

Unfortunately, the app never worked well on that device. I only used the command line for all. Have you tried to start the container and the desktop distro from the command line? What is the default user on the host SFOS (nemo or defaultuser)?
Try to use one of the scripts I uploaded to the main page (e.g debian-mouse.sh) and see what happens.

---

Last edited by edp17; 2021-11-03 at 16:02.

levone1 | # 205 | 2021-11-03, 17:42 | Report

This is what happens when trying fo run scripts (that previously worked fine until 4.2) - https://talk.maemo.org/showpost.php?...&postcount=192

The default user is defaultuser, and I have nemo symlink in /home...

I have a feeling that the apps opening in separate window could be just some missing package, but not sure. I think it's a particular type of app, (maybe xdg, or... [I don't know Linux stuff too well]), so maybe just requires some support package ...

edp17 | # 206 | 2021-11-09, 01:06 | Report

This might help, I have the following installed:
from official repo:

• nemo-qml-plugin-dbus-qt5
• sailfish-polkit-agent
• python3-base
• python3-gobject
• dbus-python3
• lxc
• lxc-templates

from downloaded .rpm:

• lxc-templates-desktop-1.1-4.noarch.rpm
• qxdisplay-0.1-2.armv7hl.rpm
• harbour-containers-0.4-1.armv7hl.rpm
• qxcompositor-0.0.5+cursor_test2.20200816190630.86af352-1.2.1.jolla.armv7hl.rpm

levone1 | # 207 | 2021-11-12, 01:44 | Report

Thanks - I'll check it out ... One thing is that I'm on aarch64, so my apps are home-built. Maybe some issue there...

megamaced | # 208 | 2021-11-23, 22:33 | Report

Hi, is the harbour containers project still going?

The qxdisplay binary has symbol lookup error on Sailfish X 4.3.0

"/usr/bin/qxdisplay: symbol lookup error: /usr/
bin/qxdisplay: undefined symbol"

I did try to compile it from the RPM spec directly on my device but it failed to compile

I saw that flatpak-runner is a fork of qxdisplay. I was able to run flatpak-runner without any arguments to start a wayland display server, and then attach inside my lxc container and modify the scripts to point to the flatpak-runner wayland server location. Using this method I was able to get XFCE on openSUSE Leap 15.3 running, however I could not resolve the DPI and scaling issue. Desktop was not a usable size and also the touch pointer was off

elros34 | # 209 | 2021-11-24, 17:47 | Report

Didn't try it on aarch64 but amrv7hl works fine on sfos 4.3.0: https://github.com/elros34/qxcomposi.../qtwayland-5.6. I guess qxdisplay do not have any relevant changes compared to qxcompositor. Also version for sfos >= 4.2.0 in my use case support dynamic orientation for chromium + matchbox ("-x -o auto" arguments) so maybe it will also works for full desktop environment like xfce.

---

Last edited by elros34; 2021-11-24 at 18:12.

Maemish | # 210 | 2021-11-24, 19:43 | Report

I find these posts entertaining. To understand linux is hard for me cause even though I have used it over ten years I am a mere end user. and tweaking mainly how to get it snappier. But these sailfish relates posts, these are something else, so cryptic if you don't know enough, even though they are just linux language. Feeling like listening someones from a different planet.