[00:09] <sergiusens> lol
[01:23] <dobey> is it possible to override system theme colors for a widget in the ui toolkit?
[02:39] <mhall119> dobey: not really easily
[02:39] <mhall119> you can sometimes poke at internals of the StyledItem.style component,but that's not a supported API so it's not recommended
[02:40] <mhall119> or you can replaced the style component all together, but then you have to replace all of the functionality just to set a color
[02:42] <dobey> mhall119: yeah i was trying to use the Dialer component, but make it not be purple. :-/
[02:44] <dobey> lol. i just realized how bad that name is
[02:44] <dobey> since it has nothign to do with phone calls
[02:44] <mhall119> yeah, "Dial" would suffice
[02:45] <dobey> or ClockThing
[02:46] <dobey> it wouldn't really make a good widget for an RPM/MPH dial for a dashboard
[02:51] <dobey> oh well. later
[05:46] <cpyarger> I have followed the phablet-dev-bootstrap download guide for revision phablet-4.4.2_r1,  but I am unable to build for maguro, or toro, I know maguro is no longer officially supported, but Where do I need to go from here to get it working with  the utopic rootfs?
[05:46] <cpyarger> I noticed that manta is the only device located under device/samsung nothing for manta even synced.
[05:49] <cpyarger> I was told by sergisens tat I do not need to do anything special for the devices supported by AOSP
[06:56] <dholbach> good morning
[06:59] <kurros> indeed it is
[08:03] <JamesTait> Good morning all; happy Friday, and happy Industrial Workers Of The World Day! :-D
[08:05] <ogra_> stgraber,
[08:05] <ogra_> 2014/06/27 02:56:40 Device is |mako|
[08:05] <ogra_> 2014/06/27 02:56:41 Flashing version 101 from ubuntu-touch/utopic-proposed channel and server https://system-image.ubuntu.com to device mako
[08:05] <ogra_> 2014/06/27 02:56:52 Get https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc: EOF
[08:05] <ogra_> stgraber, could that be related to the key change ?
[08:05] <ogra_> (thats a device in the lab)
[08:06]  * popey waits while 3 devices all do the apparmor_parser dance
[08:06] <ogra_> heh
[08:06] <ogra_> after RTM we should talk about UI feedback for apparmor
[08:08] <jjohansen> ogra_: you mean like the android "optimizing applications" message that happens during compile
[08:08] <jjohansen> could throw in qml compiles too then
[08:08] <ogra_> jjohansen, yeah, something like that
[08:08] <ogra_> so that the user knows what is going on
[08:11] <jjohansen> we need to speed the compile up
[08:11] <jjohansen> there are still some things that can be done there
[08:15] <Elleo> cwayne__: kalikiana has a fix for committing text from pre-edit, could you help testing it against your chinese passwords? https://bugs.launchpad.net/bugs/1324955
[08:21] <ogra_> jjohansen, even if we do .... there might be users that install 500 apps ...
[08:21] <jjohansen> ogra_: all the more reason to speed it up! Not arguing against having feedback though, that would be good too
[08:22] <ogra_> right, both is needed
[08:25] <popey> There are indeed users that install 500 apps
[08:25] <popey> ←
[08:26] <popey> alan@deep-thought:~$ adb shell sudo -u phablet click list | wc -l
[08:26] <popey> 369
[08:26] <popey> getting there
[08:26] <ogra_> heh, yeah
[08:27] <popey> bug 1334940 ☹
[08:28] <ogra_> funny ... for me it scans ... but doesnt scan all codecs it seems
[08:29] <ogra_> (it picks up the sintel movie, but not some commercial movie trailers that totem plays fine ootb)
[08:29] <popey> i see no videos on my device
[08:29] <popey> http://people.canonical.com/~alan/videos/
[08:29] <popey> all of those were ripped from youtube, h264 codec
[08:30] <popey> uh, wouldn't bother with the convergence brainstorm ones
[08:31]  * popey pokes davmor2 
[08:32] <ogra_> stgraber, ah, nevermind, worked now
[08:38] <seb128> mpt, hey, small question about your settings designs/mockup, some screens have items with grey bg, does it mean those are different widgets?
[08:38] <seb128> mpt, e.g https://wiki.ubuntu.com/AboutThisDevice?action=AttachFile&do=get&target=phone-about.annotated.png
[08:42] <mpt> seb128, I just do that to make clearer which parts are list items and which parts are separators
[08:42] <mpt> and which parts are just labels
[08:43] <seb128> mpt, ok, so they don't have different bg color in the implementation
[08:44] <mpt> seb128, yes, that’s poor visual design
[08:44] <mpt> I’ll talk about that with gventuri if he’s in today
[08:49] <seb128> mpt, thanks
[08:55] <seb128> mpt, small questions about https://wiki.ubuntu.com/Appearance#Phone ... should the sections that don't include the current background be collapsed by default?
[08:58] <mpt> seb128, exactly right. Added. https://wiki.ubuntu.com/Appearance?action=diff&rev2=19&rev1=18
[09:00] <popey> seb128: are you aware of a bug with system settings where it tells you that there's updates when you go back to the main screen, when there are no more because you just updated?
[09:02] <seb128> mpt, thanks, last one on that spec for now ... what should the "remove images..." button do? I guess open a dialog, but is that dialog described somewhere?
[09:03] <seb128> popey, bug #1325629?
[09:05] <popey> seb128: that'd be it! thanks
[09:05] <seb128> popey, yw, feel free to set it to confirmed!
[09:06] <popey> done
[09:06] <seb128> thanks
[09:17] <alf__> Elleo: https://code.launchpad.net/~afrantzis/unity-mir/fix-1332624-input-area/+merge/224768
[09:17] <alf__> Elleo: (FYI(
[09:18] <alf__> Elleo: I don't know if the change in input area surface placement (not at screen 0,0) also affects ubuntu-keyboard in other ways
[09:19] <alf__> Elleo: e.g., in void InputMethod::onVisibleRectChanged()
[09:20] <alf__> Elleo: besides sending the coords to applicationApiWrapper we notify the input host
[09:21] <alf__> Elleo: inputMethodHost()->setScreenRegion(QRegion(visibleRect)); and inputMethodHost()->setInputMethodArea(visibleRect, d->view);
[09:22] <alf__> Elleo: and since the new input area surface placement, visibleRect is effectively not in screen coordinates
[09:23] <alf__> Elleo: don't know what the above methods expect...
[09:24] <cpyarger> epi;d anyone be willing to help me generate a system image for a itopic maguro?
[09:25] <Elleo> alf__: will try to dig into what the input method host stuff does more today
[09:25] <cpyarger> Would* aand utopic. Sorry for my bad spelling, its been a late night
[09:26] <Elleo> alf__: has the placement actually changed then, rather than the interpretation of the results?
[09:27] <alf__> Elleo: the placement changed, so the "fullScreenItem" is actually not really fullscreen, it goes below the top bar
[09:27] <Elleo> alf__: that seemed to be the case in image 88 as well though
[09:27] <Elleo> at least that was also getting a size of 1222
[09:28] <alf__> Elleo: plus the interpretation changed (mir changed to use relative coords for input regions), and both of these combined created the issue
[09:28] <Elleo> ah, okay
[09:30] <alf__> Elleo: so my concerns about inputMethodHost() are independent of the mir coords change, only the new surface placement change
[09:31] <Elleo> alf__: right, I'll try to figure out exactly what maliit framework does with those later today and get back to you
[09:32] <Elleo> alf__: any idea when the placement changed?
[09:32] <alf__> Elleo: I think the placement is handler by unity-mir, let me check
[09:39] <alf__> Elleo: hmm, it seems the placement change is quite old, at least a few months
[09:39] <alf__> Elleo: so I guess if the keyboard has been working all this time, there is no need to worry much. In any case, better check what the host expectations are, just to be sure
[09:39] <Elleo> alf__: yep, will do
[09:41] <Elleo> alf__: presumably we'll need to land a branch rolling back the keyboard positioning workaround alongside your unity-mir fix? Otherwise it'll end up requesting a slightly too large input area
[09:43] <alf__> Elleo: if the input area surface is actually at 0,0, then relative == absolute, so I think things should still work on the mir side
[09:43] <Elleo> alf__: good point
[09:44] <alf__> Elleo: but it would be good in any case to clarify what coord system each function expects along the path expects to avoid future confusion
[09:44] <Elleo> ah, but it isnt at 0,0 is it? doesn't your patch fix the conversion to relative coords rather than the positioning of it?
[09:45] <Elleo> the keyboard work around currently looks for a difference between the screen size and the item size and applies that to its coords
[09:46] <alf__> Elleo: right, I meant if we rolled back the keyboard positioning, I don't think we would need to change unity-mir again
[09:46] <alf__> Elleo: wait, I think we are talking about different workarounds
[09:46] <Elleo> yeah, I'm talking about the one that just landed in the keyboard
[09:46] <alf__> Elleo: I am talking about moving the surface back to 0,0 (which may not be possible)
[09:46] <alf__> Elleo: ah, ok, looking
[09:46] <Elleo> right
[09:48] <alf__> Elleo: ok, so the patch makes visibleRect really be in screen coords?
[09:49] <Elleo> the keyboard one is a bit of a hack, so I'd be happy to get rid of it, we jusy introduced it as a stopgap until we understood what had changed in mir/unity-mir
[09:49] <Elleo> alf__: yeah, but it makes assumptions about how its been offset, so its not great
[09:49] <Elleo> e.g. if we moved the top bar to the bottom, it'd break
[09:52] <alf__> Elleo: ok, although as discussed above, applicationApiWrapper expects relative coords, and I don't know about the input host.
[09:53] <alf__> Elleo: so to answer the origin question now that I have understood it: "presumably we'll need to land a branch rolling back the keyboard positioning workaround alongside your unity-mir fix" => yes
[09:54] <Elleo> alf__: okay, right, I'll get a branch ready for that then
[09:54] <alf__> Elleo: (but I don't know about the effects on input host)
[09:55] <Elleo> alf__: yeah, I'll investigate that, although it sounds like that should have been an issue before now if we were relying on it
[09:56] <Elleo> alf__: from my brief scan of the maliit docs yesterday it sounded like it was mostly there to let applications know what area to avoid putting content, but we handle that separately
[09:57] <Elleo> alf__: but I'll have a poke into that code and see whats really going on there
[09:57] <alf__> Elleo: sounds good then... I wonder if we can just remove the calls to avoid confusion?
[09:58] <Elleo> alf__: possibly, will look into it
[09:58] <alf__> Elleo: great, thanks!
[10:10] <rooted> i have a problem in Lubuntu arm version , cant find a printer control model.
[10:12] <rooted> any help please
[10:15] <Elleo> rooted: I think you might have better luck asking in either #ubuntu or #ubuntu-arm; this channel focuses on ubuntu touch, which is for mobile phones and is rather different from desktop ubuntu on arm
[10:16] <rooted> Elleo , true , but that what #ubuntu-arm said , i should come here
[10:18] <Elleo> rooted: not sure we can be much help I'm afraid; we don't even support printers at the moment (not sure if we ever will)
[10:19] <rooted> thanks
[10:19] <sil2100> oSoMoN: hello! Did you have a moment to look at the flaky failures in webbrowser-app that we're seeing?
[10:44] <oSoMoN> sil2100, I looked briefly at them, they look like random flakiness, and unrelated to recent browser changes in any way
[10:44] <oSoMoN> (sorry for the delay in answering, got a power outage here)
[10:48] <KalleEatingBrain> Hi there
[10:49] <KalleEatingBrain> Me and some other guy are working on a Port of UbuntuTouch for the Sony Xperia Z Ultra
[10:50] <KalleEatingBrain> But it feels like we are missing something during the setup already
[10:51] <KalleEatingBrain> Could anyone give me a statement wether or not the porting guide on the wiki is still usable?
[10:52] <KalleEatingBrain> It feels like it wasn't updated since 2013
[11:13] <jgdx> is tr("%n file", "%n files", n) not working currently?
[11:13] <k1l> anDixx: first make sure you are allowed to install other OS on your device.
[11:13] <anDixx> already
[11:13] <anDixx> ubuntu os on it
[11:13] <anDixx> its a full windows tab
[11:14] <anDixx> now i run ubuntu on it
[11:15] <k1l> ok, then see: http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[11:16] <anDixx> witch one
[11:16] <anDixx> my tablet is not android
[11:16] <anDixx> it is a fully windows 8.1 tablet
[11:16] <k1l> see if someone from the community already did a port or start a port yourself
[11:17] <KalleEatingBrain> Since it is a windows tab, youcould be able oto install full ubuntu
[11:17] <KalleEatingBrain> and run the Unity8 preview
[11:18] <KalleEatingBrain> but there is no way of running ubuntu-touch on x86 systems atm
[11:19] <anDixx> 64 bit?
[11:19] <KalleEatingBrain> same
[11:19] <KalleEatingBrain> prepare a normal ubuntu booot stick
[11:20] <KalleEatingBrain> go to windows settings
[11:20] <KalleEatingBrain> and disable all the uefi stuff
[11:20] <KalleEatingBrain> you know the drill
[11:20] <KalleEatingBrain> then you should change the boot order, to boot from a usb stick
[11:21] <KalleEatingBrain> if this all works and you end up with a working ubuntu
[11:21] <anDixx> ok i can boot with ubuntu already
[11:21] <anDixx> but hoz can i configure unity previeuw
[11:22] <bregma> anDixx, try the live image from http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
[11:23] <KalleEatingBrain> sudo apt-get install unity8-desktop-session-mir
[11:23] <bregma> or if you can boot with Ubuntu already, you can bring up a terminal and install unity8-desktop-session-mir
[11:23] <bregma> thet requires logging out then back in to the Unity 8 session
[11:24] <KalleEatingBrain> bregma, is the image you posted Unity8 default?
[11:24] <bregma> KalleEatingBrain, it's Unity 8 _only_
[11:25] <bregma> for the brave and adventurous
[11:25] <KalleEatingBrain> Nice
[11:26] <KalleEatingBrain> I'll give it a shot right now ;)
[11:26] <bregma> https://wiki.ubuntu.com/Unity8DesktopIso
[11:27]  * bregma inserts standard disclaimer about in-development systems here
[11:28] <KalleEatingBrain> I know
[11:29] <KalleEatingBrain> The main reason I am logged in here is for my port oto the son y xperia z ultra
[11:29] <KalleEatingBrain> but I am somewhat stuck
[11:29] <KalleEatingBrain> because I am not sure if the porting guide in the wiki still works
[11:30] <KalleEatingBrain> but i ca't find any other resources
[11:30] <KalleEatingBrain> It seems like everyone stopped porting UT to phones at some point lastyear
[11:38] <anDixx> can i install
[11:38] <anDixx> unity8
[11:38] <anDixx> like an os
[11:38] <anDixx> not like a session??
[11:39] <popey> anDixx: yes
[11:40] <anDixx> can you give me this link to install
[11:40] <popey> http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
[11:40] <popey> on a desktop, right?
[11:40] <anDixx> tablet with windows
[11:40] <popey> x86?
[11:41] <sergiusens> KalleEatingBrain: what is your specific problem?
[11:41] <anDixx> 64 bit
[11:41] <anDixx> on that tablet i already installed
[11:41] <anDixx> ubuntu
[11:41] <anDixx> 14
[11:42] <popey> ok, then that link should be useful
[11:43] <davmor2> popey: I didn't think there was an install option for the unity-next iso yet
[11:43] <anDixx> popey so the iso that i am downliding froom your link
[11:43] <anDixx> put this on usb and install it like new one?
[11:44] <popey> davmor2: see above link
[11:45] <davmor2> popey: no what I mean is it ran as a live desktop for me with no install option, it may of changed
[11:45] <dpm> mandel,  does the download api exist in qml yet? And if so, do we have docs for it?
[11:46] <popey> davmor2: it has ubiquity
[11:46] <davmor2> popey: I might need to grab a newer image and try it again then :)
[11:48] <popey> that iso boots to a login screen /cc seb128
[11:48] <seb128> popey, what video card/driver?
[11:48] <popey> virtualbox
[11:48] <seb128> Mir doesn't run on virtualbox
[11:48] <seb128> so unity8 fails to start
[11:48] <popey> ah of course
[11:48] <popey> bummer
[11:48] <seb128> you get bounced back to the greeter
[11:48] <popey> thanks
[11:49] <seb128> that's on the "known issues" if you read https://wiki.ubuntu.com/Unity8DesktopIso
[11:49] <seb128> "If the image boots to a greeter login, it's likely that the unity8 session fails to start (that's the case in VMs for example) "
[11:49] <seb128> yw!
[11:49] <bregma> read???  whatis read???
[11:49] <popey> i didnt read that because that wasn't where I got the link :þ
[11:50] <seb128> bregma, indeed yeah, we should replace the greeter by a "READ" screen in those cases ;-)
[11:50] <popey> http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ should link to that wiki page
[11:50] <Laney> I'll add that there
[11:50] <seb128> how do we do that?
[11:50] <seb128> Laney, thanks
[11:50] <bregma> interesting idea...  a fallback error-page greeter
[11:50] <seb128> how do you do it?
[11:50] <Laney> I think it's in cdimage
[11:51] <Laney> reporting error is part of the plan for lightdm afaik
[11:51] <seb128> bregma, joke aside, the greeter should mention an error in those cases, I discussed it a bit with robert_ancell
[11:51] <seb128> bregma, the issue is that there is no proper greeter<->session communication channel
[11:51] <seb128> like the greeter just get the exit code from the session
[11:51] <anDixx> popey: i am rebooting now your image
[11:51] <anDixx> need to install it on special way?
[11:52] <seb128> Laney, ^
[11:52] <popey> anDixx: what video card does your tablet have?
[11:52] <bregma> I was serious, I think it's a really good idea to have lightdm fall back to some sort of error-display greeter
[11:52] <anDixx> atom?
[11:52] <seb128> bregma, yeah, as said we need a way for the greeter to know why the session exited though
[11:52] <seb128> so we need to invent a protocol there
[11:52] <seb128> or document exit codes at least
[11:53] <anDixx> intel grafic media
[11:54] <bregma> anyway, yesterday I upgraded all the apps on my phone (stock Ubuntu on an N4) and now the Camera app whitescreens and the Gallery app dies immediately...  anyone else seeing these problems?
[11:54] <popey> anDixx: ok
[12:01] <Dazax> Hello
[12:01] <anDixx> popey:
[12:01] <anDixx> is tis a touch version?
[12:01] <anDixx> i didnt see difference?
[12:01] <Dazax> Somebody else can help me
[12:01] <popey> anDixx: it's unity-next (unity 8), was made by Laney / seb128 - they can probably answer questions
[12:01] <popey> Dazax: if you ask a question, sure.
[12:01] <Dazax> I would like to install ubuntu touch on a nexus maguro.. is it possible?
[12:02] <popey> Dazax: not anymore, no longer supported
[12:02] <Dazax> oh :(
[12:06] <sergiusens> Dazax: popey until someone in the community supports it ;-)
[12:06] <popey> indeed
[12:09] <Dazax> But, somes risks are presents for this? If I would like to use it
[12:27] <anDixx> popey:
[12:27] <anDixx> black screen when i login in
[12:27] <anDixx> ?
[12:34] <Laney> link got merged, guess it'll appear on cdimage next time an image is generated
[12:34] <popey> thanks Laney
[12:34] <Laney> kein problem señor
[12:41] <cwayne> Elleo: trying out that fix, keyboard's not showing up for me at all
[12:43] <Elleo> cwayne: is maliit-server running okay?
[12:44] <cwayne> Elleo: so i rebooted and it shows up fine now, but i'm still seeing the bug
[12:45] <Elleo> cwayne: probably best to discuss it with kalikiana, he's the one work working on it
[13:03] <jdstrand> popey: I'm fixing the mediascanner one now
[13:03] <popey> cool.
[13:06] <cwayne> mardy: ping
[13:30] <mardy> cwayne: pong
[13:31] <cwayne> mardy: hey, so you said the account-plugins-as-clicks isn't "completely" working yet?  what in specific isn't working? (asking in context of we have a lot of scopes planned for RTM that need account integration)
[13:34] <mardy> cwayne: plugins are not running in their own separate process, so allowing them now would bring a considerable security risk
[13:34] <mardy> cwayne: because for example, a fitbit plugin could manipulate the facebook one
[13:40] <cwayne> mardy: and that's specific to having them click-packaged?
[13:42] <mardy> cwayne: not technically, but since click packages can be downloaded from the store, and we want the store to only contain safe stuff, we cannot put there something which could harm your device
[13:42] <mandel> dpm, yes, I spoke with mhall119 yesterday about it and we saw a small error in the docs generation that I need to fix
[13:44] <cwayne> mardy: so what do we need to do to get them running as a separate process?
[13:48] <mardy> cwayne: a lot of work, I have a branch (now bitrotting, I'm afraid) where I started working on it, but there's a lot to do
[13:48] <mardy> cwayne: it won't happen for the RTM
[13:49] <cwayne> so how are we going to ship account-plugins?
[13:50] <mardy> cwayne: you just cannot, they need to be installed as .deb packages in the image
[13:51] <cwayne> mardy: that's not good. we need to have account plugins for scopes
[13:51] <cwayne> and scopes are going to be click packaged
[13:52] <mardy> cwayne: I'm afraid you'll have to limit the scopes to use the account types already available on the image :-(
[13:53] <mardy> cwayne: or you talk to dbarth and try to find a solution -- it might not be an impossible target, but it's certainly very risky
[13:54] <cwayne> we at least need to be able to have them shipped int he custom tarball, maybe we have them not available in the store though
[13:56] <mardy> cwayne: then it's fine: if that's code that we trust, we can definitely ship it as debs in the tarball
[13:56] <mardy> cwayne: or even not as debs
[13:56] <cwayne> mardy: we can't ship debs
[13:56] <cwayne> but basically, as long as the click hooks themselves are still there, we should be fine
[13:56] <mardy> cwayne: yes, that shouldn't be a problem
[13:56] <cwayne> not having them available in the store is another thing
[13:57] <cwayne> okay, that should be at least a temporary solution until we can get stuff in the store
[13:57] <cwayne> whew, crisis averted :)
[13:59] <mardy> :-D
[14:08] <cwayne> mardy: but just to be 100% clear then, account-plugins as clicks does functionally work in the images now then
[14:13] <cwayne> niemeyer: just a heads up, the setup.sh script for go-qml should call ubuntu-app-launch now instead of upstart-app-launch
[14:13] <niemeyer> cwayne: Thanks for the note
[14:15] <cwayne> niemeyer: np, thank you for go-qml :)
[14:16] <Elleo> alf__: dug into the maliit framework a bit more; basically on other platforms besides mir (X or Wayland) it'd be using those values for what we're doing with the UbuntuApplicationWrapper there
[14:17] <Elleo> alf__: so ideally I think we should be moving the UbuntuApplicationWrapper stuff into maliit framework to make it accessible to any keyboard plugins that want to use it
[14:18] <Elleo> alf__: so as far as this bug goes those values aren't influencing anything except on platforms other than Mir (which wouldn't have unity-mir changing the position, so would be okay anyway)
[14:18] <Elleo> alf__: not that I think we actually support anything other than Mir with the ubuntu-keyboard plugin due to that UbuntuApplicationWrapper bit being embedded in the plugin rather than the framework
[14:19] <nik90> fginther: ping
[14:20] <Elleo> alf__: I'll bring up refactoring that to better match the maliit structure when bfiller gets back, I'm guessing it won't be a high priority but at least it shouldn't effect your patch to unity-mir in any way
[14:20] <seb128> do we have a way to tell if we are on a phone or another device?
[14:22] <cwayne> MacSlow: ping
[14:22] <alf__> Elleo: great, just keep in mind that unity-mir currently needs surface relative coordinates, although I think this is something we could change if needed
[14:24] <MacSlow> cwayne, yup
[14:24] <cwayne> mhall119: hiya, any chance we can get this looked at? https://bugs.launchpad.net/ubuntudeveloperportal/+bug/1328559
[14:25] <MacSlow> cwayne, ?
[14:25] <cwayne> MacSlow: hey, i was looking into how to customize the boot animation for the custom tarball, would i be able to just drop a new png as spinner-logo.png, or would it be more involved?
[14:26] <MacSlow> cwayne, if you disregard any correct sizing just changing the loaded PNG would be enough...
[14:26] <fginther> nik90, pong
[14:26] <mhall119> cwayne: is that an actual framework?
[14:26] <cwayne> mhall119: not that I know of
[14:27] <nik90> fginther: hey, can you start automatic jenkins merges on lp:ubuntu-clock-app/reboot MPs
[14:27] <nik90> fginther: currently it is only enabled for lp:ubuntu-clock-app
[14:27] <cwayne> i think it's supposed to be ubuntu-scope-network mhall119
[14:27] <seb128> what's the consensus on rotation? should any app let its content rotate when the screen rotate (asking for settings)
[14:27] <cwayne> MacSlow: so if i make a png the same size it should definitely work then?
[14:27] <MacSlow> cwayne, if you don't change the size of the newer PNG you can just swap the file without having to touching the source... apart form a different filename of course
[14:27] <nik90> fginther: the new reboot branch is required for the new clock app for RTM
[14:27] <MacSlow> cwayne, correct
[14:27] <mhall119> cwayne: I don't think that's a click framework either
[14:28] <cwayne> MacSlow: does it need to be encoded any specific way or anything like that?
[14:28] <cwayne> mhall119: says it is here: http://developer.ubuntu.com/api/scopes/sdk-14.04/index/
[14:28] <MacSlow> cwayne, usual rgba (8 bit/channel)
[14:29] <mhall119> ah those docs are from mhr3
[14:29] <cwayne> MacSlow: okay, thanks.  I'll try it out and see if I can get it working, thanks
[14:29] <MacSlow> cwayne, but remember there are two files involved... one is the logo itself... the other one is the outter glow
[14:30] <mhall119> cwayne: I'm out at the moment, will check into it more when I get back
[14:30] <cwayne> mhall119: thanks!
[14:30] <cwayne> MacSlow: ah, okay
[14:30] <cwayne> i don't suppose i can just remove the outer glow?
[14:30] <fginther> nik90, what is the reboot branch?
[14:31] <nik90> fginther: at the malta sprint, we got a new design for clock app which required a rewrite. Hence we started a new fresh branch called the reboot branch for the clock app.
[14:31] <nik90> fginther: this reboot branch will host the new clock app that will ship with the RTM
[14:31] <Elleo> alf__: yep, sure
[14:32] <nik90> fginther: it is still at early stages, so we just need jenkins to do automatic merges since we dont have AP tests yet
[14:32] <MacSlow> cwayne, usual rgba (8 bit/channel)
[14:33] <fginther> nik90, ok, I understand now, just send me the branch name and we'll get it setup
[14:33] <nik90> fginther: lp:~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0
[14:34] <nik90> fginther: https://launchpad.net/ubuntu-clock-app/reboot
[14:35] <fginther> nik90, thanks
[14:37] <beuno> cjwatson, lool, jdstrand, should I deprecate ubuntu-sdk-14.10-dev1 now that ubuntu-sdk-14.10-dev2 has been enabled?
[14:37]  * cjwatson disclaims knowledge
[14:39] <jdstrand> I'm not sure. I don't think we have established policy for that
[14:50] <keoskes> hello. i can install Ubuntu Touch to the PC?
[14:50] <Laney> cjwatson: is there a discription of the JSON returned by `click list --manifest' somewhere?
[14:50] <Laney> description*
[14:52] <lool> beuno: I've marked it as deprecated in  ttps://docs.google.com/a/canonical.com/spreadsheets/d/1t_JGpg4r8BLluzfzmqa-gAbcKUjKUOufSCTSdPpFc5g/edit?pli=1#gid=0
[14:52] <lool> beuno: there should be no reason to use -dev1 in updated click packages, and while we wont drop it outright, packages using it might already be broken (or not) and ought to move to -dev2 ASAP
[14:53] <beuno> lool, ack, I'll mark it as such so our review scripts reject it from today
[14:54] <cwayne> mterry: pingerino
[14:55] <mterry> cwayne, pongadong
[14:55] <cwayne> mterry: heya, so i've now got a binary for a customized spinner, how do i go about getting it setup to be used
[14:55] <cwayne> i'd need a special lightdm conf, right?
[14:56] <cwayne> which may or may not go into XDG_DATA_DIRS?
[14:56] <mterry> cwayne, OK, yeah.  This is slightly convoluted.  Drop a custom conf in /etc/lightdm/lightdm.conf that points at a custom script (see /usr/share/lightdm/lightdm.conf.d/52-*.conf for an example)
[14:56] <beuno> thanks lool
[14:56] <mterry> cwayne, this custom unity-system-compositor script will call USC with a different --spinner arg
[14:56] <cwayne> mterry: i can't touch anything outside of /custom
[14:57] <mterry> cwayne, see /usr/share/ubuntu-touch-setting/usc-wrapper for an example
[14:57] <mterry> cwayne, sorry, drop it in /custom
[14:57] <mterry> cwayne, I forgot.  We search XDG_DATA_DIRS
[14:57] <cwayne> ah okay
[14:57] <cjwatson> Laney: https://click.readthedocs.org/en/latest/file-format.html#control-area ?
[14:57] <cwayne> do i need like a lightdm dir inside of XDG_DATA_DIRS
[14:57] <mterry> cwayne, yeah...  /custom/lightdm/lightdm.conf.d/ I believe
[14:58] <Laney> cjwatson: I'm wondering what the constraints are on the keys of the 'hooks' dict
[14:58] <mterry> cwayne, the output from lightdm will tell you if it's picking that up (see /var/log/lightdm/lightdm.log)
[14:58] <lool> dholbach: did you end up noting the framework addition process somewhere? if so, I would add the deprecation of older -dev frameworks
[14:58] <cwayne> hm, okau
[14:58] <cjwatson> Laney: https://click.readthedocs.org/en/latest/hooks.html "this must be a dictionary mapping application names to hook sets" ?
[14:58] <cwayne> this does seem like it's gonna be a bit conoluted
[14:59] <dholbach> lool, no, I just filed a bug
[14:59] <Laney> cjwatson: what's an application name?
[14:59] <Laney> In practice they seem seem quite varied
[14:59] <Laney> Basically I'm wondering if I can apply any logic here or if I should just walk it to find a desktop file
[15:00] <cjwatson> Laney: as far as the name format goes it's defined in hooks.html, sixth bullet under "Specification"
[15:01] <cjwatson> Laney: if you need a displayable name though you should indeed walk it and find a desktop file
[15:01] <cjwatson> Laney: click_find_package_directory should help
[15:02] <Laney> e.g. "zBird" has hooks: "zFlappy" → stuff
[15:02] <cjwatson> Or click_user_get_path if you only have the package name in hand
[15:02] <cjwatson> Laney: Right, nothing to say the app name must match the package name
[15:03] <cjwatson> Laney: You should probably walk to the "desktop" hook if that's the type of thing you care about
[15:03] <Laney> Yeah
[15:03] <Laney> Could there be multiple desktop hooks?
[15:04] <Laney> I guess so, if you install multiple desktop files
[15:04] <Laney> hmm
[15:05] <cwayne> mterry: how do i make sure that it uses my custom one? is there some setting that sets the default lightdm conf to use?
[15:06] <mterry> cwayne, there is an order of precedence.  If you set a key it will override that key in previous confs
[15:06] <mterry> cwayne, order should be clear from lightdm.log
[15:07] <cwayne> mterry: hm, no mention of /custom in lightdm.log
[15:07] <mterry> cwayne, ok...  where is XDG_DATA_DIRS set?
[15:08] <cwayne> ah wait, i messed up, lemme reboot
[15:11] <cwayne> mterry: hm still no dice.  XDG_DATA_DIRS is setup from an upstart job, perhaps its not being set yet
[15:15] <cwayne> mterry: specifically its set in /usr/share/upstart/sessions/custom-env.conf
[15:15] <mterry> cwayne, ah...
[15:15] <mterry> cwayne, that's a session job.  Lightdm is a system job
[15:16] <cwayne> agh crap
[15:31] <cwayne> mterry: any idea what we should do?
[15:37] <mterry> cwayne, there needs to be a system version of custom-env.conf
[15:39] <dpm> rsalveti, can I create emulator instances for either i386 and amd64?
[15:40] <charles> nik90, I've got the DBus properties code ready for you now in a branch at bug #1318997
[16:17] <kaisoz> hi!
[16:28] <nik90> charles: damn you are fast!
[16:29] <nik90> charles: is there a way I can find out the getter and setter function call names to use that in the clock app?
[16:30] <charles> nik90, tedg had a nice suggestion on how to address the containment concerns and still use fdo Properties, I put them in their own interface (com.canonical.indicator.datetime.AlarmProperties) in their own object path
[16:31] <tedg> charles, We'll need to talk to jdstrand to ensure those get added to the sdk apparmor profile.
[16:31] <charles> so client code can subscribe to property changes on the alarm settings just as they can on any other fdo property
[16:31] <charles> tedg, right
[16:33] <charles> nik90, it'll make way more sense if you install an update of indicator-datetime (which isn't silo'ed yet afaik, but I'm hoping to needle tedg into doing that today), then run d-feet and look at com.canonical.indicator.datetime on the session bus
[16:36] <cjwatson> Laney: There can be one per app and multiple apps per package, yes
[16:36] <charles> nik90, so the getters and setters are named "Get" and "Set", where you specify the dbus interface (com.canonical.indicator.datetime.AlarmProperties) and the property name (which are listed at http://bazaar.launchpad.net/~charlesk/indicator-datetime/lp-1318997-export-properties-to-dbus/view/head:/data/com.canonical.indicator.datetime.AlarmProperties.xml)
[16:37] <kaisoz> I got a question. I would like to start contributing to Ubuntu touch but I don't have a nexus device. Do all you devs use a Nexus device for developing?
[16:37] <kaisoz> Is it enough with a porting to other device?
[16:38] <charles> kaisoz, you can do a lot of development with the emulator, see http://developer.ubuntu.com/apps/sdk/tutorials/using-the-ubuntu-emulator/
[16:39] <kaisoz> nice!
[16:40] <kaisoz> I mean not working in apps but the system itself
[16:40] <kaisoz> I could build images for the emulator and test them there right?
[16:40] <nik90> charles: ok
[16:41] <nik90> charles: fdo?
[16:42] <charles> freedesktop.org
[16:42] <nik90> charles: oh nice you added the default volume to the .xml as well..cool
[16:43] <charles> nik90, http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties has the details on the getters/setters
[16:44] <charles> and the PropertyChanged signal, which you can use if you want the clock app listen for changes and update its gui
[16:45] <nik90> charles: in qml, that is as easy as "onPropertyChanged: dosomething"...not sure iin a  c++ plugin
[16:45] <nik90> charles: I will look at the examples that dednick gave me and see how this turns up
[16:47] <nik90> charles: although looking at http://bazaar.launchpad.net/~phablet-team/telephony-service/trunk/view/head:/libtelephonyservice/callmanager.cpp, it seems that i can just copy their setDBusProperty(const QString &name, const QVariant &value) function
[16:48] <charles> nik90, yep; you'll also want the getProperties()
[16:48] <jdstrand> charles: are those ready to be added today?
[16:48] <kaisoz> i tought about porting ubuntu touch to my Galaxy Note 2. I know there some work already done, but afaik is an incomplete image
[16:49] <kaisoz> but if I could work directly with the emulator I could start from there
[16:49] <charles> jdstrand, tedg approved the MRs but they haven't been siloed yet
[16:49] <charles> jdstrand, there's nothing they're blocking on though
[16:50] <charles> jdstrand, that is, shorter answer: "yes"
[16:52] <jdstrand> charles: ok. I wasn't super clear. I am planning an apparmor-easyprof-ubuntu upload today for something else. do you have DBus apparmor policy for me to add?
[16:53] <charles> jdstrand, sure: I'm not sure what info you need, but everything that clock-app will access is on busname com.canonical.indicator.datetime, object path /com/canonical/indicator/datetime/AlarmProperties
[16:54] <charles> there's nothing else in that object path except for these things that the clock app will use
[16:56] <jdstrand> charles: so com.canonical.indicator.datetime is the interface?
[16:57] <jdstrand> charles: ack. I'll add a rule and we can finetune it if needed. this sounds perfect :)
[16:58] <charles> jdstrand, actually I made a separate interface just to make sure it was walled off from everything else, com.canonical.indicator.datetime.AlarmProperties
[16:58] <jdstrand> I see
[16:58] <jdstrand> cool
[17:00] <fginther> nik90, I've added the jobs for lp:~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.
[17:00] <fginther> 0
[17:00] <nik90> fginther: thnx :)
[17:01] <jhodapp> rsalveti: hey, are you still looking into the media playback issues atm?
[18:10] <AskUbuntu> Problem importing contacts from vcf file into Ubuntu Touch | http://askubuntu.com/q/488952
[18:18] <rsalveti> jhodapp: nops, got some other things to fix first
[18:19] <jhodapp> rsalveti: ok, planning to look at it again though?
[18:20] <rsalveti> at some point, yeah :-)
[18:20] <rsalveti> but might get just too busy because of the sprint next week
[18:20] <rsalveti> so better if you take a look instead (if you get the time)
[18:21] <jhodapp> rsalveti: yeah thought you might not, frustrating regression
[18:21] <jhodapp> I doubt I will be able to until I get audio recording working
[18:21] <rsalveti> right
[18:21] <rsalveti> might be a promotion blocker though =\
[18:22] <jhodapp> I know, it's bad
[18:22] <rsalveti> mterry: system-settings-wizard is crashing after it finishes, is that known?
[18:22] <rsalveti> just got a crash file with image 102
[18:23] <jhodapp> rsalveti:  I wish someone had caught it along the way, media clearly didn't get tested with some changes
[18:23] <rsalveti> yeah, too many moving parts now
[18:23] <jhodapp> exactly
[18:24] <jhodapp> rsalveti: makes me a little concerned that hardly anybody else tries out media
[18:25] <rsalveti> yeah
[18:25] <jhodapp> ahayzen: lol, you just missed rsalveti's reply :)
[18:26] <mterry> rsalveti, no
[18:26] <rsalveti> mterry: let me open a bug for it then
[18:27] <mterry> rsalveti, thanks
[18:28] <beuno> jdstrand, how would you feel of us going back to a static list on the reviewers tools, instead of getting it from the system?
[18:28] <beuno> jdstrand, to further isolate the scripts
[18:28] <jdstrand> beuno: that is the plan
[18:28] <jdstrand> I have a todo to do it
[18:28] <beuno> jdstrand, I have a branch then!
[18:28] <beuno> spicing up the tests
[18:29] <jdstrand> I'm not going to be able to review it today and am off next week
[18:29] <jdstrand> but there are two things I'd like to have in there
[18:29] <jdstrand> the frameworks and the security policy
[18:29]  * beuno nods
[18:29] <jdstrand> I don't think you need to do both
[18:29] <beuno> k
[18:29] <jdstrand> I have ideas on how to pull off the security bits
[18:30] <beuno> I have the frameworks nicely layed out
[18:30] <beuno> with the state of each
[18:30] <beuno> building lists we can check, etc
[18:30] <beuno> I'll throw it at dholbach on Mon
[18:30] <jdstrand> sounds great
[18:30] <jdstrand> make sure he knows that I need to do my part too before it is decoupled from the system
[18:31] <beuno> will do
[18:31] <jdstrand> (he has wanted to backport the review tools to trusty-- I know he will ask if he can with your branch. he can't)
[18:31] <jdstrand> beuno: thanks for doing that :)
[18:32] <beuno> I'll make sure he knows
[18:32] <beuno> maybe taunt him a bit
[18:32] <jdstrand> hehe
[18:32] <beuno> I wasn't intending to do this, but was too annoyed by how this was all scattered in the code
[18:32] <beuno> I should be writing up a document
[18:32] <beuno> so this is my procrastination
[18:32] <jdstrand> I think I can pull of the security tests without needing a change to easyprof
[18:32] <jdstrand> s/pull of/pull off/
[18:33] <jdstrand> so I'll look into that when I get back from holiday
[18:33] <beuno> sounds great
[18:33] <jdstrand> (there a quite a few other checks I want to add too-- these things pile up!)
[18:33] <jdstrand> several new hooks were added that we can verify
[18:34] <beuno> nice!
[18:34] <beuno> getting there
[18:34] <jdstrand> yep
[18:37] <rsalveti> mterry: nah, crash (core) is truncated
[18:38] <mterry> :(
[18:38] <rsalveti> mterry: how to make it run again on a following reboot?
[18:38] <rsalveti> can try to attach gdb
[18:38] <mterry> rsalveti, phablet-config welcome-wizard --enable
[18:39] <rsalveti> thanks
[18:54] <beuno> tedg, gatox, I hear you're trying to break the store.
[18:55]  * beuno leaves https://code.launchpad.net/~beuno/click-reviewers-tools/deprecate-14-10-dev1/+merge/224887 close to jdstrand in case he happens to look
[18:55] <beuno> tedg, gatox, alecu, so what's the plan with this payui?
[18:57] <tedg> beuno, To break the store :-)
[18:57] <beuno> tedg, gatox, alecu, we're landing support for scopes in the store
[18:57] <beuno> we could add in a third type
[18:58] <tedg> beuno, Long term it's not really a "store" thing, but apparently that's how clicks get on the image.
[18:58] <beuno> "system libraries" or whatever
[18:58] <tedg> beuno, Yeah, that'd work.
[18:58] <beuno> which you can filter off
[18:58] <tedg> Long term we don't expect it to have an "application" but be a "pay-ui" hook.
[18:58] <beuno> we'd need to be able to specify them in the manifest somehow
[18:58] <beuno> so the scanner and distinguish them
[18:59] <tedg> We're planning on doing that with them not having an application hook.
[18:59] <tedg> Sorry, "desktop"
[19:00] <tedg> So instead of "desktop" there would be "pay-ui"
[19:00] <beuno> tedg, so lack of desktop hook would indicate a system library
[19:00] <beuno> ?
[19:00] <tedg> beuno, Well, kinda. You guys probably need more categories :-)
[19:01] <tedg> beuno, For instance not just "desktop", you could have a package that was only a content-hub source.
[19:01] <tedg> Or a scope
[19:01] <tedg> Or infographic visualization
[19:01] <beuno> right
[19:01] <beuno> I'd like a specific entry that signals it's a system library
[19:01] <tedg> Not sure if you want to whitelist or blacklist there.
[19:01] <beuno> and we'll add the 3rd type
[19:01] <beuno> which you can filter off in the client
[19:02]  * cwayne just submittied his first go+qml app to the store :D
[19:02] <tedg> beuno, Yeah, not sure where that should be in the manifest though.
[19:02] <tedg> Seems like hooks isn't a good place.
[19:04] <beuno> tedg, "somewhere click-ish we can introspect"
[19:04] <beuno> :)
[19:04] <beuno> and since we're already doing it one way for scopes
[19:04] <beuno> it would be nicer to do the same for this
[19:04] <beuno> and we can do it cheaply
[19:04] <beuno> and less hacky
[19:04] <beuno> I hear rumours the plan is to > /dev/null hardcoded on the client
[19:05] <tedg> Heh, no one cares about pay until they can do in-app purchases.
[19:06] <beuno> I care!
[19:06] <beuno> but also, this is a good opportunity to support non-UI clicks
[19:06] <tedg> So anything that is a good that doesn't have a handler, will just get ignored on the client.
[19:06] <tedg> Wow, anything that is a hook.
[19:07] <beuno> such friday
[19:07] <tedg> In general, I don't have a perfect solution.
[19:07] <beuno> tedg, but you don't know that beforehand unless click index knows that
[19:07] <tedg> Probably something like "system-component" and then point that to a json file.
[19:08] <tedg> Throw it on the appstore list and see if there are other things people want to use it for.
[19:08] <beuno> right
[19:08] <beuno> so
[19:08] <beuno> if you get that sorted
[19:09] <beuno> we'll add this third type to the store
[19:09] <beuno> and automatically scan and set it
[19:09] <alecu> tedg: beuno: I stil think it's pointless to have pay-ui in the store. It's something that can't be chosen to be installed, will be filtered out from search results in the store, will be filtered out from displaying on the client, and will not make sense to update independently of system updates because it depends on libpay.
[19:09] <beuno> and you can filter like everything else
[19:09] <beuno> alecu, oh, I agree
[19:09] <beuno> I started this assuming that wasn't an option
[19:09] <tedg> alecu, It doesn't depend on libpay, we could update it independent of system image.
[19:10] <alecu> beuno: according to sergiusens, thostr asked to have every click shipped on the device be on the store. Which made sense at the time.
[19:11] <alecu> beuno: and that's why "pay-ui must be in the store". Which I think makes no sense.
[19:11] <sergiusens> another option is to have it in a customization spin
[19:11] <beuno> I agree
[19:11] <alecu> sergiusens: I don't know what that means, but I agree :-)
[19:12] <beuno> so
[19:12] <beuno> if it's blocking you
[19:12] <sergiusens> alecu: https://wiki.ubuntu.com/Touch/Customization
[19:12] <beuno> I'd say just upload it to the store, it'll be visible for a bit, but whatever
[19:12] <beuno> you can then either pull it
[19:12] <beuno> do something else
[19:12] <beuno> or we'll have support for system library types
[19:12] <beuno> which you can filter off in the scope
[19:13] <beuno> * as long as you specify this new type in the manifest, etc etc
[19:13] <tedg> I think that it's likely to end up on a customization image.
[19:14] <tedg> But I don't think that having things independently updatable is bad.
[19:14] <sergiusens> cwayne: ^^
[19:14] <sergiusens> cwayne: some Friday reading for you
[19:14] <tedg> It allows for things like the service to be able to change URLs faster.
[19:15] <cwayne> the customiztions docs are here now: http://developer.ubuntu.com/resources/oem/
[19:15] <tedg> Or if we did something like integrate with a payment service, and then that service dropped support, we could clean it up quickly.
[19:17] <alecu> tedg: I think those are valid points, but are cases that happen very rarely.
[19:17] <rsalveti> mterry: bug 1335298
[19:18] <mterry> rsalveti, thanks!
[19:37] <tedg> beuno, mail sent
[22:57] <ws-tek> I have a couple of questions about ubuntu touch.
[23:00] <ws-tek> Is it based on 14.04 LTS now? I am a little confused because of the way the site is set up. It doesnt seem there have been any improvements of making networking, telephony, and other features from like a year ago
[23:00] <ws-tek> https://wiki.ubuntu.com/Touch/ReleaseNotes
[23:05] <sarnold> wow, looks like that whole thing is quite old at this point
[23:05] <sarnold> ws-tek: ubuntu-touch was based on 14.04 for a little bit but has moved on to the devel release, the upcoming 14.10, weeks or months ago
[23:06] <ws-tek> Is there apart of the site where its tracking all the latest developments/bugs/features?
[23:10] <ws-tek> I could only find the bugs/fixes from 13.10
[23:22] <sarnold> ws-tek: look for the messages from the landing team here, e.g. https://lists.launchpad.net/ubuntu-phone/msg08796.html
[23:23] <ws-tek> thank you
[23:42] <WilsonB1> Has anyone  had success using multi-touch with touch screen on   Ubuntu/Kubuntu ? Im using an Asus X200MA
[23:42] <WilsonB1> The only thing I was able to use the multitouch on screen is Chromium Browser
[23:42] <WilsonB1> Wanted to assign guestures in ?Kubuntu