#sailfishos-meeting: Sailfish OS, open source, collaboration -- 6th November 2025

Meeting started by rainemak at 16:00:00 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 16:00:00)
    2. https://forum.sailfishos.org/t/25254 (rainemak, 16:00:00)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:00)
    1. Raine Mäkeläinen, Jolla (rainemak, 16:00:11)
    2. Peter G., Community (nephros, 16:00:56)
    3. Otto Mäkelä, community (ExTechOp, 16:01:08)
    4. Matti Viljanen, Jolla (direc85[m], 16:01:16)
    5. mal, Jolla (mal, 16:01:58)
    6. 247, community member (legacychimera247, 16:03:25)

  3. Jolla C2 order backlog (5 mins -- frankps) (rainemak, 16:05:01)
    1. <frankps> Could Jolla give us an update on the backlog situation? Estimated (rainemak, 16:05:06)
    2. <frankps> shipping time October 1st was 6-8 weeks. Where are we now? When #info <frankps> will you start shipping out ordered devices? (rainemak, 16:05:06)
    3. <Jolla> This is covered by https://forum.sailfishos.org/t/25420 (rainemak, 16:05:11)
    4. <Jolla> (rainemak, 16:05:11)
    5. <Jolla> A manufacturing slot for the next production batch Q4/25 of Jolla (rainemak, 16:05:11)
    6. <Jolla> C2 has been confirmed to take place at the week Nov 17, 2025. (rainemak, 16:05:11)
    7. <Jolla> Following from there we should be able to continue shipments by the (rainemak, 16:05:11)
    8. <Jolla> end of November. (rainemak, 16:05:12)
    9. <Jolla> (rainemak, 16:05:14)
    10. <Jolla> Let’s have open discussion. (rainemak, 16:05:16)
    11. https://forum.sailfishos.org/t/25420 (rainemak, 16:05:18)

  4. GTK support (10 mins -- pherjung) (rainemak, 16:10:00)
    1. <pherjung> The Librem 5 supports an increasing number of GTK apps. While (rainemak, 16:10:00)
    2. <pherjung> they do not adhere to Sailfish OS UI/UX guidelines, they are (rainemak, 16:10:00)
    3. <pherjung> Linux apps and would increase the number of apps available on (rainemak, 16:10:00)
    4. <pherjung> Sailfish OS. Are there any plans to support GTK, and how much (rainemak, 16:10:00)
    5. <pherjung> effort would it take? (rainemak, 16:10:02)
    6. <Jolla> Thank for this good question. Sorry for the long answer. (rainemak, 16:10:23)
    7. <Jolla> (rainemak, 16:10:23)
    8. <Jolla> The problem behind the scene is that we’re lacking xdg-shell (rainemak, 16:10:23)
    9. <Jolla> support from Qt. Thus, also from our compositor (lipstick). (rainemak, 16:10:23)
    10. <Jolla> Implementing xdg-shell support would be a good starting point and (rainemak, 16:10:23)
    11. <Jolla> then we should have means to support other toolkits than Qt for app (rainemak, 16:10:25)
    12. <Jolla> development. (rainemak, 16:10:27)
    13. <Jolla> (rainemak, 16:10:29)
    14. <Jolla> Some years back we started a project to split homescreen (lipstick) (rainemak, 16:10:31)
    15. <Jolla> properly to a homescreen and a wayland compositor. Why to split? (rainemak, 16:10:33)
    16. <Jolla> Mostly due to robustness and performance. Composition and gestures (rainemak, 16:10:35)
    17. <Jolla> should never stall. Also freezes or crashes on homescreen should (rainemak, 16:10:37)
    18. <Jolla> not affect to the other applications. Eventually this project (rainemak, 16:10:39)
    19. <Jolla> didn’t materialize. With this project we could have received also (rainemak, 16:10:41)
    20. <Jolla> xdg-shell support. (rainemak, 16:10:43)
    21. <Jolla> (rainemak, 16:10:45)
    22. <Jolla> We should try to think out-of-the-box, try to find other possible (rainemak, 16:10:47)
    23. <Jolla> solutions and use existing projects when possible. Then comes (rainemak, 16:10:51)
    24. <Jolla> projects like Weston. A Wayland compositor that is broadly used. (rainemak, 16:10:53)
    25. <Jolla> Thus, it would have more developers working on it when comparing to (rainemak, 16:10:55)
    26. <Jolla> us (Jolla & Sailfish Community). (rainemak, 16:10:57)
    27. <Jolla> (rainemak, 16:10:59)
    28. <Jolla> Conceptually we could have a Weston compositor and the “current” (rainemak, 16:11:01)
    29. <Jolla> homescreen as a wayland client (an app among the other apps). On (rainemak, 16:11:03)
    30. <Jolla> the compositor side we should deal for example window management, (rainemak, 16:11:05)
    31. <Jolla> shell, gestures and effects with very limited dependencies. Surely, (rainemak, 16:11:07)
    32. <Jolla> there are also things like text input support. (rainemak, 16:11:09)
    33. <Jolla> (rainemak, 16:11:11)
    34. <Jolla> If all this would happen, then we should also be very close to a (rainemak, 16:11:13)
    35. <Jolla> situation where we actually could have support for other toolkits (rainemak, 16:11:15)
    36. <Jolla> (easily or relatively easily) for example for GTK. Surely, changing (rainemak, 16:11:17)
    37. <Jolla> compositor architecture would be most bigger task than implementing (rainemak, 16:11:21)
    38. <Jolla> xdg-shell support for the current compositor. (rainemak, 16:11:23)
    39. https://gitlab.freedesktop.org/wayland/weston (rainemak, 16:11:38)
    40. dodoradio, community/asteroidos (dodoradio[m], 16:15:22)
    41. pherjung, community (pherjung[m], 16:29:53)

  5. Sony Xperia 10 IV/V port status (10mins -- ExTechOp) (rainemak, 16:32:32)
    1. <ExTechOp> A functional Sony device port has now been “real soon now” since (rainemak, 16:32:32)
    2. <ExTechOp> Love Day 2 in August 2024, but they still suffer from serious (rainemak, 16:32:32)
    3. <ExTechOp> issues because of Sony binary blobs. Also, a Jolla announcement (rainemak, 16:32:33)
    4. <ExTechOp> on the status of the Sony devices port has now been teased for (rainemak, 16:32:33)
    5. <ExTechOp> months, but even this hasn’t materialized. This is just getting (rainemak, 16:32:34)
    6. <ExTechOp> embarrassing. Please put out an official statement outlining (rainemak, 16:32:36)
    7. <ExTechOp> some kind of time scale when things will begin to happen, or (rainemak, 16:32:38)
    8. <ExTechOp> just admit it’s never happening. If all this fails, at least (rainemak, 16:32:40)
    9. <ExTechOp> give a time scale when you’ll be able to clarify things. (rainemak, 16:32:42)
    10. <Jolla> We fully acknowledge, we have promised to deliver Sailfish to (rainemak, 16:32:46)
    11. <Jolla> Xperia 10 IV/V and we remain committed to do our part with it as (rainemak, 16:32:46)
    12. <Jolla> far it takes and what can be feasibly done by us. By far, not all (rainemak, 16:32:48)
    13. <Jolla> can be done by us and with the currently chosen approach there has (rainemak, 16:32:52)
    14. <Jolla> been several unexpected up and downs in this project e.g. with the (rainemak, 16:32:54)
    15. <Jolla> vendor blobs: there has been blocker issues with battery indication (rainemak, 16:32:56)
    16. <Jolla> missing, camera not working, VoLTE not working and fingerprint (rainemak, 16:32:58)
    17. <Jolla> missing. (rainemak, 16:33:00)
    18. <Jolla> (rainemak, 16:33:02)
    19. <Jolla> Maybe we have totally wrong approach with the adaptation software (rainemak, 16:33:04)
    20. <Jolla> of this particular device project? Maybe it shouldn’t be done (rainemak, 16:33:06)
    21. <Jolla> primarily by Jolla and using the Open Device Program vendor blobs? (rainemak, 16:33:08)
    22. <Jolla> (rainemak, 16:33:10)
    23. <Jolla> We have also been thinking about completely different approaches by (rainemak, 16:33:12)
    24. <Jolla> enabling this thru an “officially supported community port” - (rainemak, 16:33:14)
    25. <Jolla> community port and we enable AppSupport to it – would that work for (rainemak, 16:33:16)
    26. <Jolla> the community? (rainemak, 16:33:18)
    27. <Jolla> (rainemak, 16:33:22)
    28. <Jolla> What is the definition of done in this project? What do you think (rainemak, 16:33:24)
    29. <Jolla> should be done to call it ready for the expected use? (rainemak, 16:33:26)
    30. <Jolla> (rainemak, 16:33:28)
    31. <Jolla> E.g. fingerprint – won’t be done, other examples? (rainemak, 16:33:30)

  6. Security patch level updates of the Android runtime (10 mins -- balta) (rainemak, 16:50:01)
    1. <balta> Google releases monthly security patches for Android, but sadly (rainemak, 16:50:06)
    2. <balta> these are never applied to the android app support runtime of (rainemak, 16:50:06)
    3. <balta> SailfishOS. You can check your security patch level in Settings → (rainemak, 16:50:06)
    4. <balta> Android App Support. As these patches contain security fixes they (rainemak, 16:50:06)
    5. <balta> should be included regularly in SailfishOS updates as well. Right (rainemak, 16:50:06)
    6. <balta> now on the 10V the level is from August of 2024, I think on older (rainemak, 16:50:08)
    7. <balta> devices this will be even older. Also some apps will check this and (rainemak, 16:50:09)
    8. <balta> refuse to start, e.g. I cannot use Teams for my job right now (rainemak, 16:50:11)
    9. <balta> because of a too old security patch level. Is this a big effort for (rainemak, 16:50:13)
    10. <balta> Jolla to provide an update or is it something like simply (rainemak, 16:50:15)
    11. <balta> triggering a CI chain? (rainemak, 16:50:17)
    12. <Jolla> AppSupport security patch level is usually updated on bigger (rainemak, 16:50:30)
    13. <Jolla> releases (4.5. ,4.6., 5.0...). Currently we are working on (rainemak, 16:50:30)
    14. <Jolla> AppSupport 13 security patch level update. Unfortunately, (rainemak, 16:50:30)
    15. <Jolla> AppSupport 11 no longer receive security patch level updates from (rainemak, 16:50:30)
    16. <Jolla> AOSP and it is currenty using the latest patch level. All in all, (rainemak, 16:50:31)
    17. <Jolla> it’s not a simple as triggering a CI chain. When going forward we (rainemak, 16:50:33)
    18. <Jolla> should think whether we could / should update AppSupport security (rainemak, 16:50:35)
    19. <Jolla> patch level also upon hotfix updates (when an update is available (rainemak, 16:50:37)
    20. <Jolla> and integrated). (rainemak, 16:50:39)

  7. How shall we deal with trolls in the forum (10 mins -- Fellfrosch) (rainemak, 16:56:29)
    1. <Fellfrosch> Trolls quite often ruin a discussion in the forum. It is quite (rainemak, 16:56:29)
    2. <Fellfrosch> easy for them to do so, because threads get blocked when they (rainemak, 16:56:29)
    3. <Fellfrosch> get flagged. This is stopping quite often good and helpful (rainemak, 16:56:29)
    4. <Fellfrosch> conversation. So the question is how do we want to deal with (rainemak, 16:56:30)
    5. <Fellfrosch> this problem in future. For me the better solution instead of (rainemak, 16:56:31)
    6. <Fellfrosch> freezing threads would be temporary bans for people who (rainemak, 16:56:33)
    7. <Fellfrosch> misbehave and don’t cling to the forum rules. (rainemak, 16:56:35)
    8. <Fellfrosch> I already started a thread about that problem here: (rainemak, 16:56:37)
    9. <Fellfrosch> Please stop closing threads because of trolls (rainemak, 16:56:39)
    10. https://forum.sailfishos.org/t/25369 (rainemak, 16:56:41)
    11. <Jolla> Let’s have an open discussion on this. (rainemak, 16:56:43)
    12. <Jolla> Starting point could be Sailfish OS Forum FAQ. (rainemak, 16:56:45)
    13. https://forum.sailfishos.org/faq (rainemak, 16:56:47)

  8. Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:16:04)
  9. General discussion (10 mins or something) (rainemak, 17:22:51)
  10. Next meeting time and date (2 mins) (rainemak, 17:32:40)
    1. Next meeting will be held on Thursday 20th November 2025 at 04:00pm UTC: 2025-11-20T1600Z (rainemak, 17:34:26)


Meeting ended at 17:35:19 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (216)
  2. dcaliste (18)
  3. ExTechOp (12)
  4. pherjung[m] (12)
  5. nephros (10)
  6. abr (10)
  7. mal (9)
  8. legacychimera247 (9)
  9. dodoradio[m] (5)
  10. direc85[m] (3)
  11. sailbot (2)
  12. Keto (2)
  13. roundedrectangl (1)


Generated by MeetBot 0.1.4.