**** BEGIN LOGGING AT Wed Nov 04 02:59:58 2015 Nov 04 04:27:49 Herrie, I think you’re right that webOS 3.0.5 used green and red, but that does violate the Palm UI guidelines. Nov 04 05:31:11 morning Nov 04 05:31:29 Tofe: Not sure why but seems new qtwebengine-chromium changes didn't take in new build Nov 04 05:31:49 When I check log,I only see qtwebengine, no qtwebengine-chromium :S Nov 04 05:43:27 Herrie: Morning Nov 04 05:45:23 Just have a couple of fixes for RPi (including system menu update) then it should be stable/complete. Even replaced the boot logo with the LuneOS logo so it's not Static Logo -> Pulsing Logo -> System UI like on legacy webOS Nov 04 05:45:39 s/not/now Nov 04 05:46:18 I'm going to write a cast service for beaming to webOS TVs. Any feature requests? Nov 04 05:53:14 Andolamin: Nice now just need to figure out how to integrate all ;) Nov 04 05:53:30 Anolamin: Sadly I don't have a webOS TV, so little input from my side ;) Nov 04 06:05:15 No problem. Planning on supporting at least video/audio/picture casting and control. That will cover at least the basics. I guess I should start by setting up a Preware feed. Is the feed format documented somewhere? Nov 04 06:09:01 Yes it is Nov 04 06:09:29 http://www.webos-internals.org/wiki/Packaging_Standards#Version_2.6_.28Draft.2C_LuneOS_compatibility.29 Nov 04 06:10:22 What you need the Preware feed for? Nov 04 06:10:35 In general there are existing ones where you can submit to ;) Nov 04 06:14:35 Tofe: I guess we need a rebuild of qtwebengine itself in order for the chromium change to stick. I just added a simple blank line in a file and retriggered a build to see if that helps Nov 04 06:36:13 Herrie: mmh ok, we should remove that later Nov 04 06:36:35 but it's strange, because on my side it was taken into account Nov 04 06:38:46 Herrie: what log did you check? Nov 04 06:39:20 because there is no qtwebengine-chromium recipe as-is Nov 04 06:42:59 Tofe: Yeah, but I cannot find the rev for qtwebengine-chromium in the build log Nov 04 06:43:06 Only for qtwebengine Nov 04 06:43:21 Also build only took 24 mins while rebuild of qtwebengine takes 1,5 hr on builder uusally Nov 04 06:43:53 which build log? Nov 04 06:45:46 because anyway you didn't change the srcrev, so your empty change isn't very useful ;) Nov 04 06:46:43 I did Nov 04 06:46:50 oh, sorry, didn't see Nov 04 06:47:37 https://github.com/webOS-ports/meta-webos-ports/blob/fido/meta-luneui/recipes-qt/qt5/qtwebengine_git.bbappend Nov 04 06:47:59 I'm not sure why it wasn't working previously Nov 04 06:48:04 ah it's my rss feed which lags Nov 04 06:48:21 At least both bugs were present still on both mako & maguro Nov 04 06:48:29 I verified I had the correct build Nov 04 06:49:52 This si what I did last night: https://github.com/webOS-ports/meta-webos-ports/commit/7117c863d081bf8214264db29e447209fac972b5 Nov 04 06:49:57 I guess that with same srcrev bitbake didn't bother to rebuild Nov 04 06:50:09 Which should be OK: https://github.com/webOS-ports/qtwebengine-chromium/commits/webOS-ports/master Nov 04 06:50:24 But I guess it didn't rebuild because SRCREV for qtwebengine didn't change? Nov 04 06:50:37 yup Nov 04 06:50:45 That's my only guess for now. JaMa might have another explanation Nov 04 06:50:58 So I might a non-trivial change to qtwebengine to force it to rebuild :P Nov 04 06:51:31 maybe there's a way to make the build depend on both srcrev Nov 04 06:51:59 Yeah let's ask JaMa when he's around Nov 04 06:52:36 I propose we delete the empty commit when the build is done Nov 04 06:54:34 each modification we do is something to be rebased when we change the qt version, so let's keep it minimal Nov 04 06:58:36 Tofe: Agree Nov 04 08:05:04 morning Nov 04 08:11:23 morning :) Nov 04 08:11:35 (I didn't have coffee until now :) ) Nov 04 08:18:36 Tofe: I had a strong espresso + cappucino for breakfast :P Nov 04 08:18:53 Little one decided 5 was a nice time to wake up this morning LOL.... Nov 04 08:19:17 Sometimes the Mrs can trick him back to sleep, but not today so I was up at 5:45 Nov 04 08:57:07 Tofe: Build for Mako took 1,5 hrs now, so will check it over lunch when I'm at home and flash some devices :D Nov 04 11:59:39 Tofe: It's a lot better but still a few issues ;) Nov 04 11:59:56 After my account is added (gmail) and sync is completed, email app closes Nov 04 12:00:09 Also the list of emails doesn't show anything, but I do have a counter Nov 04 12:00:16 Saying I have 9 emails Nov 04 12:02:29 Let me see if my logs say anything useful Nov 04 12:16:17 https://bpaste.net/show/43f3fe63ff59 Nov 04 12:16:25 Nov 04 13:02:02 maguro ls-hubd[647]: [2015-11-04 13:02:02:469] [0x4016c2b0] [error] [com.palm.mail.validator]: Exception in command ConnectCommand: Address resolution failed -- /home/jenkins/workspace/luneos-testing/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/mojomail-common/2.0.0-99+gitAUTOINC+3a433c00b3-r0/git/common/src/network/SocketConnection.cpp:202 Nov 04 12:16:38 Those references to Jenkins look odd to me? Nov 04 12:17:44 Also Nov 04 13:02:10 maguro ls-hubd[647]: [2015-11-04 13:02:10:474] [0x4016c2b0] [error] [com.palm.imap.session]: error downloading part: InsertCacheObject: Failed to initialize new object for 'body.html'. (MojErr -199) -- /home/jenkins/workspace/luneos-testing/webos-ports/tmp-glibc/work/maguro-webos-linux-gnueabi/mojomail-imap/2.0.0-99+gitAUTOINC+3a433c00b3-r0/git/imap/src/commands/Fetc Nov 04 12:17:44 hPartCommand.cpp:211 Nov 04 12:21:59 That was on Maguro. There it didn't crash after sync Nov 04 12:22:18 On TP it crashes after the 2 banner messages for sync: https://bpaste.net/show/dd657950f8d9 Nov 04 12:33:39 address resolution failed... weird Nov 04 12:34:23 TOfe: I'm not sure that's the "autodiscover" feature to get the account settings that gives that tbh Nov 04 12:34:25 It could be Nov 04 12:37:34 Let me reboot device. COuld actually also be a first boot issue... Nov 04 14:01:33 Tofe: Still no email list after reboot. I'm not 100% sure it's QTWE or maybe something in backend when upgrading to Fido. Will check a bit in the evening Nov 04 14:04:28 ok Nov 04 14:06:35 Basically the list with emails (2nd panel) is empty. Nov 04 15:45:29 Herrie|Veer: Best way to simulate Settings.hasPowerButton == false when developing in Qt Creator? Nov 04 15:47:59 Andolamin: We still need to rework that a bit in the future. morphis made me aware that there's something called evdev which should have all button info. We'd need to plugin libevdev into luna-next so we could use it instead of the values we currently hav Nov 04 15:48:00 e in the .conf Nov 04 15:51:20 But we need someone with proper c++ knowledge to sort that (and I clearly lack there :p) Nov 04 15:51:41 For now we can use the .conf values Nov 04 15:53:04 Herrie|Veer: seems Andolamin asks about qt creator Nov 04 15:53:22 Andolamin: i think you can use https://github.com/webOS-ports/luneos-components/blob/master/test/imports/LunaNext/Common/SettingsStub.js Nov 04 15:53:47 nizovn: Perfect. Nov 04 15:53:55 nizovn: I know, I'm just giving him some bg because we had a change of plans :P Nov 04 15:54:03 Was getting to the code shortly :P Nov 04 15:54:07 yes, SettingsStub is the right place Nov 04 15:54:16 But you beat me to it :P Nov 04 15:54:20 ah :P Nov 04 15:55:12 Herrie|Veer: So, I'm guessing that the Settings accessor is unlikely to go away, just it will be implemented with evdev sometime in the future? Nov 04 15:56:02 Andolamin: Yeah we might need to do a different check, but the basics in QML can stay there :P Nov 04 15:56:25 The buttons will not magically grow themselves from false to true :P Nov 04 15:57:02 Heh, yeah Nov 04 15:57:40 libevdev is something up in nizovn's street maybe :P Nov 04 15:57:54 But I know he's tight on time these days.... Nov 04 16:04:38 Herrie|Veer: I completely forgot about the battery... Should we add a flag for checking if the device has a battery? Nov 04 16:05:11 Andolamin: Yeah that would make sense I guess. Nov 04 16:05:34 We need some more people with solid c++ knowledge :P Nov 04 16:05:39 Ok. I can implement and open a PR Nov 04 16:05:47 I'm lost there ;) Nov 04 16:05:54 I can do the battery stuff Nov 04 16:06:07 But ideally we get libevdev plugged in sometime soon. Nov 04 16:06:37 Yeah - do you know if libevdev can check for the presence of a battery? Nov 04 16:07:59 quite sure it can... Nov 04 16:08:04 morphis: ^ Nov 04 16:09:16 Hmmmz "any input device the kernel has a driver for" :s Nov 04 16:09:20 So I guess not? Nov 04 16:10:12 Might be there's already something in the webOS power stuff for it? Nov 04 16:10:23 Check the ls2 calls for the battery Nov 04 16:10:39 Not sure what these would return when there's no battery Nov 04 16:10:54 See StatusBar.qml :P Nov 04 16:12:02 or even berret qml/StatusBar/Indicators/BatteryIndicator.qml Nov 04 16:14:20 Sorry wrong one: qml/StatusBar/SystemMenu/BatteryElement.qml has the actual LS2 calls Nov 04 16:24:39 Herrie|Veer: On the Pi, journalctl shows "Powerd: No battery device found" and "Powerd: No charger device found" then com.palm.power refuses to handle any calls Nov 04 16:25:05 hm on emulator there is fake battery Nov 04 16:26:05 Yeah, I could probably follow the emulator method and fake the battery, but I think it would be better to just remove the indicators when there isn't a battery (or fake battery) present Nov 04 16:33:21 you can set visible to false here https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/StatusBar/SystemMenu/BatteryElement.qml#L45 Nov 04 16:44:24 nizovn: Yeah, hiding it if there's an error wouldn't be a bad idea Nov 04 16:44:50 At least until we have a proper way of detecting whether there's a battery Nov 04 17:42:46 Andolamin: com.palm.power doesn't even give an error back? Nov 04 17:43:45 LS2 gives me an error, but its because com.palm.power stops handling the calls so I get the generic method was not handled error Nov 04 18:00:39 Ah ok Nov 04 18:14:07 Tofe: Enyo 1 apps (email for example) app menu doesn't work Nov 04 18:14:13 Enyo 2 apps is fine Nov 04 18:47:46 Tofe: latest stable had no problems with email, so likely due to webengine Nov 04 18:48:13 Will try some things with webinspector Nov 04 18:48:29 Also Preware 2 in landscape is broken, portrait is fine Nov 04 19:03:55 Tofe: Email errors in webinspector: http://tinypic.com/r/1z3864z/9 Nov 04 19:10:40 DougReeder: On Preware2: Seems it works OK in Portrait, just landscape seems broken on my TP Nov 04 19:17:48 elvispre: I get ... for the MR, M+, MC buttons on N4 in portrait Nov 04 19:18:33 Herrie: Yeah, if you see my extra comment on the PR, I see that too. Nov 04 19:18:50 On the formula style input my bottom row buttons are cut off both portrait and landscape Nov 04 19:18:56 On TP all fine it seems Nov 04 19:19:20 Seems it might not take gesture bar height into consideration somehow Nov 04 19:19:41 But that could be something on app rendering side in qtwebengine not your code Nov 04 19:19:44 Not sure Nov 04 19:20:33 Herrie: No, I think the font is a unique choice. If I use the browser to access my gh-pages site, that renders it just fine. Nov 04 19:21:10 I could make the font a bit smaller, but I'm not sure it is the right solution. Nov 04 19:22:27 The other evening, I initially had the "..." problem, then "something broke" and it started scaling the font properly. Nov 04 19:22:49 (Or as I expect it to, anyway.) Nov 04 19:26:46 Herrie: Shall I withdraw the PR or just leave it pending while I try again? Nov 04 19:27:22 Leave it, it's pretty good as is Nov 04 19:27:36 Just with our current webengine migration it's hard to proper test for me Nov 04 19:27:54 Should keep 1 device on webkit to see if it's caused by webengine or not :P Nov 04 19:29:43 But I guess this fancy stuff doesn't fly with webkit? Nov 04 19:50:48 Herrie: It wasn't looking right on webkit, no. It renders sort of OK (badly but usably) even on Pre 3 though. Nov 04 19:51:56 The webengine stuff wasn't scaling the font at all last week so I have my fingers crossed that these issues might go away by themselves. Nov 04 19:52:36 The N4 aspect ratio is quite extreme though. I *can* reproduce the button clipping in a desktop browser if I try hard enough. Nov 04 20:28:59 Herrie: I pushed a few more commits to my PR. Calculator renders OK on my N4 now. Probably best to see how it looks on a LuneOS release candidate before accepting it. (Maybe I'll be able to make the button font bigger again.) Nov 04 20:33:49 Herrie: Is there a notification api for prompting the user for confirmation? Nov 04 21:01:47 Andolamin: Not really currently: what you want to do? Nov 04 21:03:18 Herrie: Was looking at putting the luna restart/restart/shutdown buttons inside a drawer in the actual system menu, but then the user should be asked to confirm. Decided to just re-use the old PowerMenu notification you linked to. Nov 04 21:04:51 ok Nov 04 21:05:23 Don't reinvent the wheel when you don't have to :P Nov 04 21:05:50 Well, wasn't trying to reinvent the wheel, more invent an alternative to the wheel, but yeah. Nov 04 21:06:40 Basically, as soon as it became apparent that I'd have to implement the prompt notification as well I decided to abandon that route Nov 04 21:12:38 Yeh ;) Nov 04 21:12:54 Might be something for later when we have out own styled mochi luneos-components in qml Nov 04 21:16:06 Agreed Nov 04 21:29:03 elvispre: nice, works good on Maguro, reflashing my Mako to latest nightly now as well Nov 04 21:30:01 Andolamin: How's the QtCreator experience? I know it's not fully a device, but it's pretty neat :) Nov 04 21:38:27 elvispre: I have 2 failures in the test :P Nov 04 21:38:45 Also the list is not stuck to the left... I.e. it can float a bit Nov 04 21:39:06 Also results ara showing outside of the rows on the right on N4 Nov 04 21:39:14 But calculator itself is working fine! Nov 04 21:39:38 Herrie: wait -- I just remarked that you said: it takes 1.5hr to compile WebEngine on our release machine !? Nov 04 21:40:02 Tofe: Well it's 1 hr extra compared to a normal build Nov 04 21:40:06 So about 1hr I guess Nov 04 21:40:13 Should be a lot quicker? Nov 04 21:40:14 ah ok Nov 04 21:40:37 well, not necessarily, but when we see the beast, we would think it would be quicker Nov 04 21:40:58 Normal build in 20-30 mins. With qtwebengine rebuild + 1hr Nov 04 21:41:01 it takes ~4hr on my machine, and it's now quite old Nov 04 21:41:11 But this is then reused for maguro, grouper and tenderloin Nov 04 21:41:17 qemux86 also takes longer then Nov 04 21:41:23 sure Nov 04 21:41:31 Also about 85-90 mins Nov 04 21:41:40 I guess adding ram won't help, then :p Nov 04 21:42:00 Tofe: Could be build machine can use some tweaks in params :P Nov 04 21:42:18 And it's VM so a little slower compared to native as well (though shouldn't be much) Nov 04 21:42:57 I'm sure JaMa or ka6sox could tell more about that Nov 04 21:43:28 well, build time is still reasonable, we don't do much in 1.5hr... Nov 04 21:44:42 Tofe: Yeah and when needed can always abort :P Nov 04 21:44:55 Not sure my screenshot above is of any use Nov 04 21:45:00 But might give you some pointers Nov 04 21:45:36 elvispre: With "list doesn't stuck to the left", I mean that I have horizontal scrollbars which do funny stuff when you scroll vertically ;) Nov 04 21:47:05 Herrie: for email ? Nov 04 21:47:31 it's a great screenshot actually. Nov 04 21:48:07 Tofe: Yeah Nov 04 21:48:15 And Enyo1 appmenu's don't work Nov 04 21:48:24 You probably need to do a similar trick as for Enyo 2 ones Nov 04 21:49:33 the work I did should be for both Nov 04 21:50:00 It doesn't work for me in Tweaks and Email which both have an app menu on 3.0.x ;) Nov 04 21:50:30 On the other hand, with migration & fixes http://issues.webos-ports.org/issues/765 got sorted it seems :D Nov 04 21:50:40 So for stability quite some improvements were made in general Nov 04 21:50:53 Just a few minor things to iron out for apps it seems Nov 04 21:51:07 I doubt actually that app menu worked with qtwebkit for Enyo 1 apps Nov 04 21:51:14 I think it's been broken for quite some time Nov 04 21:51:22 Just never really paid attention tbh Nov 04 21:51:23 yes; we are now mainly dealing with bugs that were certainly there before Nov 04 21:51:48 The email/Preware 2 landscape bug I haven't seen with qtwebkit Nov 04 21:51:57 Preware 2 in portrait is fine Nov 04 21:52:11 So they MIGHT actually be the same bug somehow, not sure Nov 04 21:52:21 Could be it's something with the screen height or something, not sure Nov 04 21:52:27 Viewport maybe something? Nov 04 21:52:55 that could be. I'm constraining the width, but not the height (when there is no viewport) Nov 04 21:53:29 It's easy to try though Nov 04 21:55:32 wait - what is the bug, exactly ? preware looks fine in landscape on my device Nov 04 21:56:02 Herrie: Openning a PR for luna-next-cardshell. Don't merge it yet, want to finish this build and test on the actual device, but I figured I would go ahead and open it anyway. Nov 04 21:56:17 Andolamin: ok Nov 04 21:56:20 Tofe: Click on apps, then there are no further categories Nov 04 21:56:29 basically blank panel Nov 04 21:56:34 Also, Working with Qt Creator is going pretty well. Nov 04 21:56:45 Tofe: I'm also waiting for qtwebengine/5.5.99+5.6.0-alpha1+gitAUTOINC+68af6c2275-r0 build for very long time any webkit/webengine/chromium build is big pia Nov 04 21:56:53 Herrie: not blank here Nov 04 21:57:00 Tofe: This is me trying to tap App Menu many times in Tweaks: https://bpaste.net/show/fb35a6c71184 Nov 04 21:57:01 Herrie: maybe the scenario is a bit more complicated Nov 04 21:57:32 Herrie: looks good Nov 04 21:58:11 JaMa: ok Nov 04 21:58:48 JaMa: btw, do you know what we could do so that even if we only bump srcrev of qtwebengine-chromium (and not qtwebengine), it will trigger a rebuild ? Nov 04 21:59:26 Should we include chromium's srcrev in package's version? Nov 04 22:00:28 Tofe: Yeah log looks good but no app menu visible. z-index issue or positioning? Nov 04 22:00:59 Herrie|Veer: I don't know at all yet Nov 04 22:03:13 Just things that come to my mind Nov 04 22:05:45 Tofe: either change SRCREV_FORMAT = "qtwebengine" Nov 04 22:06:05 to SRCREV_FORMAT = "qtwebengine_chromium" Nov 04 22:06:16 or do_fetch[depends] += "SRCREV_chromium" Nov 04 22:07:55 JaMa: I like the latter proposition Nov 04 22:08:28 I'll make a PR tomorrow with that Nov 04 22:08:33 for now, sleep. Nov 04 22:08:35 gn8! Nov 04 22:08:47 gn8 Nov 04 22:09:21 Tofe: gn8 Nov 04 22:14:12 Herrie: Calculator failing tests are not so much wrong as not quite generating the results I would like to see. It was my motivation for hiding the tests panel when not in dev mode. Nov 04 22:15:28 I have not worried about the tests panel layout too much for the same reason (don't see it in release mode anyway). Nov 04 22:25:58 elvispre: OK just don't remember I saw failing tests before so just wanted to let you know :P Nov 04 22:26:04 OK on the layout Nov 04 22:26:47 For browser vs apps: We force a few things in app rendering like Prelude font. But also some other things for the LunaWebEngineView Nov 04 22:28:30 Right, so some differences are expected. Nov 04 22:29:35 Yeah Nov 04 22:29:42 We also do some things with viewport I think Nov 04 22:29:51 Tofe can tell you more about what exactly Nov 04 22:31:05 See https://github.com/webOS-ports/luna-webappmanager/commit/6e600641f5457ddf3ff19a6824f27b9c1e8b41f1 and https://github.com/webOS-ports/luna-webappmanager/commit/02ce884c95033445700988de2615fc39e8ad6767 Nov 04 22:34:31 Herrie: Interesting, thanks. Nov 05 00:03:03 Tofe: do_fetch[vardeps] not do_fetch[depends] as I said earlier.. sorry don't know what I was thinking about.. :)