**** BEGIN LOGGING AT Sun May 17 02:59:57 2020 May 17 07:43:46 Tofe: I have some small idea May 17 07:43:56 we now have: https://github.com/webosose/meta-webosose/blob/cc478cb8f6f5c71369fffb69447b182f7a5a45d7/meta-webos/classes/webos_app_generate_security_files.bbclass May 17 07:44:23 Which reads from appinfo.json and generates security files: https://github.com/webosose/meta-webosose/blob/cc478cb8f6f5c71369fffb69447b182f7a5a45d7/meta-webos/classes/webos_app_generate_security_files.bbclass#L31 May 17 07:44:51 If we add to firstuse appinfo.json the required permissions and inherit webos_app in the firstuse recipe it might actually work. May 17 07:45:20 Similar to what OSE guys did with https://github.com/webosose/com.webos.service.flowmanager/blob/master/apps/com.webos.app.mediaviewer/appinfo.json#L15 May 17 07:45:39 We would need to add settings and or system instead of media May 17 07:45:51 Just preparing breakfast and might have some time afterwards to play with it May 17 09:08:16 Morning! May 17 09:08:30 Herrie: yes, that's a good lead May 17 09:19:46 Tofe: Nope doesn't seem to solve it May 17 09:19:55 :/ ok May 17 09:20:15 I also notice that we still have com.palm.systemservice in firstuse and OSE uses com.webos.service.systemservice, but that's not the cause either May 17 09:24:22 I wonder why it is just getpreferences... what is special about it ? a servcice haven't migrated yet ? something else ?... May 17 09:45:17 Getpreferences is from luna-sysservice which we did migrate May 17 09:46:07 I probably need to check luna-next because calls there seem to work May 17 09:46:33 I remark that the qml app is started via a generic qml-launcher, and likewise WAM is also a "launcher" May 17 09:46:42 I think it's what they call a container ? May 17 09:46:56 Yes that could be the issue May 17 09:47:09 but then why would it only fail for that API... May 17 09:47:10 I saw some special cases for this on OSE May 17 09:47:35 Others are failing too, see /var/log/messages May 17 09:47:48 Calls in browser too it seems May 17 09:47:59 ah ok, I just didn't test enough :) May 17 09:48:06 Probably in phone app too May 17 09:48:12 Might be good to check May 17 09:48:18 That could be a good hint May 17 09:48:44 with ls2-monitor, we could get the sender id, maybe it's incorrect May 17 12:12:17 Tofe: needed to do some shopping and now making lunch will check afterwards when kids are asleep May 17 12:56:54 Tofe: ls-monitor output for com.palm.systemservice: https://paste.ubuntu.com/p/MxFrhJbV72/ May 17 12:57:38 ok, so the sender id is correct... May 17 13:00:38 Seems so May 17 13:03:48 Hmmz I changed everything into com.webos.service.systemservice and added org.webosports.app.firstuse to the role.json for com.webos.service.sysservice. The output looks slightly differnet then: https://paste.ubuntu.com/p/m2JCRbfkWy/ May 17 13:03:56 Let me see what I see in /var/log/messages now May 17 13:05:49 Hmmz the same it seems May 17 13:27:59 sorry I got carries away too May 17 13:28:17 LS2 doesn't output more about why it is refused? May 17 13:42:29 Not really May 17 13:42:40 Except for the SECURITY one... I had a similar one: May 17 13:13:31 qemux86-64 user.warn webos-telephonyd: [] [pmlog] LS_REQUIRES_SECURITY {"SERVICE":"com.palm.display","CATEGORY":"/","METHOD":"chargeSourceQuery"} Service security groups don't allow method call. May 17 13:44:58 Which I simply solved by adding networking.internal to com.palm.display in /usr/share/luna-service2/client-permissions.d/com.palm.luna.perm.json May 17 13:45:32 Seeing that this one is in networking.internal as per https://github.com/webOS-ports/webos-telephonyd/blob/3e5f820aae734a9c1a6cb009fd04a2e070b5ce04/files/sysbus/webos-telephonyd.api.json.in#L27 May 17 14:08:27 So something similar could work here May 17 14:08:47 Let me see if I can solve some more of these and then look into the firstuse ones May 17 16:46:13 Tofe: Still not much luck, however for apps got a clue... May 17 16:46:26 2020-05-17T16:41:52.626646Z [15.340832108] user.warning LunaWebAppManager [] LS_REQUIRES_SECURITY {"SERVICE":"(null)","CATEGORY":"/","METHOD":"launchApp"} Service security groups don't allow method call. May 17 16:46:45 Seems I forgot to include the api file for luna-webappmanager that should include the following API calls: https://github.com/webOS-ports/luna-webappmanager/blob/387f5f825759180c4a61c290c16ac358152f22ec/src/webappmanagerservice.cpp#L49 May 17 16:57:11 Herrie: ah, great, that should fix the launching of webapps indeeds May 17 17:19:37 Herrie: for getPreferences, correct me if I'm wrong, but it seems like luna-sysservice doesn't provide com.palm.systemservice anymore at all May 17 17:19:57 I only see "LSRegister("com.webos.service.systemservice", &serviceHandle, error))" in the source code May 17 17:21:28 though you already tried to change everything to com.webos.service.systemservice and it didn't work, I think it's the right way May 17 17:26:52 ah, wait, it's... rerouted ? there's something I missed here May 17 17:36:55 Tofe: We can register them under both names May 17 17:37:08 But then need to duplicate all API's etc as well May 17 17:37:14 It's a bit of a black box for me too May 17 17:37:17 don't we just miss a client-permission for luna-qml-launcher ? May 17 17:37:25 That could be it as well May 17 17:41:36 Tofe: In the dbus service file we can specify multiple names, so com.palm.webappmanager and org.webosports.webappmanager and com.webos.webappmanager for example May 17 17:44:59 Tofe: They have a qml-runner in OSE May 17 17:45:06 I guess if I copy that config and adjust it might work May 17 17:45:32 could be May 17 17:45:50 Grepping in OSE image to see where it's referenced May 17 17:59:01 Herrie: I think I fixed it, at least partially May 17 17:59:15 I provided a role and manifest for luna-qml-launcher May 17 17:59:26 and a client-permission too May 17 17:59:45 and a "container" too, but that one is probably doing nothing currently May 17 18:01:25 I just don't know what to do with it May 17 18:01:47 let me provide them to you too May 17 18:02:16 ok great May 17 18:05:49 https://github.com/webOS-ports/luna-qml-launcher/commit/98faf54a72d2426c4c9da99d3ab54d4102dec968 May 17 18:06:39 I thought the manifest file was generated automatically somehow? May 17 18:07:37 Herrie: little trick that may help here: to reparse the ls2 configuration, just do "kill -1 $(pidof ls-hubd)" May 17 18:12:19 it looks like it fixes phone app too May 17 18:22:17 Tofe: ah nice May 17 18:22:29 And the background image? May 17 18:43:00 not yet no, but that's luna-appmanager, and I saw some other ls2 issues May 17 19:10:58 Seems I didn't migrate luna-appmanager May 17 19:11:07 I think when I touched that one stuff didn't boot anymore May 17 19:11:11 I have some WIP for that though May 17 19:11:50 The manifest is generated by LS2 itself normally or during the build by one of the classes if I recall correctly May 17 19:21:08 Tofe: Hmmz for me it doesn't work... I guess I broke something else... Should start with clean qemux86-64 image I guess May 17 19:22:22 Let me try that May 17 19:34:44 Nope doesn't work for me May 17 19:35:19 Well Phone starts, lists remain empty May 17 19:39:02 Phone seems random though, sometimes starts, sometimes doesn't May 17 20:55:27 Tofe: Started a new build with the various fixes I just PR-ed May 17 20:55:43 And yours as well, so I don't get clutter from trials in there May 17 21:08:19 OK the feeds not working in FirstUse is due to non-bumped SRCREV for Firstuse May 17 21:09:15 Herrie: my commit was a bit at random, I didn't eliminate the useless stuff (container.d is probably useless, and the manifest should have been a generated one) May 17 21:09:42 still, we can eventually improve that when stuff works well May 17 21:11:02 Herrie: let's merge all your PRs ? May 17 21:11:13 or they are more for testing, as a reminder? May 17 21:13:49 merged (except the big ACG one), they seem like improvements May 17 21:18:52 Tofe: Yeah they don't hurt for sure **** ENDING LOGGING AT Mon May 18 02:59:57 2020