================================================================================= #sailfishos-meeting: Sailfish OS, open source, collaboration -- 23rd October 2025 ================================================================================= Meeting started by rainemak at 16:00:05 UTC. The full logs are available at https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2025/sailfishos-meeting.2025-10-23-16.00.log.html . Meeting summary --------------- * Meeting information and agenda can be found here: (rainemak, 16:00:05) * LINK: https://forum.sailfishos.org/t/25096 (rainemak, 16:00:05) * Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:05) * Otto Mäkelä, community (ExTechOp, 16:00:09) * Raine Mäkeläinen, Jolla (rainemak, 16:00:17) * Matti Viljanen, Jolla (direc85[m], 16:00:39) * roundedrectangle, community (roundedrectangl, 16:00:56) * Pami Ketolainen, Jolla (Keto, 16:01:54) * Fellfrosch. community (Fellfrosch, 16:02:20) * piggz community (piggz[m], 16:02:49) * mal, Jolla (mal, 16:02:59) * LINK: https://forum.sailfishos.org/t/sailfish-community-news-16th-october-2025-a-new-writer/25006 (rainemak, 16:04:30) * WPA3 status update (5 mins -- KeeperoftheKeys) (rainemak, 16:05:09) * I recently installed some simple Open Source IoT (rainemak, 16:05:21) * switches and was very surprised to find them supporting (rainemak, 16:05:21) * WPA3, this makes my Jolla phone the only thing (rainemak, 16:05:21) * preventing me from switching our home network to WPA3. I (rainemak, 16:05:21) * recall that there has been some work on this in the past (rainemak, 16:05:21) * where do things stand? Based on a little of my own (rainemak, 16:05:23) * testing (see below) it seems like it should be “in (rainemak, 16:05:24) * reach/spitting distance”. (rainemak, 16:05:26) * (rainemak, 16:05:28) * WPA3 is mostly a software issue, I have seen it working (rainemak, 16:05:30) * on Linux laptops that were built years before anyone (rainemak, 16:05:32) * even thought about WPA3, as far as I recall connman (rainemak, 16:05:34) * / wpasupplicant would need to be updated for this. (rainemak, 16:05:38) * (rainemak, 16:05:40) * Software versions: (rainemak, 16:05:42) * (rainemak, 16:05:44) * * 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) * * Per a wpa_supplicant changelog it added WPA3 in 2.10 (rainemak, 16:05:49) * and on my phone I find 2.11 and I was able to manually (rainemak, 16:05:51) * connect using it (wpa_supplicant -i wlan0 -c (rainemak, 16:05:53) * local.conf) this did not set the correct IP address (rainemak, 16:05:55) * from my router, I need to check with another device if (rainemak, 16:05:57) * this is a config issue of the testing SSID or an issue (rainemak, 16:05:59) * with the phone but after manually setting the correct (rainemak, 16:06:01) * IP address (ip addr add…) I was able to “prove” that I (rainemak, 16:06:03) * indeed connected successfully to the WPA3 SSID. (rainemak, 16:06:05) * To do all of this I also had to do some gymnastics (rainemak, 16:06:09) * with enabling/disabling wireless in the GUI to allow (rainemak, 16:06:11) * wpa_supplicant to grab control of wlan0 from connman. (rainemak, 16:06:13) * LINK: https://www.phoronix.com/news/ConnMan-1.41-IWD-1.23 (rainemak, 16:06:15) * LINK: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/refs/heads/main/wpa_supplicant/ChangeLog (rainemak, 16:06:17) * The support for WPA3 in newer connman version would not directly (rainemak, 16:06:20) * enable WPA3 support in Sailfish OS because we have a custom wifi (rainemak, 16:06:22) * plugin which needs adapting to support WPA3. Also higher level (rainemak, 16:06:24) * code using connman needs to be adapted to support WPA3 type. There (rainemak, 16:06:26) * is work in progress code for those but it does not work reliably (rainemak, 16:06:28) * on all devices yet and was missing some parts about correctly (rainemak, 16:06:30) * reporting type to higher level. (rainemak, 16:06:32) * pherjung, Community (pherjung[m], 16:07:58) * David Llewellyn-Jones, community; and of course late. (flypig, 16:08:03) * Raymaen, Community (Raymaen[m], 16:08:54) * LINK: https://github.com/sailfishos/connman/blob/master/connman/plugins/sailfish_wifi.c (rainemak, 16:12:11) * Link to Sailfish OS wifi plugin (rainemak, 16:12:51) * nephros, community, later-comer (nephros, 16:14:28) * Allow apps to use nextcloud client or add ability to configure folder sync (10mins -- KeeperoftheKeys) (rainemak, 16:15:14) * As documented in this topic Sailsync OwnCloud does not (rainemak, 16:15:14) * work out of the box with recent versions of nextcloud (rainemak, 16:15:14) * and due to Qt limitations this is only going to get (rainemak, 16:15:14) * worse, @nephros has built a newer drop in binary with Qt (rainemak, 16:15:15) * 5.15 but that is also a solution that will only hold so (rainemak, 16:15:17) * long and while those who run NC instances where they (rainemak, 16:15:19) * have full control can lower the (rainemak, 16:15:21) * minimum.supported.desktop.version they are taking a risk (rainemak, 16:15:23) * as per the NC devs. (rainemak, 16:15:25) * IMHO Sailsync OwnCloud provides a functionality that (rainemak, 16:15:27) * should just be part of the NC account settings, if that (rainemak, 16:15:29) * is not a possibility then it would be nice if it could (rainemak, 16:15:31) * leverage the builtin client (and credentials) instead of (rainemak, 16:15:33) * needing to ship its own. (rainemak, 16:15:35) * LINK: https://forum.sailfishos.org/t/22969 (rainemak, 16:15:39) * NextCloud account (and related components) could be our next (rainemak, 16:15:41) * component to open source which would also enable contributions (rainemak, 16:15:43) * from the Sailsync OwnCloud towards platform NextCloud. We shall (rainemak, 16:15:45) * take this into account as we plan this. In many cases app (rainemak, 16:15:47) * functionalities easily provide more value when / if they are (rainemak, 16:15:49) * implemented as an operating system feature. (rainemak, 16:15:51) * poetaster is late (poetaster, 16:17:05) * LINK: https://github.com/sailfishos/buteo-sync-plugin-caldav/ (abr, 16:30:32) * Support more codecs in QtMultimedia GStreamer plugin (5 mins -- roundedrectangl) (rainemak, 16:32:11) * Information about supported audio capture codecs in (rainemak, 16:32:22) * QtMultimedia GStreamer plugin seems to be hardcoded in (rainemak, 16:32:22) * Qt 5.6 here: qtmultimedia/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp (rainemak, 16:32:22) * at mer-5.6 · sailfishos/qtmultimedia · GitHub. I know (rainemak, 16:32:22) * that there are no plans for changing the core behaviour (rainemak, 16:32:22) * of this in the near future, because that would require a (rainemak, 16:32:24) * Qt update. But are there any plans for, at least, adding (rainemak, 16:32:26) * more codecs (such as Opus) to that hard-coded list? And (rainemak, 16:32:28) * would a pull request adding this get accepted? (rainemak, 16:32:30) * Related: How to record opus audio programatically? (rainemak, 16:32:32) * LINK: https://github.com/sailfishos/qtmultimedia/blob/mer-5.6/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp (rainemak, 16:32:34) * LINK: https://forum.sailfishos.org/t/how-to-record-opus-audio-programatically/25139 (rainemak, 16:32:39) * It might be possible to enable some additional codecs but it needs (rainemak, 16:32:41) * to be tested that those actually work. Pull requests are always (rainemak, 16:32:43) * welcome and we’ll review and test them. (rainemak, 16:32:45) * Linux on Mobile stand at FOSDEM in 2026 (10mins -- flypig) (rainemak, 16:45:15) * FOSDEM (https://fosdem.org) will take place again in Brussels on (rainemak, 16:45:15) * the weekend of 31 January 2026. In previous years we’ve had a (rainemak, 16:45:15) * very successful Linux on Mobile stand with Jolla being a big and (rainemak, 16:45:15) * important presence. The submission deadline for 2026 is (rainemak, 16:45:15) * approaching and I’m planning to request a Linux on Mobile stand (rainemak, 16:45:17) * again. As in previous years, it’d be fantastic to have Jolla on (rainemak, 16:45:18) * the stand. Would you consider joining the effort once again? (rainemak, 16:45:20) * Excellent flypig that you’re again orchestrating this once again. (rainemak, 16:45:41) * Very much appreciated. Indeed, the Linux on Mobile stand has been (rainemak, 16:45:41) * successful in previous years. (rainemak, 16:45:41) * (rainemak, 16:45:41) * Yes, we are joining. Who are joining is not yet confirmed but most (rainemak, 16:45:41) * likely at least Sami and Raine. (rainemak, 16:45:43) * (rainemak, 16:45:44) * Flypig, do you need anything from us? (rainemak, 16:45:46) * LINK: https://fsfe.org/activities/android/ (flypig, 16:56:46) * SFOS / Jolla pot. changes regarding the already inforced EU Cyber Resilience Act (5mins -- tmindrup) (rainemak, 16:59:33) * The EU Cyber Resilience Act (CRA) L_202402847EN.000101.fmx.xml (rainemak, 16:59:33) * imposes mandatory cybersecurity requirements on all products (rainemak, 16:59:33) * with digital elements sold in the EU, with consequences (rainemak, 16:59:33) * including significant fines, market access restrictions, and (rainemak, 16:59:33) * the loss of the CE marking for non-compliant products. (rainemak, 16:59:35) * Manufacturers, importers, and distributors face obligations to (rainemak, 16:59:39) * integrate security into product lifecycles, and some critical (rainemak, 16:59:41) * products must undergo third-party assessments. The regulation’s (rainemak, 16:59:43) * aim is to increase product security, but it creates challenges (rainemak, 16:59:45) * for businesses, especially smaller ones, in terms of compliance (rainemak, 16:59:47) * costs, testing, and the need for continuous security updates. (rainemak, 16:59:49) * LINK: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847 (rainemak, 16:59:51) * Let’s take this more like a discussion topic. (rainemak, 16:59:53) * Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:05:46) * LINK: https://github.com/sailfishos/gst-droid/pull/83 (flypig, 17:06:57) * LINK: https://github.com/sailfishos/gst-droid/pull/83 (rainemak, 17:07:49) * General discussion (10 mins or something) (rainemak, 17:12:11) * LINK: https://fosstodon.org/@piggz/115383533267498846 (flypig, 17:15:38) * LINK: https://fosstodon.org/@piggz/115385355972301576 (flypig, 17:17:15) * Next meeting time and date (2 mins) (rainemak, 17:27:19) * 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. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * rainemak (216) * flypig (52) * poetaster (23) * abr (15) * roundedrectangl (12) * ExTechOp (11) * direc85[m] (11) * mal (8) * Keto (7) * piggz[m] (7) * pherjung[m] (7) * nephros (6) * TheKit[m] (3) * sailbot (2) * Cryx[m] (2) * Fellfrosch (1) * legacychimera247 (1) * Raymaen[m] (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot