*** zbenjamin is now known as Guest44750 | 02:43 | |
*** zbenjamin_ is now known as zbenjamin | 02:43 | |
*** frinring_ is now known as frinring | 04:24 | |
*** Redfoxmoon_ is now known as Redfoxmoon | 05:32 | |
chriadam | dcaliste: sorry, am I late? I can never keep up with DST transitions | 07:10 |
---|---|---|
dcaliste_ | Hello chriadam, how are you ? Is it too early at the moment ? | 07:29 |
chriadam | I'm well thanks. we can go through our agenda whenever you're ready. I thought the proper meeting start time was in 30 minutes still, but wasn't 100% sure due to DST transition soon | 07:30 |
dcaliste_ | Yes, I'm 30 minutes early. If you are busy I can start at 8amUTC as scheduled. | 07:31 |
chriadam | ok, let's start in 30 mins - I have another meeting right now so don't want to split my focus if that's ok | 07:32 |
chriadam | thanks! | 07:32 |
dcaliste_ | Sure, of course, see you then. | 07:32 |
chriadam | thanks for your patience :-) | 08:00 |
chriadam | I hope you have been well! | 08:00 |
dcaliste_ | Yeh, it's allright. The mountain is beautiful from my window, but still unreachable :/ | 08:04 |
chriadam | being couped up inside isn't fun, it's true | 08:05 |
chriadam | I don't have many topics for the meeting today: the last week I've been sidetracked on other things unfortunately. I merged and tagged a couple of things, but the two long outstanding ones (in nemo-qml-plugin-calendars and in mkcal) are still outstanding | 08:06 |
chriadam | I saw that you're working on some more caldav improvements (although I haven't had a chance to look at the PR yet) - thanks for that | 08:06 |
dcaliste_ | I didn't have time to do many things this week neither, but I have one or two things on my mind. | 08:07 |
chriadam | :-) | 08:07 |
dcaliste_ | Indeed, I've added propfind discovery code for the home-set, so we can remove the ugly hack to find the calendar path to list calendars. | 08:07 |
chriadam | excellent | 08:08 |
dcaliste_ | Well, I keep this hack as a fallback case in fact. | 08:08 |
dcaliste_ | And I've added code to fetch the priviledge-set so we can flag calendar as read-only when necessary. | 08:08 |
dcaliste_ | I've used the new propfind test for the two new requests. | 08:08 |
dcaliste_ | But I need to modify a bit the caldav code path, so I added a new test for it also. | 08:09 |
chriadam | cool - the read-only calendar support will no doubt be appreciated by many people! | 08:09 |
dcaliste_ | Yeh, but it has an unwanted consequence (good on long term): | 08:10 |
dcaliste_ | we need to save the storage modifications for each notebook separately. | 08:11 |
dcaliste_ | And not all at once anymore. | 08:11 |
dcaliste_ | It may have unexpected side effects, because the database is modified at each notebook. | 08:11 |
chriadam | interesting | 08:12 |
dcaliste_ | I'm testing it at the moment. | 08:12 |
dcaliste_ | Found a bug that I need to investigate. | 08:13 |
dcaliste_ | It looks like the one of flypig, with an issue to delete an exception because it cannot be loaded. | 08:13 |
chriadam | I guess mkcal will emit change signals when each notebooks' modifications are committed | 08:14 |
dcaliste_ | The good point is that it offers now the possibility to save successful notebooks in case of single failure in one. | 08:14 |
chriadam | but since we store ctag per notebook, it should be a good thing for sync itself to chop it up, rather than leting entire sync fail due to one issue in one notebook | 08:14 |
chriadam | yes | 08:14 |
dcaliste_ | Yes, mkcal signals now for ewach notebook and not for the sync itself. | 08:14 |
dcaliste_ | That's I think this can be a good thing in long term, after new bugs will be ironed out. | 08:15 |
dcaliste_ | That's why... | 08:15 |
chriadam | I agree | 08:16 |
chriadam | thank you for looking into these things | 08:16 |
dcaliste_ | With this work, I have an API question about Accounts : | 08:16 |
dcaliste_ | Accounts::Account *acc = manager->account(accId); | 08:16 |
dcaliste_ | Who owns acc pointer ? | 08:16 |
dcaliste_ | The manager, or the caller ? | 08:17 |
dcaliste_ | Do we need to delete it after use ? | 08:17 |
chriadam | some bad news: I spoke to Jaymzz and apparently the blog post which detailed your email signing feature won't be posted to the jolla blog any more. he said something about putting it in the new developer forum instead, so perhaps it was deemed too technical for the "normal" blog or something | 08:17 |
chriadam | dcaliste_: I believe the manager owns it and will delete it. a&sso has.. quirks. | 08:17 |
chriadam | there are two different methods to get an account | 08:18 |
chriadam | one is some static method like ::fromAccountId or so | 08:18 |
dcaliste_ | Ok, let's wait for the developer forum then. | 08:18 |
chriadam | I don't really understand the decision, I think it would have been perfect for the blog, but :shrug: | 08:18 |
dcaliste_ | Because I think I've seen deletes in some sailfish-components-accounts but none in caldav code. | 08:18 |
chriadam | dcaliste_: the ::fromAccountId() I think takes ownership | 08:19 |
chriadam | (also it is made more confusing as it only changed recently, when we updated to a more recent accounts&sso version) | 08:19 |
chriadam | by recently, I mean about a year ago | 08:19 |
dcaliste_ | I think in caldav, we use only the manager->account(accId) form. | 08:20 |
chriadam | should be owned by the manager then, but I might be wrong | 08:21 |
dcaliste_ | I don't have space anymore to install Valgrind on device :( | 08:22 |
dcaliste_ | I need to cleanup a bit. | 08:22 |
chriadam | one hint (if you haven't done this already) is to: mv /usr/lib/debug /home/debug; ln -s /home/debug /usr/lib/debug | 08:22 |
chriadam | then all the debug packages at least don't take up space on the root partition | 08:23 |
dcaliste_ | Yeh, but home is running short also :/ | 08:23 |
dcaliste_ | Anyway, another question about caldav : | 08:24 |
dcaliste_ | I think in sailfish-settings-accounts, the discovery code for calendar path is _not_ percent decoding the paths before saving them in account settings. | 08:25 |
dcaliste_ | Let me find again the line... | 08:25 |
dcaliste_ | in caldavaccountcalendarupdater.cpp#591 | 08:27 |
dcaliste_ | Then, same file line 191 | 08:28 |
chriadam | I must be looking in wrong place | 08:28 |
dcaliste_ | So in settings after first discovery, the path are stored like /caldav/use%40domain/ for instance. | 08:29 |
dcaliste_ | It's in ui-jolla-settings-accounts/declarative/ | 08:29 |
dcaliste_ | Sorry previously, I messup with sailfish something. | 08:29 |
chriadam | oh yes, thanks | 08:30 |
dcaliste_ | Then in caldav code, we're saving discovered paths percent decoded... | 08:30 |
chriadam | I see | 08:31 |
dcaliste_ | And then, the code to match the calendars with notebooks will fails and duplicate notebooks... | 08:31 |
chriadam | yes, calendarPath = reader->readElementText(); --> we should decode this properly | 08:31 |
chriadam | good catch | 08:32 |
dcaliste_ | In caldav, see line https://git.sailfishos.org/mer-core/buteo-sync-plugin-caldav/blob/master/src/propfind.cpp#L150 | 08:32 |
chriadam | thatt might have been the cause of a few other issues over the years (e.g. double percent encoding in some cases) | 08:32 |
dcaliste_ | I've fixed this in the new discovery MR, but I wanted to share the problem with you also, so you may know about this potential problem. | 08:34 |
chriadam | thank you for pointing that out. I will fix (in both jolla-settings-accounts, and the copy in buteo-sync-plugin-carddav) | 08:34 |
dcaliste_ | To be backward compatible, I then prefer to keep the account setting percentage encoded. | 08:34 |
dcaliste_ | And do the percent decoding at the notebookagent in caldav in fact. | 08:35 |
chriadam | oh? | 08:35 |
chriadam | I see | 08:35 |
chriadam | so, just fixing in the discovery MR so that we do it at that point only, makes sense | 08:36 |
dcaliste_ | Well, currently, users have percent encoded paths in their account setting, because of code in ui-joplla-setting. | 08:36 |
dcaliste_ | I don't want to update this. | 08:36 |
chriadam | otherwise we'd need two codepaths (one to handle pre-existing accounts, and one to handle new accounts) | 08:37 |
dcaliste_ | So I prefer, to let the discovery code and matching code in caldav to work with percent encoded paths. | 08:37 |
chriadam | which is suboptimal | 08:37 |
chriadam | yep, makes sense | 08:37 |
dcaliste_ | And then in notebooksyncagent, when using the path, decode it. | 08:37 |
dcaliste_ | That's how I'm doing it in my discovery MR. | 08:37 |
dcaliste_ | The problem is that this code is intricated with other changes in caldav client... | 08:38 |
dcaliste_ | I can de-intricate it and propose a proper MR for this issue alone if you think it's worth it. | 08:38 |
chriadam | I have no problem with it being part of the discovery MR if your time is limited | 08:39 |
chriadam | if it were separated, that would be great, but not required | 08:39 |
dcaliste_ | Ok, I'll see if it's easy to move it alone first without too many conflicts on rebase. I'll ping you in Gitlab during the week on success ;) | 08:40 |
chriadam | sounds good :-) thanks very much | 08:40 |
chriadam | anything else to discuss tonight? | 08:41 |
dcaliste_ | No, I think that's it. Thank you for the exchanges. | 08:42 |
chriadam | thank you for your time and effort as always, much appreciated | 08:42 |
chriadam | I hope you and your family stay safe during these stressful times! | 08:42 |
chriadam | have a good week! | 08:42 |
uzer_ | hi, i've installed the 3.2.0.20 image and works like a charm, thank you very much guys. | 15:06 |
uzer_ | that's 3.2.1.20 | 15:07 |
uzer_ | bluetooth does not though | 15:08 |
mal | hmm, maybe it needs some fixing | 15:11 |
mal | but at least it's a start to get it even booting | 15:11 |
uzer_ | even hotspot and flashlight are fine, which were not working on the image i used before | 15:15 |
uzer_ | switching from mobile date to wifi is responsive, that was a problem too | 15:16 |
uzer_ | selfie camera does not work but i never needed that | 15:19 |
uzer_ | thank you very much, i really appreciate that you looked into this | 15:20 |
mal | many things can be probably be fixed | 15:21 |
uzer_ | the only thing i need now is bluetooth | 15:21 |
uzer_ | but there i remember reading something on the forums about fixing that | 15:21 |
uzer_ | so will do my homework | 15:21 |
mal | you need to check logs | 15:25 |
uzer_ | where can i find bluetooth logs? looked in /var/log but can't identify anything related | 16:00 |
mal | journalctl | 16:03 |
uzer_ | i get: OnePlus3 bluetooth_rfkill_event[3055]: main(bluetooth_rfkill_event.c:1228): Unknown rfkill switch 0 | 16:36 |
mal | oh, you have the same issue someone else had | 16:46 |
uzer_ | seems to be related to https://talk.maemo.org/showpost.php?p=1553049&postcount=65 but don't understand what to do about it | 17:46 |
uzer_ | did the other person solved this? is it something that i can do with a stick and maybe a silex stone, considering those as my highest skills in dealing with porting? | 17:56 |
uzer_ | how can i fix this? | 18:47 |
mal | uzer_: wait a moment | 18:47 |
uzer_ | ok, will be here | 18:48 |
mal | uzer_: on device run zypper ref and then zypper dup, latter should then suggest updating bluetooth-rfkill-event-hciattach | 18:52 |
mal | if not then I have other instructions | 18:53 |
uzer_ | got it | 18:53 |
uzer_ | i get: The following package is going to be downgraded: bluetooth-rfkill-event-hciattach | 18:57 |
uzer_ | should i accept? | 18:57 |
mal | yes | 18:59 |
mal | once that is installed reboot and try bluetooth again | 18:59 |
uzer_ | still the same | 19:05 |
uzer_ | and nothing referring directly to bluetooth in journalctl | 19:17 |
mal | anything from that bluetooth-rfkill thingy? | 19:17 |
mal | can you check what "pkcon search name bluez5" outputs | 19:18 |
uzer_ | Installed bluez5-5.50+git3-1.10.2.jolla.armv7hl (installed) Bluetooth daemon | 19:22 |
uzer_ | one of them, should i paste all? | 19:22 |
mal | is there another line similar to that | 19:23 |
mal | with bluez5-5 at the beginning | 19:23 |
uzer_ | Installed bluez5-libs-5.50+git3-1.10.2.jolla.armv7hl (installed) Bluetooth (bluez5) library | 19:24 |
uzer_ | Installed bluez5-obexd-5.50+git3-1.10.2.jolla.armv7hl (installed) OBEX server (bluez5) | 19:24 |
uzer_ | Installed bluez5-tools-5.50+git3-1.10.2.jolla.armv7hl (installed) Command line tools for Bluetooth (bluez5) | 19:25 |
uzer_ | Installed droid-config-oneplus3-bluez5-1+master.20190329053252.d3ec44a-1.26.9.jolla.armv7hl (installed)oneplus3 packages for BlueZ 5 | 19:25 |
uzer_ | Installed kf5bluezqt-bluez5-5.24.0+git17-1.4.1.jolla.armv7hl (installed)KF5BluezQt - Qt wrapper for BlueZ 5 DBus API | 19:25 |
mal | so no bluez5-5.47+git11 or something | 19:25 |
mal | run pkcon refresh | 19:26 |
uzer_ | Available bluez5-debugsource-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Debug sources for package bluez5 | 19:26 |
uzer_ | Available bluez5-hcidump-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Bluetooth (bluez5) packet analyzer | 19:26 |
uzer_ | not the only ones | 19:26 |
uzer_ | is this the one: Available bluez5-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Bluetooth daemon | 19:28 |
mal | run this: "zypper dup --from adaptation-community" | 19:29 |
mal | it should suggest downgrading the bluez5 packages | 19:29 |
uzer_ | it did, should reboot after? | 19:30 |
mal | yes | 19:30 |
uzer_ | still nothing | 19:35 |
uzer_ | and nothing bluetooth related in journalctl | 19:35 |
mal | show the whole output of "journalctl -alb --no-pager" | 19:37 |
uzer_ | that's a long list. should i make it --since or paste the hole whole thing | 19:40 |
mal | maybe try journalctl -alb --no-pager | grep bluez | 19:44 |
mal | or journalctl -alb --no-pager | grep rfkill | 19:44 |
uzer_ | first: Mar 24 21:31:03 OnePlus3 connmand[3106]: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist | 19:49 |
uzer_ | Mar 24 21:31:09 OnePlus3 dbus-daemon[3532]: dbus-daemon[3532]: [session uid=100000 pid=3532] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.20' (uid=100000 pid=4213 comm="/usr/bin/lipstick -plugin evdevtouch:/dev/input/ev") | 19:49 |
uzer_ | Mar 24 21:31:09 OnePlus3 dbus-daemon[3532]: dbus-daemon[3532]: [session uid=100000 pid=3532] Successfully activated service 'org.bluez.obex' | 19:49 |
uzer_ | and seccond is longer | 19:49 |
uzer_ | Jan 07 10:54:37 OnePlus3 systemd[1]: Configuration file /lib/systemd/system/bluetooth-rfkill-event.service is marked executable. Please remove executable permission bits. Proceeding anyway. | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 systemd[1]: Started Bluetooth rfkill event daemon. | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 bluetooth_rfkill_event[3040]: main(bluetooth_rfkill_event.c:1178): Starting bluetooth_rfkill_event | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 bluetooth_rfkill_event[3040]: load_config(bluetooth_rfkill_event.c:571): Parsing /etc/qca_rome.conf failed: Key file does not start with a group | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Unit entered failed state. | 19:50 |
uzer_ | Mar 24 21:31:02 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'. | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart. | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 bluetooth_rfkill_event[3365]: main(bluetooth_rfkill_event.c:1178): Starting bluetooth_rfkill_event | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 bluetooth_rfkill_event[3365]: load_config(bluetooth_rfkill_event.c:571): Parsing /etc/qca_rome.conf failed: Key file does not start with a group | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: Stopped Bluetooth rfkill event daemon. | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: Started Bluetooth rfkill event daemon. | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Unit entered failed state. | 19:50 |
uzer_ | Mar 24 21:31:03 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'. | 19:50 |
mal | you can see the error there | 19:50 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart. | 19:50 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: Stopped Bluetooth rfkill event daemon. | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: Started Bluetooth rfkill event daemon. | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 bluetooth_rfkill_event[3780]: main(bluetooth_rfkill_event.c:1178): Starting bluetooth_rfkill_event | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 bluetooth_rfkill_event[3780]: load_config(bluetooth_rfkill_event.c:571): Parsing /etc/qca_rome.conf failed: Key file does not start with a group | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Unit entered failed state. | 19:51 |
uzer_ | Mar 24 21:31:04 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'. | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart. | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: Stopped Bluetooth rfkill event daemon. | 19:51 |
mal | use pastebin for anything more than 3 lines | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 bluetooth_rfkill_event[4182]: main(bluetooth_rfkill_event.c:1178): Starting bluetooth_rfkill_event | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: Started Bluetooth rfkill event daemon. | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 bluetooth_rfkill_event[4182]: load_config(bluetooth_rfkill_event.c:571): Parsing /etc/qca_rome.conf failed: Key file does not start with a group | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Unit entered failed state. | 19:51 |
uzer_ | Mar 24 21:31:05 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'exit-code'. | 19:51 |
uzer_ | Mar 24 21:31:07 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Service hold-off time over, scheduling restart. | 19:51 |
uzer_ | Mar 24 21:31:07 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Start request repeated too quickly. | 19:51 |
uzer_ | Mar 24 21:31:07 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Unit entered failed state. | 19:51 |
mal | why did you think pasting that many lines was a good idea | 19:51 |
uzer_ | Mar 24 21:31:07 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'start-limit'. | 19:51 |
uzer_ | ok | 19:51 |
uzer_ | sorry about that | 19:51 |
uzer_ | it was a bad move, sorry | 19:54 |
mal | you can see it fails with "Parsing /etc/qca_rome.conf failed: Key file does not start with a group" | 20:12 |
mal | you need to check that file | 20:12 |
uzer_ | looking there right now but don't know what to change | 20:20 |
uzer_ | the values are set as here https://github.com/delaya73/droid-config-oneplus3/blob/master/sparse/etc/qca_rome.conf | 20:21 |
mal | that error is very odd | 20:58 |
uzer_ | i can confirm that bluetooth works in lineageos. | 21:00 |
uzer_ | have to get some sleep now. thank for everything mal. nite | 21:31 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!