18:00:03 #startmeeting Mer-hybris Porters bug triage 18:00:03 Meeting started Tue Jan 20 18:00:03 2015 UTC. The chair is sledges. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 18:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:00:10 Welcome to the Mer-hybris Porters bug triage! 18:00:19 Hey 18:00:29 o/ situ 18:00:49 #info we have only one bug, but quite serious 18:00:55 #info We'll start with the bugs: https://bugs.nemomobile.org/buglist.cgi?bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=trivial&bug_status=NEEDINFO&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=TRIAGEDUPSTREAM&bug_status=REOPENED&component=Hybris-ing&email1=need-triage&emailassigned_to1=1&emailtype1=substring&order=bug_id&product=Hardware%20adaptation&query_format=advanced 18:01:06 #topic https://bugs.nemomobile.org/show_bug.cgi?id=785 - 2015-01-19 12:58:44 18:01:06 Nemo bug 785 in Hybris-ing "[hammerhead][mako] SailfishOS 1.1.1.27 "not responding" banner keeps appearing" [Normal,New] 18:01:26 it is affecting all devices except (ofc) jolla phone 18:02:14 I think I have seen it too. 18:03:30 it is fixed internally, but since i didn't find the package/commit, i don't know whether it will land into update11 or only update12 (as in jolla we are now working on 2 updates simultaneously) 18:04:18 it is not critical 18:04:25 as the banner can be dismissed 18:04:34 but annoying 18:05:19 High/major 18:05:24 ? 18:08:48 3...2... 18:09:04 o/ bijjal 18:09:17 o/ 18:10:12 we were just discussing that update10 introduced UX glitches on all devices except jolla :) 18:10:26 probably expected, as no QA, and tablet work is also ongoing 18:10:38 (which is why the glitch has been fixed in devel) 18:11:00 but i can't find the fixing commit, even after asking sailors around :D 18:12:48 are you referring to the UI "stuttering" ? (just got back from my lessons) 18:13:16 nope, about https://bugs.nemomobile.org/show_bug.cgi?id=785 18:13:16 Nemo bug 785 in Hybris-ing "[hammerhead][mako] SailfishOS 1.1.1.27 "not responding" banner keeps appearing" [Major,New] 18:14:05 ^ which is caused by notable absence of animations when bringing app to front 18:14:41 (homescreen doesn't scroll smoothly to reveal clock at that moment it just jumps straight there, and app just appears instead of fading-in) 18:15:44 sledges: ah, yes that was fixed, let me check bug fixes list 18:16:33 nice! good timing you're here :D 18:17:59 it was fixed in lipstick-jolla-home 18:18:26 oh ok cool, it might be complicated to backport it 18:18:31 how come jolla phone works 18:18:33 though 18:20:34 but bijjal , that fix has made it into update10, why are other devices still failing?.. 18:21:22 sounds libhybris related 18:21:29 think it happens on anything 4.4 18:21:37 mako is no 4.4 18:21:40 +t 18:21:44 also happening 18:21:51 now thats a good question, i do know that its not *fully* resolved, but the occurrence should really be low.. let me see if there are more fixes around that in devel 18:21:51 and is not happening for fingerterm 18:22:13 and voicecall-ui also works fine 18:22:54 bijjal: not responding is side-effect of rootcause, as e.g. nexus 5 doesn't produce not responding, unless under heavier load (faster cpu) 18:24:21 Stskeeps: internal devel build for nexus5 fixes it, libhybris still from outside, so no 18:24:25 hmm 18:24:27 that's curious 18:24:42 indeedski 18:26:31 it can be that it got fixed without developer not knowing this ^ problem, so no-one will be able to tell 18:26:39 just got fixed as a bonus 18:26:49 still checking bug lists.. didnt run away :P 18:27:05 no rush :) we got only 1 bug today :D and 60mins :)) 18:37:36 Stskeeps: would this help: https://bugs.nemomobile.org/attachment.cgi?id=93 ? 18:39:58 bijjal: i'll build an internal RC image for nexus5 and see if landed there, and to rule out devel being too slow due to debugging enabled / race conditions 18:41:57 sledges: ok, there are a couple of fixes to oom killer and app freezing conditions in internal RC, you may want to check them 18:42:41 bijjal: i'm putting my money on compositor, as per attachment: https://bugs.nemomobile.org/attachment.cgi?id=93 18:42:59 wl_display.sync is missing for those devices exposing symptoms 18:43:00 :) 18:44:05 but i checked quite a bit of repos which in/directly call wl_display (qtwayland, hwc, ..), and didn't find differences u10 vs devel 18:44:28 * sledges flabbergasted tbh 18:45:15 it's not critical, as one can still live with this glitch, hopefully until u11, yet annoying:) 18:54:13 i hope it goes away with u11, couldnt find anything more that shouts in this direction 19:06:03 bijjal: thanks for digging, being there for us :) 19:06:25 #info hope to test on u11 to narrow down suspects 19:06:30 thanks every1! 19:06:35 #endmeeting