[01:20] <mhall119> gerlowskija: https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04/ is the correct link for that
[01:21] <gerlowskija> Thanks mhall119, is there any way I can help update the links on the golang.org documentation so they point a legit pages?
[01:22] <gerlowskija> (e.g. https://godoc.org/launchpad.net/go-unityscopes/v2#NewPreviewWidget)
[01:23] <gerlowskija> (There's a few broken links that have corresponding SDK doc pages, and could probably be updated.  Though maybe there's a reason they're not linked up)
[01:26] <mhall119> gerlowskija: I'm not sure who manages those, but I'm sure there's a way you can help fix them if we find someone who can tell us how
[01:32] <mhall119> gerlowskija: I'm guessing it comes from https://launchpad.net/go-unityscopes
[01:33] <mhall119> maybe tedg can help you contribute
[01:33] <mhall119> I'd recommend cwayne, but he's on holiday for a while
[01:36] <mhall119> gerlowskija: yeah, looks like it's here: http://bazaar.launchpad.net/~unity-team/go-unityscopes/v2/view/head:/previewwidget.go
[01:37] <mhall119> so you should be able to make a merge proposal against that project to correct the inline docs
[03:34] <tedg> mhall119: Someone on the scopes team would be best, jamesh or alecu would be good contacts there.
[03:49] <alecu> gerlowskija: thanks for letting us know about those broken links and outdated docs
[03:49] <alecu> I'll make sure we find the right person to fix it
[03:51] <mhall119> alecu: if you see him/her online again, you've got an offer to get it fixed already :)
[03:51] <mhall119> just need to know where and how
[06:24] <dholbach> good morning
[13:40] <mhall119> bzoltan_: do we ship QtQuick.Controls as part of the base image yet? If not, do we have any plans to do so?
[13:43] <bzoltan_> mhall119: the QtQuick Controls are provided by the qml-module-qtquick-controls  qtdeclarative5-controls-plugin packages and no, they are not on the default image
[13:44] <bzoltan_> mhall119: I would not recommend to include them to the phone image
[13:44] <bzoltan_> mhall119:  the quick controls are very much about desktops
[13:51] <mhall119> bzoltan_: they would be useful when our phones are powering desktops
[13:51] <mhall119> but I understand the reasons
[14:12] <bzoltan_> mhall119:  it does not take more then adding it to the seeds. But the apps using quick controls would surelly look funny on a high dpi small screen :)
[18:15] <mcphail> Is the SDK PPA ready for wily?
[18:20] <mcphail> I can't quite work out from the launchpad page whether wily builds are up and running...
[19:29] <mcphail> Sorry to repeat, but does anyone know if it is safe to install the SDK PPA on wily?
[19:31] <ahoneybun> mcphail: you don't need the ppa
[19:31] <ahoneybun> only was for 14.04 / trusty
[19:31] <ahoneybun> 14.10 forward has the sdk in the repos but 14.10 hit EOL
[19:31] <mcphail> ahoneybun: Aah. OK. I was using it on vivid (I think...) :)
[19:32] <ahoneybun> yea with vivid your good
[19:32] <ahoneybun> the ubuntuphone is still based on 15.04 anyway
[19:33] <mcphail> ahoneybun: so I can just apt-get install ubuntu-sdk on wily and everything will work?
[19:33] <ahoneybun> yep
[19:33] <ahoneybun> if you just want to install it on a phone you can just install ubuntu-device-flash
[19:33] <ahoneybun> but if you want to develop as well the ubuntu-sdk is what you need
[19:33] <mcphail> yep. Cheers
[19:34] <ahoneybun> np
[20:58] <mcphail> Aargh. This is so frustrating. I installed the Ubuntu-SDK, and now mediascanner is melting my CPU. Is there any way to stop it?
[21:01] <mcphail> Even when "idle", it is consuming 10% of CPU, but it keeps cranking up to 150%
[21:02] <mcphail> This must be a bug. Nothing else on my system is hogging resources to that extent
[21:15] <mcphail> OK, I've found https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614 . This is really broken
[21:15] <ubot5`> Ubuntu bug 1398614 in mediascanner2 (Ubuntu) "mediascanner-service-2.0 using large amounts of CPU" [High,Confirmed]
[21:54] <ahayzen> mcphail, it is probably just trying to scan your media directories... you can prevent the process from respawning by editing this file /usr/share/upstart/sessions/mediascanner-2.0.conf
[21:55] <ahayzen> mcphail, IIRC you can put a .nomedia file (or something similar) in any folders you want it to skip, ie external media
[22:15] <mcphail> ahayzen: it has had hours to scan them, but still keeps spiking. I'll need to uninstall
[22:16] <ahayzen> mcphail, have a look at the log, sometimes if it hits a bad file format/metadata it wasn't expect it'll keep looping
[22:16] <ahayzen> *expecting
[22:16] <mcphail> ahayzen: where's the log?
[22:17] <ahayzen> mcphail, on the phone its in ~/.cache/upstart/mediascanner-2.0.log or something like that..so assume similar on the desktop
[22:18] <mcphail> ahayzen: yes, log is there: all 819150 lines of it...
[22:18] <ahayzen> haha grep it for like error or something
[22:19] <ahayzen> bet it is looping
[22:20] <mcphail> Lots of errors on .xcf files, but not sure there is any looping...
[22:21] <ahayzen> maybe worth just reading the last part of the file with $ tail -n NUMBEROFLINES ... or just renaming the file and letting it generate a new one
[22:22] <mcphail> But an 800000 line log file for an package which was only installed 2 hours ago is extreme, to say the least
[22:23] <mcphail> 55 megabytes. Seriously?
[22:23]  * ahayzen hides
[22:23] <mcphail> ha!
[22:23] <ahayzen> yeah its scary what it does :-/
[22:23]  * ahayzen has the service disabled and manually runs when required
[22:24] <ahayzen> its a pretty big worry for when we start converging tbh
[22:24] <mcphail> Unfortunately I can't uninstall without breaking the SDK
[22:25] <ahayzen> just disable the service
[22:25] <mcphail> OK, will try
[22:25] <ahayzen> mcphail, make the file look like this http://pastebin.ubuntu.com/12784565/
[22:26] <ahayzen> then just do the $ stop mediascanner-2.0 or use killall
[22:27] <ahayzen> mcphail, but whatever is causing it to loop and go mental should really be investigated and reported :-)
[22:28] <mcphail> ahayzen: at least I now have an email address for my hitlist... :)
[22:28] <ahayzen> mcphail, pahah
[22:29] <mcphail> OK, that seems to have worked. All's quiet on the mediascanner front for now
[22:29] <mcphail> Cheers
[22:30] <ahayzen> mcphail, no problem, and if it managed to scan enough most mediascanner things still work, eg i work on the  music-app with my service disabled :-) (just don't get new files until i rerun it)
[22:30] <mcphail> ahayzen: I think that, in itself, is a sad indictment of the package
[22:31] <ahayzen> mcphail, yeah it is really not in a good state when you have 50+ GB of music and like 25+ of photos/videos for it to scan
[22:31] <mcphail> I'll try and trawl through the logs to see if there are any clues to the badness
[22:32] <ahayzen> thanks
[22:32] <mcphail> I do worry, though, that it is just not very efficient
[22:33] <ahayzen> from my analysis it seems to commit to its db between indexing every file, i feel it would speed it up if the commit was batched
[22:33] <ahayzen> you can see the sqlite tmp lock file being create/destroyed rapidly as it is indexing
[22:33] <mcphail> oh dear. that is bad
[22:34] <ahayzen> yup
[22:34] <mcphail> Presumably (if it uses > 100% CPU) it is threaded as well, so all those locks are going to be blocking something
[22:35] <ahayzen> isn't sqlite not good with concurrency ?!
[22:36] <mcphail> Ha! sqlite is a nightmare, isn;t it?
[22:36] <ahayzen> :-)
[22:38] <mcphail> I agree. It should only dommit every few seconds. RAM isn't going to be exhausted as it caches for a moment
[22:38] <mcphail> *commit
[22:38] <ahayzen> i'm pretty sure that is what is happening anyway, things may have changed when i last tried to investigate
[22:41] <mcphail> I'm not a developer, but I have hacked a fair bit of code on thesilversearcher (a grep-like program) and you can cache a lot of search results if you do it efficiently
[22:43] <ahayzen> yeah it should be simple todo if this is what it causing the slowdown
[22:48] <mcphail> ahayzen: do you know the correct person(s) to poke about this?
[22:49] <ahayzen> mcphail, jamesh ;-)
[22:49] <mcphail> does he IRC? I don't recognise the nick
[22:49] <ahayzen> mcphail, he is a AU timezone, so usually appears a different times to us EU/US folks
[22:50] <ahayzen> mcphail, oh he is in #ubuntu-touch you could try there, but i've found he is more responsive to emails
[22:50] <mcphail> OK, i'll email him. Cheers - off to bed now
[22:50] <ahayzen> :-)