[08:20] <didrocks> hey mmrazik, how are you?
[10:37] <tsdgeos> Mirv: just tried new packages for https://bugs.launchpad.net/unity/+bug/1067357 and seems the whole feature has regressed?
[11:06] <Mirv> tsdgeos: I think you are right. the Unity menu or other texts don't seem to disappear at all?
[11:07] <tsdgeos> yeah, i've i'm on firefox and press alt+f1 i still have the firefox text, not the launcher texts in the panel
[11:07] <Mirv> tsdgeos: could you file a new bug about it? I guess it's anyway related to the commit touching those things. and we need to stop the SRU process for unity.
[11:07] <tsdgeos> a new bug? ok
[11:08] <Mirv> and we'd really need a autopilot testing if the text is shown
[11:09] <didrocks> mhr3: hey, do you know where the music store scope went?
[11:09] <didrocks> trying to find to what it was renamed :p
[11:09] <didrocks> pstolowski: knows as well maybe ^
[11:10] <didrocks> it has always been in the unity-lens-music?
[11:11] <pstolowski> didrocks: yes, it's in music lens
[11:11] <didrocks> pstolowski: ok, thanks :)
[11:11] <mhr3> right, ^^
[11:30] <Mirv> tsdgeos: after filing a bug, since you know the code you could maybe also work on fixing it? :)
[11:31] <tsdgeos> Mirv: to busy elsewhere, sorry :-/
[11:31] <Mirv> tsdgeos: ok
[11:31] <tsdgeos> actually afair i did a unittest
[11:31] <tsdgeos> that is either failing
[11:31] <tsdgeos> or is a bad unittest :D
[11:32]  * tsdgeos has a look at the bzr log and wonders what broke
[11:42] <Mirv> at least it didn't show up in our autopilot run as failing
[13:18] <Mirv> tsdgeos_: did you file the bug against unity?
[13:45] <mmrazik> didrocks: FYI -- the autopilot tests just started with the staging compiz and they seem to be running
[13:45] <didrocks> mmrazik: sweeeeetness! :)
[13:46] <didrocks> mmrazik: I'm trying to bootstrap the whole stack now to have the ~ubuntu-unity ready for autopilot running it
[13:49] <didrocks> popey: https://launchpadlibrarian.net/124506429/buildlog_ubuntu-raring-armhf.unity_6.12.0bzr2942pkg0raring0_FAILEDTOBUILD.txt.gz :(
[13:49] <didrocks> popey: maybe Mirv can have a look? Trying to get everything ready when we can release
[13:49] <didrocks> popey: or bregma
[13:49] <didrocks> hey bregma!
[13:50] <bregma> unh?
[13:50] <didrocks> bregma: in addition to that, did you have the time to look at http://pad.ubuntu.com/ubuntu-unity?
[13:50] <bregma> didrocks, it's on this morning's agenda
[13:50] <popey> didrocks, yeah, sure!
[13:50] <didrocks> bregma: thanks! people are getting anxious to have an unity release (I start to get a lot of pings…)
[13:51] <didrocks> bregma: so right now, it seems the only two blockers are the armhf issue and this pad
[13:51] <bregma> I've been avoiding pinging you myself so you could focus on getting it done
[13:52] <mmrazik> bregma: we also had some compiz issues. Due to a wrong version in changelog (that is fixed) we were running our tests with bzr version of unity but compiz was from daily ISO. Since yesterday we started to get crash dumps. It looks like there was an ABI breakage which wasn't handled properly in packaging..
[13:52]  * mmrazik is searching for the bug#
[13:52] <mmrazik> https://bugs.launchpad.net/compiz/+bug/1067585
[13:52] <bregma> saw the fix go through, didn;t know what it was for
[13:53] <mmrazik> bregma: the tests started few minutes back and it seems to be gone
[13:53] <mmrazik> but I guess we should bump some abi version somewhere
[13:54] <mmrazik> mhm... just looking at the bugreport and I'm not sure anymore how it is related :-/
[13:54] <didrocks> bregma: do yo uwant me doing it?
[13:54] <didrocks> bumping the compiz soname
[13:54] <mmrazik> srry. that must be a bogus bug
[13:55] <bregma> none of the compiz folk are around today (as far as I know), so could you please do the necessary?  I don't feel I have enough grasp on the problem to do the right thing at this point.
[13:55] <didrocks> bregma: no worry, doing it :)
[13:55] <didrocks> one secundo
[13:56] <didrocks> bregma: setting the ABI to today as we don't know when it was broken
[13:57] <bregma> yeah
[13:59] <didrocks> bregma: https://code.launchpad.net/~didrocks/compiz/bumpabi/+merge/137199
[13:59] <tsdgeos_> Mirv: oh, i thought your comment in the bug saying verification-failed was enough, want me to open it?
[14:02] <popey> tsdgeos_, yes please :)
[14:03] <didrocks> mmrazik: once that's merged we need an unity rebuild ^
[14:03] <didrocks> (or a fix for armfh merged!)
[14:03] <didrocks> :)
[14:05] <didrocks> pstolowski: mhr3: what is unity extra?
[14:06] <didrocks> something new that should be shipped by libunity-dev package?
[14:06] <tsdgeos_> Mirv: popey: https://bugs.launchpad.net/unity/+bug/1085045 not one of my best english literature though
[14:07] <popey> thanks tsdgeos_
[14:08] <Mirv> tsdgeos_: thanks!
[14:08] <Mirv> targeting 6.0
[14:13] <Mirv> bregma: regarding the ARM build failure, 2941 built successfully (only tests failed) in staging, in 2942 sil2100 modified a test like this http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2942
[14:15] <Mirv> and 2941 compiled the tests ok, only running some of those failed.
[14:16] <didrocks> Mirv: can you have a look, please? https://code.launchpad.net/~didrocks/dee/missingchangelog/+merge/137204
[14:16] <didrocks> (I'll have a bunch of those)
[14:16] <Mirv> didrocks: sure
[14:17] <Mirv> approved
[14:17] <didrocks> thanks
[14:18] <didrocks> Mirv: https://code.launchpad.net/~didrocks/libunity/add-missing-changelog/+merge/137205
[14:20] <Mirv> done
[14:25] <didrocks> Mirv: https://code.launchpad.net/~didrocks/unity-lens-music/updatepackage/+merge/137207
[14:29] <didrocks> Mirv: https://code.launchpad.net/~didrocks/unity-lens-photos/add-missing-changelog/+merge/137209
[14:32] <didrocks> Mirv: https://code.launchpad.net/~didrocks/unity-lens-shopping/update-package/+merge/137211
[14:32] <Mirv> 2*ok. need to soonish start leaving for evening's Mr. Bond, though, but still here
[14:32] <didrocks> Mirv: don't miss the last one :p
[14:32] <Mirv> for maybe 20mins
[14:33] <didrocks> sure, I'll bother popey I guess then! :)
[14:33] <popey> heh
[14:33] <Mirv> done too
[14:33] <didrocks> thanks Mirv ;)
[14:33] <popey> ohh, Bond, good idea!
[14:33]  * Mirv prints tickets :)
[14:34] <mhr3> didrocks, yes
[14:35] <didrocks> mhr3: should we just distribute it with libunity?
[14:35] <didrocks> like same binary package?
[14:35] <didrocks> (that's what is done currently)
[14:35] <didrocks> same, just one -dev
[14:36] <mhr3> yea, why not
[14:37] <mhr3> it deps on libunity itself anyway
[14:37] <didrocks> let's have them in the same package for now
[14:37] <Mirv> umm unity 2943 in staging had different error on armel about undefined reference in libicui18n.so.48.. https://launchpadlibrarian.net/124509377/buildlog_ubuntu-quantal-armel.unity_6.12.0bzr2943pkg0quantal0_FAILEDTOBUILD.txt.gz
[14:38] <Mirv> armhf still building at https://launchpad.net/~unity-team/+archive/staging/+build/4024562
[14:38] <pstolowski> didrocks: yes, that's fine (sorry, missed your question earlier)
[14:38] <didrocks> thanks mhr3 pstolowski :)
[14:46] <didrocks> popey: https://code.launchpad.net/~didrocks/unity-scope-gdrive/clean-package/+merge/137214
[14:49] <popey> k
[14:51] <popey> done
[14:52] <didrocks> thanks :)
[14:53] <popey> yw
[15:07] <mmrazik> fginther: so far we have been testing with old version of compiz in our job (due to packaging/versioning bug the compiz version in staging was lower than the one on daily iso)
[15:08] <mmrazik> fginther, didrocks: it looks like the fail rate popped up to ~10% (slightly more) with the newest compiz :-/
[15:08] <mmrazik> fginther: could you have a look on that, please?
[15:08] <didrocks> mmrazik: urgh
[15:08] <mmrazik> fginther: its build #50
[15:08] <mmrazik> 88 failures out of 876 tests
[15:08] <mmrazik> (intel seems to be just broken)
[15:10] <fginther> mmrazik, otp, check in a moment
[15:18] <mmrazik> fginther: didrocks: it seems to be the maximized window issue that popped up on nvidia for a while and then wasn't visible anymore (windows that are supposed to start as maximized are not)
[15:20] <bregma> hey folks, does an MP that's been merged but the PS Jenkins bot still says 'Pending' mean the automated mechanism has been manually bypassed?
[15:21] <mmrazik> bregma: no
[15:21] <didrocks> mmrazik: at least, if it's just one behavior failing…
[15:22] <mmrazik> bregma: at some point of time there was a discussion about not generating unnecessary e-mails
[15:22] <mmrazik> bregma: and if you Approve and everything goes well the ps-jenkins bot doesn't say Approved but merges right away
[15:22] <mmrazik> I think the "Pending" part is some left-over and probably a but
[15:22] <mmrazik> s/but/bug/
[15:23] <mmrazik> bregma: you should see the committer in bzr log if you want to double-check
[15:23] <mmrazik> bregma: if it says tarmac then it was jenkins doing the merge
[15:23] <bregma> right, makes sense, but it would be nice if there was a convenient link from the MP
[15:23] <mmrazik> didrocks, fginther: it looks like most of the new failures are panel tests
[15:24] <mmrazik> bregma: link to what?
[15:25] <didrocks> bregma: do you reproduce this issue with latest everything? ^
[15:27] <fginther> mmrazik, looking now
[15:27] <bregma> didrocks, which issue... the armhf failure?
[15:27]  * bregma is juggling too many balls at once
[15:27] <didrocks> bregma: the one mmrazik is discussing here
[15:27] <didrocks> mmrazik: https://code.launchpad.net/~didrocks/unity-lens-photos/add-missing-changelog/+merge/137209, is it stalled?
[15:28] <mmrazik> didrocks: looks like no autolanding configured..
[15:29] <mmrazik> didrocks: btw. have you seen the shopping lens failures?
[15:29] <mmrazik> didrocks: either because of raring vs quantal or the need of local ppa...
[15:29] <mmrazik> I as just looking into it
[15:29] <didrocks> mmrazik: I see those failures, seems that you don't have a dependency system
[15:29] <didrocks> oh?
[15:29] <didrocks> mmrazik: can you fix those? here is the list of failures:
[15:29] <didrocks> because of the same issue I guess
[15:29] <didrocks> so shopping
[15:30] <didrocks> https://code.launchpad.net/~didrocks/unity-lens-music/updatepackage/+merge/137207
[15:30] <fginther> ackk! no unity-lens-photos autolanding... I can fix that
[15:30] <mmrazik> fginther: I'm wondering if we can just add the local repo via a hook
[15:30] <mmrazik> fginther: given these are leaf packages and probably don't need the full mbs machinery
[15:31] <mmrazik> fginther: the same for shopping lens and lens-music
[15:31] <didrocks> mmrazik: is the drive issue the same? https://code.launchpad.net/~didrocks/unity-scope-gdrive/clean-package/+merge/137214
[15:31] <mmrazik> didrocks: nope
[15:31] <mmrazik> didrocks: looks like missing build dep to me
[15:32] <didrocks> I need to find this IP… :/
[15:32] <mmrazik> didrocks:  my guess is python-distutils-extra
[15:32] <fginther> mmrazik, a hook to the local repo should work
[15:32] <fginther> mmrazik, I'll get to work on it
[15:45] <mmrazik> fginther: fyi -- I'm taking care of the unity-scrope-gdrive issue
[15:49] <fginther> mmrazik, thanks
[15:52] <mvo> Trevinho: hi, sorry for naging, but could I ask for lp:~mvo/unity/sc-launcher-integration-fixes :)?
[15:58] <fginther> didrocks, https://code.launchpad.net/~didrocks/unity-lens-photos/add-missing-changelog/+merge/137209 merged
[15:58] <didrocks> fginther: thanks!
[16:00] <bregma> unity build 6.12.0bzr2943pkg0raring0 on armhf finished successfully, I think the previous failure may have been hardware (or transient ABI disconnect)
[16:04] <fginther> mmrazik, didrocks, I'm looking into those autopilot regressions, does appear to be a problem with maximizing a window
[16:05] <didrocks> fginther: keep me posted :)
[17:01] <didrocks> fginther: did you fix the dep issue for https://code.launchpad.net/~didrocks/unity-lens-music/updatepackage/+merge/137207 and https://code.launchpad.net/~didrocks/unity-lens-shopping/update-package/+merge/137211?
[17:02] <bobweaver> didrocks,  what is Jenkins ?
[17:03] <didrocks> bobweaver: what is merging the branches
[17:03] <bobweaver> it is a bot ?
[17:03] <didrocks> bobweaver: http://jenkins-ci.org/
[17:03] <bobweaver> thanks
[17:05] <bobweaver> didrocks,  do you know how to layer with nux ?
[17:05] <fginther> didrocks, sorry, I didn't see that. I'm looking at it now
[17:05] <didrocks> bobweaver: not really, I didn't touch nux for 1 year and half now :)
[17:05] <didrocks> fginther: oh? I thought mmrazik was on it, but as he wasn't around :) Thanks!
[17:05] <bobweaver> didrocks,  dang thanks for responding though
[19:19] <Trevinho> mvo: I'll look to that, no worries
[19:20] <bobweaver> no meeting ?
[19:20] <bobweaver> oh it is invite only
[21:10] <bobweaver> How to make it so that the layout in nux is telling the lens_bar_  to be on the right ?    *.cpp >> http://paste.ubuntu.com/1400581/      *.h   http://paste.ubuntu.com/1400583/
[21:10] <bobweaver> I want it on the left
[21:12] <bobweaver> http://imagebin.org/237726
[21:12] <bobweaver> screen shot ^^
[21:13] <bobweaver> I tried changing the minor and major axis but it still stays to the left . I tryed to put in other layout_ model , that also did not work out. Must be my code ?
[22:31] <bobweaver> Ok for real then no one will even look ?
[22:31] <bobweaver> how about this the most simple effing thing to do in any widget lib  add a background
[22:32] <bobweaver> can do that either
[22:32] <bobweaver>   //adding background Have I told you that this is the hardest widget lib ever ?
[22:32] <bobweaver>   nux::Image* background = NULL;
[22:32] <bobweaver>   nux::Layout* backgroundimg()
[22:32] <bobweaver>   {
[22:32] <bobweaver>   nux::VLayout* layout = new nux::VLayout(NUX_TRACKER_LOCATION);
[22:32] <bobweaver>   background = new nux::Image(NUX_TRACKER_LOCATION);
[22:32] <bobweaver>   {
[22:32] <bobweaver>   nux::Image *image = new nux::Image();
[22:32] <bobweaver>   image->LoadImageFile(PKGDATADIR"dash/ff-tv/tvbk.png");
[22:32] <bobweaver> /         background->SetLayoutType(nux::Button::HORIZONTAL);
[22:32] <bobweaver> /         background->SetDistribution(nux::Button::CENTER_OF_LAYOUT);
[22:32] <bobweaver> /         background->SetSpaceBetweenItems(0);
[22:32] <bobweaver> /         background->SetImage(image);
[22:32] <bobweaver>          image->UnReference();
[22:32] <bobweaver>          layout->AddView(background, 1, nux::MINOR_POSITION_CENTER, nux::MINOR_SIZE_FULL);
[22:32] <bobweaver>   }
[22:32] <bobweaver> }
[22:32] <bobweaver>   
[22:32] <bobweaver> dont work
[22:36] <bobweaver> I am going to loose it
[22:37] <bschaefer> bobweaver, hmm sorry, a lot of people are off already
[22:37] <bschaefer> bobweaver, a good place for examples is: bzr branch lp:nuxplayground
[22:37] <bobweaver> tried that what has changed in 3.0 to 4.0 ?
[22:37] <bschaefer> nothing, just the number
[22:38] <bobweaver> I mean it should not be this hard at all to get a bkg image to show up
[22:38] <bschaefer> no it shouldn't...hmm what does it do?
[22:38] <bschaefer> compile error?
[22:38] <bobweaver> yeah
[22:38] <bschaefer> what is it yelling about?
[22:39] <bobweaver> select layout type is not a not a class type
[22:39] <bobweaver> also says that bakgreoundimg can not be declared in scope thpough it is
[22:40] <bobweaver> can not find  function LoadImageFile
[22:40] <bobweaver> the list goes on and on
[22:40] <bschaefer> hmm can I see the file in a pastebin?
[22:41] <bobweaver> all I want to do is add a background image.  sure I will pastebinit
[22:41] <bschaefer> thanks, sometimes getting the headers right in nux is ... odd
[22:42] <bobweaver> thanks for your help bschaefer  it mean alot to me
[22:42] <bschaefer> no problem
[22:42] <bschaefer> hopefully I can help out :)
[22:42] <bobweaver>  *.cpp  >> http://paste.ubuntu.com/1400763/
[22:43] <bobweaver>  *.h >> http://paste.ubuntu.com/1400766/
[22:43] <bschaefer> hmm that is a large file, so you're trying to add an image to the Dash?
[22:44] <bobweaver> Branch  >> https://code.launchpad.net/~ubuntu-tv-developers/ubuntutv/trunk
[22:44] <bobweaver> yeah well I made new binary in cmake to make 2 dashs
[22:44] <bobweaver> one for TV and one for well unity the og onee
[22:45] <bobweaver> dash/ff-tv/*
[22:45] <bobweaver> bschaefer,  I am trying to add the image that was used in unity 2d for the background of the tv
[22:45] <bobweaver> I will push branch to what I have
[22:45] <bschaefer> bobweaver, hmm c++ code doesn't seem to be valid...
[22:46] <bschaefer> line 124
[22:46] <bschaefer> in the diff...
[22:46] <bschaefer> do you want it to be part of the ctor?
[22:46] <bobweaver> what is ctor ?
[22:46] <bobweaver> sorry I am new
[22:47] <bobweaver> Oh NM
[22:47] <bschaefer> constructor
[22:47] <bschaefer> as on line 124, that is the closing bracket, then you have your stuff
[22:48] <bschaefer> sorry, im trying to read it, soo yeah have a function called: backgroundimg?
[22:48] <bschaefer> but that isn't apart of the DashLayout class
[22:50] <bschaefer> and does PKGDATADIR get set to anything?
[22:51] <bschaefer> to test that you can just drop PKGDATADIR from that call, because load images takes
[22:52] <bschaefer> void LoadImageFile(const std::string &filename);
[22:52] <bobweaver> ont sure I am super new to nux just following example on playground
[22:52] <bschaefer> yeah, the PKGDATADIR gets set in the make files n playground
[22:53] <bschaefer> i bet if you droped that it wouldn't yell at that any more
[22:56] <bobweaver> I must fix returning non-void [-Werror=return-type]
[22:58] <bschaefer> well look at your function
[22:58] <bschaefer> nux::Layout* backgroundimg()
[22:58] <bschaefer> you are returning a nux::Layout*
[22:58] <bschaefer> if you don't want to just do
[22:58] <bschaefer> void backgroundimg()
[23:03] <bobweaver> thanks
[23:07] <bobweaver> bschaefer, is there any way what so ever that I can get a example from you ?  I know that it is alot to ask but I am thinking about drooping everything that I am doing with this because it is so hard
[23:08] <bschaefer> bobweaver, hmm an example on what?
[23:08] <bobweaver> maybe I am not putting things together but boy was qml qt alot easier to work with. I am sure that I will get this just going to take some time and I do not know if I have that
[23:09] <bschaefer> bobweaver, overall, im quite busy working on unity stuff but there is a bunch of examples through out nux/unity on how to use nux
[23:09] <bobweaver> NM bschaefer  BUT thanks a bunch for trying to help me out but I am a failure sorry to waste your time. I give up have fun making something.
[23:09] <bschaefer> nux is hard ...
[23:09] <bschaefer> but it is very powerful
[23:10] <bobweaver> again thanks for trying to help
[23:10] <bschaefer> bobweaver, it takes a while to learn things, dont give up completely :)
[23:10] <bschaefer> focus on the foundations of c and c++, if you weren't sure what:  fix returning non-void [-Werror=return-type]
[23:11] <bschaefer> was, then I would say c++ is what you should be learning, not nux
[23:11]  * bschaefer still doesn't understand nux 100%
[23:14] <bobweaver> no I understand C++ not the best I am average. I understand abut the c99 but I need to learn more. should have went to school for CS
[23:14] <bobweaver> back to the drawing board
[23:15] <bobweaver> thanks again