| *** feodoran_ is now known as feodoran | 03:31 | |
| *** jvd is now known as jvd_ | 06:36 | |
| dcaliste | Hello chriadam, how are you ? | 07:56 |
|---|---|---|
| chriadam | hi, I'm well thanks! how are you? | 07:56 |
| dcaliste | Fine, thank you. I've got some minor questions if you have time (and I've answered your (valid) remark about my latest secret PR). | 07:57 |
| chriadam | great, I'll check that later tonight | 07:57 |
| dcaliste | First, how can I get debug info from a 'invoker …' command line ? Usually I do 'export Q_LOGGING_LEVEL="*.debug true"', or something like that, but when using invoker, I got nothing. | 07:58 |
| chriadam | usually invoker sets up the environment according to some conf file | 07:59 |
| dcaliste | I need it, because from cli, calling "gpg2 -s" or "jolla-email" and signing make the collection unlock request appears, but when jolla-email is called through invoker, I don't get it. | 07:59 |
| chriadam | under /var/lib/environment/ I think | 08:00 |
| dcaliste | Ok, I'm looking at it… | 08:02 |
| dcaliste | Second question is about staging accepted MR in gerrit for messagingframework: https://codereview.qt-project.org/#/c/247158/ has a +2 and I've a button to stage it, but since another PR entered first, what is the prefered way to go? | 08:03 |
| dcaliste | Stage it and this may create a merge commit, or rebase it anf force push it again ? | 08:03 |
| chriadam | I personally would rebase it if the other one has been merged in the meantime | 08:04 |
| dcaliste | Ok, so let's go that way. | 08:04 |
| chriadam | but it may not matter. I'm not sure how the gerrit machinery does CR merges - it may do a cherry pick anyway | 08:04 |
| chriadam | dcaliste: regarding the email signing end-to-end stuff, are we still waiting for anything on QMF side? | 08:06 |
| chriadam | I see that there are a couple of CRs up there still - are they necessary? | 08:06 |
| chriadam | or should we be able to merge the jolla-email + n-q-p-em + jolla-settings-accounts changes already? jpetrell how do you see those? | 08:06 |
| dcaliste | To send attachments, the one I'm speaking about is required. I've modified the IMAP strategy to download parts to ensure that signed email with attachments are not downloading things twice, it's https://codereview.qt-project.org/#/c/248214/ | 08:07 |
| jpetrell | chriadam: asked earlier pvuorela to check those before merging, afaik he hasn't had time to do that yet. pekka did say few days back that we should get those things merged so it is on his mind. | 08:08 |
| jpetrell | I am ok merging | 08:08 |
| jpetrell | pekka currently knows the email domain the best | 08:08 |
| dcaliste | These two MRs in QMF are to correct bugs about signed email with attachments, that I didn't test properly during the first part of my work, when I concentrate on having simple text mails already working. | 08:08 |
| chriadam | jpetrell: dcaliste: I guess there's no huge rush - if those upstream QMF patches are needed ot make attachment signing work properly, maybe we can just come back to this after Christmas, and get everything in then? | 08:10 |
| chriadam | I mean, I was hoping to get it in before Christmas, but probably best to integrate when attachments are ready too, I guess | 08:10 |
| dcaliste | About the Mer side of things, the QMF MR will have to be ajusted to get the latest commit from upstream, otherwise, the other parts are ready. | 08:10 |
| dcaliste | We need the MR in GPGme https://git.merproject.org/mer-core/gpgme/merge_requests/4 to go in also to be able to sign emails with S/MIME without running a GPG agent first. | 08:12 |
| dcaliste | chriadam: I've explained in detail how the patch adding the function callback is actually making the launch of a GPG agent on the fly working. | 08:13 |
| chriadam | just saw that, thanks | 08:13 |
| chriadam | can you add that as context to the commit message also? | 08:14 |
| chriadam | then I'll merge/tag that one | 08:14 |
| dcaliste | chriadam: we can also merge all MR from Mer side to be able to have more people test the UI flow and design and have early feedback. Then, when the attachment MR are accepted upstream, we just need to update the upstream commit in Mer QMF. | 08:14 |
| dcaliste | chriadam: ok to update the commit message, sure. | 08:14 |
| chriadam | dcaliste: on mer side what remains? was there something outstanding in n-q-p-email or mer qmf? | 08:16 |
| chriadam | (well and that gpgme one) | 08:16 |
| chriadam | ah https://git.merproject.org/mer-core/nemo-qml-plugin-email/merge_requests/33 | 08:17 |
| dcaliste | in mer qmf: the packaging of the crypto plugin: https://git.merproject.org/mer-core/messagingframework/merge_requests/18 | 08:17 |
| dcaliste | in nemo-qml-plugin-email: https://git.merproject.org/mer-core/nemo-qml-plugin-email/merge_requests/33 to add QML bindings for signature status. | 08:18 |
| chriadam | that packaging one LGTM. I will do a smoke test/build tomorrow and then merge it / tag it, unless someone says otherwise | 08:19 |
| dcaliste | Great, thanks. | 08:20 |
| dcaliste | chriadam: I've rebased https://codereview.qt-project.org/#/c/247158/ and requires (again) a +2 to be staged. | 08:20 |
| chriadam | done | 08:20 |
| chriadam | regarding the nqpemail qml binding for signature support, I think that one is fine but would like pvuorela to review first too. | 08:21 |
| dcaliste | Sure (and thanks for the CR about attachment boundaries, I've pushed the stage button). | 08:21 |
| dcaliste | So, just https://codereview.qt-project.org/248214 remains, but requires full review (also pvuorela, if you have time, thank you in advance). | 08:22 |
| chriadam | Thursday I'll ping matt | 08:23 |
| chriadam | dcaliste: regarding the jolla-email (and jolla-settings-accounts) PRs, can you use JB#43783 as the bug number for that | 08:23 |
| chriadam | e.g. in the commit message etc | 08:23 |
| dcaliste | chriadam: I think I'll update Mer QMF packaging request for upstream to point on latest after the attachment boundary fix is in. | 08:24 |
| chriadam | ok | 08:24 |
| chriadam | i'll hold off on that one for now then | 08:24 |
| dcaliste | I'll do it later today I think. | 08:24 |
| dcaliste | Ok, to update the commit messages in jolla-email and setting. | 08:25 |
| chriadam | thanks very much | 08:25 |
| chriadam | ok, so just to summarise: | 08:25 |
| chriadam | 1) mer-qmf packaging commit, waiting on the boundary change from upstream but then I will merge/tag | 08:25 |
| chriadam | 2) nemo-qml-plugin-email needs review from pvuorela, but LGTM and I think jpetrell also reviewed it a while ago | 08:26 |
| chriadam | 3) gpgme - LGTM once the commit message is updated then I will merge/tag | 08:26 |
| dcaliste | Exact. I would add also: | 08:26 |
| chriadam | 4) jolla-settings-accounts + jolla-email -> just need the bug number updated to JB#43783, then pvuorela to give final review. I won't merge that, but will leave to jpetrell or pvuorela I think. | 08:26 |
| dcaliste | 5) add dirmngr in the public repo when publishing the SFOS release x+1. | 08:27 |
| chriadam | lbt: will that (5) happen automatically or is there something I have to do? I guess in that qmf packaging PR we need to ensure that it has "Requires: dirmngr" in the .spec? | 08:28 |
| dcaliste | I've added a Requires: on it in Mer QMF packaging | 08:28 |
| chriadam | I think that's all that should be required, but let's wait for lbt to confirm | 08:28 |
| chriadam | or pketo if lbt is on vacation | 08:28 |
| dcaliste | But it's not a BuildRequires: so just mentioning it in case ;) You may not notice it without actually installing QMF. | 08:29 |
| dcaliste | About the bug raised by lipstick-secuiry-ui, do you have any idea how we can proceed, it hanged on me again yesterday. | 08:29 |
| dcaliste | I've quickly looked in the commit messages of QtWayland without finding anything that may be related. | 08:30 |
| chriadam | dcaliste: I do not :-( | 08:30 |
| chriadam | jpetrell: is that one a candidate for maintenance task? | 08:30 |
| dcaliste | I'm a bit afraid to rebase Mer QtWayland on QtWayland upstream @ 5.6.3 and test on device. | 08:30 |
| chriadam | if so I can look into it over the next couple of days | 08:30 |
| chriadam | dcaliste: that won't work anyway, really | 08:31 |
| chriadam | upstream changed a lot | 08:31 |
| chriadam | hopefully we move to qt5.9 soon and then we can try again, in the meantime it's mostly just hacking wayland internals :-/ | 08:31 |
| dcaliste | Just using "secrets-tools --get-user-input" repeatedly and pressing cancel to go quicker make the thing finally hangs. | 08:32 |
| dcaliste | But I've no idea where to put debug printf to get a clue on why the server side is not responding… | 08:33 |
| dcaliste | When Googleing for the symbol found with gdb, I also just arrive on hybris egl, which confuses me a bit more. Well I guess QtWayland is using EGL implementation provided by libhybris. | 08:34 |
| dcaliste | But then, where to debug ? Maybe, I need to look in Hybris more than QtWayland… | 08:35 |
| chriadam | dcaliste: frajo might be able to help a bit also | 08:35 |
| chriadam | my expectation is: | 08:35 |
| chriadam | the compositor (lipstick) talks to clients (e.g. lipstick-security-ui) via wayland. internally, it allocates egl surfaces via libhybris (-> android surfaceflinger) | 08:36 |
| chriadam | so lipstick-security-ui at low level has qtwayland waiting for a response from the compositor (lipstick) | 08:37 |
| chriadam | but ALL OF THAT may be totally wrong | 08:37 |
| chriadam | because I have NFI about any of that stuff | 08:37 |
| chriadam | abranson may be able to shed some light ^ | 08:37 |
| pvuorela | lots of highlight on my name here :) yea, i'm aiming to do a review round on the signing stuff. | 08:38 |
| pvuorela | for gerrit, i think it just always cherry-picks commits. | 08:39 |
| abranson | sorry, no idea how the compositing works. it's on my list of things to find out at some point :) | 08:39 |
| chriadam | pvuorela: no rush, if you don't get to it this week it's no huge problem, just would be nice to get this stuff merged before christmas. thanks! | 08:40 |
| chriadam | abranson: me too ;-) | 08:40 |
| pketo | dirmngr needs to be added in our internal OBS, an in the release filtering rules | 08:45 |
| chriadam | pketo: oh! thanks - is there something we need to do for that? (it was previously added to the gitlab Maintainers file also) | 08:47 |
| dcaliste | pvuorela: thanks, and ok for next time I'll stage even if not base on master (if it can be cherry picked without conflict of course). | 08:47 |
| chriadam | dcaliste: I created JB#44199 internally to track the lipstick security ui issue and asked for it to be prioritised. with any luck I will be able to do some investigation later this week, but let's see | 08:48 |
| pketo | chriadam: probably best if you file a bug about it, I'm not sure of all the steps | 08:48 |
| chriadam | pketo: Ok I will do that, thanks | 08:49 |
| dcaliste | chriadam: great, huge thanks. I'll dig into various sources myself to better understand how the composition is working and where it may fail. | 08:49 |
| chriadam | dcaliste: no problem. thanks again for your hard work and patience. greatly appreciated, and I'm sure lots of SFOS users will appreciate the signatures feature once it all gets integrated. | 08:51 |
| dcaliste | Well, I didn't loose my time, now I understand much better the process of file signing and feel more confident to use it. I don't like magic processes. | 08:52 |
| chriadam | :-) | 08:53 |
| chriadam | pketo: created JB#44200 for that one | 08:54 |
| dcaliste | chriadam: I've just updated the commit message in GPGme to explain the rational of the patch. | 08:55 |
| chriadam | thanks | 08:55 |
| chriadam | I will merge that one tomorrow (and the secrets one) | 08:56 |
| dcaliste | Sure, thank you. | 08:56 |
| chriadam | ok, I have to head home. Thanks for the productive meeting. If we don't chat on IRC before the weekend, I hope you have a great Christmas and New Year. I work this week, then will be back in the office from the 2nd of January. | 08:57 |
| chriadam | I will track carefully those PRs this week, hopefully we can get everything merged, but if not, I guess the new year. | 08:57 |
| dcaliste | Sure, I wish you a happy Xmas time too. | 08:58 |
| chriadam | :-) | 08:58 |
| chriadam | gnight! | 08:58 |
| dcaliste | I'll be off from the 24th to the 3rd of January myself. | 08:58 |
| *** Renault_ is now known as Renault | 13:25 | |
| *** Renault_ is now known as Renault | 16:06 | |
| *** Renault_ is now known as Renault | 16:54 | |
| GreatEmerald | I just updated my Jolla 1 to SFOS 3 (it was a bit rocky but it worked), and all seems good, except for one issue | 19:59 |
| GreatEmerald | When I take a picture, it's shown in the camera app history, but disappears | 20:00 |
| GreatEmerald | As soon as I close the app, it's gone, and it's not shown in the gallery while the camera app is open either | 20:00 |
| GreatEmerald | In the camera app I can see its name, so it looks like the file physically exists somewhere | 20:01 |
| r0kk3rz | how long ago did you update? | 20:01 |
| GreatEmerald | Yesterday | 20:02 |
| GreatEmerald | Hm, I think the files exist, but they aren't indexed | 20:02 |
| r0kk3rz | ok tracker should be well and truly finished reindexing by now | 20:03 |
| r0kk3rz | where have you set the pictures to be stored? | 20:03 |
| GreatEmerald | Default location | 20:04 |
| GreatEmerald | So that's Pictures/Camera | 20:04 |
| r0kk3rz | double check the pictures are there using the file browser | 20:05 |
| GreatEmerald | I used the terminal and I think ls shows them there | 20:06 |
| GreatEmerald | I'll sftp that to my laptop | 20:06 |
| mal | are the file sizes ok? | 20:06 |
| mal | GreatEmerald: if the files are ok but not showing in gallery then install sailfish utilities and clear the media database from settings->utilities so it will refresh it using tracker, hopefully that will help | 20:08 |
| GreatEmerald | mal: Yeap, the pictures are fine | 20:08 |
| r0kk3rz | or 'tracker -se' if you cant be bothered installing the utilities | 20:11 |
| mal | yep, there is of course a manual way | 20:12 |
| GreatEmerald | That's easy | 20:12 |
| GreatEmerald | r0kk3rz: -se is not a tracker command | 20:13 |
| r0kk3rz | tracker-control maybe, its been a long time since ive prodded around with it | 20:13 |
| GreatEmerald | r0kk3rz: No such command, do you mean `tracker reset`? | 20:17 |
| r0kk3rz | yeah basically reset and reindex | 20:20 |
| r0kk3rz | perhaps the management commands have changed over the years | 20:20 |
| GreatEmerald | I did a soft reset | 20:25 |
| GreatEmerald | Now tracker status kind of just sits there waiting | 20:25 |
| GreatEmerald | Oh, now it says complete | 20:32 |
| GreatEmerald | Sure enough, now the photos are there | 20:32 |
| GreatEmerald | Thanks! | 20:32 |
| mal | GreatEmerald: do new photos also appear there? | 20:39 |
| GreatEmerald | mal: Good question | 20:50 |
| GreatEmerald | One I would probably be able to answer if the Camera app would start, hm | 20:51 |
| GreatEmerald | mal: Looks like the answer is no | 20:54 |
| GreatEmerald | The lockscreen camera app works | 20:54 |
| mal | GreatEmerald: how did you update the device, what issues did you have when updating? | 21:10 |
| GreatEmerald | mal: Using the updater in settings | 21:13 |
| GreatEmerald | mal: I had the issue of it not finishing the update; the boot screen showed "Sailfish OS" at 100%, but wouldn't finish throughout the night | 21:13 |
| GreatEmerald | So I had to pull the battery, and after the reset it seemed to work just fine | 21:14 |
| GreatEmerald | But it may not, indeed | 21:14 |
| mal | ok, long press of power button would have rebooted it also | 21:14 |
| GreatEmerald | I tried that | 21:14 |
| GreatEmerald | It didn't work | 21:14 |
| GreatEmerald | I held it for like 10 seconds | 21:15 |
| mal | or vol up + power button for a long time | 21:15 |
| mal | it needs to be qutie long time | 21:15 |
| GreatEmerald | I tried that too, but for not as long | 21:15 |
| mal | check output of journalctl when you try to use camera app | 21:17 |
| GreatEmerald | Uh oh | 21:19 |
| GreatEmerald | I/O errors in mmcblk1 | 21:20 |
| GreatEmerald | There's a lot of things about msm | 21:23 |
| GreatEmerald | But it looks like debug/info, not warnings | 21:24 |
| GreatEmerald | The SD card dying happens twice in a row for me :\ That's weird | 21:26 |
| mal | I have always found sd cards to be quite easy to break | 21:45 |
| r0kk3rz | there are a lot of dodgy ones around | 21:59 |
| GreatEmerald | I buy ones with a life-long warranty | 22:10 |
| GreatEmerald | Which comes in handy more often than I'd like | 22:11 |
| *** Renault_ is now known as Renault | 22:12 | |
| flav0r | is there a good browser out yet ? | 22:12 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!