[05:47] <MrChrisDruif> Probably something that could be added to the FAQ but can I sideload Android apps like WhatsApp?
[05:48] <duflu> MrChrisDruif: Android apps are not supported, by any means
[05:49] <duflu> Normally you wouldn't document "things that don't work and are not intended to work", but I think this might be an exception. Because using the Android device and kernel people may well think Android apps would run
[05:55] <MrChrisDruif> Seeing that Android apps aren't the default on Sailfish OS but you can sideload them, I wouldn't be surprised if that question came up more frequently.
[06:17] <duflu> MrChrisDruif: Yeah I'm surprised too. Although maybe it does and I don't notice the IRC/web questions more often
[06:18] <duflu> I can't imagine a technical reason why someone can't some day add Android app support. It would be a significant effort though
[08:30] <Mikaela> SailfishOS people are unhappy about Android support as it takes resources from native apps and it's easier to get Android than native app to store and people won't bother making native apps as they can make Android apps. No idea where SailfishOS would be if the agreement with aliendalvik wasn't done though.
[08:46] <brunch875> I don't remember who told me before that the desktop yakketak comes with colorful smileys. Does it also come with easy means to type them?
[08:48] <sil2100> dpm: hey!
[08:48] <sil2100> dpm: we would need another package included in ubuntu-rtm/15.04 translations - sync-monitor
[08:49] <sil2100> It got recently pushed to translations.launchpad.net
[08:51] <dpm> sil2100, looking... I did see it when scanning for other missing translation templates after approving indicator-keyboard, but I didn't approve it as IIRC it was an old template from 2015
[08:53] <sil2100> dpm: yeah, I think upstream pushed the new one yesterday IIRC
[08:54] <dpm> sil2100, can you see this page? https://translations.launchpad.net/ubuntu-rtm/15.04/+source/sync-monitor/+imports
[08:54] <dpm> sil2100, it shows the 2015 upload, but not the most recent one
[08:58] <sil2100> hm
[08:58] <sil2100> I wonder where they pushed it?
[09:33] <sil2100> dpm_: so we need upstreams to push the pot files to the rtm series still, yes?
[09:33] <dpm_> sil2100, it'd be good to find out if a recent package upload happened and if that package contained the .pot file
[09:36] <sil2100> hm, ok so this happened so far:
[09:36] <sil2100> 21:14 < bfiller> renato, sil2100 : sync-monitor should now be configured properly in lp for translations
[09:36] <sil2100> 21:15 < bfiller> renato, please make sure to push the most updated .pot file to trunk directly
[09:36] <sil2100> 21:15 < renato> bfiller, it is up-to-date already
[09:36] <sil2100> Do we now need another package upload for sync-monitor then?
[09:49] <dpm> sil2100, it seems that the upstream project has been set up for translations, but probably the source package has not been set up for creating a .pot package on upload?
[12:03] <jgdx> mardy, ping
[12:10] <jgdx> zsombi, hey, after upgrading to yakkety, I'm having issues running apps locally. It used to work just fine on xenial. Have you experienced that?
[12:10] <jgdx> the bt says libubuntutoolkit is involved
[12:11] <zsombi> jgdx: afaik the yakkety is in pretty bad shape, we don't have stable version on 5.6 yet
[12:12] <jgdx> zsombi, okay, will look at downgrading
[12:14] <jgdx> or just buy a new laptop
[12:24] <mardy> jgdx: hi!
[12:25] <jgdx> mardy, hey, I'm debugging a crash in system settings, specifically in the About page. We load a plugin using pluginManager.getByName("foo") and then create a pagecomponent. This works fine once, but subsequent attempts will often lead to a crash.
[12:27] <jgdx> mardy, you're the author of that from what I can gather. Do you have any thoughts?
[12:28] <mardy> jgdx: I seem to remember that once kenvandine fixed a similar issue with a change which was apparently unrelated... let me see if I can find it
[12:28] <mardy> jgdx: it was some weird thing in QML
[12:28] <jgdx> mardy, this is also a qml runtime segfault
[12:28]  * kenvandine has a vague memory of this
[12:32] <jgdx> there are some qobject destruction via delete, that's the leading theory right now.
[12:32] <jgdx> (in the plugin manager)
[12:33] <kenvandine> jgdx, is this happening on vivid?
[12:33] <jgdx> kenvandine, yes
[12:33] <kenvandine> so we can't blame the new qt :/
[12:33] <jgdx> kenvandine, i think this is very old
[12:34] <kenvandine> jgdx, a crash in the about panel?
[12:34] <kenvandine> i haven't seen it crash
[12:34] <jgdx> kenvandine, bug 1617217
[12:35] <jgdx> kenvandine, the last comment is important
[12:36] <mardy> jgdx, kenvandine: could it have been rev 1521?
[12:37] <mardy> I remember that it was an apparent meaningless change, but it was actually fixing a crash
[12:37] <jgdx> on mako, a slower device than turbo, on which the bug can be reproduced reliably, it doesn't crash, but rather the pageComponent comes back falsy.
[12:38] <jgdx> mardy, let me try it
[12:39] <jgdx> mardy, lol, fixes it.
[12:40] <kenvandine> wow
[12:40] <kenvandine> mardy, good memory!
[12:40] <jgdx> jackprot
[12:40] <kenvandine> mardy remembers what i do better than i do :)
[12:41] <kenvandine> i vaguely remember fumbling around with this and being shocked at the fix
[12:41] <mardy> jgdx: now your task is to understand why that fixes it and document it ,-)
[12:41] <kenvandine> that's the challenge
[12:42] <jgdx> kenvandine, heeeey r1521 has to be amended
[12:42] <kenvandine> :)
[12:42] <mardy> kenvandine: it's surprising how you came up with this fix in the first place, it's certainly not something which would have ever crossed my mind :-)
[12:42] <jgdx> mardy, thanks btw
[12:42] <mardy> jgdx: yw :-)
[12:43] <kenvandine> my only thought is the qml runtime treated upPlugin or updatePage as a global or some nonsense
[12:44] <kenvandine> that was my theory at the time... but i had trouble believing that was actually the case
[12:44] <kenvandine> jgdx, it might be interesting to try only half the fix
[12:44] <kenvandine> like rename the page variable but not the plugin
[12:45] <kenvandine> and also try renaming the plugin variable and not the apge
[12:45] <kenvandine> page
[12:45] <kenvandine> narrow down the fix
[12:47] <jgdx> kenvandine, narrows it down to “plugin”'s absence leads to a crash
[12:48] <kenvandine> ok, so i guess upPlugin has some crazy scope
[12:48] <kenvandine> using that in multiple panels
[12:48] <kenvandine> i wonder if that's actually a qt bug
[12:58] <jgdx> mardy, kenvandine: an alternative fix is just keeping upPlugin in scope by assigning it to some element in the About page.
[12:58] <jgdx> so I think since pageComponent is the only thing we hold a reference to, some other things get collected by the engine, but not if we hold a ref to upPlugin
[13:01] <pmcgowan> bfiller, I am going to submit a branch to hide the character count option, its way complicated
[13:02] <bfiller> pmcgowan, ack
[13:04] <pmcgowan> bfiller, I will write up the design fwiw since now we understand it
[13:54] <rvr> popey: What's the url of your click backup site?
[13:56] <jgdx> rvr, it died/was moved (partially iirc) here: http://people.canonical.com/~alan/clicks/
[13:56] <rvr> jgdx: Thanks!
[14:16] <rvr> dpm: Hi. Did sil2100 ask you to add sync-monitor to ubuntu-rtm/15.04 series?
[14:17] <rvr> dpm: sil2100: Just read this https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617916
[14:19] <sil2100> rvr: yes, I asked, but it seems we need something done by the sync-monitor upstream still
[14:20] <sil2100> renatu: ping
[14:21] <sil2100> renatu: is sync-monitor correctly configured to build the pot files and export them to launchpad?
[14:21] <renatu> sil2100, just fixed that: https://requests.ci-train.ubuntu.com/#/ticket/1870
[14:21] <sil2100> renatu: excellent
[14:22] <sil2100> rvr: ^
[14:22] <sil2100> rvr: could we put that on the priority list?
[14:23] <sil2100> renatu: are all those fixes in the silo for OTA-13? I see one bug report not being targetted for any release?
[14:23] <renatu> let me re-check
[14:23] <sil2100> renatu: since we need to get this pot fix ASAP
[14:23] <renatu> they should
[14:23] <sil2100> So that people still have time to translate before we get our final images built
[14:24] <renatu> sil2100, if you prefer I can create a new silo only for that
[14:25] <renatu> kenvandine, could you review this? https://code.launchpad.net/~renatofilho/sync-monitor/fix-pot-build/+merge/304510
[14:26] <kenvandine> renatu, done
[14:27] <renatu> sil2100, I could push it direct to the trunk. Since this no need test
[14:28] <rvr> sil2100: Let me see
[14:28] <rvr> sil2100: To me it is ok
[14:29] <sil2100> renatu: I'll let rvr decide what he thinks, but I would personally like to fast-track the pot change ASAP, but if the other changes look fine then we could leave it as is and just ask QA to prioritize it a bit
[14:29] <renatu> kenvandine, could you top approval that :D
[14:30] <kenvandine> renatu, done
[14:30] <renatu> kenvandine, thanks
[14:30] <kenvandine> np
[14:30] <rvr> sil2100: "#1617916 Snyc-Monitor doesn't use translations in OTA-12" is on the regression list, so it's ok to do that silo
[14:31] <renatu> rvr, do you see any problem of pushing it to trunk without silo. Only for this mr?
[14:31] <renatu> https://code.launchpad.net/~renatofilho/sync-monitor/fix-pot-build/+merge/304510
[14:31] <rvr> renatu: I prefer to go through silos
[14:31] <renatu> ok
[14:31] <rvr> We are not in panic mode to commit to trunk :)
[14:31] <rvr> Let's follow the rules as usual