[00:00] <daniel31> (for clumsy people like me anyway ;-) )
[00:00] <bact> the thing about android, and what I really dislike is that new version of software heavily depend on the soc manufacturers releasing newer binary blobs
[00:00] <daniel31> right, I see
[00:01] <bact> so soc's like qualcomm, they do for a while, but obviously not forever
[00:01] <daniel31> yeah and good luck getting that from unknown chinese manufacturers right.. heh..
[00:01] <bact> yeah
[00:01] <bact> mediatek have a sour history on that front
[00:01] <daniel31> i'll certainly follw your advice in staying away from them, whatever I decide..
[00:02] <bact> I think the moto g is nicely priced device
[00:02] <bact> but it doesn't have a chance of getting ubuntu touch
[00:03] <daniel31> yeah I hear you
[00:06] <daniel31> you know, I still cant help thinking it is apity u4a never developed an open community around it. I reckon u4a would have the chance to be compatible with more current generation handsets than ubuntu touch will be when its relased.. :-\
[00:06] <daniel31> I mean, I could be wrong about that obviously..
[00:07] <bact> mmm
[00:07] <daniel31> kind of like how cyanogen start off..
[00:08] <bact> maybe just shuttleworth thought it would be more efficient to allocate all the resources to touch
[00:09] <daniel31> yeah, its totally understandable. I'm not ruing canonical not backing it, its just apity the community didnt express more of an interest. but I guess the community is all in the waiting-for-ubuntu-touch-mode just now.
[00:10] <daniel31> I mean youre totally right that canonical should be devoting resources to touch just now
[00:10] <daniel31> instead of u4a
[00:12] <daniel31> well I think I must go tto sleep now. thanks fo rthe stimulating conversation, bact.
[00:12] <daniel31> talk to u later
[00:51] <Steve[cloud]> tis sadz that the N10 is no longer supported
[02:14] <dobey> Steve[cloud]: what? nexust 10 is supported still.
[03:57] <Zeh_Gordinho> Hi everyone ...
[03:59] <Zeh_Gordinho> I'm thinking in start a ubuntu phone ... with my LG e425f or L3II is the same ...
[03:59] <Zeh_Gordinho> iss there anyone here that already tried
[03:59] <Zeh_Gordinho> ?
[04:06] <Zeh_Gordinho> is there anyone online here ?
[04:48] <Zeh_Gordinho> Is there anyone using Ubuntu Touch on LG L series phone ?
[06:34] <dholbach> good morning
[07:14] <TyrfingMjolnir> What will it take to make debian-touch?
[07:20] <TyrfingMjolnir> Is Ubuntu Touch its own separate thing?
[07:20] <TyrfingMjolnir> Or does it relate to android?
[07:23] <RAOF> TyrfingMjolnir: debian-touch? You could do that yourself, if you really wanted :)
[07:27] <nhaines> TyrfingMjolnir: I suspect to make debian touch you'd have to do a *lot* of porting things to Debian.  I wonder what the use would be?
[07:55] <mpt> cyphermox, MacSlow: Does bug 1315419 really belong to indicator-network, or does it belong to notify-osd?
[07:56] <MacSlow> mpt, that would still be notifictions... there's a bug/feature-requrest in the pipe to make timeouts configurable
[07:57] <MacSlow> mpt, certainly not a bug for network menu
[07:57] <MacSlow> mpt, but rather unity8's notifications
[07:58] <MacSlow> mpt, the real fix is to move all dialog-like abuses out of notifications, but that'll take some time
[08:00] <JamesTait> Good morning all; happy No Homework Day - my boys will be thrilled!  :-D
[09:07] <mpt> thanks MacSlow, I moved it to unity8
[09:07] <MacSlow> mpt, ok
[09:08] <mpt> MacSlow, and does bug 1315734 belong to notify-osd or to friends?
[09:10] <MacSlow> mpt, notify-osd never had sound support, so this is probably an issue with "friends"
[09:12] <mpt> That’s what I thought, thanks
[09:12] <MacSlow> mpt, btw... I'm currently adding sound-support to unity8's notifications
[09:12] <mpt> Containers are blamed for their contents
[09:12] <MacSlow> mpt, I've a thick skin :)
[09:43] <TyrfingMjolnir> ""
[09:43] <TyrfingMjolnir> No more smart quotes Yey!
[09:59] <davmor2> Morning all
[09:59] <MacSlow> hi davmor2
[11:26] <dpm> is it possible to upgrade a phone that's got trusty installed to utopic via System Settings, or does it need to be reflashed? I'm guessing the latter, but asking just in case :)
[11:31] <ogra_> dpm, it should automaticallyoffer you the upgrade if you properly used the devel or devel-proposed channels
[11:31] <ogra_> if you didnt: adb shell system-image-cli --channel devel -b 0 -v
[11:31] <ogra_> that will switch channels for you
[11:31] <ogra_> (and upgrade you at the same time)
[11:32] <dpm> ah, nice, thanks ogra_, I'll get them to test that!
[11:33] <ogra_> should theoretically also woth from the terminal app (with sudo indeed) if you dont have a second machine for adb
[11:33] <ogra_> *work
[11:43] <kaisoz_> hi
[11:43] <bact> ogra_: does m.here.com work well in ubuntu touch?
[11:43] <bact> I just remembered it existed
[11:44] <ogra_> bact, it should ... getting a GPS fix means i would have to sit outdoors for 20min to actually test it though
[11:44] <bact> but is it smooth?
[11:44] <ogra_> as smooth as it is on android
[11:45] <bact> cool
[12:03] <facundobatista> hello!
[12:03] <facundobatista> question: I'm using the ubuntu-emulator... put the phone in "spanish", then tried to get into the dash, and it stays blank (after 10')
[12:04] <facundobatista> I'm seeing, in the terminal where I started it, an error like .../GLESv2Imp.cpp:glReadPixels:1610 error 0x500
[12:05]  * facundobatista restarts the emulator
[12:06] <oSoMoN_> Mirv, hey, can I get a silo for my latest landing request? I talked to dbarth and it’s ok to put line 15 on hold again (there is a pending issue that needs resolving before it’s ready to merge anyway), perhaps we can reuse silo 3 ?
[12:06] <Mirv> oSoMoN_: yes, I just discussed it on #ubuntu-ci-eng with him
[12:07] <oSoMoN_> ah, I should probably join that channel too
[12:21] <facundobatista> question: how can I make the emulator (that is currently in 14.04 r262) to upgrade to 14.10 #9 ? thanks!!
[12:22] <pmcgowan> davmor2, popey did you happen to see my inquiry on the updates bug when you have system and apps available
[12:23] <davmor2> pmcgowan: I've not had apps and updates available at the same time so I don't know
[12:24] <davmor2> pmcgowan: I've not seen it at least
[12:24] <pmcgowan> davmor2, ok, I see it all the time, and I unclear why folks are not squawking about it
[12:24] <davmor2> pmcgowan: only time updater has played up for me has been when I hit the routing issue.
[12:25] <pmcgowan> davmor2, its easy to reproduce by going back a revision or two when core apps have been updated
[12:25] <Spektr> is this a dev irc?
[12:26] <popey> pmcgowan: no, what?
[12:26] <pmcgowan> popey, let me get the bug #
[12:27] <pmcgowan> https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1309015
[12:28] <popey> pmcgowan: i have seen the updates page clear sometimes, ogra_ has seen that too, not seen it crash
[12:28] <pmcgowan> popey, yes I see the clearing much more often, crash not anymore
[12:29] <pmcgowan> its a race with the app results, when they come back it seems to mess up the qml
[12:29] <pmcgowan> but it effectively prevents updating unless you remove your U1 account
[12:29] <popey> oof
[12:30] <seb128> gatox said he would work on that
[12:30] <seb128> not sure what's the status though
[12:31] <pmcgowan> seb128, ok good, I was concerned since its been there for some time in spite of being so easy to reproduce
[12:32] <seb128> pmcgowan, you are the only one who seem to run into it/report it for some reason
[12:32] <gatox> seb128, pmcgowan yes, i'm working in several system-settings related issues, right now i'm finishing a branch with a couple of fixes
[12:32] <seb128> well, I mean we didn't get much pings/reports about the issue
[12:33] <seb128> not sure if that's because most people just update the system images and regularly and don't end up in situations were click&system are outdated
[12:33]  * gatox is building on the phone to test everything
[12:33] <seb128> gatox, great, thanks for the work on those issues!
[12:34] <pmcgowan> seb128, yep understood
[12:34] <pmcgowan> gatox, great
[12:34] <gatox> pmcgowan, right now i'm testing everything with real image and click updates
[12:34] <pmcgowan> gatox, awesome, if you need a tester let me know
[12:35] <gatox> pmcgowan, ack, thanks
[12:39] <shine911> hello all
[12:39] <shine911>   i want make ubuntu touch for codina, now i have system.img what can i do next to create zip file?
[12:42] <ogra_> shine911, we dont use zip files anymore ... flash recovery and kernel imgs from your build and then follow the manual install instructions from the install wikipage
[12:44] <shine911> how? where you can tell me? please... thank so much, i see i9100 also use zip file and flash via cwm...
[12:45] <ogra_> https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation
[12:53] <shine911> ok thanks!
[12:58] <shine911> hmm... my device not have fastboot
[12:59] <ogra_> well, flash recovery and boot as you would normally do
[12:59] <ogra_> then boot into recovery
[12:59] <ogra_> all the further stuff happens via recovery anyway
[13:00] <ogra_> (you said samsung, so i assume you can use heimdal or some such)
[13:02] <shine911> maybe odin? right?...
[13:03] <ogra_> or that, right
[13:03] <ogra_> whatever you neeed to use to flash :)
[13:07] <shine911> ok, i will try, hope it boot....
[13:07] <shine911> thank a lot
[13:07] <gatox> seb128, when you have the time: https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/duplicate-and-credentials/+merge/218414
[13:07] <seb128> gatox, looking
[13:08] <ogra_> bzoltan1, looking at https://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/AbstractButton.qml#L85 ... are devs not supposed to be able to set/unset their own haptics freedback in apps ? that seems a little heavy to hardcode
[13:29] <bzoltan1> ogra_: I would say, that devs are better leave the haptics alone... at least for now. The HapticsEffect should be and maybe will be part of the component styles
[13:30] <ogra_> bzoltan1, so i cant have buttons in apps that dont do any haptic effect ?
[13:38] <kalikiana_> ogra_: can you give an example of where you want a button with no feedback?
[13:39] <ogra_> kalikiana_, i have my own little ebook reader app (with white font on black bg etc) to read in bed ... while i now added gestures to flip pages i initially used back forward buttons ... but my GF complained about the noise all the time
[13:40] <ogra_> kalikiana_, i can imagine that there are many usecases where a dev wants to switch it off for in-app buttons
[13:40] <kalikiana_> ogra_: presumably the noise would be an issue with any button at all, not just that app
[13:40] <kalikiana_> right?
[13:40] <ogra_> yes
[13:40] <ogra_> but i wouldnt use other buttons while reading or using that specific app
[13:40] <ogra_> i agree there should be haptics for all system elements
[13:40] <ogra_> but i thinnk it should be configurable for in-app elements
[13:41] <zsombi> ogra_ well, then that needs to be disabled in the whole system then
[13:41] <kalikiana_> thing is, is it really in-app, if you completely want to avoid the noise coming from vibrations
[13:41] <zsombi> ogra_ haptics is an accessibility element, you cannot really disable in one app...
[13:41] <ogra_> zsombi, AbstarctButtonHaptic vs AbstractButton ;)
[13:42] <kalikiana_> ogra_: that makes no sense
[13:42] <zsombi> orga_ :) yeah, make a haptic version of each component in the toolkit :D
[13:42] <ogra_> kalikiana_, well, i think it makes no sense to force it on the dev ... we have configurable haptics effects but i cant make any use of that due to the hardcoding
[13:43] <kalikiana_> ogra_: so tell me, is it "the dev" or the phone as a whole device with all apps?
[13:43] <kalikiana_> I don't see why the ebook reader is special
[13:43] <ogra_> on, the reader was just an example
[13:43] <ogra_> i think it should generally be configurable for devs
[13:43] <kalikiana_> if you send tons of texts your better half would be just as annoyed I assume
[13:44] <kalikiana_> as long as it makes that noise
[13:44] <zsombi> ogra_ as said, haptics belongs to the accessibility group, not really an in-app opt-out story
[13:44] <ogra_> well, ignore the noise :) i just dont like that it is hardcoded :)
[13:44] <t1mp> we can add property bool haptics: true to components
[13:45] <kalikiana_> which will… do what?
[13:45] <ogra_> t1mp, that would be perfect
[13:45] <kalikiana_> breakAccessibility: true
[13:45] <t1mp> kalikiana_: you can set it to false to switch off the haptics
[13:45] <ogra_> kalikiana_, allow me as a dev to disable haptics in my app elements
[13:45] <ogra_> or even the whole app
[13:46] <kalikiana_> ogra_: I still don't see the use case
[13:46] <ogra_> alternatively just make the settings configurable ... (intensity, duration fadetime etc)
[13:46] <t1mp> kalikiana_: camera-app.. you don't want your phone to be vibrating every time you are taking a photo
[13:46] <ogra_> so you could set it all to 0
[13:46] <ogra_> heh, or vibrate during taking a video
[13:47] <t1mp> ogra_: you don't keep pressing while making a video. but in a photo (especially with long shutter time) you should keep your device still
[13:47] <ogra_> how about http://pad.lv/1290201
[13:47] <ogra_> hmm, pad.lv is dead
[13:47] <ogra_> bug 1290201
[13:47] <kalikiana_> ogra_: I'm with you on that, if we're talking about "no vibration for typing" or "no vibration for pressing buttons" globally - in which case it won't be totally up to the whim of every app dev
[13:48] <ogra_> kalikiana_, i just dont like that we hardcode ... if it is configurable on demand i'm fine
[13:48] <ogra_> default should be with haptic ... but there should be ways to disable or  adjust imho
[13:49] <kalikiana_> ogra_: it was originally like this: we had no feedback. we added feedback. nobody had time to do anything fancy
[13:49] <kalikiana_> no evil intent behind it
[13:49] <Spiko-bG> ey guys I have a question, prolly u are sick of these but I was wondering if you can point me any tablet that's supporting ubuntu touch on 100% (cellular module included) Nexus 7 does that?
[13:49] <ogra_> kalikiana_, i know :)
[13:50] <ogra_> kalikiana_, but i also guess that code needs to be touched before we go to market (in 2-3 months) ... since the current feedback is really not proper yet
[13:50] <ogra_> thats why i bring it up now ... so we have time to get something proper in place
[13:51] <ogra_> kalikiana_, take bug 1290201 as reference, i think thats even a better example than my own hacked together app
[13:55] <kalikiana_> ogra_: hmm yeah. maybe it would make sense to lower intensity during calls.
[13:56] <a700> Hi guys, short question while porting a device... To make the lxc container startup, i must convert the ueventd.rc to lxc android container rules?
[13:56] <ogra_> kalikiana_, well, also during video capturing and photos ... you dont want haptics to vibrate the phone when you press the shutter ;)
[13:57] <ogra_> or change video settings while recording
[13:57] <kalikiana_> ogra_: but you may want them to click, ie. what Android calls "touch sounds"
[13:57] <ogra_> a700, you need to turn them into udev rules so the devices get also created outside of the container
[13:57] <ogra_> kalikiana_, not while taking a video
[13:57] <ogra_> for the shutter when taking a photo
[13:58] <kalikiana_> ogra_: actually it might be the same as the call case then, you don't want to disturb the audio input
[13:58] <ogra_> but setting the ISO settings while taking a video should be silent for example ... i dont want phone sounds on my video and i dont want it to vibrate either which will cause bulr
[13:58] <ogra_> *blur
[13:59] <kalikiana_> maybe what we need here is for enabling the microphone to disable haptic feedback
[14:00] <ogra_> once we have something that reflects "mic enabled" to the toolkit that could work, yes
[14:01] <a700> ogra_, thanks like the supported device 70-flo.rules?
[14:01] <ogra_> a700, thats for the 2013 netxus 7 ...
[14:01] <kalikiana_> or even usensord itself - since you can cause vibrations regardless of the toolkit otherwise which we might want to avoid
[14:01] <kalikiana_> but, not sure
[14:01] <kalikiana_> might be there's still a corner case in- between
[14:02] <ogra_> well, i think i would also want to be able to play with haptics settings if i was a game dev for example
[14:02] <ogra_> where i would expect them to be adjustable to my needs
[14:02] <kalikiana_> that's what I mean, you can use the QML API if you like, we won't artificially prevent you from that
[14:02] <kalikiana_> but then you still don't want to disturb your video, right?
[14:03] <ogra_> right
[14:03] <ogra_> or m calls or the taking of photos
[14:06] <kalikiana_> maybe sergiusens can give an opinion if that is feasible, lp lists him in the latest usensord changes
[14:08] <ogra_> kalikiana_, in case you want to keep the hardcoding, we really need to review the settings for it i think ... (not sure how much you use the phone during the day, but the current setup is pretty awful)
[14:09]  * ogra_ is always happe there are only two screws in the N4 case ... i fear it would have fallen apart by now if there were more ... 
[14:09] <ogra_> :)
[14:09] <ogra_> s/happe/hoping/
[14:09] <bact> fallen apart?
[14:09]  * ogra_ glares at his fingers
[14:10] <bact> most devices don't even use screws, just clips
[14:10] <ogra_> bact, the haptic feedback is pretty heavy, long and violent atm ... just to have "something" ...
[14:10] <t1mp> kalikiana_: are we currently using any system settings in uitk apps?
[14:11] <ogra_> strong enough to loosens screws :)
[14:11] <bact> Oh, I see, you were making a funny
[14:11] <ogra_> *loosen
[14:11] <awe_> Wellark, do you know the current status of SIM PIN Unlock in the UI?  I was testing yesterday and it wasn't in the network menu anymore, and try as I might, I couldn't find where it had migrated to in the UI?
[14:11] <ogra_> bact, not really ... it needs to become better for final release ...
[14:11] <kalikiana_> ogra_: it's not so much about hard-coding. but being smarter than arbitrary one/off per app
[14:11] <kalikiana_> it should be defaults, if we did have settings for it
[14:12] <kalikiana_> but it's "hard-coded" as there is nothing else
[14:12] <ogra_> right
[14:12] <ogra_> i just mean if we ship with the hard coded stuff it needs adjustment
[14:13] <ogra_> (i wouldnt expect a perfect solution for the first going to market ... but a usable one for the default at least)
[14:14] <kalikiana_> I definitely want a no-vibrations-nor-sounds mode before we ship
[14:14] <kalikiana_> easily enough to switch when I enter/leave the place
[14:14] <ogra_> right
[14:16] <ogra_> that too ... but the current vibration defaults also need to be better ... compare teh haptics of an android phone button press to ours ...
[14:16] <ogra_> ours feels to long and to strong ...
[14:17] <ogra_> (not saying that android has it right, but it feeels a lot less like the phone will soon fall apart due to it :) )
[14:18] <kalikiana_> heh. yeah, it's stronger than the Android phone I have here
[14:19] <kalikiana_> though I find it more problematic that Android often fails to provide any feedback depending on cpu
[14:19] <kalikiana_> not sure if we'll inherit that limitation somehow or if we can do better
[14:19] <ogra_> hmm, where do we install AbstractButton.qml to ? i'm happy to play with it a bit to get saner values
[14:19] <ogra_> well, thats usually a limitaion of the hardware ...
[14:20] <ogra_> i.e. the nexus7 devices simply dont have a vibrator
[14:20] <t1mp> ogra_: dpkg -L qtdeclarative5-ubuntu-ui-toolkit-plugin|grep AbstractButton
[14:20] <ogra_> geez
[14:20] <ogra_> t1mp, thanks ... 9 years ubuntu and thats still not on my blood ...
[14:21] <kalikiana_> ogra_: /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/
[14:21] <ogra_> yeah
[14:21] <t1mp> I always need to use it on device to test something quick, because I don't know where the files end up there
[14:21] <ogra_> i'm so spoiled by locate working everywhere :)
[14:21] <t1mp> well it is probably not that hard to remember, but dpkg -L is easier to remember
[14:53] <robotfuel> bfiller: what else needs to be done to merge the gallery-app MP?
[14:55] <robotfuel> bfiller: I replied to your email, tests are passing for both utopic on the phone and also the desktop.
[14:55] <bfiller> robotfuel: in process of being merged
[14:56] <robotfuel> bfiller: thanks :D
[14:56] <bfiller> robotfuel: once that happens just need to upload new clicks to the store, sergiusens can you help with that today?
[14:56] <bfiller> sergiusens: need new clicks for camera, notes and gallery uploaded (once latest gallery MR is merged)
[14:59] <sergiusens> bfiller: yeah, just tell me when, and I will
[15:03] <shine911> :( port for codina => Stuck at splash screen
[15:35] <bact> when the two official ubuntu touch phones come out are the team at canonical going to build towards those instead of nexus's?
[15:36] <ogra_> we will keep building for nexus as well as these phones
[15:37] <ogra_> at least for a while
[15:38] <bact> do you have a hardware partner for a tablet sized device?
[15:38] <ogra_> not sure ...
[15:39]  * ogra_ isnt so close to sales 
[15:39] <daniel31> is it possible to install ubuntu for android (not ubuntu touch) on the google nexus series?
[15:39] <daniel31> a develop preview for example
[15:39] <ogra_> daniel31, nope
[15:39] <daniel31> so there have been no developer previews released? I have seen some comments saying it was available but I guess they were getting it confused with ubuntu touch..?
[15:39] <ogra_> ubuntu for android is suspended ... no work is going on with it and it will only be resumed if a partner shows up
[15:40] <ogra_> it requires heavy changes to the android, so it can only be done with an actual manufacturer
[15:40] <bact> ogra_: how difficulty would it be to build ubuntu touch for an x86 chipset?
[15:40] <ogra_> UfA has never been released to the public
[15:40] <daniel31> yes, I understand it has been suspended… but we have all seen the canonical videos of it running on a nexus. I was hoping if anyone knew about whether the source code for it had been released to the community in any case..
[15:41] <ogra_> bact, we have x86 rootfs images ... you just need to build the android HAL for it
[15:41] <bact> hmmm
[15:41] <ogra_> daniel31, it hasnt been releases
[15:41] <ogra_> *released
[15:42] <daniel31> pity :-)
[15:42] <bact> hi daniel31, from last night
[15:42] <daniel31> hi bact. sorry I'm here again :-P
[15:42] <ogra_> daniel31, and afaik the source wouldnt help you if you would not also have the source to the binary drivers
[15:43] <bact> I hate that
[15:43] <bact> bloody binary blobs
[15:43] <daniel31> I hear you
[15:43] <bact> why is it okay for arm soc's do that?
[15:43] <ogra_> (but i'm only guessing, dont quote me on that, i know there are  deep changes needed on teh android side)
[15:44] <bact> *to do
[15:44] <ogra_> bact, why is it not ?
[15:44] <ogra_> they own the HW and they own the driver code
[15:44] <ogra_> nobody can force them to open it
[15:45] <bact> is this meizu x3 ubuntu edition going to be much of the same?
[15:45] <ogra_> i agree it would be nice ... and social and all ... but there is no reason for them to do that beyond being friendly
[15:45] <bact> binary blobs and all that
[15:45] <ogra_> i think so
[15:45] <ogra_> meizu is just a manuafacturer
[15:45] <ogra_> they are not the creators of the chips they use
[15:46] <ogra_> so they have to take what the supplier gives to them
[15:46] <bact> so it's still a qualcomm chipset or whoever
[15:46] <ogra_> indeed
[15:47] <ogra_> if you want to produce phones where you at least get the investment back that you made top develop it you wont be able to build something open easily ... after all they have to pay the salaries of their employees too
[15:48] <ogra_> the only entitiy i see that could apply some pressure on manufacturers would be google
[15:48] <ogra_> to actually require them to open it
[15:49] <Stskeeps> (and just look at the AOSP debacles that JBQ had, to see that even that doesn't work..)
[15:49] <ogra_> yeah
[15:49] <ogra_> well, google *could* have done better if they wanted
[15:49] <ogra_> they are in power here
[15:50] <daniel31> it does seem to me that the smart investor would focus on high-quality (e.g. apple-like, they do make good hardware) hardware with open software. that way they benefit from community-supplied patches, modifications and security but have a loyal user base around the software. never mind all this 'value-added' crap of generic devices where the differentiator is which crappy software gets loaded with the device. I hope thats what we start to see with ubun
[15:50] <ogra_> you cut off
[15:50] <daniel31> *sorry I should say they build a loyal user base around the hardware
[15:50] <ogra_> "I hope thats what we start to see with ubun"
[15:50] <daniel31> Oh. I just said I hope thats what we start to see with ubuntu-touch based devices..
[15:51] <ogra_> you will see such a thing if canonical ever gets as big as google :)
[15:51] <daniel31> unlikely, unfortunately..
[15:51] <ogra_> but until then i doubt there is any interest for chip manufacturers to open up all their drivers
[15:52] <daniel31> I am sort of in the market for a new laptop as well you see and coming from the apple world as a loyal user for many years (but don't get me started on that) there is really not much in the way of hardware which is as high-quality as what they make. its a shame they are such a horrible company in general. please correct me if I am wrong of course..
[15:53] <daniel31> laptop and computer-wise anyway, iphones are a different issue..
[15:55] <daniel31> well, roll on ubuntu and ubuntu touch I say..!
[15:59] <john-mcaleely> ogra_, any suggestions where to file a bug about disk space exhaution? specifically if the user copies logs of movies to the device
[15:59] <doanac> mterry: good news. plars is merging your unlock change as we speak.
[16:00] <doanac> hopefully we can iterate from there more easily now
[16:00] <mterry> doanac, oh that is awesome!
[16:00] <mterry> doanac, thanks
[16:00] <plars> mterry: sorry for the delay, wanted to do it when no other jobs were running
[16:00] <plars> just to be on the safe side
[16:01] <dobey> daniel31: get a dell xps13 sputnik that comes pre-loaded with ubuntu
[16:02] <ogra_> john-mcaleely, well, since the expected fix didnt work file it against android ... we attempted to fix it in the system-image-upgrader script in the recovery image
[16:02] <ogra_> (the android package that is)
[16:02] <john-mcaleely> ogra_, ok, will do. thanks
[16:03] <john-mcaleely> pmcgowan, in an unrelated question, where do bugs against SD card support belong? (user side, UI stuff)
[16:03] <ogra_> john-mcaleely, we cant really do anything with SD card support on nexus
[16:03] <ogra_> there is no slot
[16:03] <daniel31> thanks dobey :-)
[16:03] <john-mcaleely> ogra_, but do we have some way to exercise it?
[16:04] <ogra_> not really i think
[16:05] <john-mcaleely> ogra_, hmm. I thought there were plans for support
[16:05] <pmcgowan> john-mcaleely, phonedations team needs the phone with sd slot
[16:05] <ogra_> right
[16:05] <ogra_> we can work on that once we have an actual device with the hardware
[16:05] <pmcgowan> I suspect its not a big issue
[16:06] <ogra_> we could fake the world and would still not be able to make sure the fake reflects reality
[16:06] <pmcgowan> ogra_,  did you work out the other out of disk problem
[16:06] <ogra_> pmcgowan, yes, i was the one who "fixed" it :/
[16:06] <pmcgowan> but why did john-mcaleely see it?
[16:06] <john-mcaleely> ogra_, pmcgowan ok, fair enough.
[16:07] <ogra_> pmcgowan, because the fix apparently does not work
[16:07] <pmcgowan> lol
[16:07] <pmcgowan> hence "fixed"
[16:07] <ogra_> right
[16:09] <ogra_> john-mcaleely, pmcgowan bug 1270248
[16:09] <john-mcaleely> ogra_, thanks
[16:09] <ogra_> the android task in there was actually for the system-image-upgrader change ...
[16:12] <ogra_> https://code-review.phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=blob_plain;f=system-image-upgrader;hb=dbfe068decc0685b1222fa91e8def2bb8e58e42b
[16:12] <ogra_> the tune2fs line near the bottom was supposed to fix it
[16:14] <john-mcaleely> ogra_, ok, I'll document how it fails for me, and see if that helps
[16:14] <ogra_> thanks
[16:15] <ogra_> i assume we might need to be more strict than -m
[16:16] <ogra_> probably -r instead
[16:16] <ogra_> or additionally
[16:22]  * john-mcaleely reading the bug
[16:35] <ogra_> kalikiana_, t1mp, bzoltan https://code.launchpad.net/~ogra/ubuntu-ui-toolkit/improve-haptics/+merge/218466 ... one for you
[16:35] <ogra_> that gives more realistic defaults
[16:37] <cwayne> t1mp, heya, i saw some headers MP's go into lp:ubuntu-ui-toolkit/staging -- is there a ppa for that anywhere, or should i just build it myself?
[16:42] <cwayne> dpm, ping
[16:42] <dpm> hey cwayne
[16:42] <john-mcaleely> ogra_, yes -r looks like my case - will write up in the morning
[16:43] <ogra_> thanks !
[16:44] <cwayne> dpm, hey, did you log a bug for savilerow about the scopes translations?
[16:44] <dpm> cwayne, I didn't yet. Let me do that in the next few mins
[16:50] <t1mp> cwayne: I think there is no PPA, but there were talks about it some time ago, let me check
[16:50] <cwayne> t1mp, thanks.  how often do we release uitk from staging btw?
[16:52] <t1mp> cwayne: as often as possible. Should be at least weekly, but it happens that there are external issues that prevent us from doing a release every week
[16:53] <cwayne> t1mp, ah, awesome
[16:53] <t1mp> bzoltan: ^ we don't have a staging ppa right?
[16:53] <didrocks> cwayne: mterry did the change if I'm correct, you can ask him to answer on the ML ;)
[16:54] <didrocks> (re: overrides)
[16:54] <cwayne> didrocks, yep, thanks. realized right after i sent that mail :)
[16:59] <t1mp> cwayne: what we have in staging can put the actions, back button, tabs drawer in the header
[16:59] <t1mp> cwayne: what else did you need?
[17:00] <cwayne> t1mp, i *think* those are the main things we needed, well other than getting the core apps using the new headers
[17:00] <t1mp> cwayne: if you use Actions to define the ToolbarButtons, all you need to do in apps is change MainView.useDeprecatedToolbar to false, and it should magically work :)
[17:00] <cwayne> t1mp, awesome!
[17:01] <t1mp> I will send an e-mail to the mailing lists when we have it in trunk and the image
[17:01] <cwayne> t1mp, perfection, thank you for all the help on this :)
[17:03] <t1mp> cwayne: np :) I'm quite sure the work is not done yet. Apps will need to be modified and when people start using the new header we will find new bugs
[17:03] <cwayne> t1mp, of course, but this is the start that we needed :)
[17:15] <ogra_> fginther, i think cjwatson should be involved in that meeting about "building images per landing" since he just implemented launchpad buildd support to roll images
[17:15] <ogra_> i assume that is what we should use for that case
[17:16] <ogra_> i know he also worked on PPA support fro this setup, but i'm not sure this is included yet
[17:16] <ogra_> plars, ^^
[17:19] <cjwatson> ogra_: It's still in progress, but I plan to have it rolled out by Malta
[17:19] <ogra_> sounds perfect
[17:19] <ogra_> i added you to the CC list of the mail i was referring to
[17:19] <cjwatson> ogra_: At least some of the changes necessary to use a PPA are in place, but I haven't tested it and I suspect there are still a few bits missing
[17:20] <cjwatson> The touch use case is absolutely one of the ones I've had in mind though
[17:20] <ogra_> well, it still uses livecd-rootfs internally, no ? worst case we could add a switch there as interim solution
[17:20] <fginther> ogra_, thanks
[17:20] <cjwatson> I expect that making it use a PPA will involve a little work in livecd-rootfs, yes, but we can do it more elegantly than a hard switch
[17:21] <fginther> cjwatson, I'm curious as to how click packages are incorporated
[17:21] <cjwatson> The source archive, if any, is passed down through launchpad-buildd
[17:21] <cjwatson> fginther: No different from how it's done today
[17:21] <cjwatson> live-build/ubuntu-touch/hooks/60-install-click.chroot in livecd-rootfs
[17:21] <cjwatson> (i.e. a fairly crude hack)
[17:22] <fginther> as long as it's the correct crude hack
[17:22] <ogra_> that might need extension so we can test with "PPA" click packages
[17:22] <cjwatson> One thing I was thinking of was maybe stuffing it into the LiveFS metadata (which is an arbitrary dict in LP)
[17:22] <ogra_> i.e. an additional staging area for clicks ...
[17:23] <cjwatson> Like, say, a URL that provides the list of click packages to install
[17:23] <ogra_> yeah
[17:26] <cjwatson> Anyway, this is literally my sole focus right now, but the first priority is making sure I have a correct like-for-like replacement for the current system
[17:27] <ogra_> yeah
[17:27] <ogra_> well, francis didnt sound like he wants it today :)
[17:49] <cwayne> oof, building uitk in an armhf chroot is not fast.
[18:00] <pmcgowan> gatox, fyi https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1309015/comments/14
[18:01] <gatox> pmcgowan, yes.... that's how i'm reproducing that bug
[18:02] <pmcgowan> gatox, I never thought to go the other way ;)
[18:02] <pmcgowan> how is it different, anyway
[18:02] <gatox> pmcgowan, i usually use updates button, so i wasn't able to reproduce it first... but then i figure it out
[18:02] <pmcgowan> sorry  I didnt figure it out earlier
[18:03] <pmcgowan> I expected it to use the same code
[18:03] <gatox> pmcgowan, no idea.. i'm fixing some other issue (fixing some issues that touches those things and make everthing cleaner), and that one will be the next one... but i'm working on that widget right now
[18:03] <pmcgowan> gatox, very good
[18:03] <gatox> pmcgowan, maybe in the way that pushes the page into the stack or something
[18:04] <gatox> pmcgowan, i proposed a couple of branches for system settings today
[18:04] <pmcgowan> gatox, yeah so since updates button works, should be easy to fix it to do  the same
[18:04] <gatox> pmcgowan, waiting for reviews
[18:04] <pmcgowan> ok
[18:05] <dpm> cwayne, https://bugs.launchpad.net/savilerow/+bug/1316713
[18:09] <cwayne> dpm, thanks
[18:10] <mhall119> yay! r13 here I come
[18:11] <mhall119> strange, the item showing the download name and progress disappears
[18:12] <mhall119> jhodapp: is the new media-hub in r13?
[18:13] <jhodapp> mhall119, yeah, it's been in since r7
[18:13] <mhall119> well r13 is the first non-proposed image since r2
[18:13] <mhall119> jhodapp: anything that plays audio through the Qt API should take advantage of that right? and keep playing when the screen is off or app is in the background?
[18:14] <jhodapp> mhall119, correct, for audio only
[18:14]  * mhall119 is going to try his podcast app
[18:14] <mhall119> jhodapp: makes sense, playing video with the screen off isn't the best experience :)
[18:14] <jhodapp> mhall119, excellent, I tested out a number of various apps in the store including 3 podcast apps
[18:14] <mhall119> awesome
[18:14] <jhodapp> mhall119, unless you like to image the video ;)
[18:15] <jhodapp> imagine, err
[18:15] <mhall119> jhodapp: sometimes it better that way
[18:16] <jhodapp> hehe
[18:17] <mhall119> ah ha! it works, brilliant!
[18:17] <mhall119> does daker's Rad.io work too?
[18:18] <dobey> is it possible to have passwords stored for webapps?
[18:18] <mhall119> dobey: you can use the browser's storage, but that's not secure
[18:18] <daker> mhall119: i tested it using the first utopic image
[18:19] <dobey> is it possible to have passwords stored (securely) for webapps?
[18:19] <dobey> :)
[18:19] <mhall119> dobey: you can use OnlineAccounts if you have a provider for your webapp
[18:19] <daker> mhall119: but the sound stops once it loses the focus
[18:19] <mhall119> wait...I'm thinking html5 apps, nvm
[18:19] <dobey> mhall119: but webapp-container doesn't magically fill the password form with data from online accounts does it?
[18:20] <mhall119> daker: are you using something other than the Qt APIs? or are you continuously downloading new bits of audio
[18:20] <mhall119> dobey: no
[18:20] <daker> mhall119: gstreamer directly...
[18:20] <daker> brb
[18:20] <mhall119> daker: ah, that might be the issue, can you use the Qt APIs?
[18:20] <dobey> so basically, online-accounts, qml+oxide, and lots of javascript, if i want to do it?
[18:22] <mhall119> yeah, unless you want to draft a spec for the WebApps API to let is securely remember login info
[18:22] <jhodapp> mhall119, should
[18:22] <dobey> grooveshark stops playing audio when backgrounded on image #13 still
[18:23] <dobey> so i guess oxide needs fixed?
[18:23] <jhodapp> daker, you'll want to switch over to using the Audio component in QML
[18:29] <jhodapp> dobey, Oxide doesn't take advantage of media-hub at all yet
[18:29] <jhodapp> dobey, so backgrounding won't work for it
[18:31] <dobey> right
[18:32] <dobey> so i guess oxide needs fixed :)
[18:33] <jhodapp> dobey, definitely
[18:34] <ogra_> nah, we should just enhance media-hub with a browser
[19:00] <mhall119> yay, I have working alarms again!
[19:14] <jhodapp> ogra_, lol
[19:15] <jhodapp> ogra_, the new emacs!
[19:49] <daker> jhodapp: the QML audio component doesn't support GST_TAG_TITLE
[19:50] <jhodapp> daker, what exactly do you want to be able to do then, can you describe the use case?
[19:53] <daker> jhodapp: this https://bazaar.launchpad.net/~rad.io-devs/rad.io/trunk/view/head:/plugin/player.cpp#L57
[19:54] <daker> the NowPlaying title from the stream
[19:56] <jhodapp> daker, ok, we could at least solve that by adding support to the platform-api
[19:56] <daker> jhodapp: two things :
[19:56] <daker> - i should be able to get the stream title
[19:57] <daker> - i should be able to the NowPlaying title(aka GST_TAG_TITLE)
[19:58] <daker> and i think this would be a benefit to all the upcoming stream/radio players
[19:58] <jhodapp> daker, indeed...it looks like the QML layer just doesn't export this, seems to be there via the C++ Qt object: http://qt-project.org/doc/qt-5/qml-qtmultimedia-mediaplayer.html
[19:59] <rsalveti> ogra_: https://code.launchpad.net/~rsalveti/project-rootstock-ng/adding_option_distro_series/+merge/218502
[19:59] <jhodapp> daker, err, that is the qml object
[19:59] <cwayne> t1mp, \o/ got new headers on my device here, looks awesome :D
[19:59] <daker> jhodapp: ya i have tested that...
[20:01] <jhodapp> daker, what'd you find?
[20:02] <daker> jhodapp: the first time, i thought that i could find the NowPlaying track in metaData.title
[20:04] <mhall119> cwayne: oh? what build?
[20:05] <jhodapp> daker, but what'd you find?
[20:05] <daker> jhodapp: what do you mean ?
[20:05] <jhodapp> daker, did you get no data, the wrong data, etc?
[20:05] <jhodapp> daker, looking for some more details :)
[20:05] <daker> jhodapp: undefined :)
[20:05] <daker> and i couldn't find any Onchange func...
[20:06] <jhodapp> daker, any QML property inherently has an onChange function
[20:06] <cwayne> mhall119, i grabbed some uitk debs, not in an image yet
[20:06] <daker> jhodapp: ok i'll test it again now
[20:07] <jhodapp> daker, alright cool, it may be that I have to add some code to qtubuntu-media, but hopefully not
[20:11] <mhall119> cwayne: can I see a screenshot?
[20:11] <mhall119> tease the internets
[20:12] <cwayne> mhall119, trying now, but running into issues with phablet-screenshot
[20:12] <mhall119> oh, right, mir changes broke it didn't they
[20:12] <cwayne> yar
[20:14] <mhall119> hmmm, I can't update apps on r13, can anybody else?
[20:14] <mhall119> popey: ^^
[20:14] <mhall119> they just stay at 0%
[20:14] <mhall119> Calculator and Notes
[20:14] <popey> they do update for me
[20:14] <popey> but the % doesnt move
[20:14] <popey> on #14 they do
[20:15] <mhall119> oh, ok, so maybe I just need to wait
[20:15] <mhall119> still, not big apps, they should be done by now
[20:16] <popey> i believe it's a bug in u-d-m or u-s-s
[20:19] <pmcgowan> mhall119, I have the same problem
[20:19] <pmcgowan> I am running 14
[20:22] <cwayne> mhall119, huh, even on a promoted image phablet-screenshot fails
[20:25] <mhall119> cwayne: have you updated phablet-tools? maybe there's a fix there
[20:25] <pmcgowan> mhall119, could it be on the server side I wonder
[20:25] <mhall119> maybe, beuno ^^
[20:25] <cwayne> mhall119, just tried, no update
[20:25] <pmcgowan> cwayne, there was a fix made wrt adb and the screenshot tool
[20:25] <pmcgowan> couple weeks ago maybe
[20:26] <daker> jhodapp: http://paste.ubuntu.com/7406659/
[20:26] <pmcgowan> cwayne, what happens
[20:26] <cwayne> pmcgowan, im up-to-date
[20:26] <daker> Cannot assign to non-existent property "onMetaDataChanged"
[20:26] <cwayne> pmcgowan, remote object '/tmp/mir_screencast_1200x1920.rgba' does not exist
[20:27] <pmcgowan> cwayne, same here, mir busted
[20:27] <beuno> what what?
[20:27] <pmcgowan> cwayne, you want to enter the bug?
[20:27] <cwayne> pmcgowan, sure thing
[20:27] <pmcgowan> beuno, mhall119 and I are not able to download app updates
[20:27] <pmcgowan> download manager is timing out it seems
[20:28] <mhall119> beuno: system-settings says Calculator 1.3.253 and Notes 1.4.262 are available, but download never starts, stays at 0%
[20:28] <pmcgowan> I0506 16:22:22.248090  3959 base_daemon.cpp:154] Timeout reached, shutdown service.
[20:28] <mhall119> popey said the progress bar is broken, but even letting it sit for 10 minutes results in nothing happening
[20:28] <pmcgowan> bugs everywhere today
[20:29] <mhall119> yay promotion!
[20:29] <pmcgowan> mhall119, its not downloading for sure here
[20:29] <mhall119> but alarms work and music plays when the screen is off, so still a net improvement
[20:29] <pmcgowan> two steps forward, ...
[20:29] <mhall119> yup
[20:30] <beuno> so
[20:30] <beuno> let me test
[20:30] <pmcgowan> beuno, anyway I was pondering whther it could possibly be the server not responding
[20:30] <pmcgowan> ok
[20:30] <daker> anyone having this bug https://i.imgur.com/OZZrY3D.png ?
[20:30] <beuno> pmcgowan, mhall119, server is downloading fine
[20:31] <pmcgowan> daker, that is reported yes
[20:32] <daker> pmcgowan: ok thanks
[20:32] <pmcgowan> mhall119, I will file a bug fwiw
[20:38] <pmcgowan> mhall119, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1316794
[20:40] <beuno> pmcgowan, mhall119, my bets are on an authentication issue
[20:41] <beuno> or improper signing of the URLs
[20:41] <pmcgowan> which urls? to the store
[20:42] <beuno> yeah
[20:42] <beuno> the download
[20:42] <beuno> but without logs, I don't know
[20:42] <beuno> I can manually download stuff, no problem
[20:44] <pmcgowan> beuno, care to comment on the bug or also affects?
[20:51] <t1mp> cwayne: awesome :) which app are you testing with?
[20:53] <t1mp> mhall119: here is a screenshot of the new header with the flashback app https://www.dropbox.com/s/h23z0g29e4nxm8e/Screenshot%202014-05-01%2020.42.11.png
[20:55] <ahayzen> t1mp, has the new back button in header landed?
[20:55] <beuno> pmcgowan, done
[20:58] <t1mp> ahayzen: I'm not sure. There is a lot of new header stuff in our staging, I'll check if the back button went to trunk already
[20:59] <t1mp> ahayzen: yes, it is in our trunk :)
[21:00] <t1mp> ahayzen: and it is all automatic, if you set your MainView useDeprecatedToolbar to false and you are using a PageStack the back button will appear (when there is something on the stack to pop)
[21:04] <ahayzen> t1mp, ah cool thanks i'll have a play about see if i can get the music-app to use it :)
[21:05] <t1mp> ahayzen: the actions from the toolbar are not in the header yet in trunk, but the code is in our staging already so it will be included in our next landing (this week hopefully)
[21:05] <pmcgowan> cwayne, whats that screenshot bug? I think its just looking for the wrong filename
[21:06] <ahayzen> t1mp, ah cool i'll hang fire then :)
[21:08] <t1mp> ahayzen: or you bzr branch lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/staging && cd staging && qmake && make && source export_modules_dir.sh && run your app :)
[21:08] <ahayzen> :)
[21:09] <ahayzen> t1mp, while ur here who do i talk to for design approval of https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-1315775/+merge/218206
[21:09] <popey> pmcgowan: the filename has _60Hz added now
[21:09] <popey> cwayne: ^
[21:09] <pmcgowan> popey, right
[21:09] <pmcgowan> so the script doesnt match now
[21:09] <popey> which I dont *quite* understand for a static screenshot
[21:10] <daker> popey: yes i had to do that too
[21:10] <daker> i was told by ogra_ to add _60Hz to be able to take a screenshot again
[21:11] <t1mp> ahayzen: I'm thinking..
[21:11] <ahayzen> heh
[21:11] <t1mp> ahayzen: maybe it is an obvious bug that we don't need UX design approval for?
[21:12] <ahayzen> t1mp, idk do u think it is?
[21:13] <pmcgowan> popey, I am guessing mirscreencast was updated to capture video
[21:13] <ahayzen> t1mp, whether scrolling outside of the sheet should scroll the background page could be up for debate..but inside is definitely wrong
[21:13] <t1mp> ahayzen: yes
[21:13] <popey> pmcgowan: pass, i dont use it
[21:13] <mhall119> t1mp: while you're taking requests, I filed a couple of header-related bugs
[21:13] <t1mp> ahayzen: I thought when a popover is open nothing should happen to the background
[21:13] <popey> well, it already did video
[21:13] <t1mp> mhall119: I saw one, assigned it to me. I'll try to confirm it tomorrow
[21:13] <ahayzen> t1mp, magic :)
[21:14] <mhall119> t1mp: the other is wishlist, probably needs design input: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1315884
[21:15] <t1mp> ahayzen: you could ask johnlea whether no events at all should pass trough for all popups
[21:15] <ahayzen> t1mp, cool he is in london offices right?
[21:15] <t1mp> ahayzen: yes
[21:16] <t1mp> mhall119: I would definitely get design feedback on that one first before implementing that
[21:16] <mhall119> t1mp: the new headers look *nice*
[21:16] <t1mp> mhall119: do you have a good use case for having a different header color/image/textcolor per page?
[21:16] <ahayzen> t1mp, thanks
[21:17] <mhall119> t1mp: Android apps do it
[21:17] <mhall119> t1mp: I'm making an Android->Ubuntu converter, trying to re-create as much of the GUI as I can from Android's layout and theme files
[21:18] <t1mp> mhall119: yes I think the new header looks much cleaner than the previous one. And in the screenshot it is also nik90s app that makes it look good :)
[21:18] <mhall119> also, pages with different background colors might want different matching or complimentary header colors
[21:18] <t1mp> mhall119: "android has it" is not convincing enough for me ;)
[21:18] <mhall119> t1mp: my working example is Telegram, which has a blue header on most pages, but a black one on it's gallery page, since the gallery page has a black background
[21:18] <t1mp> mhall119: but it is more a decision for design to make than for me :)
[21:19] <t1mp> mhall119: you could set the backgroundColor of the MainView depending on which page is active
[21:19] <t1mp> although that seems like a workaround
[21:20] <taiebot> Hello talking about design. I have been using UT for 6 month and i think this one needs to be considered by the design team https://bugs.launchpad.net/ubuntu-ux/+bug/1295993
[21:20] <t1mp> mhall119: if you change background colors, the whole theme would have to change (text color for example)
[21:20] <pmcgowan> popey, cwayne https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1316806
[21:21] <mhall119> t1mp: text color was on the list
[21:21] <t1mp> mhall119: not only the header text, all text
[21:21] <mhall119> not if only the header text is changing
[21:21] <mhall119> header color
[21:21] <t1mp> mhall119: the header is supposed to look transparent, so it has the same background color as the page
[21:22] <mhall119> is it? I never got that impression
[21:23] <mhall119> anyway, at least one of our apps (Karma Machine) has forcibly set a background color on the Header only through some QML hacks
[21:23] <mhall119> I've seen some design mockups on G+ that did similar things
[21:23] <mhall119> so having a sanctioned way of doing it would be nice
[21:24] <ahayzen> mhall119, music-app has the header colour set
[21:24] <mhall119> beuno: pmcgowan: I removed and re-added my U1 account and still can't download updates, so it's not stale credentials
[21:24] <mhall119> t1mp: ^^ there's another example
[21:25] <mhall119> ahayzen: and music-app is based on the Canonical design team's design, right?
[21:25] <t1mp> mhall119: sure. If you can get feedback from a designer on that bug that would be great
[21:25] <ahayzen> mhall119, well
[21:25] <mhall119> t1mp: any designer in particular?
[21:26] <ahayzen> mhall119, think this was outside of the original designs as they have morphed quite a bit
[21:26] <t1mp> mhall119: I don't know, best ask john who to ask
[21:27] <pmcgowan> mhall119, new apps install as well
[21:27] <t1mp> taiebot: I haven't used in the sun much yet, but your bug makes sense. Most designers are in London and at this time I guess they are not online anymore to ask them to check the bug now
[21:28] <mhall119> t1mp: ok, I'll try and catch him tomorrow
[21:45] <taiebot> t1mp: thanks if you can confirm it or pass it on to the correct person that would be great.
[21:57] <beuno> mhall119, download work from trust 303
[21:57] <beuno> trusty
[21:57] <beuno> so it's something in image 13
[22:00] <ahayzen> t1mp, the new tab header stuff is awesome, nice work :)
[22:09] <dobey> beuno, mhall119: looks like probably an issue with system-settings, as i didn't see any u-d-m log activity when trying to install updates, but i could install an application just fine via click scope.
[22:32] <cwayne> mhall119, if you still wanted it: http://people.canonical.com/~cwayne/contact.png