| ExTechOp | Good morning everyone! | 06:57 |
|---|---|---|
| poetaster | Good morning! | 06:57 |
| attah | Good morning | 06:57 |
| Solrac[m] | Good Morning/Evening | 06:58 |
| dcaliste | Hello ! | 06:59 |
| flypig | Good morning! | 06:59 |
| rainemak | Good morning! | 06:59 |
| flypig | Okay, let's begin :) | 07:00 |
| flypig | #startmeeting Sailfish OS, open source, collaboration -- 7th July 2022 | 07:00 |
| sailbot | Meeting started Thu Jul 7 07:00:57 2022 UTC. The chair is flypig. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:00 |
| sailbot | Useful Commands: #action #agreed #help #info #idea #link #topic. | 07:00 |
| *** sailbot changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:00 | |
| flypig | #info Meeting information and agenda can be found here: | 07:01 |
| flypig | #link https://forum.sailfishos.org/t/community-meeting-on-irc-7th-july-2022/12069 | 07:01 |
| flypig | I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and nose wearing. | 07:01 |
| flypig | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 07:01 |
| *** sailbot changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:01 | |
| ExTechOp | #info Otto Mäkelä, community | 07:01 |
| flypig | #info David Llewellyn-Jones, sailor @ jolla | 07:01 |
| Solrac[m] | #info Carlos Orama, community | 07:01 |
| poetaster | #info poetaster (Mark), community | 07:01 |
| attah | #info Anton Thomasson, community | 07:01 |
| Nico | #info Nico, community | 07:01 |
| rainemak | #info Raine Mäkeläinen, sailor @ Jolla | 07:03 |
| dcaliste | #info Damien Caliste, community | 07:03 |
| flypig | A nice community turn out today! | 07:03 |
| fridlmue | #info fridlmue, community | 07:04 |
| sledges | #info Simonas Leleiva -- privateer | 07:04 |
| flypig | The community have it at 7-3 today! It's great to have everyone here, and good to see we have at least one of our questioners too. | 07:06 |
| Thaodan | #info Björn Bidar - sailor @ Jolla | 07:06 |
| poetaster | Ah, good company :) | 07:06 |
| flypig | Please continue to add your info during the meeting if anyone was missed. | 07:07 |
| flypig | Do we have remote though? | 07:07 |
| flypig | #topic PulseAudio update (5 min -- asked by remote) | 07:07 |
| *** sailbot changes topic to "PulseAudio update (5 min -- asked by remote) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:07 | |
| flypig | #info <remote> I'd like to inquire into PulseAudio version bump. | 07:07 |
| flypig | #info <remote> Version 15 brings high quality codecs support for BT headphones. | 07:07 |
| flypig | #info <remote> Is it planned? | 07:07 |
| flypig | This is our first question. Here's our prepared answer. | 07:08 |
| flypig | #info <Jolla> For general information, the PulseAudio repo can be found here: | 07:08 |
| flypig | #link https://github.com/sailfishos/pulseaudio/ | 07:08 |
| flypig | #info <Jolla> As can be seen there, we're currently on version 14.2, updated with the following commit. | 07:08 |
| flypig | #link https://github.com/sailfishos/pulseaudio/commit/e0a3accd8840ecc728c32c1607c2950be5329eb8 | 07:08 |
| flypig | #info <Jolla> Although it's no guarantee of future timescales, historically we've updated to even versions, with a roughly 18 month cadence between updates. | 07:08 |
| flypig | #info <Jolla> Theres no update planned per se now. It's highly likely that this will happen at some point. | 07:08 |
| flypig | #info <Jolla> Unfortunately our Audio expert is on summer holiday, thus we could not get his opinion for the PulseAudio update. | 07:08 |
| flypig | #info <Jolla> We therefore propose that we come back to this topic during the next meeting in two weeks' time. | 07:08 |
| flypig | That's the answer. Any comments/thoughts? Does returning to it sound okay? | 07:09 |
| poetaster | Sounds good. | 07:09 |
| Nico | Where there any thoughts of switching to pipewire? :D | 07:09 |
| Solrac[m] | When reading the question, I thought about Pipewire as well. | 07:10 |
| rainemak | We did discuss switching to pipewire last year but that's much bigger effort | 07:10 |
| Nico | But yeah, returning sounds okay :3 | 07:10 |
| poetaster | I'm still an alsa+jack guy :) | 07:11 |
| flypig | rainemak, that's useful info I think; I'll add it to the minutes | 07:11 |
| flypig | #info <rainemak>: We did discuss switching to pipewire last year but that's much bigger effort | 07:11 |
| Nico | rainemak, agreed. It is also still a bit crashy here, leaving me without audio after a week of runtime sometimes. But it has some nice audio routing stuff :3 | 07:11 |
| Nico | Maybe in 18 months... | 07:12 |
| flypig | remote seems to be concerned about Bluetooth audio codecs. Would Pipewire help with that? | 07:12 |
| Thaodan | I think creating a PR is never wrong to push things along | 07:12 |
| attah | That is my impression... as should PA 15 | 07:12 |
| Nico | Yes, pipewire has those codecs too and better audio input handling too, afaik | 07:12 |
| Nico | (over bluetooth) | 07:13 |
| flypig | #info Both PulseAudio 15 and Pipewire would help with Bluetooth audio codec support. | 07:13 |
| Thaodan | pipewire is a whole different beast it would require to have new pipewire modules | 07:13 |
| attah | I'm afraid PulseAudio on Sailfish has much more than one commit on top of master... | 07:14 |
| Nico | Well, you can use a lot of pulseaudio client stuff on top of pipewire, not sure about modules though | 07:14 |
| flypig | attah, your point is that creating a PR isn't straightforward? | 07:14 |
| Nico | And it is probably long term where desktop linux will move to | 07:14 |
| attah | Precisely - still worthwhile... just hard | 07:15 |
| Nico | But there is certainly no rush | 07:15 |
| attah | The info above sounded like it was only the one commit | 07:16 |
| flypig | attah, yes, sorry, that's poor communication from me I'm afraid. | 07:16 |
| attah | No worries, good to have that cleared up | 07:16 |
| Thaodan | it's not just one commit but rebasign the current SailfishOS version can be still done. | 07:17 |
| Thaodan | pipewire would require porting all the routing and policy modules | 07:17 |
| Thaodan | jusa could say more | 07:17 |
| Thaodan | (by rebasing I meant rebasign sfos pa) | 07:18 |
| flypig | Not a small undertaking by the sounds of it. | 07:18 |
| poetaster | I don't see the demand? | 07:18 |
| poetaster | Other than broad scale abandonment of pulse.... | 07:19 |
| Nico | Well, it has lower latency and better sound quality here than pulseaudio | 07:19 |
| Nico | And better sound routing | 07:19 |
| Nico | And better bluetooth audio support | 07:19 |
| Nico | I.e. patapon is unplayable on my desktop with pulse | 07:19 |
| poetaster | alsa + jack has both of those, but that doesn't make it appropriate. | 07:19 |
| poetaster | what is patapon? | 07:20 |
| Nico | Well, PW has the jack API implemented! | 07:20 |
| Nico | patapon is a rythm game | 07:20 |
| flypig | Good discussion and useful info, but I let this run a bit over already. Anything to add to the minutes before we move on? | 07:21 |
| poetaster | Sorry, my audio machines are stripped down for 24 channel (firewire, BOB) audio recording. I'm not a fan of pulse. just not sure the effort is called for now? | 07:21 |
| Nico | Well, maybe not, but it does everything slightly better than pulse | 07:21 |
| Nico | But yeah, we can also discuss that next meeting :3 | 07:22 |
| poetaster | cool. reading to do. | 07:22 |
| flypig | Nico, having a dedicated Pipewire discussion would be interesting for sure. | 07:22 |
| flypig | Let's move on, otherwise poetaster won't get his question answered :) | 07:23 |
| Solrac[m] | Expanding on PW. While I think it may not see use in phones, or at least as commonly; I'd like to point out that because of the better routing, it can open more possibilities, such as midi devices and maybe multiple mics, granted an application could make use of these. | 07:23 |
| Solrac[m] | Oh my apologies | 07:23 |
| flypig | Don't apologise; that's good info to have. | 07:23 |
| flypig | We can return to PW in the General Topic at the end too. | 07:23 |
| flypig | #topic RGB channel swapping in Canvas, Label, etc. (10 -- asked by poetaster) | 07:23 |
| *** sailbot changes topic to "RGB channel swapping in Canvas, Label, etc. (10 -- asked by poetaster) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:23 | |
| dcaliste | I may mention https://forum.sailfishos.org/t/pipewire-replacing-pulseaudio/6196 for records also. | 07:23 |
| dcaliste | Oops sorry a bit too late… | 07:24 |
| flypig | #undo | 07:24 |
| sailbot | Removing item from minutes: <MeetBot.items.Topic object at 0x7f23b9c24b00> | 07:24 |
| flypig | #info https://forum.sailfishos.org/t/pipewire-replacing-pulseaudio/6196 | 07:24 |
| flypig | #topic RGB channel swapping in Canvas, Label, etc. (10 -- asked by poetaster) | 07:24 |
| *** sailbot changes topic to "RGB channel swapping in Canvas, Label, etc. (10 -- asked by poetaster) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:24 | |
| flypig | Hopefully that will work... | 07:24 |
| flypig | #info <poetaster> drawImage of Canvas renders images channel swapped. | 07:24 |
| flypig | #info <poetaster> To expand see the Stopmotion code which applies the same fixes I applied to "Paint". | 07:24 |
| flypig | #info <poetaster> Beside the RBG<->GBR swapping it also fixes the issue that image meta data (orientation for Portrait photos) is not being used when loading a url directly to Canvas. | 07:25 |
| flypig | #link https://github.com/poetaster/harbour-stopmotion/blob/ee5ab00ab4328151ba0d9d78f7bca192c493a15a/src/ImageProvider.h#L95 | 07:25 |
| flypig | #info See also: | 07:25 |
| flypig | #link https://forum.sailfishos.org/t/canvas-requestpaint-renders-image-data-tinted-blue/11349 | 07:25 |
| flypig | #link https://forum.sailfishos.org/t/qml-label-dispays-images-with-a-blue-ish-tint/8818 | 07:25 |
| flypig | I had trouble summarising your question a bit poetaster; hopefully that makes sense. Here's our prepared answer. | 07:25 |
| flypig | #info <Jolla> Thank you poetaster for raising this, and also to gabrielg, Edz, attah and others in the forum for all your excellent detective work. This made understanding the problem a lot easier. | 07:26 |
| flypig | #info <Jolla> We explored this a bit more internally and think we've got a solution. The qtscenegraph-adaptation package is used to store large images in hardware textures to speed up rendering. | 07:26 |
| poetaster | Thank you. I suck. Too many digressions. | 07:26 |
| flypig | #info <Jolla> On hybris devices, when such an image needs to be accessed by the CPU it's done via the HybrisTextureFactory::image() function, in which eglHybrisLockNativeBuffer locks the buffer and provides a pointer to data in the buffer's native format. | 07:26 |
| flypig | #info <Jolla> This can be either hybris's BGRA_8888 or RGBA_8888 and in this case it's hybris's RGBA_8888 format. Then the buffer is copied into a QImage(). | 07:26 |
| flypig | #info <Jolla> But when we copy the data out we only specify Qt formats which are equivalent to hybris's BGRA_8888 order, consequently RGBA_8888 images come out with their colours swapped. The following change should fix it: | 07:26 |
| flypig | #link https://github.com/sailfishos/qtscenegraph-adaptation/pull/2 | 07:26 |
| flypig | #info <Jolla> However, we've not had a chance to test this across devices or use cases. | 07:26 |
| flypig | #info <Jolla> Before merging the change, it would be especially helpful if members of the community could test the change with various apps on different devices. | 07:27 |
| flypig | #info <Jolla> Testing it requires building and deploying the fixed branch of the qtscenegraph-adaptation package. Building can be performed using the application SDK. | 07:27 |
| Nico | Wow, that is nice! | 07:27 |
| attah | Woohoo! | 07:27 |
| poetaster | Great! | 07:27 |
| flypig | No worries poetaster, the question made sense, just a little hard to summarise. | 07:27 |
| dcaliste | Great investigations from both sides. | 07:27 |
| flypig | Yes, indeed, as I understand it the info everyone provided on the forum was a big help. | 07:28 |
| flypig | Would anyone be able to test it? | 07:29 |
| poetaster | I'll try. | 07:29 |
| flypig | Super, thank you poetaster. It would be a great help. | 07:29 |
| flypig | If you run into any trouble getting the package built, message me (but I tested it out, and didn't hit anything unusual). | 07:29 |
| poetaster | Cool. | 07:30 |
| dcaliste | Testing compilation at the moment in application SDK, everything run fine. | 07:31 |
| flypig | poetaster, you have two apps with this issue, is that correct? | 07:31 |
| flypig | Great, thanks for checking dcaliste. | 07:31 |
| poetaster | 3 | 07:31 |
| flypig | Paint, Stopmotion and... ? | 07:32 |
| poetaster | and tidings, presumably | 07:32 |
| flypig | Ah yes, Tidings. | 07:32 |
| flypig | What is the status of Stopmotion? | 07:33 |
| poetaster | It's functional but still a 'raw' prototype. I did party tricks with it last weekend. people said 'ooh!' | 07:33 |
| flypig | I haven't had a chance to look at it, but am excited to see the results, I have to say. | 07:34 |
| attah | that's the sound of success | 07:34 |
| flypig | Yeah, good to hear you got a good reception :) | 07:34 |
| poetaster | a lot of ideas/inspiration from several sources. | 07:34 |
| flypig | That's the best way :) | 07:35 |
| poetaster | True! | 07:35 |
| poetaster | dcaliste, you've finished all the testing I presume :) | 07:35 |
| flypig | Haha :) | 07:35 |
| flypig | We're hitting time on this. Anything anyone would like added to the minutes before we move on? | 07:36 |
| poetaster | just thanks! | 07:36 |
| attah | indeed, nicely done | 07:36 |
| flypig | #info poetaster expressed his appreciation :) | 07:37 |
| dcaliste | I'm trying it on device. As far as I remember the issue was visible in tidings. But I've a slow data mobile connection at the moment. I need to get some example of RSS flux were it failed. | 07:37 |
| Nico | That's a rare achievement! | 07:37 |
| flypig | I'll pass the thanks on too. | 07:37 |
| flypig | dcaliste, we'll move to the next question, but let us know if you find out. | 07:37 |
| flypig | #topic Community Bug Coordination Team summary (5 min -- asked by pherjung) | 07:38 |
| *** sailbot changes topic to "Community Bug Coordination Team summary (5 min -- asked by pherjung) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:38 | |
| flypig | #info <pherjung> Untracked bug reports | 07:38 |
| flypig | #link https://forum.sailfishos.org/t/community-meeting-on-irc-7th-july-2022/12069/2 | 07:38 |
| flypig | This is our usual Community But Coordination Team summary. | 07:38 |
| flypig | #info <Jolla> The Community Bug Coordination Team have done a superb job once again this fortnight. | 07:38 |
| flypig | #info <Jolla> As a result of their work, we now have: | 07:38 |
| flypig | #info <Jolla> - 10 new high quality bug reports recorded internally and tagged as "tracked". | 07:38 |
| flypig | #info <Jolla> - 5 topics moved into different categories as they weren't really bugs. | 07:38 |
| flypig | #info <Jolla> - 4 bug reports marked as "pending" more info. | 07:38 |
| flypig | #info <Jolla> - 2 bug reports tagged as "fixed". | 07:38 |
| flypig | #info <Jolla> - 2 bug reports related to RBG-BBR swapping which hopefully we'll be able to mark as "fixed" soon. | 07:38 |
| flypig | Are there any CBCT members here? | 07:39 |
| Nico | Well, in theory I am in the same chat group, but not really active rn ;p | 07:39 |
| Nico | So no idea what there would be to add, apart from the usual thank you :3 | 07:40 |
| flypig | Yes, thank you from me too. I'm continually impressed, especially with how the team tests the bugs and writes up notes for how to reproduce them. | 07:40 |
| Nico | I am too :D | 07:41 |
| poetaster | Kudos from me too. I find it increases signal to noise a great deal. | 07:42 |
| flypig | Okay, we shall move on then. | 07:43 |
| flypig | #topic Open Pull Requests (5 min -- asked by rainemak) | 07:43 |
| *** sailbot changes topic to "Open Pull Requests (5 min -- asked by rainemak) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:43 | |
| flypig | #info <flypig> During the last meeting we agreed to have a section on open Pull Requests, to help prioritise our work in reviewing them. What did we get? | 07:43 |
| flypig | #info <Jolla> We didn't get any submitted before the meeting, but everyone is welcome to raise interesting PRs for us to consider now. | 07:43 |
| flypig | So, this is a chance to raise any lingering PRs that aren't getting the attention they deserve. | 07:44 |
| Nico | Heh, I didn't open any, because I was busy with work and other stuff, I'll get there some day! | 07:44 |
| flypig | There is, of course, no obligation :) But for future reference, you can propose others' PRs as well. | 07:45 |
| Thaodan | Most PRs open right now are either wip or not so important to mention I think. | 07:45 |
| flypig | Okay, that's useful to know. Thanks Thaodan. | 07:46 |
| Nico | Yeah, I haven't seen any complaints about lack of review the last 2 weeks .-. | 07:46 |
| flypig | This is good. | 07:46 |
| Nico | Oh, maybe I can dig one up | 07:46 |
| Thaodan | Some are great as usual but are discussed elsewhere e.g. dcaliste | 07:46 |
| Nico | dcaliste has a few browser PRs: https://github.com/sailfishos/sailfish-browser/pull/957 | 07:47 |
| Nico | https://github.com/sailfishos/sailfish-browser/pull/959 | 07:47 |
| dcaliste | Indeed, pvuorela thanksfully took some of his time before summer vacations to give feedback on calendar stack ones. Thanks to him. | 07:47 |
| Thaodan | I wouldn't mind more testers on: https://github.com/sailfishos/droidmedia/pull/92 | 07:48 |
| flypig | #info dcaliste has a couple of browser PRs that have been opened for some time. | 07:48 |
| flypig | #link https://github.com/sailfishos/sailfish-browser/pull/957 | 07:48 |
| flypig | #link https://github.com/sailfishos/sailfish-browser/pull/959 | 07:49 |
| Thaodan | I like dcaliste's PRs. The press and hold scheme sounds like good idea. | 07:49 |
| flypig | #info Thaodan requested testing on one of his PRs. | 07:49 |
| flypig | #link https://github.com/sailfishos/droidmedia/pull/92 | 07:49 |
| Nico | I guess those might need feedback from whoever is responsible for design stuff | 07:49 |
| Thaodan | I almost tried to do this out of instinct. | 07:49 |
| Nico | Thaodan, same | 07:49 |
| dcaliste | Nico, about 959, I've used it for a while and while I like the consistency, I find it a bit cumbersome to have to long-press and them tap to close one tab, which is the usual action I'm doing. | 07:49 |
| flypig | rainemak, do you have any comment on dcaliste's browser PRs? | 07:50 |
| dcaliste | The target to close is easier to get though. But I'm not totally convinced of its advantages. | 07:50 |
| dcaliste | It requires more discussion and feedback from people who tried it I think. | 07:50 |
| Nico | dcaliste, sounds reasonable, maybe moing the close button to below the tab cards is bettter? | 07:50 |
| Nico | And not doing the long press | 07:51 |
| Nico | (I mostly close my currently open tab using the menu action instead of the tab view) | 07:51 |
| attah | :) | 07:51 |
| dcaliste | Nico, I should change my habit for the menu then ;) | 07:52 |
| attah | I think long-press is a good pattern here, that would allow slightly bigger buttons too... the current one is hard to hit | 07:52 |
| Nico | I think I'll just try out the long press patch for a bit | 07:52 |
| dcaliste | Just for records, one way to see all opened PR on SailfishOS is https://github.com/pulls?q=is%3Aopen+is%3Apr+org%3Asailfishos | 07:52 |
| thilo[m] | Thaodan: how do we know if the pr is working? | 07:53 |
| flypig | "No results matched your search."? | 07:53 |
| dcaliste | flypig, maybe you need to get logged in ? Strange. | 07:54 |
| Thaodan | thilo[m]: nothing breaks and for affected devices the camera app doesn't freeze | 07:54 |
| ExTechOp | Just tried that URL when not logged in, it gave the 404 page but allowed me to log in and then showed the PRs | 07:54 |
| thilo[m] | Sounds doable ;) | 07:55 |
| flypig | I think it's an encoding thing. The following works for me: https://github.com/pulls?q=is:open+is:Apr+org:sailfishos+ | 07:55 |
| pherjung | Hi, | 07:56 |
| pherjung | I'm bit a late :) | 07:56 |
| flypig | Nice to have you here pherjung. | 07:56 |
| poetaster | ditto! | 07:56 |
| pherjung | :) | 07:56 |
| Solrac[m] | Welcome~ | 07:57 |
| flypig | #info <dcaliste> Just for records, one way to see all opened PR on SailfishOS is | 07:57 |
| flypig | #link https://github.com/pulls?q=is%3Aopen+is%3Apr+org%3Asailfishos | 07:57 |
| Nico | We already did the bug roundup, did you have anything to add? | 07:57 |
| flypig | Let me move us on to General discussion; thanks for the info about the PRs. | 07:57 |
| flypig | #topic General discussion (20 min) | 07:57 |
| *** sailbot changes topic to "General discussion (20 min) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 07:57 | |
| pherjung | I have an question. Could it be possible to do the same as PR review, but with bug reports? There are some I have no idea how to reproduce them | 07:57 |
| pherjung | Idea is to pick one and Jolla give some hint where we, the community, should look | 07:58 |
| flypig | It sounds like a nice idea to me. Did you have a bug in mind for an example? | 07:59 |
| pherjung | Not now, but we can pick up one for the next meeting just as test | 07:59 |
| ExTechOp | There's the very-long-standing issue of failing network switching with Android applications, here's one leaf of the tree: https://forum.sailfishos.org/t/android-connectivity-issues-analysis/12091 | 07:59 |
| ExTechOp | This hits me pretty much on a daily basis (home wifi / phone network while going to work / work wifi), is anyone working seriously on this? | 07:59 |
| rainemak | I could try to give a look & comment to dcaliste's browser PRs during this week. | 08:00 |
| attah | Are there any news on the ownership and "super secret engineering effort" front? | 08:01 |
| pherjung | this one is already tracked, no? | 08:01 |
| Nico | Oh, what SSEE? I never heard of that, sounds interesting! | 08:01 |
| flypig | pherjung, I think that'd be a great idea. Could you flag it in advance in your bug roundup? | 08:01 |
| pherjung | I'll do :) | 08:02 |
| flypig | Great, thank you. If it works, we can then make it a regular thing. | 08:02 |
| pherjung | cool | 08:02 |
| flypig | rainemak, I will add your comment to the minutes, I think that's nice to hear :) | 08:03 |
| flypig | #info <rainemak> I could try to give a look & comment to dcaliste's browser PRs during this week. | 08:03 |
| rainemak | #info all Sailfish OS PRs: click the "Pull requests" link at the header, enter "is:open is:pr org:sailfishos" to the search field, press enter | 08:04 |
| flypig | ExTechOp, I know there has been a lot of work on it (and fixes) in the past, and my understanding is that work continues, but I'd have to check to make sure. | 08:04 |
| flypig | #info ExTechOp raised the issue of long-standing network issues with Android. | 08:05 |
| flypig | #link https://forum.sailfishos.org/t/android-connectivity-issues-analysis/12091 | 08:05 |
| ExTechOp | As I said, still there on a daily basis. Occasionally Utilities / Restart network helps, sometimes the only thing to do is to reboot the phone. | 08:05 |
| flypig | Thanks rainemak, useful info. | 08:05 |
| pherjung | flypig: here an example: https://forum.sailfishos.org/t/weather-display-on-events-screen-constantly-loses-network-connection/11962/ | 08:06 |
| pherjung | could be great for instance to enable some logs | 08:06 |
| pherjung | so we can find how to easily reproduce it | 08:07 |
| Nico | I know someone whose phone just doesn't connect to the mobile network at all after boot and needs toggling of the flightmode to connect... | 08:07 |
| Nico | I don't know if that was a bad flash or not yet though, but it worked at some point | 08:07 |
| flypig | So the question, pherjung, is how to help find a way to reproduce the issue reliably? | 08:08 |
| pherjung | yes | 08:08 |
| sledges | ExTechOp: also try restarting App Support, as last resort before reboot | 08:08 |
| dcaliste | Sorry got side tracked. Thank you rainemak. | 08:08 |
| attah | No company news to share then? | 08:10 |
| flypig | pherjung, I would say that some of these don't have an easy answer unfortunately, but if you could add it for the next meeting, that would be great. | 08:11 |
| Nico | attah, did you buy Jolla yet? :D | 08:11 |
| attah | i wish | 08:11 |
| Nico | No news then... | 08:12 |
| flypig | attah, thanks for asking, but I think there's no additional news to share today. | 08:12 |
| attah | okay, thanks for info | 08:12 |
| flypig | Do please ask again though :) | 08:12 |
| Nico | Does it smell like there might be news in the near future? | 08:12 |
| attah | count on it | 08:12 |
| pherjung | and about engineering work? | 08:12 |
| flypig | Anything particular related to the engineering work? | 08:13 |
| poetaster | having installed scenegraph (hybristexture config), reboot? restart lipstick? | 08:13 |
| attah | Since we don't know what it is... it is hard to be specific.... but how is it going? | 08:14 |
| pherjung | well, community news has been reduce to worg on engineering stuff. So we are curious which part | 08:14 |
| flypig | poetaster, in my testing, just restarting the app was enough, but restart lipstick if you want it across the board. | 08:14 |
| Nico | I'm sure they are porting to qt6 atm, right? | 08:14 |
| flypig | pherjung, ah, yes, it's in relation to that. Thanks for clarifying. | 08:14 |
| poetaster | sigh. | 08:15 |
| flypig | Oh, that's a bad sign. | 08:15 |
| attah | Nico: that is what i choose to believe too :P | 08:15 |
| poetaster | CONFIG += plugin verbose dither eglgralloctexture hybristexture ... no changes in app behaviour | 08:15 |
| Nico | attah: With a secret we can dream of anything we want! | 08:16 |
| flypig | poetaster, can you share a minimal working example of the problem? We used the one provided by Edz for testing, but maybe what you're seeing is something different. | 08:16 |
| attah | And you changed to the pr commit, not just downloaded it? (definitely not speaking from experience) | 08:18 |
| flypig | pherjung, attah, Nico, concerning engineering work, there's nothing specific to report, but if you want the situation expanded upon, I think best to ask a question for us to prepare an answer for in a future meeting. | 08:19 |
| poetaster | yup. But += could be wrong. | 08:19 |
| Nico | Well, I only heard about it just now! | 08:20 |
| flypig | poetaster, you shouldn't need to make any changes to *your* project to have the fix, you should just need to install the updated qtscenegraph-adaptation package. | 08:20 |
| flypig | Yes, sorry Nico, that's due to me following the conversation backwards poorly :) | 08:22 |
| poetaster | you need to specify in the scenegraph pro which (hybristexture for instance) to build | 08:22 |
| flypig | poetaster, okay, then I'm misunderstanding. Apologies. | 08:22 |
| Nico | flypig, no worries. Just spill the beans to apologize! (That's how this works, right?) ;p | 08:22 |
| attah | i just did "sfdk build" | 08:23 |
| flypig | Nico: :D | 08:23 |
| mal | hey, a small comment about pulseaudio updating, it needs first moving to meson since autotools support was dropped in pulseaudio 15, this means changing the custom patches to work with meson, I have done that but no pull requests yet, might need some more testing first | 08:23 |
| poetaster | Project MESSAGE: Enable the above features by adding them to the qmake config, for instance: | 08:24 |
| flypig | #info <mal> a small comment about pulseaudio updating, it needs first moving to meson since autotools support was dropped in pulseaudio 15, this means changing the custom patches to work with meson, I have done that but no pull requests yet, might need some more testing first | 08:24 |
| Nico | Mhm, meson, yummy. So much nicer than autotools | 08:24 |
| flypig | Thanks mal, nice info. | 08:24 |
| flypig | We are hitting time for today. Anything else to add to the minutes before we wrap up? | 08:24 |
| flypig | Alright, final topic then. | 08:27 |
| flypig | #info Next meeting will be held on Thursday 21st July 2022 at 07:00am UTC: 2022-07-21T0700Z | 08:27 |
| flypig | Oops, that was premature. | 08:27 |
| flypig | #undo | 08:27 |
| sailbot | Removing item from minutes: <MeetBot.items.Info object at 0x7f23b9be44e0> | 08:27 |
| flypig | #topic Next meeting time and date (5 min) | 08:27 |
| *** sailbot changes topic to "Next meeting time and date (5 min) (Meeting topic: Sailfish OS, open source, collaboration -- 7th July 2022)" | 08:27 | |
| flypig | Proposing Thursday 21st July at 07:00am UTC | 08:27 |
| Nico | 20 seconds to disagree, otherwise it is accepted? :D | 08:27 |
| ExTechOp | WorksForMe | 08:28 |
| flypig | ... 10 ... | 08:28 |
| poetaster | Ditto | 08:28 |
| flypig | Excellent. Let's go with that then. | 08:28 |
| flypig | 3 | 08:28 |
| flypig | 2 | 08:28 |
| flypig | 1 | 08:28 |
| poetaster | color fix works! | 08:28 |
| flypig | #info Next meeting will be held on Thursday 21st July 2022 at 07:00am UTC: 2022-07-21T0700Z | 08:28 |
| flypig | poetaster, fantastic! And just in time too :D | 08:28 |
| attah | Nice | 08:28 |
| poetaster | now for orientation :) | 08:28 |
| flypig | #info <poetaster> color fix works! | 08:28 |
| attah | Thanks for hosting | 08:29 |
| poetaster | ditto! | 08:29 |
| Nico | Thanks everyone! | 08:29 |
| flypig | And thanks everyone for joining and for the great discussion. | 08:29 |
| flypig | #endmeeting | 08:29 |
| sailbot | Meeting ended Thu Jul 7 08:29:17 2022 UTC. | 08:29 |
| sailbot | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-07-07-07.00.html | 08:29 |
| sailbot | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-07-07-07.00.txt | 08:29 |
| sailbot | Log: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-07-07-07.00.log.html | 08:29 |
| *** sailbot changes topic to "Next meeting will be held on Thursday 7th July 2022 at 07:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-7th-july-2022/12069" | 08:29 | |
| ExTechOp | Thanks, everyone! | 08:29 |
| poetaster | Yipee! | 08:29 |
| Solrac[m] | 🎊 | 08:29 |
| *** ChanServ changes topic to "Next meeting will be held on Thursday 21st July 2022 at 07:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-21st-july-2022/12221" | 08:32 | |
| sledges | 08:20 < Nico> Well, I only heard about it just now! | 08:57 |
| sledges | Nico: things are much more active than predicted here: https://forum.sailfishos.org/t/sailfish-community-news-24-march-games/10779#update-on-jollas-situation-and-community-activities-2 | 08:57 |
| Nico | fancy :3 | 09:02 |
| *** Neo is now known as Guest4416 | 09:14 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!