#sailfishos-meeting: Sailfish OS, open source, collaboration -- 23rd October 2025

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

Meeting summary

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

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:05)
    1. Otto Mäkelä, community (ExTechOp, 16:00:09)
    2. Raine Mäkeläinen, Jolla (rainemak, 16:00:17)
    3. Matti Viljanen, Jolla (direc85[m], 16:00:39)
    4. roundedrectangle, community (roundedrectangl, 16:00:56)
    5. Pami Ketolainen, Jolla (Keto, 16:01:54)
    6. Fellfrosch. community (Fellfrosch, 16:02:20)
    7. piggz community (piggz[m], 16:02:49)
    8. mal, Jolla (mal, 16:02:59)
    9. https://forum.sailfishos.org/t/sailfish-community-news-16th-october-2025-a-new-writer/25006 (rainemak, 16:04:30)

  3. WPA3 status update (5 mins -- KeeperoftheKeys) (rainemak, 16:05:09)
    1. <KeeperoftheKeys> I recently installed some simple Open Source IoT (rainemak, 16:05:21)
    2. <KeeperoftheKeys> switches and was very surprised to find them supporting (rainemak, 16:05:21)
    3. <KeeperoftheKeys> WPA3, this makes my Jolla phone the only thing (rainemak, 16:05:21)
    4. <KeeperoftheKeys> preventing me from switching our home network to WPA3. I (rainemak, 16:05:21)
    5. <KeeperoftheKeys> recall that there has been some work on this in the past (rainemak, 16:05:21)
    6. <KeeperoftheKeys> where do things stand? Based on a little of my own (rainemak, 16:05:23)
    7. <KeeperoftheKeys> testing (see below) it seems like it should be “in (rainemak, 16:05:24)
    8. <KeeperoftheKeys> reach/spitting distance”. (rainemak, 16:05:26)
    9. <KeeperoftheKeys> (rainemak, 16:05:28)
    10. <KeeperoftheKeys> WPA3 is mostly a software issue, I have seen it working (rainemak, 16:05:30)
    11. <KeeperoftheKeys> on Linux laptops that were built years before anyone (rainemak, 16:05:32)
    12. <KeeperoftheKeys> even thought about WPA3, as far as I recall connman (rainemak, 16:05:34)
    13. <KeeperoftheKeys> / wpasupplicant would need to be updated for this. (rainemak, 16:05:38)
    14. <KeeperoftheKeys> (rainemak, 16:05:40)
    15. <KeeperoftheKeys> Software versions: (rainemak, 16:05:42)
    16. <KeeperoftheKeys> (rainemak, 16:05:44)
    17. <KeeperoftheKeys> * Connman 1.41 shipped initial WPA3-SAE support based on phoronix, the current version on my phone [SFOS 5 (10ii)] is 1.38 (rainemak, 16:05:46)
    18. <KeeperoftheKeys> * Per a wpa_supplicant changelog it added WPA3 in 2.10 (rainemak, 16:05:49)
    19. <KeeperoftheKeys> and on my phone I find 2.11 and I was able to manually (rainemak, 16:05:51)
    20. <KeeperoftheKeys> connect using it (wpa_supplicant -i wlan0 -c (rainemak, 16:05:53)
    21. <KeeperoftheKeys> local.conf) this did not set the correct IP address (rainemak, 16:05:55)
    22. <KeeperoftheKeys> from my router, I need to check with another device if (rainemak, 16:05:57)
    23. <KeeperoftheKeys> this is a config issue of the testing SSID or an issue (rainemak, 16:05:59)
    24. <KeeperoftheKeys> with the phone but after manually setting the correct (rainemak, 16:06:01)
    25. <KeeperoftheKeys> IP address (ip addr add…) I was able to “prove” that I (rainemak, 16:06:03)
    26. <KeeperoftheKeys> indeed connected successfully to the WPA3 SSID. (rainemak, 16:06:05)
    27. <KeeperoftheKeys> To do all of this I also had to do some gymnastics (rainemak, 16:06:09)
    28. <KeeperoftheKeys> with enabling/disabling wireless in the GUI to allow (rainemak, 16:06:11)
    29. <KeeperoftheKeys> wpa_supplicant to grab control of wlan0 from connman. (rainemak, 16:06:13)
    30. https://www.phoronix.com/news/ConnMan-1.41-IWD-1.23 (rainemak, 16:06:15)
    31. https://android.googlesource.com/platform/external/wpa_supplicant_8/+/refs/heads/main/wpa_supplicant/ChangeLog (rainemak, 16:06:17)
    32. <Jolla> The support for WPA3 in newer connman version would not directly (rainemak, 16:06:20)
    33. <Jolla> enable WPA3 support in Sailfish OS because we have a custom wifi (rainemak, 16:06:22)
    34. <Jolla> plugin which needs adapting to support WPA3. Also higher level (rainemak, 16:06:24)
    35. <Jolla> code using connman needs to be adapted to support WPA3 type. There (rainemak, 16:06:26)
    36. <Jolla> is work in progress code for those but it does not work reliably (rainemak, 16:06:28)
    37. <Jolla> on all devices yet and was missing some parts about correctly (rainemak, 16:06:30)
    38. <Jolla> reporting type to higher level. (rainemak, 16:06:32)
    39. pherjung, Community (pherjung[m], 16:07:58)
    40. David Llewellyn-Jones, community; and of course late. (flypig, 16:08:03)
    41. Raymaen, Community (Raymaen[m], 16:08:54)
    42. https://github.com/sailfishos/connman/blob/master/connman/plugins/sailfish_wifi.c (rainemak, 16:12:11)
    43. Link to Sailfish OS wifi plugin (rainemak, 16:12:51)
    44. nephros, community, later-comer (nephros, 16:14:28)

  4. Allow apps to use nextcloud client or add ability to configure folder sync (10mins -- KeeperoftheKeys) (rainemak, 16:15:14)
    1. <KeeperoftheKeys> As documented in this topic Sailsync OwnCloud does not (rainemak, 16:15:14)
    2. <KeeperoftheKeys> work out of the box with recent versions of nextcloud (rainemak, 16:15:14)
    3. <KeeperoftheKeys> and due to Qt limitations this is only going to get (rainemak, 16:15:14)
    4. <KeeperoftheKeys> worse, @nephros has built a newer drop in binary with Qt (rainemak, 16:15:15)
    5. <KeeperoftheKeys> 5.15 but that is also a solution that will only hold so (rainemak, 16:15:17)
    6. <KeeperoftheKeys> long and while those who run NC instances where they (rainemak, 16:15:19)
    7. <KeeperoftheKeys> have full control can lower the (rainemak, 16:15:21)
    8. <KeeperoftheKeys> minimum.supported.desktop.version they are taking a risk (rainemak, 16:15:23)
    9. <KeeperoftheKeys> as per the NC devs. (rainemak, 16:15:25)
    10. <KeeperoftheKeys> IMHO Sailsync OwnCloud provides a functionality that (rainemak, 16:15:27)
    11. <KeeperoftheKeys> should just be part of the NC account settings, if that (rainemak, 16:15:29)
    12. <KeeperoftheKeys> is not a possibility then it would be nice if it could (rainemak, 16:15:31)
    13. <KeeperoftheKeys> leverage the builtin client (and credentials) instead of (rainemak, 16:15:33)
    14. <KeeperoftheKeys> needing to ship its own. (rainemak, 16:15:35)
    15. https://forum.sailfishos.org/t/22969 (rainemak, 16:15:39)
    16. <Jolla> NextCloud account (and related components) could be our next (rainemak, 16:15:41)
    17. <Jolla> component to open source which would also enable contributions (rainemak, 16:15:43)
    18. <Jolla> from the Sailsync OwnCloud towards platform NextCloud. We shall (rainemak, 16:15:45)
    19. <Jolla> take this into account as we plan this. In many cases app (rainemak, 16:15:47)
    20. <Jolla> functionalities easily provide more value when / if they are (rainemak, 16:15:49)
    21. <Jolla> implemented as an operating system feature. (rainemak, 16:15:51)
    22. poetaster is late (poetaster, 16:17:05)
    23. https://github.com/sailfishos/buteo-sync-plugin-caldav/ (abr, 16:30:32)

  5. Support more codecs in QtMultimedia GStreamer plugin (5 mins -- roundedrectangl) (rainemak, 16:32:11)
    1. <roundedrectangl> Information about supported audio capture codecs in (rainemak, 16:32:22)
    2. <roundedrectangl> QtMultimedia GStreamer plugin seems to be hardcoded in (rainemak, 16:32:22)
    3. <roundedrectangl> Qt 5.6 here: qtmultimedia/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp (rainemak, 16:32:22)
    4. <roundedrectangl> at mer-5.6 · sailfishos/qtmultimedia · GitHub. I know (rainemak, 16:32:22)
    5. <roundedrectangl> that there are no plans for changing the core behaviour (rainemak, 16:32:22)
    6. <roundedrectangl> of this in the near future, because that would require a (rainemak, 16:32:24)
    7. <roundedrectangl> Qt update. But are there any plans for, at least, adding (rainemak, 16:32:26)
    8. <roundedrectangl> more codecs (such as Opus) to that hard-coded list? And (rainemak, 16:32:28)
    9. <roundedrectangl> would a pull request adding this get accepted? (rainemak, 16:32:30)
    10. <roundedrectangl> Related: How to record opus audio programatically? (rainemak, 16:32:32)
    11. https://github.com/sailfishos/qtmultimedia/blob/mer-5.6/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp (rainemak, 16:32:34)
    12. https://forum.sailfishos.org/t/how-to-record-opus-audio-programatically/25139 (rainemak, 16:32:39)
    13. <Jolla> It might be possible to enable some additional codecs but it needs (rainemak, 16:32:41)
    14. <Jolla> to be tested that those actually work. Pull requests are always (rainemak, 16:32:43)
    15. <Jolla> welcome and we’ll review and test them. (rainemak, 16:32:45)

  6. Linux on Mobile stand at FOSDEM in 2026 (10mins -- flypig) (rainemak, 16:45:15)
    1. <flypig> FOSDEM (https://fosdem.org) will take place again in Brussels on (rainemak, 16:45:15)
    2. <flypig> the weekend of 31 January 2026. In previous years we’ve had a (rainemak, 16:45:15)
    3. <flypig> very successful Linux on Mobile stand with Jolla being a big and (rainemak, 16:45:15)
    4. <flypig> important presence. The submission deadline for 2026 is (rainemak, 16:45:15)
    5. <flypig> approaching and I’m planning to request a Linux on Mobile stand (rainemak, 16:45:17)
    6. <flypig> again. As in previous years, it’d be fantastic to have Jolla on (rainemak, 16:45:18)
    7. <flypig> the stand. Would you consider joining the effort once again? (rainemak, 16:45:20)
    8. <Jolla> Excellent flypig that you’re again orchestrating this once again. (rainemak, 16:45:41)
    9. <Jolla> Very much appreciated. Indeed, the Linux on Mobile stand has been (rainemak, 16:45:41)
    10. <Jolla> successful in previous years. (rainemak, 16:45:41)
    11. <Jolla> (rainemak, 16:45:41)
    12. <Jolla> Yes, we are joining. Who are joining is not yet confirmed but most (rainemak, 16:45:41)
    13. <Jolla> likely at least Sami and Raine. (rainemak, 16:45:43)
    14. <Jolla> (rainemak, 16:45:44)
    15. <Jolla> Flypig, do you need anything from us? (rainemak, 16:45:46)
    16. https://fsfe.org/activities/android/ (flypig, 16:56:46)

  7. SFOS / Jolla pot. changes regarding the already inforced EU Cyber Resilience Act (5mins -- tmindrup) (rainemak, 16:59:33)
    1. <tmindrup> The EU Cyber Resilience Act (CRA) L_202402847EN.000101.fmx.xml (rainemak, 16:59:33)
    2. <tmindrup> imposes mandatory cybersecurity requirements on all products (rainemak, 16:59:33)
    3. <tmindrup> with digital elements sold in the EU, with consequences (rainemak, 16:59:33)
    4. <tmindrup> including significant fines, market access restrictions, and (rainemak, 16:59:33)
    5. <tmindrup> the loss of the CE marking for non-compliant products. (rainemak, 16:59:35)
    6. <tmindrup> Manufacturers, importers, and distributors face obligations to (rainemak, 16:59:39)
    7. <tmindrup> integrate security into product lifecycles, and some critical (rainemak, 16:59:41)
    8. <tmindrup> products must undergo third-party assessments. The regulation’s (rainemak, 16:59:43)
    9. <tmindrup> aim is to increase product security, but it creates challenges (rainemak, 16:59:45)
    10. <tmindrup> for businesses, especially smaller ones, in terms of compliance (rainemak, 16:59:47)
    11. <tmindrup> costs, testing, and the need for continuous security updates. (rainemak, 16:59:49)
    12. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847 (rainemak, 16:59:51)
    13. <Jolla> Let’s take this more like a discussion topic. (rainemak, 16:59:53)

  8. Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:05:46)
    1. https://github.com/sailfishos/gst-droid/pull/83 (flypig, 17:06:57)
    2. https://github.com/sailfishos/gst-droid/pull/83 (rainemak, 17:07:49)

  9. General discussion (10 mins or something) (rainemak, 17:12:11)
    1. https://fosstodon.org/@piggz/115383533267498846 (flypig, 17:15:38)
    2. https://fosstodon.org/@piggz/115385355972301576 (flypig, 17:17:15)

  10. Next meeting time and date (2 mins) (rainemak, 17:27:19)
    1. Next meeting will be held on Thursday 6th November 2025 at 04:00pm UTC: 2025-11-06T1600Z (rainemak, 17:33:00)


Meeting ended at 17:33:17 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (216)
  2. flypig (52)
  3. poetaster (23)
  4. abr (15)
  5. roundedrectangl (12)
  6. ExTechOp (11)
  7. direc85[m] (11)
  8. mal (8)
  9. Keto (7)
  10. piggz[m] (7)
  11. pherjung[m] (7)
  12. nephros (6)
  13. TheKit[m] (3)
  14. sailbot (2)
  15. Cryx[m] (2)
  16. Fellfrosch (1)
  17. legacychimera247 (1)
  18. Raymaen[m] (1)


Generated by MeetBot 0.1.4.