[06:57] <mardy> mpt: good question; I guess it depends on whether the requesting application window is currently on the foreground or not
[06:58] <mardy> mpt: the authentication window might be triggered by some background processes, such as contact synchronization
[06:58] <mardy> mpt: so at least in those cases I don't think that we should pop it up out of blue
[07:43] <Kaleo> tedg, hmmm, writing is unexpected unless maybe they set the theme but even then that should not write
[07:46] <Kaleo> tedg, I see the code that would trigger that; ogra_ you there?
[07:46] <ogra_> yep
[07:46] <Kaleo> ogra_, you're the one that raised the theme.ini issue?
[07:47] <ogra_> well, it doesnt seem to happen anymore with a proper XDG_DATA_DIR set
[07:47] <ogra_> we had the error in the lab smoke tests ...
[07:47] <Kaleo> ogra_, right
[07:47] <Kaleo> ogra_, so it does write
[07:47] <ogra_> seems like, yes
[07:47] <Kaleo> ogra_, but if you give a writable path it does not fail?
[07:48] <ogra_> https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/250/consoleFull
[07:48] <ogra_> search for .ini
[07:48] <ogra_> right
[07:48] <ogra_> it doesnt fail ... though this error comes from autopilot
[07:49] <ogra_> name="/home/phablet/autopilot/fakeenv/tmpthzwqdgz/.config/ubuntu-ui-toolkit/theme.ini.TJ2716"
[07:49] <ogra_> not sure if you can blame the app here
[07:52] <Kaleo> ogra_, all good then
[07:52] <Kaleo> ogra_, not *all* good :)
[07:52] <Kaleo> ogra_, the toolkit tries to write in a location that apparmor has not allowed
[07:53] <ogra_> yep
[07:53] <Kaleo> ogra_, which does not really break anything
[07:53] <Kaleo> ogra_, but still
[07:53] <ogra_> well, it broke a lot of smoketests yesterday
[07:53] <ogra_> http://ci.ubuntu.com/smokeng/utopic/touch/mako/68:20140605.2:20140530/8424/
[07:53] <Kaleo> oh really? how come only now?
[07:54] <Kaleo> this write has been there for over 1 year
[07:54] <ogra_> split greeter switched us away from processing Xsession.d scripts ...
[07:54] <ogra_> which made us end up without XDG_DATA_DIR set
[07:54] <Kaleo> I see
[07:54] <Kaleo> but you fixed that?
[07:54] <ogra_> it sets that itself now
[07:55] <Kaleo> when you said: "<ogra_> well, it doesnt seem to happen anymore with a proper XDG_DATA_DIR set" did you mean that you set the XDG_DATA_DIR in the lab now?
[07:55] <Kaleo> or that's just a possible solution not implemented yet?
[07:55] <ogra_> all fine ... but indeed in a world with readonly home or full homedir your apps might not be able to start anymore if this is also used in real life
[07:55] <ogra_> the greeter sets XDG_DATA_DIR when starting sessions
[07:55] <Kaleo> hmmmm
[07:56] <Kaleo> so, hmmm
[07:56] <Kaleo> XDG_DATA_DIR needs to be set so that we can read from the readonly home I suppose
[07:56] <ogra_> (the Xsession.d script code was copy/pasted into the session start scripts)
[07:56] <Kaleo> and the app shouldn't totally fail if it's readonly
[07:56] <Kaleo> interesting
[07:56] <Kaleo> ok
[07:56] <Kaleo> any action needed then?
[07:57] <Kaleo> urgent action at least?
[07:57] <ogra_> no, we're all fine since the var is set again
[07:57] <Kaleo> right
[07:57] <Kaleo> ok
[07:57] <ogra_> long term it would be good to test apps with readonly home though
[07:57] <Kaleo> I was convinced jamie and the sec team had a least of all policy violations
[07:57] <Kaleo> in a bug somewhere
[07:58] <ogra_> i.e. if your home is full your session still needs to be able to start and you need to be able to make an emergency call
[07:58] <Kaleo> ogra_, yeah I don't think app breaks if home is not readable
[07:58] <Kaleo> apps break*
[07:59] <ogra_> i heard some reports from people using that image who could npot start the clock-apüp anymore
[07:59] <Kaleo> that's possible that a couple of apps do funny things
[07:59] <ogra_> right
[07:59] <ogra_> we need to make sure dialer is not among them
[07:59] <Kaleo> that should be detected by the sanity checks in qtcreator and at click upload time
[07:59] <Kaleo> I guess
[07:59] <Kaleo> right
[07:59] <Kaleo> ogra_, worth checking then, or asking bfiller to add an automated test of some sort?
[08:00] <Kaleo> (dialer and unity8)
[08:01] <Kaleo> can't believe I wrote 'least' instead of 'list' earlier
[08:02] <ogra_> i have another bug open about readonly home ... which will result in a readonly home test ... i'll make sure that unity8 and dialer are the apps that get tested in that
[08:02] <Kaleo> cool
[08:03] <Kaleo> for future reference, toolkit related issues go to zsombi :)
[08:03] <ogra_> yeah, i didnt ping you :)
[08:04] <Kaleo> tedg,  for future reference, toolkit related issues go to zsombi :)
[08:04] <Kaleo> ;)
[08:04] <ogra_> i would have gone to bzoltan though ... just because i'm used to it ;)
[08:04] <Kaleo> ogra_, that works too
[08:19] <janimo> ogra_, hi, is SWAP going to be there for RTM ?
[08:20] <ogra_> janimo, i hope not
[08:20] <janimo> ogra_, who's in charge of that?
[08:20] <ogra_> probably rsalveti, tvoss and me
[08:20] <ogra_> we need to test the lifecycle stuff without it and need to know it doesnt regress etc
[08:23] <Saviq> popey, you're making me cry ;P *please* apport-cli .crash files before uploading anywhere
[08:23] <popey> sorry dude
[08:23] <Saviq> otherwise it's missing details :)
[08:23] <popey> will do now
[08:23] <popey> Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers.
[08:23] <Saviq> popey, hum there's no core there anyway
[08:23] <popey> well that was useful
[08:23] <Saviq> popey, yeah, core collection failed (OOM)
[08:24] <Saviq> so that's not gonna help
[08:24] <Saviq> popey, the message is also misleading... your computer *did* not have enough memory at the time of the crash
[08:25] <Saviq> popey, so there's nothing we can get out of it now
[08:25] <popey> ☹
[08:25] <popey> anything i can do at the time when/if it happens again?
[08:26] <Saviq> pray you have enough memory for the dump to be processed...
[08:26] <popey> hah
[08:26] <Saviq> i.e. don't run 15 apps! ;)
[08:26] <popey> can we put a popup on the phone that says "Don't open apps, our phone isn't designed for that!" ? :þ
[08:26] <Saviq> ')
[08:26] <Saviq> it's *designed* for that
[08:26] <Saviq> it's just not implemented yet ;)
[08:26] <popey> haha!
[08:27] <popey> shitcanonicalsays dot tumblr dot come
[08:27] <popey> -e
[08:50] <mpt> mardy, hmm, that’s an interesting problem. Do you have any other ideas for when/how it should be presented?
[08:54] <mpt> mardy, perhaps it could be something flagged on the relevant app? A contact syncing problem gives the Contacts app a launcher badge, a calendar syncing problem gives the Calendar app a launcher badge, and s on.
[08:54] <mpt> *so on
[08:57] <Mirv> didrocks: heya. sil2100 is away today, and we have no knowledge on how to restore the spreadsheet functional after jenkins was down for a few hours earlier today (out of disk space again). could you help?
[08:58] <didrocks> Mirv: hum? what do you need exactly? the spreadsheet should just sync up and pick from there
[08:58] <didrocks> Mirv: or did you change any urls?
[09:00] <Mirv> didrocks: no url:s, just downtime. more like about debugging what's wrong, I don't really know why eg refreshSilos gives an error (empty JSON)
[09:01] <didrocks> Mirv: nothing should be needed then. Can you access the backend json files, aren't they empty?
[09:01] <Mirv> didrocks: no I don't know/remember what/where are backend json files..
[09:02] <didrocks> Mirv: they are http://people.canonical.com/~platform/citrain/
[09:02] <didrocks> you should try to check with json files are empty
[09:02] <Mirv> there's one empty for some reason
[09:03] <didrocks> Mirv: maybe start from this?
[09:04] <Mirv> trying to look at 008
[09:07] <anjan> hello
[09:08] <anjan> i have built a intel core i3 3220 with gigabyte dg61 mobo and 4gb ram. whenever, i tried to install ubuntu 14.04 lts amd64, i got an error message "invalid or corrupt kernel image"
[09:08] <anjan> pl. hel
[09:08] <anjan> pl. help
[09:09] <Mirv> didrocks: I can't seem to figure out how to kick jenkins to write something on top of that 0 length landing-008 file, since all operations fail on that
[09:09] <mardy> mpt: it doesn't sound very easy. Though, if you design it like that, I'm sure we'd find a way to implement it
[09:10] <didrocks> Mirv: I guess the short way of fixing this is to remove the config file, maybe add a try: except: in the code otherwise
[09:10] <mardy> mpt: just to make sure I understood the high level plan: we wouldn't pop up any windows, but signal the user (probably via the launcher) that an application needs his attention; then, when he clicks on the "thing", the authentication window will be presented; is this correct?
[09:11] <mpt> mardy, that’s not a high-level plan, it’s just one possibility I thought of :)
[09:11] <mpt> but yes
[09:14] <Mirv> didrocks: how'd I remove the file? should I have ccess to the ~platform account?
[09:14] <popey> anjan: i think you probably want #ubuntu for tech support.
[09:17] <didrocks> Mirv: landing-008, right?
[09:17] <Mirv> didrocks: yes
[09:17] <didrocks> Mirv: deleted
[09:18] <didrocks> hum, actually
[09:18] <didrocks> that's not enough
[09:18] <didrocks> it will be synced back from the backend
[09:18] <didrocks> Mirv: you need to check with webops to do that in the backend
[09:18] <didrocks> Mirv: or run a jenkins job to do it
[09:18] <Mirv> ok, I'll go there. thanks for your help!
[09:18] <didrocks> Mirv: yw ;)
[09:27] <Mirv> problem solved, restored one more id from prepare silo logs and now all seems good again
[09:29] <didrocks> excellent!
[10:23] <seb128> do we have an api to query the device type?
[10:23] <seb128> type being phone/tablet/desktop
[10:24] <seb128> that's for https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1258211
[10:25] <seb128> the design says it should be "about this phone" on a phone and be "device" otherwise
[10:30] <oSoMoN> Mirv, hey, can I get a silo for line 18 ?
[10:40] <ogra_> MacSlow, hey ... so i enabled the spinner on my flo ... is it really wanted to have it that tiny ? on the flo screen it looks quite lost (about 1cm only)
[10:41] <MacSlow> ogra_, it's not that large... it's size is GU-based
[10:41] <MacSlow> I've two screencasts (one on n4, one on n10) for comparision if you want...
[10:42] <ogra_> which would the flo (N7) get ?
[10:42] <ogra_> i assume we currently ship the N4 version by default ?
[10:42] <MacSlow> ogra_, here you go www.youtube.com/watch?v=iieDMszha9Q
[10:43] <Mirv> oSoMoN: done
[10:43] <oSoMoN> Mirv, thanks!
[10:43] <ogra_> MacSlow, on the phone it actually looks reasonable ... on the tablet i find it way to small
[10:43] <MacSlow> ogra_, since I don't have access to a n7, I can't tell
[10:44] <MacSlow> ogra_, the question is, is the GU used (read from a file, since $GRID_UNIT_PX isn't set up that early in the boot-process) on the N7 correct?
[10:45] <MacSlow> ogra_, I mean the value stored in the filesystem of the n7 image
[10:45] <ogra_> it is set up by ubuntu-touch-session ... whihc runs after u-s-c when either the greeter or unity8 start
[10:46] <ogra_> so yeah, i guess only after you started
[10:46] <MacSlow> ogra_, I've written a decicated function for the spinner-binary to load the grid-unit value from the file it is stored in
[10:46] <ogra_> s/set up/exported into the env/
[10:47] <ogra_> MacSlow, hmm, not a good idea, that file will move into the andrid container soon ... better make it configurable so we can adjust it then
[10:47] <ogra_> (all HW related config and data is supposed to move out of the rootfs)
[10:48] <MacSlow> ogra_, I'm a gfx-guy... weeks back, pulling it from the fs was the only option available to me to get hold of the GU-value
[10:48] <ogra_> yeah, it still iss ... and will probably still be by RTM ... but the file location will change
[10:49] <MacSlow> ogra_, plans change constantly... but I wanted to get the project forward instead of just sitting there
[10:49] <ogra_> i wonder if we could somehow inject it into the env on early boot
[10:49] <MacSlow> ogra_, besides all that needs to be alter is the, way the GU is supplied... everything else - since it's GU-based - does not have t obe touched and works today
[10:49] <ogra_> you are not the only one using the file directly ... sadly ...
[10:50] <MacSlow> ogra_, again I don't follow the boot-process planning/development very closely
[10:50] <ogra_> well, the other graphical bits only run after upstart started a session ... in which case the GU value gets into the upstart global environment
[10:51] <ogra_> they dont need to read the file
[10:51] <MacSlow> ogra_, I was not happy with having to pull in the libandroid-properties dependency for the spinner-binary
[10:51] <ogra_> yeah
[10:51] <ogra_> oh, you read it from android ?
[10:52] <MacSlow> ogra_, this is one of those sweet spots where idealism hits reality :)
[10:52] <ogra_> well, you should not need it ... what do you read with it exactly ?
[10:52] <ogra_> we should make that availablle to you in the environment instead
[10:52] <MacSlow> ogra_, yeah I had to use a specific android/hybris-related property call to obtain it
[10:52] <ogra_> the GU ?
[10:53] <ogra_> i thought you read it from the file
[10:53] <ogra_> (especially since we dont set a GU property at all ... what you get might be an unused android value if you read it from there)
[10:56] <ogra_> MacSlow, we should look into that before RTM, i'd like to provide you a way where you dont need android deps ...
[10:57] <MacSlow> ogra_, see lines 34-92 here bazaar.launchpad.net/~unity-system-compositor-team/unity-system-compositor/trunk/view/head:/spinner/eglspinner.c
[10:58] <ogra_> ah, just for the device name ... we'll solve that once the file moves into the container ... but i think it would be even more elegant if an early upstart job could just set a global var for you
[10:59] <MacSlow> ogra_, I am not familiar with upstart... I've to trust what people - more familiar with the boot-process - tell me.
[11:00] <MacSlow> ogra_, when I wrote the spinner, using libhybris to read that property was the suggested way to go... so I did.
[11:01] <ogra_> bug 1327172
[11:02] <MacSlow> ogra_, what could be - in the case of the n7 - that it fails to find the correct value via libhybris and just falls back to the default value of 10, which might be too small for the n7
[11:03] <MacSlow> ogra_, can you quickly check the value of $GRID_UNIT_PX or a fully booted N7 for comparision?
[11:03] <ogra_> phablet@ubuntu-phablet:~$ echo $GRID_UNIT_PX
[11:03] <ogra_> 18
[11:04] <MacSlow> ogra_, how much smaller is the spinner on the n7 compared to the n10... roughly?
[11:04] <ogra_> it is as big as on the phone in your video
[11:04] <ogra_> just with a 7" screen around it
[11:04] <MacSlow> ogra_, well... that's sounds about right then
[11:04] <ogra_> (doesnt seen to be scaled up)
[11:05] <ogra_> compared to the flahing animation it looks very tiny :)
[11:05] <ogra_> *flashing
[11:05] <ogra_> (though this will get re-work as well i was told)
[11:06] <MacSlow> ogra_, true... the spinning logo during the device-flashing is "too big" if I recall Design
[11:06] <ogra_> (flashing as in applying an update ... not as in *blink* :) )
[11:06] <ogra_> ah, k
[11:06] <MacSlow> ogra_, but such things you've to discuss with Design and not me :)
[11:06] <ogra_> well, as long as they are consistent :)
[11:06] <MacSlow> +1
[11:07] <ogra_> i'll let you know when the above bug is fixed, then you can dro the android dep
[11:07] <ogra_> and just use getenv ;)
[11:07] <MacSlow> ogra_, although I've to admit, that Design's focus is on the most likely UI an end-user will see... which is Dash, Scopes etc... and not device flashing :)
[11:08] <ogra_> enduser see the flashing animation on every update
[11:08] <ogra_> well, system image update ...
[11:08] <MacSlow> ogra_, ok... if that's available at some point, the needed change will be tiny I guess
[11:11] <om26er> who works on powerd these days ?
[11:12] <ogra_> jdstrand, the mir socket moved to /var/run ... we have a security test failure due to that, i think you need to update something
[11:13] <ogra_> (the apparmor-easyprof-ubuntu test seems to check for /tmp/mir_socket)
[11:19] <om26er> bug 1327180
[11:36] <asac> anyone saw the problem where the shell stops responding to input? e.g. no swipe, no start of apps etc.?
[11:37] <asac> i had that yestetrday again, thought it was a crash, but this never resurrected even after waiting over 1h
[11:40] <ogra_> asac, did you check via adb if apport was running or some such ?
[11:41] <asac> ogra_: i was out in the park and needed to take pictures, o i couldnt do adb :)
[11:41] <asac> ogra_: but it was over 1h
[11:41] <asac> so i dont think its apport
[11:41] <asac> it was just a hang
[11:41] <ogra_> yeah, doesnt sound like
[11:41] <asac> from my pov
[11:41] <asac> think it was even 2h
[11:41] <asac> i waited for this thing to recover/restart
[11:41] <ogra_> we had issues before where gestures didnt work
[11:42] <ogra_> but taps and the like still did
[11:43]  * asac upgrades to 71
[11:49] <asac> so this choppy sound when on a phone call, thats going to be fixed with pulse droid?
[11:50] <asac> isnt that a buffering problem that could be fixed quickly without having to wait for that?
[11:53] <jdstrand> ogra_: ack
[11:53] <Guest25032> jjust listening iin first
[11:54] <Guest25032> quit
[11:54] <ogra_> asac, you would have to ask rsalveti (he worked on that) ... but he is out til monday ...
[11:55] <Guest25032> does ubuntu SDK actually work properly with 14.04LTS?
[11:56] <ogra_> it should, yes
[11:56] <Guest25032> Hmmm... must be doing somehting wrong then.
[11:57] <Guest25032> I was quite happy with Qt5 under 12.04LTS. Upgraded to 14.04LTS which gave me *heaps* more battery life (magic).
[11:58] <Guest25032> Then got SDK iso Qtcreator, but toolchain doesnt autodetect. No Run or Debg avail for examples, etc.
[11:59] <Guest25032> Have gcc 4 x64 installed, entire OS is pretty much as new.
[11:59] <Guest25032> Cant find any other hints on what's missing / needs to be dropped in first.
[12:00] <Guest25032> Any hints?
[12:02] <Guest25032> (must be lunchtime - is quiet here)
[12:02] <asac> tedg: good morning
[12:02] <asac> tedg: let me know what you need to nail down the annoying gmail bug i have (think dbarth believes that its your url-dispatcher causing this)
[12:03] <Guest25032> .
[12:05] <asac> whats this SDK iso Qtcreator?
[12:05] <asac> bzoltan: ^^
[12:05] <asac> are we releasing a qtcreator optimized image now?
[12:05] <asac> 13:58 < Guest25032> Then got SDK iso Qtcreator, but toolchain doesnt autodetect. No Run or Debg avail for examples, etc.
[12:05] <asac> thats the context
[12:11] <ogra_> asac, bzoltan is off today ...
[12:19] <asac> ogra_: is mfrey off today? u remember?
[12:19]  * asac remembers something, but might be a mix up
[12:19] <ogra_> asac, yes
[12:26] <mterry> seb128, do you have an ubuntu online week session for client-1410-unity8-desktop-iso ?
[12:26] <seb128> mterry, no, but dholbach suggested we should have one
[12:27] <mterry> seb128, so did kgunn  :)
[12:27] <seb128> great
[12:27] <mterry> seb128, I'm happy to help lead it / attend it
[12:28] <seb128> mterry, thanks
[12:28] <seb128> I need to get it on the schedule, I'm going to have a look to that in a bit
[12:29] <ogra_> mterry, seemy my language settings were not picked up by the greeter wehn i upgraded from 64 to 71 today
[12:29] <mterry> ogra_, ooh, interesting
[12:29] <mterry> ogra_, we have code to support that
[12:29] <ogra_> the session was fine but the greeter showed AM/PM time
[12:30] <mterry> ogra_, we set LC_ALL to whatever is in your AccountsService FormatsLocale or some such
[12:30] <ogra_> after switching the language settings to US ... rebooting, setting it back to german ... all was fine
[12:30] <mterry> ogra_, maybe there's something else I have to do
[12:30] <mterry> ogra_, oh odd
[12:30] <mterry> ogra_, so it was only an upgrade issue?
[12:30] <ogra_> it didnt pick it up on upgrade it seems
[12:30] <mterry> ...  why on earth would that happen...
[12:31] <ogra_> which was old greeter -> new greeter ... essentially
[12:31] <mterry> AS values are kept
[12:31] <ogra_> (FYI i just promoted image 71 ... so avengers now have the new greeter)
[12:31] <mterry> I could *imagine* some bug around the lightdm HOME becoming persistent, but that shouldn't matter
[12:31] <mterry> ogra_, oh yay
[13:44] <dbarth> asac. tedg: on that issue, i have a patch that solves the problem, just inside webapp-container
[13:45] <dbarth> asac. tedg: but now i'm fighting with some regressions in other webapps; still needs a bit more polishing
[13:45] <tedg> dbarth, Sorry, I think I'm missing some context :-)
[13:50] <tedg> dbarth, What's the issue?
[13:53] <asac> tedg: read my ping earlier today. that was about bug:
[13:53] <asac> tedg: https://bugs.launchpad.net/webapps-core/+bug/1324848
[13:53] <asac> tedg: you said you cant repro
[13:53] <asac> check the dupe bug screenshot... thats 100%
[13:53] <dbarth> tedg: an internal navigation request, that slips out, and which url-dispatcher can't handle
[13:53] <dbarth> even if it's a valid http url
[13:54] <dbarth> asac: the main issue is in webapp-container, and now fixed (modulo the regressions right now)
[13:54] <dbarth> tedg: but you may want to add a test case for that type of URL, cause they seemed legit to me
[13:54] <asac> yeah please add tests
[13:55] <asac> dbarth: ok thanks. thougth maybe ted could make a cleaner fix is what the bug suggested
[13:55] <asac> but if you feel its clearly webapp-container, thats cool too for me :)
[13:55] <asac> please update bug and update tasks
[13:55] <dbarth> asac: it's really down to how webapps manages popups
[13:55] <dbarth> asac: which is still a bit of black art on the phone
[13:56] <tedg> asac, So it's 100% repoducable when the DB gets in an errored state. The issue is getting it there.
[13:56] <dbarth> (cause we don't really have popups there)
[13:56] <tedg> It seems that a few of the integration tests are showing the recoverable error, so I plan on investigating it there.
[13:56] <asac> tedg: ok dont know about your level, but if i use my gmail webapp it ALWAYS happens :)
[13:56] <asac> you sy i have a local DB that causes this?
[13:57] <tedg> asac, There's a URL dispatcher cache db. If you delete ~/.cache/url-dispatcher/urls-1.db and relogin it'll repair itself.
[13:57] <tedg> Which is good/bad :-)
[13:57] <asac> dbarth: tedg: anyway, dont need to be directly involved. if you need anyuthing let me know, otherwise, just update the bug with what you two agree
[13:57] <asac> :)
[13:57] <asac> tedg: so you say removing that file migh tworkaround?
[13:58] <asac> thats cool. guess i will leave it in that state though so i can validate that your fix recovers this :)
[13:58] <tedg> asac, Yeah, it'll rebuild itself on login.
[13:59] <asac> tedg: what does that entry in the db do? precache IP resolution?
[13:59] <asac> or which apps etc. to use?
[14:00] <asac> guess the latter
[14:00] <tedg> asac, which app, yeah
[14:00] <asac> so we dont need to parse .desktop etc. all the time. ic
[14:00] <asac> and to save user choice if we ever allow suers to choose which handler to use
[14:00] <asac> ok got it :)
[14:00] <tedg> We don't have the user choice feature yet, after RTM :-)
[14:02] <tedg> dbarth, asac, just FYI, here's a test that reported that error: http://ci.ubuntu.com/smokeng/utopic/touch/mako/70:20140606:20140530/8429/calendar_app/
[14:04] <asac> tedg: nice
[14:04] <asac> tedg: not so nice that we ignore community app tests failing
[14:05] <asac> and think its the app
[14:05] <asac> popey: ^
[14:05] <asac> :)
[14:05] <asac> not sure if you can fix it. think helping us to move to same landing process with backout etc. as other apps it would help. plus one consolidated effort with bill and qa folks to get everything to green
[14:06] <tedg> In this case I don't think it's reported as a failure.
[14:07] <tedg> It's just an extra artifact in the test run.
[14:12] <asac> tedg: are you affiliated with the indicators?
[14:13] <asac> :)
[14:13] <asac> tedg: the messaging indicator always seems to show blue even though all is cleared out
[14:13] <asac> and then when i try to navigate there its not blue anymore
[14:13] <asac> this feels new in 71
[14:13] <asac> oh
[14:13] <asac> its always blue on the greeter :)
[14:13] <ogra_> your lightdm has a message ;)
[14:14] <asac> ogra_: something i cannot read/see anywhere?
[14:14] <ogra_> (thatrs a mterry thing ... and he is off today ... )
[14:14] <asac> what could that be?
[14:14] <asac> "CAPS LOCK ON" :)
[14:14] <ogra_> you should not get messages for lightdm
[14:14] <ogra_> lol
[14:14] <tedg> It's probably not updating the accounts service data.
[14:14] <ogra_> the user message queue should be routed through afaik
[14:14] <tedg> I have a work item to look into that, but we're waiting on some updated designs.
[14:14] <pmcgowan> there are two states, one in the greeter and one in the shell
[14:14] <pmcgowan> known bug
[14:15] <ogra_> right, there are four or five bugs open like that
[14:15] <tedg> They should be coming today or early next week, then we can fix messaging menu in the greeter.
[14:15]  * pmcgowan boots 71 :)
[14:35] <mhall119> woohoo a new promoted image!
[14:36] <popey> ☻
[14:36] <popey> knew you'd like that
[14:58] <doflaherty> I haven't been able to start calendar-app on mako in a while - is there a known issue with this?
[14:59] <ogra_> starts fine here
[14:59] <doflaherty> it seems to get added to "Recent apps" but all I get is a white screen
[15:03] <Tassadar> I get when I update apps which are open at the time
[15:03] <Tassadar> like open clock -> update clock app from system settings -> clock app works fine -> close clock -> open clock
[15:03] <Tassadar> and it won't open
[15:05] <Tassadar> reboot fixes it though
[15:08] <ogra_> Tassadar, thats definitely worth a bug (if there isnt one already)
[15:08] <Tassadar> okay, which launchpad project does that belong to
[15:08] <Tassadar> ?
[15:09] <Tassadar> something click related, I guess
[15:11] <Tassadar> probably related to bug #1232130
[15:23] <doflaherty> neither uninstalling/reinstalling nor rebooting seems to fix it
[15:40] <ogra_> doflaherty, what image version is that ?
[15:41] <doflaherty> I'm running the latest, r71, but I've had the problem for a while
[15:43] <ogra_> weird, did you try uninstalling and reinstalling that app ?
[15:44] <ogra_> perhaps that helps ...
[15:44] <ogra_> also do you run devel-peoposed or devel ?
[15:44] <ogra_> *proposed
[15:44] <doflaherty> devel
[15:44] <ogra_> proposed had some seriously broken images recently (like the last ten or so) ...
[15:44] <doflaherty> tried uninstalling/reinstalling
[15:45] <ogra_> didnt help ?
[15:45] <doflaherty> nope
[15:45] <ogra_> very stramge
[15:45] <ogra_> *strange even
[15:45] <doflaherty> it's the only one I'm having this issue with - all the other core apps seem to work
[15:49] <asac> ogra_: so what was this with the YOUTUBE celebration i saw earlier?
[15:49] <asac> ogra_: is that already in 71?
[15:49] <ogra_> yep
[15:49] <ogra_> go to m.youtube.com
[15:49] <asac> for me youtube still stops when screen is off (well, first time it didnt stop, but guess its a bug)
[15:49] <ogra_> you can now play videos
[15:49] <asac> i can play videos, yes
[15:49] <ogra_> no, thats expectede
[15:49] <ogra_> right, you couldnt before
[15:49] <ogra_> it would just reload the page
[15:50] <asac> i know. didnt know what now improved :)
[15:50] <ogra_> it plays :)
[15:50] <asac> hmm... ok so became more reliable
[15:50] <ogra_> no fullscreen yet and integrating the browser with media-hub seems to be very hard
[15:50] <asac> ok thanks
[15:50] <asac> ogra_: i dont even see a full screen button
[15:50] <ogra_> and without media-hub stopping is expected
[15:51] <ogra_> there is none yet
[15:51] <asac> is that sure
[15:51] <asac> err
[15:51] <ogra_> "no fullscreen yet" :)
[15:51] <asac> sure :)
[15:51] <asac> ogra_: how dowes the website figure if there is a fullscreen button to be displayed?
[15:51] <asac> is there a capability exported?
[15:51] <asac> dbarth: ?
[15:51] <ogra_> dunno ...
[15:51] <ogra_> chrisccoulson, or dbarth should knwo though
[15:52] <asac> righty
[15:52] <asac> guess they might be gone already
[15:53] <chrisccoulson> ogra_, asac, bug 1326852
[15:53] <asac> chrisccoulson: are you doing the media-hub integration?
[15:53] <ogra_> chrisccoulson, uuh, why would you want play/pause
[15:53] <asac> lol
[15:53] <ogra_> the UI is way to small
[15:54] <asac> i want voice control and mental instruction transfer technology :)
[15:54]  * ogra_ just taps the screen 
[15:54] <lotuspsychje> i tested dailymotion on ubuntu-touch on my n7 and works nicely
[15:54] <ogra_> great
[15:54] <lotuspsychje> also youtube webversion works and mobile version doesnt wanna play
[15:55] <asac> chrisccoulson: when do you think will the code land?
[15:55] <asac> in image?
[15:55] <ogra_> which code ?
[15:55] <asac> ogra_: that is fixed committed for the controls
[15:55] <asac> see the bug
[15:55] <ogra_> there is no fix
[15:55] <asac> 17:52 < ubot5> bug 1326852 in Oxide 1.0 "missing controls on toolbar of youtube videos" [Critical,Fix committed] https://launchpad.net/bugs/1326852
[15:55] <dbarth> asac: not sure myself
[15:56] <dbarth> about FS
[15:56] <ogra_> it just refers to the code that landed today
[15:56] <asac> ogra_: that bug status feels there is a fix released and a fix committed
[15:56] <ogra_> hmm
[15:56] <asac> i dont understand
[15:56] <asac> the titlee says "missing controls" the status is fix released and fix committed :P
[15:57] <asac> I assume we will get this whenever 1.0.2 gets released into our image
[15:57] <dbarth> it's released on oxide trunk afaict
[15:57] <ogra_> hmm, i see some scaling code looking at the branch
[15:58] <ogra_> but nothing that talks about fullscreen
[15:58] <dbarth> not in the image
[15:58] <dbarth> the FS code itself has been in oxide for a while
[15:58] <ogra_> ah
[16:00] <asac> is it a split greeter regression that the notification to accept an alarm is hidden behind the greeter?
[16:00] <asac> or is that old?
[16:03] <ogra_> asac, new and tracked
[16:09] <chrisccoulson> asac, soon ;) (for the image)
[16:10] <chrisccoulson> just doing some other things atm
[16:10] <asac> chrisccoulson: like fixing media-hub?
[16:10] <asac> err oxide to use media-hub :P
[16:10] <chrisccoulson> asac, bug 1249387 ;)
[16:11] <asac> chrisccoulson: that is indeed the "other things" you referred to?
[16:11] <asac> go go go
[16:11] <asac> must be super trivial for you nowadays :P
[16:11] <chrisccoulson> hah :)
[16:11] <asac> so guess on wednesday i will have nice background playback :P
[16:25] <ogra_> asac, huh, what ? wednesday ? why waste a workday !
[16:27] <asac> ogra_: dunno. wanted to allow chrisccoulson to claim it was very hard and struggled till the end, but in reality he already has the code ready and takes 2 days off :)
[16:27] <ogra_> haha
[16:28] <ogra_> yeah, it might take 4 weeks til he can land it, who knows how the images look on monday
[17:40] <jdstrand> I'm currently on r50 on devel. I see that r71 was promoted (yay!). will push notifications eventually tell me that I can update?
[18:10] <robotfuel> tedg: ping, I've run in to this bug a lot last night with the monkey runner we are using to stress test the phone, are you someone who can triage the bug? or do you know who to ask? https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1327033
[18:11] <tedg> robotfuel, First, it's not a crash, it's a recoverable error. The Monkey Runner should probably distinguish that.
[18:12] <tedg> robotfuel, We added that error to track down another bug that's happening occasionally
[18:12] <tedg> robotfuel, Let me find the bug.
[18:12] <robotfuel> tedg: I am just looking for crash files, now I can have it look for more closely.
[18:13] <tedg> robotfuel, https://bugs.launchpad.net/webapps-core/+bug/1324848
[18:13] <robotfuel> for *that
[18:14] <tedg> robotfuel, They have a "ProblemType" field in them that describes what they are.
[18:16] <robotfuel> tedg: okay have it skip those in my /etc/apport/crashdb.conf, thanks for the tip.
[18:17] <tedg> robotfuel, Please still upload them though, just don't stop the runner based on them.
[18:17] <robotfuel> tedg: oh we upload the results and then restart the test.
[18:17] <robotfuel> tedg: it happens automatically...
[18:17] <tedg> robotfuel, I thought the test went until something crashed?
[18:21] <robotfuel> tedg: it goes until a crash file shows up. I can make look at the problem type as you say though. it's better to let the test continue to run on a recoverable error.
[18:44] <xenos1984> hi all, i have a problem with ubuntu touch on a nexus 7. i used it already some months ago and it worked more or less with trusty. recently i updated to the newest trusty build and it was just hanging a bit after the unity desktop appeared. in this irc channel i got the advice to switch to the devel channel instead, and to do a full bootstrap. now i did that and installed the devel version (utopic i guess). however, now it does not
[18:44] <xenos1984> boot at all and just hangs in the bootloader. recovery also does not boot and the device does not show up on adb devices. any ideas what could be wrong? the device was connected all the time during flashing. what should i do now to flash a new image?
[18:44] <fishscene> Nexus 7 2003 edition?
[18:45] <xenos1984> fishscene: yes
[18:46] <fishscene> I had the older Nexus 7 model and sometimes it would get stuck. When that happened, I unplugged it, popped the back cover off and disconnected the battery. Waited a few seconds, then plugged everything back in and it would work properly for flashing
[18:48] <fishscene> I'm not sure if that would help you, but it's worth a shot.
[18:49] <xenos1984> fishscene: hm... i see, i guess i will try that (unless i find a different solution without some hardware manipulation)
[18:52] <xenos1984> so what would happen if this works? does it boot into recovery again, or show up on adb devices?
[18:54] <fishscene> It might show up in adb devices. Honestly, I don't recall what I did next as I haven't flashed mine since December. But I do remember mine wouldn't fully reboot/shutdown even when I told it to and it was in a similar state you are describing.
[18:54] <fishscene> I would just try the normal full flash
[18:56] <xenos1984> ah, i see - thanks, i'll give it a try (maybe after some further researching)
[18:56] <fishscene> NP mate
[20:39] <ahayzen> which project do i mark bugs with the infographics against? libusermetrics or unity8 or something else?
[20:41] <xenos1984> fishscene: by the way, i got the nexus working again (even though not with ubuntu yet), at least it does not hang in the bootloader anymore - i just had to reinstall the recovery with fastboot flash recovery
[20:45] <fishscene> ah. Excellent
[21:33] <popey> ahayzen: unity8, Saviq will soon re-assign it ㋛
[21:33] <popey> (j/k)
[21:34] <ahayzen> popey, ah i put as libusermetrics lol.... shall i put both as it is todo with translations?
[21:34] <ahayzen> popey, it'll probably get seen to quicker if i assign to unity8 as well ;) hehe
[21:34] <popey> not sure who owns libusermetrics
[21:34] <ahayzen> popey, https://bugs.launchpad.net/libusermetrics/+bug/1327419
[21:34] <popey> ta
[21:34] <Saviq> ahayzen, bear in mind the infographics system is completely reworked in https://code.launchpad.net/~unity-team/libusermetrics/file-based-infographics/+merge/214020 which will land soon
[21:35] <Saviq> ahayzen, that isn't to say that this bug won't exist there (probably will, even more so, actually)
[21:35] <ahayzen> Saviq, ah i see ... so where would you say this bug should go? https://bugs.launchpad.net/libusermetrics/+bug/1327419
[21:35] <Saviq> ahayzen, I think it's fine there
[21:35] <ahayzen> Saviq, cool :)
[21:49] <cwayne> Saviq: is there any doc detailing the infographics rework?
[21:50]  * cwayne is just curious as to what's changed, and what file-based-infographics means :)
[21:50] <Saviq> cwayne, effectively data sources will write files, visualizers will read those and output SVGs
[21:53] <cwayne> Saviq: so we'll support different visualizations? or still just the circles
[21:53] <Saviq> cwayne, oh no, different ones
[21:53] <Saviq> cwayne, and click-installable
[21:53] <cwayne> oooh
[21:53] <cwayne> fancy
[21:53]  * cwayne is excited
[21:53] <Saviq> cwayne, and they'll be able to aggregate data from different sources
[21:54] <cwayne> Saviq: cool!
[21:54] <cwayne> that sounds awesome
[21:58] <popey> cwayne: uploaded a new set of "all the clicks" to people.canonical.com/
[21:58] <popey> ~alan/clicks
[21:59] <cwayne> awesome :)