Tuesday, 2020-03-24

*** zbenjamin is now known as Guest4475002:43
*** zbenjamin_ is now known as zbenjamin02:43
*** frinring_ is now known as frinring04:24
*** Redfoxmoon_ is now known as Redfoxmoon05:32
chriadamdcaliste: sorry, am I late?  I can never keep up with DST transitions07:10
dcaliste_Hello chriadam, how are you ? Is it too early at the moment ?07:29
chriadamI'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 soon07:30
dcaliste_Yes, I'm 30 minutes early. If you are busy I can start at 8amUTC as scheduled.07:31
chriadamok, let's start in 30 mins - I have another meeting right now so don't want to split my focus if that's ok07:32
chriadamthanks!07:32
dcaliste_Sure, of course, see you then.07:32
chriadamthanks for your patience :-)08:00
chriadamI hope you have been well!08:00
dcaliste_Yeh, it's allright. The mountain is beautiful from my window, but still unreachable :/08:04
chriadambeing couped up inside isn't fun, it's true08:05
chriadamI 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 outstanding08:06
chriadamI 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 that08: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
chriadamexcellent08: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
chriadamcool - 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
chriadaminteresting08: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
chriadamI guess mkcal will emit change signals when each notebooks' modifications are committed08: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
chriadambut 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 notebook08:14
chriadamyes08: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
chriadamI agree08:16
chriadamthank you for looking into these things08: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
chriadamsome 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 something08:17
chriadamdcaliste_: I believe the manager owns it and will delete it.  a&sso has.. quirks.08:17
chriadamthere are two different methods to get an account08:18
chriadamone is some static method like ::fromAccountId or so08:18
dcaliste_Ok, let's wait for the developer forum then.08:18
chriadamI 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
chriadamdcaliste_: the ::fromAccountId() I think takes ownership08: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
chriadamby recently, I mean about a year ago08:19
dcaliste_I think in caldav, we use only the manager->account(accId) form.08:20
chriadamshould be owned by the manager then, but I might be wrong08:21
dcaliste_I don't have space anymore to install Valgrind on device :(08:22
dcaliste_I need to cleanup a bit.08:22
chriadamone hint (if you haven't done this already) is to: mv /usr/lib/debug /home/debug; ln -s /home/debug /usr/lib/debug08:22
chriadamthen all the debug packages at least don't take up space on the root partition08: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#59108:27
dcaliste_Then, same file line 19108:28
chriadamI must be looking in wrong place08: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
chriadamoh yes, thanks08:30
dcaliste_Then in caldav code, we're saving discovered paths percent decoded...08:30
chriadamI see08:31
dcaliste_And then, the code to match the calendars with notebooks will fails and duplicate notebooks...08:31
chriadamyes, calendarPath = reader->readElementText(); --> we should decode this properly08:31
chriadamgood catch08:32
dcaliste_In caldav, see line  https://git.sailfishos.org/mer-core/buteo-sync-plugin-caldav/blob/master/src/propfind.cpp#L15008:32
chriadamthatt 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
chriadamthank 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
chriadamoh?08:35
chriadamI see08:35
chriadamso, just fixing in the discovery MR so that we do it at that point only, makes sense08: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
chriadamotherwise 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
chriadamwhich is suboptimal08:37
chriadamyep, makes sense08: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
chriadamI have no problem with it being part of the discovery MR if your time is limited08:39
chriadamif it were separated, that would be great, but not required08: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
chriadamsounds good :-)  thanks very much08:40
chriadamanything else to discuss tonight?08:41
dcaliste_No, I think that's it. Thank you for the exchanges.08:42
chriadamthank you for your time and effort as always, much appreciated08:42
chriadamI hope you and your family stay safe during these stressful times!08:42
chriadamhave 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.2015:07
uzer_bluetooth does not though15:08
malhmm, maybe it needs some fixing15:11
malbut at least it's a start to get it even booting15:11
uzer_even hotspot and flashlight are fine, which were not working on the image i used before15:15
uzer_switching from mobile date to wifi is responsive, that was a problem too15:16
uzer_selfie camera does not work but i never needed that15:19
uzer_thank you very much, i really appreciate that you looked into this15:20
malmany things can be probably be fixed15:21
uzer_the only thing i need now is bluetooth15:21
uzer_but there i remember reading something on the forums about fixing that15:21
uzer_so will do my homework15:21
malyou need to check logs15:25
uzer_where can i find bluetooth logs? looked in /var/log but can't identify anything related16:00
maljournalctl16:03
uzer_i get: OnePlus3 bluetooth_rfkill_event[3055]: main(bluetooth_rfkill_event.c:1228): Unknown rfkill switch 016:36
maloh, you have the same issue someone else had16: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 it17: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
maluzer_: wait a moment18:47
uzer_ok, will be here18:48
maluzer_: on device run zypper ref and then zypper dup, latter should then suggest updating bluetooth-rfkill-event-hciattach18:52
malif not then I have other instructions18:53
uzer_got it18:53
uzer_i get: The following package is going to be downgraded:  bluetooth-rfkill-event-hciattach18:57
uzer_should i accept?18:57
malyes18:59
malonce that is installed reboot and try bluetooth again18:59
uzer_still the same19:05
uzer_and nothing referring directly to bluetooth in journalctl19:17
malanything from that bluetooth-rfkill thingy?19:17
malcan you check what "pkcon search name bluez5" outputs19:18
uzer_Installed   bluez5-5.50+git3-1.10.2.jolla.armv7hl (installed)           Bluetooth daemon19:22
uzer_one of them, should i paste all?19:22
malis there another line similar to that19:23
malwith bluez5-5 at the beginning19:23
uzer_Installed   bluez5-libs-5.50+git3-1.10.2.jolla.armv7hl (installed)      Bluetooth (bluez5) library19: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 519:25
uzer_Installed   kf5bluezqt-bluez5-5.24.0+git17-1.4.1.jolla.armv7hl (installed)KF5BluezQt - Qt wrapper for BlueZ 5 DBus API19:25
malso no bluez5-5.47+git11 or something19:25
malrun pkcon refresh19:26
uzer_Available   bluez5-debugsource-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Debug sources for package bluez519:26
uzer_Available   bluez5-hcidump-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Bluetooth (bluez5) packet analyzer19:26
uzer_not the only ones19:26
uzer_is this the one: Available   bluez5-5.47+git11+master.20190401115635.1.g00fe8fbeb-1.6.6.jolla.armv7hl (adaptation-community)Bluetooth daemon19:28
malrun this: "zypper dup --from adaptation-community"19:29
malit should suggest downgrading the bluez5 packages19:29
uzer_it did, should reboot after?19:30
malyes19:30
uzer_still nothing19:35
uzer_and nothing bluetooth related in journalctl19:35
malshow 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 thing19:40
malmaybe try journalctl -alb --no-pager | grep bluez19:44
malor journalctl -alb --no-pager | grep rfkill19:44
uzer_first: Mar 24 21:31:03 OnePlus3 connmand[3106]: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist19: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 longer19: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_event19: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 group19:50
uzer_Mar 24 21:31:02 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE19: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_event19: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 group19: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/FAILURE19: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
malyou can see the error there19: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_event19: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 group19:51
uzer_Mar 24 21:31:04 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE19: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
maluse pastebin for anything more than 3 lines19:51
uzer_Mar 24 21:31:05 OnePlus3 bluetooth_rfkill_event[4182]: main(bluetooth_rfkill_event.c:1178): Starting bluetooth_rfkill_event19: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 group19:51
uzer_Mar 24 21:31:05 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Main process exited, code=exited, status=1/FAILURE19: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
malwhy did you think pasting that many lines was a good idea19:51
uzer_Mar 24 21:31:07 OnePlus3 systemd[1]: bluetooth-rfkill-event.service: Failed with result 'start-limit'.19:51
uzer_ok19:51
uzer_sorry about that19:51
uzer_it was a bad move, sorry19:54
malyou can see it fails with "Parsing /etc/qca_rome.conf failed: Key file does not start with a group"20:12
malyou need to check that file20:12
uzer_looking there right now but don't know what to change20:20
uzer_the values are set as here https://github.com/delaya73/droid-config-oneplus3/blob/master/sparse/etc/qca_rome.conf20:21
malthat error is very odd20:58
uzer_i can confirm that bluetooth works in lineageos.21:00
uzer_have to get some sleep now. thank for everything mal. nite21:31

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!