[SailfishDevel] Flatpak for Sailfish

[E.S. Rosenberg]

Native apps rely on the libs shipped with the OS, thus they don't ship with
unsecure libs unless Jolla is shipping them and they become secure the
moment Jolla updated the libs (and should the update break binary
compatibility will require a new release compiled against the new libs).
Flatpacks and snaps are security nightmares, instead of getting them lets
work on moving the SFOS platform along.

Op zo 29 dec. 2019 om 20:41 schreef rinigus <rinigus.git at gmail.com>:

> Hi,
>
> If you refer to http://flatkill.org/ , it does have lot of good points.
> In this respect, its similar to what we have with the native apps, as soon
> as some security flaws are used. At the moment, I would prefer to get
> access to the latest Qt and other recent software. But users are still
> responsible for thinking before installing, as they are now. Note that in
> many aspects our current packaging together with bundled libs is similar to
> flatpak already. So, why not to make it with the recent libs as well?
>
> Cheers,
>
> Rinigus
>
>
> On Sun, Dec 29, 2019 at 8:26 PM E.S. Rosenberg <
> es.rosenberg+sailfishos.org at gmail.com> wrote:
>
>> No one is bothered by the serious (bad) security implications of running
>> flatpacks?
>> Though I guess we are all tolerating the claim to "security" on ancient
>> kernels so we have no right to blab about security now 🤔
>>
>> Op za 28 dec. 2019 om 12:04 schreef rinigus <rinigus.git at gmail.com>:
>>
>>> Hi,
>>>
>>> I am not 100% sure whether xdg-shell availability is the blocker. There
>>> is something going on which I cannot explain yet - its as if Wayland
>>> rendering disappears even when I use qxcomposer.
>>>
>>> qxcomposer does allow me to minimize and then restore. However, when
>>> keeping app minimized and switching to other apps, I do get (with
>>> WAYLAND_DEBUG=1)
>>>
>>> [2294832.935] wl_pointer at 8.motion(207667, 0.000000, 0.000000)
>>> [2299966.213] qt_extended_surface at 29.onscreen_visibility(1)
>>> [2303645.301] qt_extended_surface at 29.onscreen_visibility(0)
>>> [2303647.486]  -> wl_surface at 26.destroy()
>>> [2303648.296]  -> wl_buffer at 4278190080.destroy()
>>> [2303648.395]  -> wl_buffer at 4278190082.destroy()
>>> [2303648.448]  -> wl_buffer at 4278190081.destroy()
>>>
>>> and the app window disappears from qxcomposer.
>>>
>>> Same happens when running directly using SFOS composer:
>>>
>>> [2614530.331] qt_extended_surface at 29.onscreen_visibility(0)
>>> [2614552.802]  -> wl_surface at 26.destroy()
>>> [2614555.653]  -> wl_buffer at 4278190080.destroy()
>>> [2614556.795]  -> wl_buffer at 4278190082.destroy()
>>> [2614557.099]  -> wl_buffer at 4278190081.destroy()
>>>
>>> So, looks like the surface gets destroyed, but nothing really restores
>>> it.
>>>
>>> As such, some kind of wrapper, similar to qxcomposer, around Flatpak
>>> programs maybe handy. It could take few tasks, such as
>>>
>>> - follow orientation of the screen
>>> - restore app after wl_buffer.destroy()
>>> - provide keyboard support
>>>
>>> I don't know enough about Wayland to be efficient in working on it. So,
>>> I wonder if someone would like to step in and help with this part. If there
>>> is interest, I will work on packaging libhybris extension and provide an
>>> example at OBS for Xperia Tama devices.
>>>
>>> Cheers,
>>>
>>> Rinigus
>>>
>>> On Sat, Dec 28, 2019 at 12:54 AM Damien Caliste <dcaliste at free.fr>
>>> wrote:
>>>
>>>> Thank you Rinigus for all of this. Indeed, the current main blocker
>>>> seems to be the fact that xdg-shell is not available in Lipstick. This is
>>>> linked to the ancient version of QtWayland, even not 5.6, but still 5.4 !
>>>> They already have a 5.9 branch in SailfishOS git (
>>>> https://git.sailfishos.org/mer-core/qtwayland/tree/mer-5.9), but we
>>>> need to wait for Jolla to make the Qt switch. I don't think it's something
>>>> community can change on device... I hope I can be proven wrong though.
>>>>
>>>> Damien.
>>>> _______________________________________________
>>>> SailfishOS.org Devel mailing list
>>>> To unsubscribe, please send a mail to
>>>> devel-unsubscribe at lists.sailfishos.org
>>>
>>> _______________________________________________
>>> SailfishOS.org Devel mailing list
>>> To unsubscribe, please send a mail to
>>> devel-unsubscribe at lists.sailfishos.org
>>
>> _______________________________________________
>> SailfishOS.org Devel mailing list
>> To unsubscribe, please send a mail to
>> devel-unsubscribe at lists.sailfishos.org
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscribe at lists.sailfishos.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20191229/71f15473/attachment-0001.html>