[01:20] gerlowskija: https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04/ is the correct link for that [01:21] 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] (e.g. https://godoc.org/launchpad.net/go-unityscopes/v2#NewPreviewWidget) [01:23] (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] 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] gerlowskija: I'm guessing it comes from https://launchpad.net/go-unityscopes [01:33] maybe tedg can help you contribute [01:33] I'd recommend cwayne, but he's on holiday for a while [01:36] gerlowskija: yeah, looks like it's here: http://bazaar.launchpad.net/~unity-team/go-unityscopes/v2/view/head:/previewwidget.go [01:37] so you should be able to make a merge proposal against that project to correct the inline docs === chihchun_afk is now known as chihchun [03:34] mhall119: Someone on the scopes team would be best, jamesh or alecu would be good contacts there. [03:49] gerlowskija: thanks for letting us know about those broken links and outdated docs [03:49] I'll make sure we find the right person to fix it [03:51] alecu: if you see him/her online again, you've got an offer to get it fixed already :) [03:51] just need to know where and how === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [06:24] good morning === chriadam is now known as chriadam|away === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === davidcalle_ is now known as davidcalle === tux_ is now known as soupnanodesukar === oSoMoN_ is now known as oSoMoN === Acn0w- is now known as Acn0w === JMulholland_ is now known as JMulholland === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === _salem is now known as salem_ [13:40] 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] 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] mhall119: I would not recommend to include them to the phone image [13:44] mhall119: the quick controls are very much about desktops [13:51] bzoltan_: they would be useful when our phones are powering desktops [13:51] but I understand the reasons [14:12] 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 :) === Guest77290 is now known as balloons === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [18:15] Is the SDK PPA ready for wily? [18:20] I can't quite work out from the launchpad page whether wily builds are up and running... [19:29] Sorry to repeat, but does anyone know if it is safe to install the SDK PPA on wily? [19:31] mcphail: you don't need the ppa [19:31] only was for 14.04 / trusty [19:31] 14.10 forward has the sdk in the repos but 14.10 hit EOL [19:31] ahoneybun: Aah. OK. I was using it on vivid (I think...) :) [19:32] yea with vivid your good [19:32] the ubuntuphone is still based on 15.04 anyway [19:33] ahoneybun: so I can just apt-get install ubuntu-sdk on wily and everything will work? [19:33] yep [19:33] if you just want to install it on a phone you can just install ubuntu-device-flash [19:33] but if you want to develop as well the ubuntu-sdk is what you need [19:33] yep. Cheers [19:34] np [20:58] 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] Even when "idle", it is consuming 10% of CPU, but it keeps cranking up to 150% [21:02] This must be a bug. Nothing else on my system is hogging resources to that extent [21:15] OK, I've found https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614 . This is really broken [21:15] Ubuntu bug 1398614 in mediascanner2 (Ubuntu) "mediascanner-service-2.0 using large amounts of CPU" [High,Confirmed] === salem_ is now known as _salem [21:54] 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] mcphail, IIRC you can put a .nomedia file (or something similar) in any folders you want it to skip, ie external media [22:15] ahayzen: it has had hours to scan them, but still keeps spiking. I'll need to uninstall [22:16] 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] *expecting [22:16] ahayzen: where's the log? [22:17] mcphail, on the phone its in ~/.cache/upstart/mediascanner-2.0.log or something like that..so assume similar on the desktop [22:18] ahayzen: yes, log is there: all 819150 lines of it... [22:18] haha grep it for like error or something [22:19] bet it is looping [22:20] Lots of errors on .xcf files, but not sure there is any looping... [22:21] 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] But an 800000 line log file for an package which was only installed 2 hours ago is extreme, to say the least [22:23] 55 megabytes. Seriously? [22:23] * ahayzen hides [22:23] ha! [22:23] yeah its scary what it does :-/ [22:23] * ahayzen has the service disabled and manually runs when required [22:24] its a pretty big worry for when we start converging tbh [22:24] Unfortunately I can't uninstall without breaking the SDK [22:25] just disable the service [22:25] OK, will try [22:25] mcphail, make the file look like this http://pastebin.ubuntu.com/12784565/ [22:26] then just do the $ stop mediascanner-2.0 or use killall [22:27] mcphail, but whatever is causing it to loop and go mental should really be investigated and reported :-) [22:28] ahayzen: at least I now have an email address for my hitlist... :) [22:28] mcphail, pahah [22:29] OK, that seems to have worked. All's quiet on the mediascanner front for now [22:29] Cheers [22:30] 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] ahayzen: I think that, in itself, is a sad indictment of the package [22:31] 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] I'll try and trawl through the logs to see if there are any clues to the badness [22:32] thanks [22:32] I do worry, though, that it is just not very efficient [22:33] 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] you can see the sqlite tmp lock file being create/destroyed rapidly as it is indexing [22:33] oh dear. that is bad [22:34] yup [22:34] Presumably (if it uses > 100% CPU) it is threaded as well, so all those locks are going to be blocking something [22:35] isn't sqlite not good with concurrency ?! [22:36] Ha! sqlite is a nightmare, isn;t it? [22:36] :-) [22:38] I agree. It should only dommit every few seconds. RAM isn't going to be exhausted as it caches for a moment [22:38] *commit [22:38] i'm pretty sure that is what is happening anyway, things may have changed when i last tried to investigate [22:41] 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] yeah it should be simple todo if this is what it causing the slowdown [22:48] ahayzen: do you know the correct person(s) to poke about this? [22:49] mcphail, jamesh ;-) [22:49] does he IRC? I don't recognise the nick [22:49] mcphail, he is a AU timezone, so usually appears a different times to us EU/US folks [22:50] mcphail, oh he is in #ubuntu-touch you could try there, but i've found he is more responsive to emails [22:50] OK, i'll email him. Cheers - off to bed now [22:50] :-)