| arno11 | dsc_: i fixed the issues on my device :) will explain in bug tracker a bit later | 10:18 |
|---|---|---|
| arno11 | root cause seems racy things between hsm, addressbook and tg account plugin | 10:19 |
| arno11 | not conversations | 10:19 |
| dsc_ | arno11: I found another possible strange thing with the Tg connection manager, when you go offline, all Tg contacts dissapear from abook too | 13:44 |
| dsc_ | i dont recall that happening for the other protocols | 13:44 |
| Wizzup | I think that's normal | 14:15 |
| Wizzup | unless you make them an actual permanent contact | 14:15 |
| Wizzup | these are ephemeral and only show while you're online | 14:15 |
| Wizzup | it's the same for slack, I'd get like 500 folks added to abook | 14:15 |
| Wizzup | I don't want those to be permanent | 14:15 |
| dsc_ | ah ok | 14:18 |
| arno11 | Wizzup: dsc_: so the only issue i had was h-s-m starting to early: starting it later solved the 2 main issues: | 14:22 |
| arno11 | 1) now the account survives on reboot | 14:22 |
| arno11 | 2) no troubles with chats (crash) | 14:23 |
| arno11 | i suppose it should be the same for other haze plugins like signal | 14:23 |
| arno11 | it was really racy because every time we enable tg plugin again after each boot, a new one was created | 14:25 |
| arno11 | now that's fine. so it means that h-s-m starts to be buggy on boot when we add a haze plugin like fb or tg | 14:28 |
| arno11 | otherwise no troubles | 14:28 |
| arno11 | (to start hsm later, i mv'd 15h-s-m to 75h-s-m in Xsession.post, like i did with fb long time ago) | 14:31 |
| Wizzup | arno11: seems like we need to fix a plugin in h-s-m | 15:03 |
| arno11 | yep | 15:05 |
| arno11 | the good news are for conversations itself: works very well :) | 15:07 |
| dsc_ | :) | 15:42 |
| freemangordon | do we know which one (plugin)? | 15:47 |
| freemangordon | accounts? | 15:47 |
| arno11 | no idea but i see some troubles only with tp haze stuff atm | 16:02 |
| freemangordon | what's it, account is not being connected on boot? | 16:05 |
| arno11 | account is simply not visible after boot and apparently not enabled | 16:07 |
| freemangordon | yep, I see | 16:07 |
| freemangordon | ok, will have a look | 16:08 |
| arno11 | cool | 16:08 |
| dsc_ | this happened to me with apparmor, but I dont think this is relevant whilst on actual devices | 16:11 |
| dsc_ | as there is no apparmor there | 16:11 |
| freemangordon | I still wonder how SFOS does not lose SMSes on powerup | 16:30 |
| arno11 | didn't they modify ofono 2 ? | 16:32 |
| freemangordon | no | 16:34 |
| freemangordon | but it does not matter | 16:34 |
| freemangordon | or rather - they are on 1.29 (heavily patched), but I see nothing relevant in their code | 16:35 |
| freemangordon | might be just missing it, but still | 16:35 |
| arno11 | freemangordon: according to maemo-gpt (web search), SFOS uses commhistory-daemon to record sms-es in RT and other processes use libcommhistory to read them | 23:15 |
| arno11 | yeah, it does the trick, they also use commhistory for calls received while offline | 23:45 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!