[00:23] <daniel_> I seen the lastest OTA arrived tonight which i think was version 26 which OTA number was it and have you a link to the latest update changes?
[00:24] <slangasek> daniel_: hi - this was an accidental early publication of an update; it's been withdrawn again from the servers, sorry about that
[00:25] <slangasek> daniel_: if you got it installed, you're one of the lucky few and you get to keep the new OTA-7 code early
[00:25] <sil2100> daniel_: it will be officially available around Monday
[00:25] <daniel_> also, on reboot i find that the bq aquarius doesnt reboot even if there is battery power! until i plug in into mains power supply then a reboot happens
[00:26] <slangasek> is that a new problem you're seeing after downloading this new update?
[00:26] <daniel_> guess i am a lucky one, ref OTA 7
[00:26] <pmcgowan> daniel_, hey, the OTA is still being qualified so it was unintentional that it showed up, did you download or just looking for whats to come?
[00:27] <daniel_> had the latest OTA 7 update from what i see it downloaded and rebooted phone
[00:28] <daniel_> i wasn't expecting it this time i waited normally i check to see when its arrival date is
[00:28] <daniel_> this won't inhibit my phone will it?
[00:29] <slangasek> daniel_: it should not.  you have the same code that we were planning to release to all users early next week
[00:30] <daniel_> whats is there that has come or about to come?
[00:30] <sil2100> daniel_: the update is safe, it passed QA testing already so all should be good - there was just still one test that our QA team wanted to do, which is why the image release date is next week
[00:30] <sil2100> daniel_: sadly, the official release notes are not yet ready ;)
[00:31] <daniel_> how unusual for me! i feel blessed if thats the phrase i should coin! this was the version 26 release? how many others did it go out to?
[00:33] <sil2100> daniel_: we hope that not too many ;) We always feel a bit bad if an image that did not have all of our QA processes finished going out to the users, so we hope only a few people got it
[00:34] <pmcgowan> daniel_, thats not any sort of known issue
[00:34] <sil2100> Nothing bad if people got it, but still, we prefer if the image is released with phasing and in proper timelines
[00:34] <pmcgowan> daniel_, its the final version to be released early next week so its ok that you got it, but we were awaiting more testing results
[00:34] <pmcgowan> daniel_, is your reboot issue new?
[00:35] <daniel_> i didn't file a bug report as it only happens occassionally!
[00:37] <daniel_> i chatted with some one else on freenode they had the same issue and plugging into mains power corrected it! luckky for me i am not reliant on the phone on a business basis and this effect happened when i was on a beach and needed some time out anyway! phone rebooted and operational now though
[00:38] <daniel_> will i need to make any further adjustments when the official OTA is released?
[00:40] <daniel_> also had a battery deprecation from about 50% down to zero today at around 9pm uk time! seemed very odd!
[00:41] <sil2100> daniel_: hey, no, no adjustments needed :) As for battery usage issues, we're looking into these all the time but it's hard to get all of them fixed
[00:41] <daniel_> never had a power consumption like that with no other resources or processes  running at that time
[00:42] <daniel_> yes tricky one to fix unless your rebooting phone constantly i guess luckyily for me its only happend on two or three occasions
[00:44] <daniel_> as to the sudden drop in battery eariler i wondered if i was near a magnet of some sort! is this possible say for a person to carry a device to zero out your battery level?
[00:55] <ahoneybun> jose: are you the one who rejected me
[00:58] <ahoneybun> lol
[01:00] <daniel_> do you have a reply to the 50% to zero battery life i experienced earlier or should i not be concerned?
[01:00] <daniel_> no apps or resources were being used at that period of time!
[01:04] <slangasek> daniel_: as pmcgowan said, it's not a known issue.  there's probably not anyone around currently who could try to debug this with you, sorry - but it doesn't seem to be a common problem
[01:04] <sil2100> daniel_: did you fill in a bug already? I don't think I can help here, since I did not experience it on my arale phone yet
[01:04] <slangasek> I'm not saying you shouldn't be concerned about it... having your phone's battery drain *is* concerning
[01:06] <daniel_> just wondered thought it maybe a freak of nature or was paranoid that someone had a deivce locally that would drain it unnecessarily
[01:07] <pmcgowan> daniel_, which phone do you have?
[01:08] <daniel_> thanks again for your information! i will  forward to the official release ntoes when the become avaiable
[01:08] <pmcgowan> on arale there are reports of occasional fairly rapid battery drain, but BQ devices should be better than android
[01:08] <daniel_> using the BQ aquarius E4.5
[01:08] <pmcgowan> i.e. mx4
[01:09] <pmcgowan> daniel_, no that should be very good on battery, you may want to file a report
[01:09] <daniel_> never had this occur before
[01:09] <daniel_> i'll file a report if i get a repeat of the occurance
[01:10] <pmcgowan> thanks
[01:10] <daniel_> love this phone so far and when time comes will update to an newer phone running ubuntu!
[01:11] <pmcgowan> thank you
[01:12] <daniel_> are you the devs involved with the release cycles?
[01:13] <pmcgowan> yes, many are on this channel all the time
[01:13] <daniel_> nice to know that i can relay back to you and i'll try not to take up too much of your time!!
[01:13] <sil2100> Yes, glad to hear you like it!
[01:13] <sil2100> No worries, we're all here to help as much as we can
[01:15] <jose> ahoneybun: sorry? rejected you from what?
[01:15] <daniel_> will have a play around from the user experience and perhaps join you again on a future gogole hang out !
[01:15] <ahoneybun> oh not you then lol
[01:15] <ahoneybun> jose: I tried to get into the loco council ml
[01:15] <jose> I'm no longer part of the loco council, and that ml is private
[01:16] <jose> sorry :)
[01:18] <ahoneybun> jose: I just wanted to see if someone put my name forward lol
[01:18] <daniel_> user experience point of view! yet to delve into contributing ubuntu will have to join an OS project of some kind!
[01:18] <ahoneybun> mailing list should not be private
[01:18] <jose> ahoneybun: (#ubuntu-locoteams)
[01:19] <daniel_> slaters people
[01:24] <sil2100> Goodnight o/
[03:22] <lotuspsychje> good morning
[03:24] <lotuspsychje> i have an issue on my bq 4.5 updated to latest: everytime i try to install something it re-asks my ubuntu one account and loops back to it with 'account error' even tryed to make a new account but problem remains..is this a known bug?
[03:29] <lotuspsychje> cant install logviewer to see whats going on, no syslog or dmesg errors neither
[06:31] <EdwardMorbius> morning :) is OTA-6 hotfix phased like other updates?
[06:50] <dholbach> good morning
[07:24] <DanChapman> good morning o/
[08:08] <matv1> hmm i just smashed my bq on the floor which is now unusable. Luckily i still had the nexus4 with some ancient UT release. I reflashed it with --wipe. all looks well but what i noticed is that last update date shows 1/1/70
[08:10] <matv1> known bug?
[08:10] <matv1> reflashed it to stable i should add
[08:11] <mcphail> What's the bq OTA this morning? A security fix for the "test" app or a full OTA?
[08:13]  * matv1 is wondering where that would be registered to.. Canonical system image??
[08:15] <mcphail> Actually, I've clicked on the "Updates" page and the OTA isn't there. Why did I get a notification???
[08:35] <EdwardMorbius> for me the hotfix didnt arrive yet as well
[08:35] <teve> "So, due to a unfortunate mistake the OTA-7 update got prematurely"
[08:35] <teve> published for a few minutes last night - which is why people had the
[08:35] <teve> update notification on their phones.
[08:36] <EdwardMorbius> is hotfix phased like other ota updates?
[08:40] <mcphail> I've not had any updates for ages, so was quite pleased to see the update notification this morning
[08:40] <mcphail> Buth nothing was there :(
[08:41] <EdwardMorbius> mcphail I think last update was on 20.9 or something, otas come once every 6 weeks or so I believe.
[08:42] <mcphail> Yes, but was expecting a hotfix. Or is that just for meizu phones?
[08:42] <EdwardMorbius> hotfix should be for all phones but I am also waiting for it
[08:42] <mcphail> EdwardMorbius: you on bq?
[08:42] <EdwardMorbius> mcphail yes E4.5 from one of the flash sales
[08:43] <mcphail> EdwardMorbius: I wonder if bq are doing their usual lengthy QA on it
[08:43] <EdwardMorbius> mcphail I dont know which why I asked whether ota with hotfix is maybe phased because than would mean 24 hours to get it
[08:44] <EdwardMorbius> mcphail not that I downloaded the test application, but I still like my updates :D
[08:44] <mcphail> EdwardMorbius: I'm hoping they sneak a couple of bugfixes along with it :)
[08:45] <EdwardMorbius> mcphail I dont think so, if I read the mail on the mailing list correctly its the same as OTA-6 but with this hotfix, OTA-7 will come next week with fixes :)
[08:46]  * mcphail tries to be patient
[08:47] <matv1> mcphail EdwardMorbius As far as I saw in earlier OTA's BQ was always quite quick with their part
[08:47] <EdwardMorbius> mcphail still much better than android, new ota every 6 weeks plus bugs like this fixed fast, on android you wait for months for your manufacturer to release a point release update for Android, if you get it at all.
[08:47] <EdwardMorbius> mcphail mostly yes, though last ota came some days after meizu because of their testing.
[08:47] <mcphail> matv1: OTA6 took about 5 days longer from bq
[08:49] <EdwardMorbius> I understand that bq wants more testing, not fun getting your support spammed if something goes wrong with the image :))
[08:50] <EdwardMorbius> by the way did anyone have their weather apps stop working properly? like opensweathermap api is down or something? michael zanettis app for example
[08:51] <mcphail> I have never actually used the weather app
[08:52] <EdwardMorbius> mcphail I used michael zanettis app but for some reason weather is not update for some days now, I installed another weather application and it seems to be working, weird.
[08:52] <EdwardMorbius> default weather app is a bit underwhelming
[08:52] <matv1> EdwardMorbius I just checked. Same here.
[08:53] <EdwardMorbius> matv1 then its probably something on the openweather side
[08:53] <EdwardMorbius> though yaoswa app seems to be working
[08:53] <matv1> must be. changing to the weatherchannel as data input helps
[08:54] <EdwardMorbius> matv1 unfortunately mz's app doesnt have another backend
[08:54] <matv1> ah i see. I mostly just look out the window :)
[08:55] <matv1> that backend always works
[08:55] <EdwardMorbius> matv1 me too but sometimes I like to check the temperature or a short forecast
[08:55] <EdwardMorbius> at least there is no shortage of weather apps in the store :D
[08:56] <matv1> EdwardMorbius true :)
[08:56] <EdwardMorbius> weather apps on android are often just for eye candy because they look pretty on the home screen
[08:58] <matv1> EdwardMorbius well pretty counts too. I am glad Canonical design pays attention to pretty :)
[08:59] <EdwardMorbius> matv1 yes design is pretty important to users, too bad they changed the overall theme, I liked the old theme during development better, the dark one that looked more ubuntu
[09:00] <JamesTait> Good morning all; happy Friday, and happy World Food Day! 😃
[09:01] <EdwardMorbius> when some people saw apps scope on my phone they said it looks a bit like ios which I didnt take as a compliment XD
[09:01] <matv1> EdwardMorbius I agree mostly. But i understand why its easier to do design with a consistent whitish background
[09:02] <matv1> haha no that is downright insulting :D
[09:02] <EdwardMorbius> matv1 probably yes though theming is planned in the future I believe
[09:03] <EdwardMorbius> I am not sure if the messaging app in ota-6 was a bug or a feature, it has new lines, separators or something that dont look good.
[09:39] <robin-hero> Hi! I got a notification about a new release this morning, but when I clicked on it the update manager showed there's no available update. What was this?
[09:45] <dholbach> robin-hero, https://lists.launchpad.net/ubuntu-phone/msg16258.html
[09:46] <robin-hero> dholbach: Thanks
[09:46] <robin-hero> but I only got a notification
[09:47] <dholbach> yeah, it was pulled again
[09:49] <DrColossos> Hello, I'd love to get Ubuntu on my HTC Desire Z ... no luck so far
[09:50] <DrColossos> I followed the guide at https://wiki.ubuntu.com/Touch/Devices/flipped_vision, both via phablet-flash, and manual flashing via 4ext recovery ...
[09:51] <robin-hero> dholbach: Sorry, but I don't understand what you mean on this.
[09:51] <DrColossos> in either case, it does not work - screen stays black, backlight comes on a few times, but gets all black again ... doing that over and over again
[09:51] <dholbach> robin-hero, the update was released prematurely, when discovered it got pulled from the channel again - it was available for 18 mins and will be put out there officially in due time
[09:52] <DrColossos> I was able to get cyanogenMod 10.1 on it, so the device sure works
[09:52] <robin-hero> dholbach: Oh thanks, I got it
[09:54] <DrColossos> anybody has a clue what I could do to get Ubuntu running on my HTC Desire Z?
[10:05] <sil2100> uh oh topic too long
[10:08] <sil2100> Better, although a bit less verbose
[10:54] <tvoss> mardy, around?
[11:13] <Saviq> charles, hey, is it a known issue that the BT indicator on flo/vivid would show BT as being off, when it actually works?
[11:15] <doko> pstolowski, tvoss sent me here. is mediascanner2 in -proposed still targeted for wily?
[11:16] <pstolowski> doko, not sure, jamesh may know?
[11:17] <neolynx> hi all
[11:17] <doko> oh man, I like being passed around :-/
[11:17] <neolynx> I'm trying to boot with break=top on an bq aquaris E4.5 ubuntu phone, without success. adb shell does not find a device
[11:17] <pstolowski> doko, sorry, not my baby ;)
[11:17] <neolynx> any ideas on this ?
[11:18] <akik> adb works on the ubuntu phone?
[11:18] <neolynx> akik: yes as soon as the android HAL container has initialized the hardware
[11:19] <neolynx> as fas as i can tell
[11:19] <akik> do you have android installed on the e4.5 ?
[11:19] <tvoss> doko, it's only hope 2 :)
[11:19] <neolynx> akik: please read my question, it's an ubuntu phone
[11:19] <tvoss> hop, even :)
[11:19] <akik> neolynx: i'm just wondering how android and ubuntu go together?
[11:20] <neolynx> akik: ubuntu phone piggy backs on android in an LXC for hardware abstraction
[11:20] <akik> neolynx: where can i read more about this? i'm interested to learn more
[11:21] <akik> do you know if meizu mx4 has the same kind of container?
[11:23] <doko> tvoss, pstolowski: this is https://bugs.launchpad.net/ubuntu/+source/qtubuntu-media/+bug/1500859. is OTA7 before the wily release?
[11:23] <ubot5`> Ubuntu bug 1500859 in qtubuntu-media (Ubuntu) "hard coded dependency on non-existing version of runtime library" [Critical,Fix committed]
[11:23] <neolynx> akik: https://developer.ubuntu.com/static/devportal_uploaded/136981fa-6287-49d3-9874-06f40b2e4eb7-cms_page_media/380/ubuntu_touch_architecture.png
[11:23] <ahoneybun> somebody should update some of the images on d.u.com
[11:24] <neolynx> does anyone know if kernel parameters break= are supposed to work on bq aquaris e4.5 ?
[11:25] <davidcalle> ogra_, ^ do you know?
[11:25] <ogra_> davidcalle, which one ? :P
[11:25] <davidcalle> Pick one :D
[11:25] <ogra_> haha
[11:26] <ogra_> neolynx, how would you interact with it ? (neither a frameboffer console nor a serial one are enabled by default, even if you could manage to attach a keyboard)
[11:27] <ogra_> neolynx, though technically the initrd is the same as on every other ubuntu ... i.e. break= would stop the boot and try to give you a shell
[11:27] <neolynx> according to https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[11:28] <neolynx> there should be the possibility to boot with break=top, which should initiate an adb server
[11:28] <ogra_> that assumes there is adbd in the initrd
[11:28] <ogra_> i think that was dropped for production devices
[11:28] <neolynx> well, there is if you look in it
[11:28] <ogra_> yes, but it is a binary that can not run
[11:29] <ogra_> you could replace it with a binary that can run (like a very old version from the archive)
[11:29] <neolynx> but as hw is not initialized, this is useless. therefore my question how this is supposed to work. is this a mediatek chip issue and works with other chipsets ?
[11:29] <ogra_> it works with any chip
[11:30] <neolynx> ogra_: so the shipped adbd in the boot-img is broken ?
[11:30] <jgdx> mardy, hey, will you be able to comment on niklas's e-mail? That is, if you know what we are referring to when we talk about the notification I see/saw on the desktop
[11:30] <ogra_> buut the script that starts adbd and the adbd binary itslef have not been adjusted in a long time, it wont work in the current state
[11:30] <ogra_> it is broken for use inside an initrd, yes
[11:31] <ogra_> (the binary got a check for the screen lock state added at some point, it will never allow any connections if there is no UI up)
[11:31] <neolynx> ogra_: what is the reason it is broken ? the hardware is initialized enough to support usn connections ?
[11:31] <ogra_> the hardware is fine, the adbd binary isnt
[11:32] <neolynx> ogra_: ah, I see !
[11:32] <ogra_> it cant work in this context ... that the binary is in the initrd is actually an oversight
[11:32] <neolynx> ogra_: thanks for the info
[11:32] <ogra_> (though it does no harm)
[11:33] <ogra_> if you re-pack the initrd and replace the binary with one that can "just work" it should get you an adb shell in the initrd
[11:33] <neolynx> ogra_: do you know if the wireless interface would be initialized enough ? or does it need the android container to work ?
[11:33] <ogra_> it does
[11:33] <ogra_> only adb shell can work at this point
[11:34] <neolynx> ogra_: perfect. make sense
[11:34] <robin-hero> Hey, Can I somehow install the OTA-7 without channel change? I want to use the stable channel, just want to install this update earlier.
[11:48] <robin-hero> Anyone?
[11:49] <robin-hero> If I change the channel to rc, install the image and change back to the stable it will be update to the latest stable release or I can use the latest rc image?
[11:49] <davmor2> robin-hero: no it isn't released yet
[11:51] <robin-hero> davmor2: Thanks, could you answer my second question too? :)
[11:52] <davmor2> robin-hero: no you don't understand there is another fix landing in it, it doesn't exist yet there is no ota7, when it is built it will be landing possible Monday
[11:52] <davmor2> possibly even
[11:53] <robin-hero> fix for what?
[11:54] <davmor2> robin-hero: patched tarball
[11:55] <robin-hero> davmor2: Thanks :) But I'd like to know what is the patch about? :)
[11:56] <davmor2> robin-hero: no idea you'll have to wait and see :)
[12:03] <robin-hero> davmor2: And what's up with the users who were updated unforunately in the morning ? :)
[12:04] <davmor2> robin-hero: they will get the new image when it lands too and ota to that
[12:05] <davmor2> robin-hero: there is nothing wrong with that image it was just missing the final fix so was never meant to be release just built
[12:11] <sturmflut2> Isn't my krillin supposed to update to r26 because of that security fix?
[12:15] <ogra_> not sure there are extra images spun ... the main issue was the store which wont let in such packages anymore, the click fix itself will come on monday anyway
[12:20] <jgdx> Chipaca, hey, do you have any idea what might cause this on amd64? http://pastebin.ubuntu.com/12798213/
[12:20] <Chipaca> jgdx: gremlins
[12:21]  * Chipaca opens the link
[12:21] <jgdx> hey, that's my current conclusion as well
[12:22] <Chipaca> jgdx: what go version?
[12:23] <Chipaca> anyway
[12:23] <jgdx> Chipaca, go version go1.5.1 linux/amd64
[12:23] <Chipaca> that's a whole bunhc of errors
[12:24] <Chipaca> and the warnings at the top always distract me
[12:24] <jgdx> they're probably pertinent, but it's environmental because builds were passing a week ago
[12:24] <Chipaca> the warnings are because of gcc5 iirc
[12:24] <Chipaca> ignorable
[12:25] <Chipaca> but the errors, no idea
[12:25] <Chipaca> pedronis-land i think
[12:26] <jgdx> Chipaca, okay, and he's back next week I think
[12:26] <Chipaca> jgdx: isn't he at a spinrt this week?
[12:26] <Chipaca> sprint*
[12:27] <Chipaca> jgdx: is this in a silo, or in a real machine?
[12:27] <Chipaca> i mean
[12:27] <jgdx> Chipaca, right, sprint this week and hopefully back Monday
[12:27] <Chipaca> what're the chances of the problem being "incredibly overloaded machine making all the timing tests flake"
[12:27] <jgdx> Chipaca, silo and in my amd64 chroot
[12:27] <Chipaca> chroot should be fine
[12:28] <jgdx> 4-5 builds in a row now, so prob not flaky
[12:28] <jgdx> Should be fine, how?
[12:28] <Chipaca> jgdx: there's one that makes no sense
[12:29] <Chipaca> unless you're running the tests as root
[12:29] <Chipaca> TestDeviceListenError
[12:29] <Chipaca> tries to bind port 99
[12:29] <Chipaca> that *will* fail unless you're root :)
[12:29] <Chipaca> and yet you're getting no error
[12:30] <Chipaca> jgdx: you're not running the tests as root are you?
[12:30] <jgdx> Chipaca, sorry, here are the real errors: https://launchpadlibrarian.net/221441633/buildlog_ubuntu-wily-amd64.ubuntu-push_0.68%2B15.10.20151016-0ubuntu1_BUILDING.txt.gz
[12:33] <robin-hero> ogra_: If I flash the latest image from the rc channel, and then I change the channel to stable: what will happen?
[12:34] <Chipaca> jgdx: very different errors!
[12:34] <Chipaca> jgdx: nothing jumps to mind as to why it might be, i'd have to look at whatever changed
[12:34] <Chipaca> jgdx: what's changed?
[12:35] <jgdx> Chipaca, this [1] is the only thing AFAIK. Let me check more closely. [1] https://code.launchpad.net/~jonas-drange/ubuntu-push/poller-checks-send-recv/+merge/272927
[12:36] <jgdx> that's the only one
[12:36] <Chipaca> jgdx: try building without it?
[12:38] <Chipaca> jgdx: it's entirely possible something changed elsewhere in the stack, and that push FTBFS as a consequence
[12:38] <robin-hero> davmor2: Could you answer my question? :) If I flash the latest image from the rc channel, and then I change the channel to stable: what will happen? It will show the newest image as OTA update from the stable channel?
[12:39] <ogra_> robin-hero, it will do a full install of the image in the target channel
[12:40] <Chipaca> and bring forth the apocalypse
[12:40]  * Chipaca -> lunch
[12:40] <robin-hero> the flash, but the change channel command too?
[12:41] <ogra_> you might get probs with apps since the rc-proposed channel has a newer framework, so if you switch to stable you go backwards in time with the system, but the apps stay
[12:41] <ogra_> if you switch to stable only after OTA the risk is low though
[12:41] <jgdx> Chipaca, might be you're right. This is the log ouput from head-1: http://pastebin.ubuntu.com/12798371/
[12:42] <Chipaca> jgdx: that's your problem right there: earth and moon have been swapped in their orbits! we are doomed!
[12:42]  * Chipaca -> really lunch now
[12:42] <jgdx> okok :)
[12:43] <pmcgowan> robin-hero, stand by for the next annoucnement, you should stay with stable if thats what you want
[12:43] <pmcgowan> we are still working out details
[12:43] <robin-hero> ogra_: I'm talking about rc, not rc-proposed
[12:43] <ogra_> rc ?
[12:43] <robin-hero> yes, http://system-image.ubuntu.com/ubuntu-touch/rc/
[12:44] <ogra_> if you switch to RC right now you most likely get the same image you are running
[12:44] <pmcgowan> robin-hero, which image do you want?
[12:44] <ogra_> not sure the OTA candidate was copied over yet
[12:44] <ogra_> RC only gets populated shortly before release for upgrade testing and the like
[12:44] <robin-hero> pmcgowan: the release which was released this morning ( I know it was only an accident)
[12:45] <pmcgowan> robin-hero, ok so give us a little time
[12:46] <robin-hero> why? :) is it release today? :) (not at Monday)
[12:46] <ogra_> no, it is on monday
[12:47] <pmcgowan> ogra_, thats what is being discussed
[12:47] <pmcgowan> robin-hero, like I said, if you can wait just a bit
[12:47] <ogra_> well, the official OTA rollout is definitely monday  ... there might be ways to obtain it earlier ;)
[12:48] <ogra_> for the eager ones :)
[12:48] <robin-hero> It sounds interesting :)
[12:48] <ogra_> robin-hero, just watch the mailing list, if there is such a thing it will be announced there (or here)
[12:48] <ogra_> no promises :)
[12:49] <robin-hero> thanks, I'm subscribed to the mailing list. :)
[12:58] <tathhu> Ahh that was the update.. :P
[13:25] <jgdx> tedg, you had some "error opening shm" failures in UAL, right?
[13:27] <tedg> jgdx: We had, we removed them by making the LTTng stuff only activated by an environment variable.
[13:28] <jgdx> tedg, okay. Do you know what causes this? http://pastebin.ubuntu.com/12798718/
[13:28] <ogra_> well, could it be that this var is always set ?
[13:28]  * ogra_ sees 100s of lines of ltt-ng spam in all app logs
[13:29] <ogra_> err
[13:29] <ogra_> ltt-ust
[13:29] <tedg> Yeah, I believe it is the LTTng tracepoints in the QPA
[13:29] <tedg> I mean, the QPA plugin, not the interface itself.
[13:30] <tedg> jgdx: ^
[13:31] <jgdx> tedg, in a go project?
[13:33] <tedg> jgdx: Is it using Qt?
[13:34] <jgdx> tedg, hm, yeah.
[13:34] <jgdx> but it's not just noise, it's failing to start
[13:37] <tedg> I doubt the LTTng meesages are causing it to fail to start.
[13:37] <tedg> If it is Go, I'd be guessing that a bunch of libraries are expecting GLibMainloops that don't exist.
[13:38] <tedg> Go really isn't a good language for middleware.
[13:50] <jgdx> tedg, okay, thanks
[14:21] <jgdx> Chipaca, upc doesn't even start on wily
[14:26] <tvoss> mardy, ping
[14:33] <Chipaca> jgdx: on wily desktop?
[14:37] <charles> Saviq, sounds a little like https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1499687
[14:37] <ubot5`> Ubuntu bug 1499687 in indicator-bluetooth (Ubuntu) "Bluetooth turn on automatically " [Undecided,New]
[14:37] <charles> Saviq, but probably not the same
[14:37] <charles> Saviq, is it repeatable?
[14:38] <Chipaca> jgdx: it should be able to run, but you need a ton of stuff, plus point it at the right config
[14:39] <jgdx> Chipaca, okay
[14:39] <Chipaca> jgdx: how does it fail to start for you?
[14:39] <Chipaca> jgdx: for me it's complaining about not having a launcher. and also about running out of memory (?)
[14:41] <jgdx> Chipaca, I shut down my wily, let me get back to you. But okay, so nothing related to the failing test we saw..
[14:45] <Saviq> charles, yeah, my flo does that on every bood
[14:46] <Saviq> boot, even
[14:46] <Saviq> charles, it looks like the indicator starts early, when the adapter isn't there yet
[14:46] <Saviq> charles, and bails out - the weird thing is that when you go to settings everything, except for the on/off switch is working, and BT in fact works
[14:46] <charles> wonderful if it's that easy. it ought to always be watching for the adapter to appear
[14:47] <Saviq> charles, some error msgs from the indicator log: http://pastebin.ubuntu.com/12799432/
[14:48] <charles> Saviq, could you file a new ticket for this?
[14:48] <Saviq> charles, yeah, wanna test with BlueZ 5 first to see if worth investigating even
[14:48] <charles> ack
[15:03] <dobey> jgdx: if you want to use push client under X, the hard part will probably be getting the u1 account created, because you have to do with with the qt online-accounts, which requires mir
[15:05] <jgdx> dobey, isn't it possible to just choose another qpa plugin (x)?
[15:07] <dobey> jgdx: no. trusted sessions require mir
[15:08] <dobey> jgdx: you might be able to run system-settings under the mir-on-x thing that mhall119 was playing with
[19:19] <robin-hero> Hey! Just flashed the r26 release from the stable channel, but not I have got an empty sound indicator with the following title: indicator-sound
[19:26] <robin-hero> Oh, a restart fixed it
[19:51] <kyrofa> Does anyone know where I can download the most recent boot.img for the mako?
[21:58] <tathhu> r26 = ota-7?