[04:31] <Mirv> morning, unity8 fails to build https://bugs.launchpad.net/unity8/+bug/1215737
[04:32] <Mirv> + bug #1215739 for unity-mir
[04:46] <Mirv> Saviq: ^ I guess I should highlight you still today :)
[06:31] <ricotz> Trevinho, hi :), http://paste.debian.net/plain/28852 prevents a glib bump on 2.34
[07:03] <tsdgeos> hmmm
[07:04] <tsdgeos> didn't we do those "build stacks" that prevented things in the lower layer to break things in the upper one?
[07:22] <Saviq> Mirv, thanks :)
[07:26] <Saviq> jeeez wth is happening :/
[07:26] <tsdgeos> unity changed below our feet
[07:26] <tsdgeos> https://code.launchpad.net/~mzanetti/unity8/launcher-add-setUser/+merge/181639 is supposed to fix it
[07:27] <tsdgeos> but can't get past running the tests on the devices it seems
[07:27] <tsdgeos> is that new?
[07:27] <Saviq> yeah http://s-jenkins:8080/job/generic-mediumtests-runner-mako/159/testReport/junit/unity8.shell.tests.test_lock_screen/TestLockscreen/test_can_unlock_passphrase_screen_Native_Device_/ is new
[07:28] <Saviq> it doesn't seem to be able to type the password in
[07:31] <Saviq> but anyway I don't really see how the setUser thing could cause / fix anything - no failures actually mention it
[07:31] <Saviq> and of course it's a freakin' mako
[07:34] <Saviq> ok that does https://jenkins.qa.ubuntu.com/job/unity8-saucy-armhf-ci/737/console
[07:39] <mzanetti> Saviq: yes, its' that
[07:40] <mzanetti> Saviq: the unity-api one was approved/merged withouth thinking that it forces the other API's to update at the same time.
[07:40] <mzanetti> my fault I'd say
[07:40] <mzanetti> sorry for that
[07:40] <Saviq> mzanetti, I saw there were all kinds of issues - network problems on devices - some weird build error - and the most prevalent one is that mako fails to type the password in
[07:42] <mzanetti> Saviq: yeah, network issues should be resoved by now. veebers took care of that.
[07:43] <Saviq> mzanetti, https://code.launchpad.net/~saviq/unity8/ap-raise-on-typing/+merge/181730 btw
[07:44] <mzanetti> Saviq: approved... top-approving doesn't seem to make much sense right now :/
[07:45] <Saviq> mzanetti, yeah
[07:45] <Saviq> mzanetti, I forced a run of setUser autolanding http://s-jenkins:8080/job/unity8-autolanding/266/console
[07:45] <Saviq> mzanetti, will be monitoring it closely
[07:45] <mzanetti> good
[07:45] <mzanetti> we reached 500 tests btw :)
[07:46] <Saviq> yeah, I saw that
[07:46] <mzanetti> do we get cookies when we are at 1000?
[07:49] <Saviq> mzanetti, from veebers, yes
[07:51] <Saviq> ah, compiz update... this will be interesting...
[07:52] <Saviq> mzanetti, thanks, btw, for staying late with that
[07:52] <mzanetti> Saviq: no problem.. need to prepare for next 2 weeks :D
[07:52] <Saviq> you're off earlier today, right?
[07:52] <Saviq> ;)
[07:52] <mzanetti> Saviq: dunno. will go for test driving a car at 2pm :)
[07:52] <mzanetti> and then come back for work though
[07:53] <Saviq> mzanetti, right, something interesting or you can't be bothered anyway? ;)
[07:53] <mzanetti> the car?
[07:53] <Saviq> yeah
[07:54] <mzanetti> BMW 1 :D
[07:54] <Saviq> ah, a Smart, then ;D
[07:54] <mzanetti> no...
[07:54] <Saviq> j/k
[07:54] <mzanetti> not really... the smart is more like the Mini
[07:54] <mzanetti> sort of (don't telly anyone here in southern germany I've said that)
[07:54] <Saviq> no, I know, the 1 is ok
[07:55] <Saviq> rofl
[07:55] <Saviq> I'm fond of my big cars around here, seeing the road kill statistics...
[07:55] <Saviq> it's not Russia, but not far enough from it unfortunately
[07:56] <mzanetti> hmm...are the cars bigger over there?
[07:57] <Saviq> mzanetti, no, the drivers are crazy over here
[07:57] <Saviq> mzanetti, so a big car is +10 to survivability
[07:58] <Saviq> mzanetti, there's 6k people killed on the roads every year
[07:58] <mzanetti> Saviq: that is a lot... I think its less around here
[07:58] <Saviq> mzanetti, I _know_ it is
[07:59] <Saviq> mzanetti, ok, I overstated, 3-4k a year
[07:59] <mzanetti> still... quite a lot. but then, poland is bigger than one would think
[08:00] <Saviq> mzanetti, well, there's 39M people, Germany is bigger than that
[08:00] <mzanetti> right... double
[08:00] <Saviq> mzanetti, one of the biggest issue is DUI
[08:00] <Saviq> 190k people stopped last year...
[08:03] <Saviq> mzanetti, so yeah, I'm driving a small tank in hope it will give me that +10 when shit hits the fan https://www.google.com/search?client=ubuntu&hs=Nqn&channel=fs&tbm=isch&q=volvo+xc70+2012&revid=2136598478&biw=1305&bih=782
[08:04] <mzanetti> :)
[08:04] <greyback> ah, we're talking about "the Beast" are we?
[08:04] <mzanetti> lol
[08:06] <greyback> Saviq: did you get the optional water cannon extra installed in the end? Or just just kept with the riot-proof glass?
[08:06] <Saviq> greyback, water... pfffft...
[08:12] <mzanetti> Saviq: yay! merged
[08:12] <Saviq> mzanetti, indeed
[08:12] <Saviq> what *will* you guys do without me ;P
[08:13] <Saviq> mzanetti, btw, I think I have one major argument for keeping the setting in dconf as well
[08:13] <Saviq> mzanetti, at least in my head it is that
[08:13] <mzanetti> which is?
[08:13] <Saviq> mzanetti, AS stores data outside of the user's home dir
[08:14] <Saviq> mzanetti, and sure, we can do e.g. backup for AS as well
[08:14] <tsdgeos> yay
[08:14] <mzanetti> right...
[08:14] <tsdgeos> setUserMeregd
[08:14] <mzanetti> :)
[08:14] <Saviq> mzanetti, but this breaks the general assumption that everything you do as your user is inside your $HOME
[08:14]  * mzanetti reapproves his 10 pending merges
[08:14] <Saviq> mzanetti, just try one for now, k?
[08:15] <Saviq> and I wouldn't like to break that assumption
[08:15] <mzanetti> Saviq: yes. you do have a point re: dconf
[08:15]  * Saviq did some thinking before bed, as you can see ;)
[08:15] <Saviq> or well, at the beginning of bed...
[08:16] <mzanetti> Saviq: well, fine with me... just wanted to avoid duplication of stuff as long as there isn't a real reason for it
[08:16] <mzanetti> duplication is always bad
[08:16] <Saviq> mzanetti, sure
[08:16] <Saviq> mzanetti, in my mind AS was always a "cache/proxy" of data, never an owner
[08:18] <Saviq> mzanetti, but anyway, let's have a chat when you're back (and me, too, dentist's at 3:30... hence the standup move)
[08:19] <Saviq> hey paulliu
[08:21] <mzanetti> Saviq: ack mterry should be around then too
[08:21] <Saviq> yup
[08:24] <Saviq> mzanetti, to add to the above... just read about someone who wanted to pass a driver's exam... DUI...
[08:25] <mzanetti> well... not that I wouldn't know people who did...
[08:25] <mzanetti> actually only one... but he made it
[08:25] <mzanetti> no. not me :D
[08:30] <Saviq> ;)
[08:31] <dednick> Saviq: i have a going away present for you ;)
[08:31] <Saviq> dednick, \o/
[08:31] <Saviq> mzanetti, with over a promil of blood alcohol level? ;)
[08:31] <mzanetti> Saviq: no.
[08:31] <Saviq> exactly ;)
[08:32] <Saviq> "per mille" ugh..
[08:33] <dednick> Saviq: https://code.launchpad.net/~nick-dedekind/unity8/indicators.menu-items-cleaning/+merge/181410
[08:34] <dednick> Basically just moving responsibility of signals/updates for menu items into the MenuItemFactory. Abstracting away the menumodel code from the items.
[08:34] <Saviq> dednick, thanks! ;d
[08:34] <dednick> i aim to please :)
[08:35] <dednick> should get some more people involved with these indicator reviews. i feel sorry for you :)
[08:37] <seb128> nic-doffay, hey
[08:37] <nic-doffay> seb128, hey
[08:38] <seb128> nic-doffay, question about OptionSelector, can you put subtitle/caption text for an option?
[08:38] <seb128> nic-doffay, I'm asking for https://wiki.ubuntu.com/SoftwareUpdates?action=AttachFile&do=get&target=phone-settings-updates-checking.png
[08:38] <seb128> nic-doffay, the bottom option (On any data connection\nData charges may apply.)
[08:39] <nic-doffay> seb128, not currently, but I'm going to implement that today. There will also be support for a picture too.
[08:39] <seb128> nic-doffay, excellent
[08:41] <seb128> nic-doffay, did you get the +1 from the sdk team to land OptionSelector? (I saw CI is still unhappy on the mr)
[08:42] <nic-doffay> seb128, going to chat with om26er about that today
[08:42] <nic-doffay> It's good though as it gives me time to sort what we just spoke about :P
[08:42]  * seb128 wants that widget to land
[08:42] <seb128> we are waiting on it
[08:43] <nic-doffay> seb128, I'd like to resolve it asap. The filters are ready to land too which rely on that branch.
[08:45] <nic-doffay> seb128, are there any designs for this additional text?
[08:45] <nic-doffay> Any mockups of a design for a component it will be used for or anything?
[08:46] <seb128> nic-doffay, the one I just pointed, you have the url 15 lines up or so
[08:47] <seb128> nic-doffay, the 3rd option of the selector as the bottom "On any data connection"
[08:47] <seb128> mpt said it should have "Data charges may apply" as a caption
[08:47] <nic-doffay> seb128, I mean something with set sizes etc approved by design.
[08:47] <seb128> mpt said it should be the same size than Caption
[08:47] <seb128> mpt, ^
[08:50] <Saviq> mzanetti, something's wrong with input on mako http://<IP_ADDRESS>:8080/job/generic-mediumtests-runner-mako/161/console :/
[08:52] <tsdgeos> pstolowski: can you give https://code.launchpad.net/~stolowski/unity8/fix-filter-activation/+merge/181619 a better commit message?
[08:55] <Saviq> mzanetti, yeah, it's going to fail
[08:59] <mzanetti> yep...
[08:59] <mzanetti> Saviq: so this happens only on mako, not on maguro, right?
[08:59] <Saviq> mzanetti, yeah
[08:59] <mzanetti> I think I can temporarily disable the mako tests then and ask om26er to look at it before reenabling
[09:00] <mzanetti> Saviq: ^
[09:00] <Saviq> mzanetti, yes please
[09:03] <Saviq> mzanetti, also, if you could try and reproduce
[09:03] <Saviq> mzanetti, on your mako
[09:03] <mzanetti> Saviq: hmm... but there are green test runs: http://s-jenkins:8080/job/generic-mediumtests-runner-mako/
[09:04] <Saviq> mzanetti, well, yeah, setUser merged, didn't it
[09:04] <Saviq> mzanetti, it's intermittent
[09:05] <Saviq> mzanetti, it feels like it's ubuntuappmanager input loss again - like the device wasn't rebooted or re-set somehow
[09:06] <mzanetti> Saviq: according to the logs there are mako 2 devices attached. the failure only happens on one of them
[09:06] <Saviq> mzanetti, oh
[09:06] <Saviq> mzanetti, interesting, can you disconnect just the one device?
[09:07] <mzanetti> Saviq: need to check... this infrastructure is new since I left QA
[09:07] <Saviq> mzanetti, I know
[09:08] <Saviq> mzanetti, there's actually four it seems
[09:08] <Saviq> http://s-jenkins:8080/label/mako/?
[09:08] <mzanetti> Saviq: yeah, they did it really properly :)
[09:08] <mzanetti> mako-0090f741e3d141bc is the bad one
[09:09] <mzanetti> Saviq: marked it as offline. no new runs should run on this one
[09:09] <Saviq> mzanetti, ok, let's see
[09:09] <Saviq> om26er, just in time ;)
[09:10] <mzanetti> hi om26er :)
[09:10] <om26er> Saviq, about the broken CI jobs, I guess ;)
[09:10] <om26er> mzanetti, hey
[09:10] <mzanetti> om26er: I just marked mako-0090f741e3d141bc as offline as keyboard input seems to fail on this one
[09:10] <Saviq> for unity8 at least
[09:10] <mzanetti> om26er: good job on the mediumtests-touch btw :)
[09:10] <Saviq> om26er, are the devices restarted / reflashed between tests?
[09:10] <om26er> Saviq, they are flashed only when a new image is available
[09:11] <om26er> Saviq, we flash new packages from the local repo every test run
[09:11] <Saviq> om26er, rebooted between runs?
[09:11] <om26er> Saviq, yes, we reboot always
[09:11] <Saviq> om26er, ok, that should be fine, let's see if it's actually just ...bc that fails
[09:12] <om26er> mzanetti, I think I also saw mako having a lot of failures yesterday, that's probably the reason for that mako is borked
[09:13] <om26er> Saviq, is the package download thing working today? yesterday the phone CI jobs were not able to download stuff from s-jenkins
[09:13] <Saviq> om26er, yeah, network is back
[09:13] <Saviq> om26er, veebers took care of that
[09:22] <Saviq> mzanetti, doesn't seem limited to ...bc actually: http://s-jenkins:8080/job/generic-mediumtests-runner-mako/143/
[09:22] <Saviq> mzanetti, this one ran on ...34
[09:22] <Saviq> mzanetti, and this one on ...ea http://s-jenkins:8080/job/generic-mediumtests-runner-mako/136/
[09:23] <Saviq> it seems just that ...bc simply ran most of the jobs
[09:23] <Saviq> so had the highest failure rate :/
[09:24] <om26er> Saviq, FWIW this test: unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_passphrase_screen
[09:24] <om26er> its not stable on touch devices
[09:24] <om26er> I have seen its random failures since yesterday
[09:24] <Saviq> om26er, yeah, thing is it's just typing stuff into a text entry (and is stable on maguro - just not on mako)
[09:25] <mzanetti> Saviq: but looking back the history, it seems only to fail on ..bc since yesterday morning
[09:25] <nic-doffay> seb128, subtext has been added can you confirm we will in fact be needing images for the option selector?
[09:25] <om26er> there is a failure on maguro: http://<IP_ADDRESS>:8080/job/generic-mediumtests-runner-maguro/163/?
[09:25] <nic-doffay> Need to know if it's a safe bet to add one now.
[09:25] <mzanetti> Saviq: om26er: perhaps there is something that makes devices go into a bad state and then they recover only when flashed next time
[09:25] <Saviq> om26er, ah, indeed
[09:25] <Saviq> mzanetti, or reboot at least
[09:26] <om26er> Saviq, before running the suite, we reboot the device and wait-for-device and then sleep 60 seconds just so that the device settles. then the shell is stopped and the tests are run
[09:26] <om26er> I would assume stopping the shell is not playing well
[09:26] <seb128> nic-doffay, I'm not a designer, I've not seen designs where there is an image ... maybe better check with JohnLea or mpt
[09:27] <mpt> seb128, wi-fi networks maybe?
[09:27] <Saviq> om26er, can we add one thing to the job in the mean time - `kill $(pidof ubuntuappmanager)`?
[09:28] <Saviq> om26er, to see if that has any impact?
[09:28] <om26er> Saviq, sure
[09:28] <seb128> mpt, good example yes
[09:28] <Saviq> om26er, after stopping unity8
[09:28] <Saviq> om26er, and needs to be run as root
[09:29] <seb128> nic-doffay, ^
[09:29] <Saviq> om26er, we've seen a similar issue before - ubuntuappmanager was confused by "real" unity8 stopping
[09:29] <Saviq> om26er, we thought we got them all out the door, but maybe that's not the case
[09:30] <om26er> Saviq, how about just pkill ubuntuappmanager ?
[09:30] <Saviq> om26er, wasn't working for me for some reason
[09:30] <Saviq> om26er, but if it does for you
[09:30] <Saviq> om26er, it's respawning, so you can see if pid changes
[09:31] <nic-doffay> seb128, right, I'll do some digging then.
[09:33] <Cimi> tsdgeos, ping :)
[09:33] <tsdgeos> Cimi: hiho
[09:33] <Cimi> tsdgeos, howdy
[09:34] <Cimi> tsdgeos, it was you to write the edge area boa boa or daniel?
[09:34] <Cimi> tsdgeos, we want to make the hudbutton appear with after, so after a longer swipe, I was wondering which property I should touch
[09:34] <tsdgeos> you mean DirectionalDragArea and friends?
[09:34] <tsdgeos> it was danieal
[09:34] <tsdgeos> daniel
[09:35] <tsdgeos> not much insight into it's properties to be honest
[09:36] <Cimi> ok
[09:36] <Cimi> I'm looking for the C++ files
[09:36] <Cimi> but I wasn't convinced :)
[09:37] <mzanetti> Saviq: now that we disabled ..1bc, we had 3 green runs in a row
[09:37] <mzanetti> must be something that borks the device until the next flash
[09:37] <Saviq> mzanetti, yeah, or at least makes it more apparent
[09:37] <Saviq> mzanetti, we can always force a reflash to see
[09:37] <mzanetti> om26er: do you think it would be possible to flash devices after after a failed run?
[09:38] <Saviq> mzanetti, that's probably excessive :/
[09:38] <mzanetti> Saviq: why? actually I think they should be flashed after each test run
[09:39] <mzanetti> Saviq: note "after", not "before"
[09:39] <Saviq> mzanetti, except we might be killing the devices this way
[09:39] <mzanetti> you mean wear out the flash?
[09:39] <Saviq> yeah
[09:39] <jamesh> sil2100: hi.  I saw unity-scope-mediascanner made it into the daily-build PPA.  What do we need to do next to get mediascanner+unity-scope-mediascanner+dependencies into main?
[09:40] <mzanetti> Saviq: I think the ./run_on_device is worse in that regard
[09:41] <mzanetti> Saviq: and I haven't ever seen a device with worn out flash tbh
[09:41] <mzanetti> not sure if that still easily happens with modern hardware
[09:41] <Saviq> mzanetti, maybe, but TBH we should actually *fix* the issue instead ;)
[09:42] <Saviq> mzanetti, sure it does, only it has built in protection now
[09:42] <Saviq> mzanetti, i.e. CoW, remapping broken cells etc.
[09:42] <Saviq> so it might be less visible, not that it's not there
[09:43] <mzanetti> Saviq: so... it should still last more than half a year then even if we flash. I'm quite sure battery has bigger problem with being attached constantly
[09:43] <Saviq> mzanetti, but we don't rely on battery ;)
[09:43] <mzanetti> and CPU with all the head that is constantly caused during the test runs and reboots
[09:44] <Cimi> jounih, the header white highlight on the separators when using dark themes is killing my eyes… is it on track?
[09:44] <Saviq> mzanetti, right, we killed the pandas' RAM instead
[09:44] <mzanetti> anyways... I don't see that as a real issue tbh. but yes, we should fix the other issue too. Thing is, you can't guarantee someone commits something that breaks the setup
[09:44] <jounih> Cimi: probably needs updating the asset with the latest design. we're doing a bug tracking session now with rosie, will flag that. thanks!
[09:45] <Cimi> jounih, it will never work with a static asset
[09:45] <Cimi> jounih, it needs to be recolored...
[09:45] <jounih> Cimi: we have different assets for each of the 3 themes
[09:45] <Cimi> jounih, ok but you can specify every colour you like with surugradient
[09:46] <Cimi> jounih, so it will work only for some combinations
[09:46] <sil2100> jamesh: Ok, so now I need someone to pre-NEW it
[09:47] <jounih> that's true, we might have to track the L value of the HSL color beneath it and adjust opacity accordingly
[09:47] <jamesh> sil2100: I think the non-main dependencies are grilo, grilo-plugins and lucene++
[09:48] <jounih> Cimi: maybe an approach like that would get us around using separate hard coded values for the 3 themese elsewhere too. will pick it up with Kaleo
[09:49] <sil2100> jamesh: we'll file a MIR on Monday and get that migrated, good thing we have it in universe at least
[09:50] <jamesh> yep
[09:50] <jamesh> sil2100: I assume unity-scope-mediascanner will make it from daily-build into the archive without much trouble?
[09:51] <sil2100> Yes, just some small intervention will be needed
[09:51] <sil2100> But nothing big
[09:55] <om26er> Saviq, retry now
[09:55] <Saviq> om26er, yeah, it's trying by itself - we have a queue )
[09:55] <Saviq> ;)
[09:56] <Saviq> om26er, I'm doing:
[09:56] <Saviq> $ for i in {1..20}; do adb reboot; adb wait-for-device; sleep 60; phablet-test-run -n unity8; done
[09:56] <Saviq> locally now
[09:56] <Saviq> on maguro - 3 runs OK now
[09:56] <Saviq> mzanetti, can you trigger the same on mako ↑?
[09:57] <mzanetti> Saviq: sure
[09:58] <Saviq> mzanetti, but first flash; adb shell apt-get install -y ssh; phablet-test-run -i -p unity8-autopilot -n unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_passphrase_screen
[09:58] <jamesh> sil2100: thanks for all your help so far.
[09:58] <om26er> Saviq, instead of phablet-test-run we just 'autopilot run unity8' on the device as phablet user, but that's pretty similar in logic
[09:58] <Saviq> to get all the stuff on the device
[09:58] <Saviq> om26er, yeah, I doubt it has any impact at all
[10:01] <om26er> mzanetti, about the reflash-on-failure, what we can do is reflash if the tests failed but we don't know if the tests were real failures or device problem
[10:01] <Saviq> mzanetti, wth is that about http://<IP_ADDRESS>:8080/job/generic-mediumtests-builder-saucy/2537/console
[10:02] <mzanetti> Saviq: setUser
[10:02] <Saviq> mzanetti, ah, didn't pick up the merge yet
[10:02] <Saviq> mzanetti, yeah, found it
[10:02] <mzanetti> om26er: yeah... that's true... maybe on 2 failures in a row on the same hardware?
[10:03] <mzanetti> just brainstorming here
[10:04] <om26er> I don't think the problem is to do with the need of reflashing, because tests for all apps are working fine, and I believe they have been working fine for unity8 as well till yesterday from when we started to stop unity8 before starting the suite
[10:05] <mzanetti> om26er: hmm, ok
[10:05] <mzanetti> in that case...
[10:06] <Saviq> of course... holidays coming... http://pastebin.ubuntu.com/6017105/
[10:07] <Saviq> om26er, mzanetti yeah, I suspect ubuntuappmanager to be the culprit again
[10:07] <om26er> Saviq, so killing it should workaround the issue ?
[10:07] <Saviq> om26er, hopefully, yes
[10:08] <Saviq> om26er, or well, I'm not sure it would have anything to do with keyboard input, if touch input works...
[10:08] <Saviq> om26er, there is a webcam in the lab is there?
[10:09] <Saviq> om26er, I talked with gema before it would be awesome if we could get videos of the device when there's a failed run
[10:09] <om26er> Saviq, three of the devices have webcam pointed at them, others don't
[10:09] <Saviq> mzanetti, tsdgeos, dednick, any idea about https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1268/console ?
[10:09] <om26er> mako-0090f741e3d141bc is one of those
[10:09] <Saviq> we've had more and more of those recently :/
[10:10] <om26er> yes, qmluitests have been failing a lot for the last few days
[10:11] <dednick> Saviq: is there a build timeout set on jenkins?
[10:11] <Saviq> dednick, well, yes, the test gets stuck
[10:11] <Saviq> dednick, and jenkins interrupts after an hour
[10:11] <dednick> Saviq: is it just the tests, or the build + tests?
[10:11] <Saviq> dednick, it takes 30 mins for a successful run
[10:11] <dednick> i c
[10:11] <tsdgeos> testDash getting stuck
[10:12] <tsdgeos> not the first time we've had that right
[10:12] <Saviq> tsdgeos, yeah
[10:13] <Saviq> too many times recently
[10:16] <Saviq> 20 runs locally, all green :/
[10:16] <tsdgeos> Saviq: do you have some more links?
[10:16] <tsdgeos> wondering if it's always MockScope5 that hangs
[10:16] <Saviq> tsdgeos, https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1265/console
[10:16] <Saviq> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1240/console
[10:16] <dednick> Saviq: do we have test xml from that ?
[10:16] <Saviq> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1229/console
[10:17] <Saviq> dednick, no, 'cause the job was killed
[10:17] <Saviq> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1225/console
[10:17] <Saviq> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1211/console
[10:17] <Saviq> most of the red ones from https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/ are timing out
[10:18] <nic-doffay> Saviq, you cool with having an "All" filter option in the filter selection. The option selector doesn't really support not having a selection which would equate to the "all" filter being used. Design signed the idea off.
[10:19] <Saviq> nic-doffay, yeah, of course
[10:19] <nic-doffay> Saviq, awesome.
[10:19] <Saviq> nic-doffay, pstolowski, where do you think we should put ↑ in?
[10:19] <Saviq> nic-doffay, GenericOptionsModel?
[10:19] <Saviq> pstolowski, ↑
[10:19] <tsdgeos> Saviq: so 4 fail in the same place and two in a different place :-/
[10:19] <Saviq> tsdgeos, yeah, doesn't mean a different issue, though
[10:20] <tsdgeos> sure
[10:20] <tsdgeos> Saviq: i'd say the best bet is detacching one of the jenkins slaves and running the test in there in a loop
[10:20] <tsdgeos> and try to figure out why it's failing
[10:21] <dednick> Saviq: any way to get output of how long tests are taking? doesnt seem to put in log/xml
[10:21] <pete-woods> cyphermox: hi - did you manage to get round to sorting out landing for the secret agent package?
[10:21] <Saviq> dednick, not really, om26er about that ↑↑, can we get timestamps in the jenkins logs?
[10:21] <Saviq> om26er, someone mentioned somewhere on a mailing list somewhen recently
[10:22] <Saviq> that they saw jenkins having a timestamp for each line in the console log
[10:22] <Saviq> could be pretty useful
[10:22] <pstolowski> Saviq, nic-doffay : need to contemplate this a bit.. in the scopes we have a dedicated property in the filter to show 'All' button, so it's a kind of special case (not a regular option)
[10:23] <Saviq> tsdgeos, dednick, mzanetti we're also getting a lot of http://<IP_ADDRESS>:8080/job/generic-mediumtests-runner-saucy/2145/ recently :/
[10:23] <pstolowski> Saviq, nic-doffay : but it probably makes sense to hide this from QML and make it an option in the options model
[10:23] <Saviq> pstolowski, yeah, we need it in the model
[10:24] <Saviq> pstolowski, what is that property exactly? just a bool whether to show all? it's settable, or do we need to unactivate all options?
[10:24] <dednick> yeah, i've got that on a couple of MPs
[10:25] <tsdgeos> Saviq: we have timestamps in kde's jenkins
[10:25] <tsdgeos> so it's possible
[10:25] <Saviq> tsdgeos, right
[10:25] <Saviq> tsdgeos, I think it was actually mzanetti that linked to it ;)
[10:25]  * mzanetti is in a phone call
[10:25] <Saviq> mzanetti,
[10:25] <om26er> Saviq, no, not really sure what you mean, we want a timestamp for what ?
[10:25] <Saviq> mzanetti,
[10:25] <Saviq> mzanetti,
[10:25] <Saviq> mzanetti,
[10:25] <Saviq> mzanetti,
[10:25] <Saviq> mzanetti,
[10:25] <om26er> wow :D
[10:26] <Saviq> om26er, in the logs
[10:26] <Saviq> om26er, so each line could have a datetime at the beginning
[10:26] <Saviq> om26er, say https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1211/console
[10:26] <tsdgeos> let me get an example
[10:26] <mzanetti> ???
[10:26] <Saviq> mzanetti, nothing ;)
[10:26] <Saviq> mzanetti, just wanted to troll you
[10:26] <tsdgeos> http://build.kde.org/view/All/job/kdepim_master/3454/console
[10:27] <tsdgeos> http://build.kde.org/view/All/job/kdepim_master/3454/consoleFull
[10:27] <Saviq> om26er, ↑
[10:27] <Saviq> oh and it's smart, with elapsed time
[10:28] <Saviq> "Jenkins ver. 1.523"
[10:28] <Saviq> we're at "Jenkins ver. 1.480.2"
[10:28] <tsdgeos> pete-woods: do you know if https://bugs.launchpad.net/unity8/+bug/1205097 should be on the repos already?
[10:29] <pete-woods> tsdgeos: it certainly looks like it should
[10:29] <Saviq> tsdgeos, https://launchpad.net/ubuntu/+source/hud
[10:29] <Saviq> tsdgeos, 13.10.1+13.10.20130822.4-0ubuntu1 should be there
[10:29] <tsdgeos> ok
[10:29] <Saviq> and be there
[10:29] <tsdgeos> pete-woods: do i need to try it works or?
[10:29] <Saviq> brb
[10:30] <om26er> Saviq, I think that comes with this plugin for jenkins https://wiki.jenkins-ci.org/display/JENKINS/Timestamper
[10:30] <pete-woods> tsdgeos: if HUD's broken again, I think I will just give in
[10:30] <tsdgeos> pete-woods: lol :D
[10:30] <om26er> so we'll need to enable that and it should produce logs with timestamps
[10:30]  * pete-woods reflashes his tablet to get clean test
[10:31] <tsdgeos> om26er: i can ask the kde jenkins admin if we are going to enable it, if not, no need to bug him
[10:32] <om26er> tsdgeos, I'll talk to fginther when he comes online and let you you if we are going to enable it, makes sense to me that we enable it
[10:32] <tsdgeos> oki
[10:32] <tsdgeos> tx
[10:34] <pstolowski> Saviq: it's a bool and it's read only.  digging it into unity-core code to see how it's handled
[10:40] <pstolowski> Saviq: yeah, in unitycore it has special button and it just deselects all options; i'll do something similar for you, so no work on QML side
[10:41] <pstolowski> nic-doffay: ^
[10:41] <nic-doffay> pstolowski, cool
[10:41] <om26er> Saviq, should we just skip/disable unity8.shell.tests.test_lock_screen.TestLockscreen.test_can_unlock_passphrase_screen  ?
[10:42] <om26er> from what I can see its failing on the phones and VM (aka desktop)
[10:42] <tsdgeos> pete-woods: seems to work fine for me
[10:42] <pete-woods> whew!
[10:43] <Saviq> om26er, on the VM it's failing for a different reason
[10:44] <Saviq> om26er, i.e. VM is too slow
[10:44] <pete-woods> tsdgeos: if you're interested, it was a threading issue - HUD is supposed to be single-threaded, but the platform API's callbacks were being triggered on its own thread
[10:44] <tsdgeos> oh
[10:44] <tsdgeos> nasty
[10:44] <pete-woods> yep
[10:45] <Saviq> om26er, who do I talk to about the plugin? :)
[10:45] <Saviq> om26er, right, will bug fginther :)
[10:45] <om26er> Saviq, fginther, he should be online in ~1hour
[10:46] <Saviq> om26er, so, let's not skip the test, will give us more incentive to look into them and fix
[10:46] <tsdgeos> Saviq: moved today's standup?
[10:46] <Saviq> tsdgeos, yeah
[10:46] <tsdgeos> oka
[10:46] <tsdgeos> just wanted to make sure it was not a mistake :d
[10:47] <Saviq> tsdgeos, got a dentist's appointment at 3:30 and didn't want to miss my last standup ;)
[10:47] <tsdgeos> ;)
[10:48] <Saviq> mzanetti, in autolanding we're still at 499 tests :D
[10:48] <Saviq> mzanetti, one of your branches brings the tipping point, right? ;)
[10:48] <mzanetti> yeah
[10:48] <mzanetti> it should
[10:58] <Saviq> fail :/
[11:04] <Saviq> ah, the fail was actually something weird
[11:05] <Saviq> om26er, unlock_screen.py still runs under unity8 suite, should probably be disabled
[11:06] <om26er> Saviq, I run it with -q which just swipes the screen (without starting unity in testability mode)... I use to so that it lightens up the screen
[11:06] <om26er> Saviq, basically it creates a touch event so that the device' screen turns on
[11:06] <Saviq> om26er, yeah, not needed for unity8 suite
[11:06] <Saviq> om26er, but ok, shouldn't matter either
[11:06] <om26er> ah - ok never knew that
[11:06] <Saviq> om26er, well, it will just light up with the first test anyway
[11:07] <Saviq> assuming it will actually shut down between `initctl stop unity8` and the first test
[11:07] <Saviq> which I expect will not happen
[11:09] <om26er> Saviq, cool, is that part of unity8 to turn on the screen when it starts ?
[11:09] <om26er> aha, so the screen turns on when it tries to unlock it, right ?
[11:12]  * greyback needs some fresh air, will be back in an hour
[11:13] <Saviq> om26er, yeah
[11:21] <mhr3_> Wellark, following yesterday's discussion i'm pushing http://paste.ubuntu.com/6017300/ to the branch k?
[11:44] <Wellark> mhr3_: yep. go for it
[11:44] <Wellark> mhr3_: I will catch up with that branch today
[11:44] <Wellark> as with the launcher, too
[11:45] <Wellark> unless something blocks some stack from landing or the usual stuff that gets in the way
[11:45] <Wellark> like getting hit by a bus
[12:22] <mhr3_> Saviq, i have a treat for you - i have a branch that removes all IconUtils.from_gicon(), but need https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/unity-theme-icon-provider/+merge/180805
[12:22] <mhr3_> work your magic :)
[12:25] <Saviq> mhr3_, it's WiP for any reason?
[12:26] <mhr3_> Saviq, Wellark wanted to take a second look
[12:26] <Saviq> mhr3_, so it's Needs Review, really
[12:26] <mhr3_> Saviq, but imo it's ready, yea
[12:26] <Saviq> done
[12:58] <tsdgeos> simple "less includes is good" review for anyone? https://code.launchpad.net/~aacid/unity8/noQtQmlInclude/+merge/181802
[13:02] <Saviq> kgunn, MacSlow, dednick, nic-doffay, if you can, we're doing standup early today
[13:02] <dednick> now you mean?
[13:03] <Saviq> dednick, now :)
[13:03] <dednick> Saviq: hang on. just got some food in my mouth :)
[13:03] <Saviq> dednick, sorry, just join when you can
[13:03] <nic-doffay> Saviq, now?
[13:04] <Saviq> nic-doffay, if you can, yes
[13:04] <nic-doffay> np
[13:04] <MacSlow> Saviq, right now?!
[13:04] <Saviq> MacSlow, I *did* update the invite ;D
[13:15] <kgunn> Saviq: yeah...you did...and i saw it last night....just forgot :-P
[13:23] <Cimi> tsdgeos, Saviq the hud button is *always* on screen, with opacity 0… is that affecting rendering? why not setting visible: false?
[13:25] <tsdgeos> i would hope that they are smart enough to not render a opacity 0 item
[13:25] <tsdgeos> but yeah you can add a
[13:25] <tsdgeos> visiblity: opactivy != 0
[13:25] <tsdgeos> won't hurt i guess
[13:25] <Cimi> yeah
[13:25] <Cimi> that's what I meant
[13:25] <Cimi> wondering why we didn't add it in the first place
[13:26] <Cimi> tsdgeos, same thing for launcher maybe
[13:32] <Cimi> stupid question: to put a mouse area underneath I simply play with z index or there's a more clever way now?
[13:36] <tsdgeos> is launchpad down?
[13:36] <tsdgeos> i just pushed new stuff into a branch
[13:36] <tsdgeos> and isn't showing
[13:36] <tsdgeos> Cimi: underneath what?
[13:36] <Cimi> tsdgeos, the hud button
[13:37] <Cimi> tsdgeos, simply set hudButton z : 1now
[13:43] <Cimi> tsdgeos, Saviq https://code.launchpad.net/~unity-team/unity8/unity8.new_hud-button_interaction/+merge/181829
[13:43] <Cimi> lp is still slow...
[13:44] <Cimi> guess we need tests now...
[13:45] <Cimi> why we don't have any tests for bottom bar already?
[13:48] <Cimi> I have an issue, the hud button is not "eating" the clicks
[13:48] <Cimi> it's an AbstractButton with onClicked
[13:51] <dednick> larsu: were you able to start on any of those qmenumodel branch reviews?
[13:55] <larsu> dednick: I was able to start yes. Sorry I haven't been able to finish yet. I don't have much more time today, but I'll try to find an hour or two on the weekend
[13:56] <dednick> larsu: bah. dont do it on the weekend!
[13:56] <dednick> larsu: next week will be ok
[13:56] <larsu> dednick: ha, thanks :)
[13:57] <dednick> larsu: just need it to switch over messaging menus to UnityMenuModel. not a massive rush.
[13:57] <tsdgeos> Cimi: that's been there forever, the shell and the apps both get the clicks
[13:58] <Cimi> tsdgeos, I need to eat them
[13:58] <Cimi> gnam gnam
[13:59] <Cimi> tsdgeos, because otherwise if you click on the hud button, you activate stuff underneath
[14:00] <mterry> oh!  The meeting got moved 30  earlier, instead of 30 later
[14:00] <mterry> ahem
[14:01] <mterry> will add myself to notes
[14:03] <greyback> can someone do me a favour: on phone, open notepad app, tap a note to open the OSK. Then rotate the device both to its left, and to its right. Is the OSK always correctly positioned?
[14:04] <tsdgeos> greyback: yep, even upsidedown is fine
[14:05] <greyback> tsdgeos: ok. Then I've work to do :)
[14:08] <Cimi> https://code.launchpad.net/~unity-team/unity8/unity8.hide_launcher_when_hidden/+merge/181837
[14:08] <Cimi> Saviq ^ :P
[14:10] <tsdgeos> Cimi: don't give to Saviq man, he's going on holidays
[14:10] <Cimi> tsdgeos, you can do as well, it's one liner
[14:16] <tsdgeos> dednick: we don't have tests for  lp:~nick-dedekind/unity8/indicators.menu-items-cleaning ?
[14:17] <tsdgeos> dednick: i mean you're changing quite a few names of properties and stuff
[14:17] <tsdgeos> nothing breaks?
[14:24] <dednick> tsdgeos: we've never had tests for the indicator components. it's a TODO.
[14:24] <dednick> but it all seems to work still, so..
[14:25] <tsdgeos> ah
[14:28] <tsdgeos> dednick: i guess the test is, run into phone and check indicators kind of still wor
[14:29] <tsdgeos> dednick: anything in particular i should check for?
[14:36] <Cimi> tsdgeos, you know how I could eat those events?
[14:38] <tsdgeos> Cimi: check what the laucnher does to eat them
[14:38] <Cimi> it's what I was doing :)
[14:40] <Cimi> mzanetti, how can I eat events?
[14:40] <Cimi> mzanetti, how does the launcher eat?
[14:43] <dednick> tsdgeos: just that all the menu items are displaying their data correctly.
[14:43] <tsdgeos> dednick: menu items as in?
[14:43] <dednick> tsdgeos: as in no regression. there's no new functionailty there
[14:44] <dednick> eg, the network access points, the labels, all buttons and switches work.
[14:44] <tsdgeos> oka
[14:48] <seb128> mterry, ok, I had slightly misunderstood the design requirement, that setting is only "lock on suspend", e.g whether we should kick the greeter it on or not on resume
[14:49] <mterry> seb128, OK
[14:51] <Cimi> tsdgeos, my opinion is that mouse area eats events
[14:52] <Cimi> tsdgeos, but not my abstractbutton
[14:54] <tsdgeos> Cimi: isn't anstractubbon a mouse area?
[14:54] <Cimi> tsdgeos, it's an actionitem
[14:55] <tsdgeos> is it?
[14:55] <Cimi> tsdgeos, yes, we'll see soon though, I'm running on device...
[14:56] <tsdgeos> Cimi: well sure it's an ActionItem
[14:56] <tsdgeos> with a MouseArea inside
[14:56] <tsdgeos> :D
[14:56] <Cimi> nope...
[14:56] <Cimi> it doesn't work
[14:56] <Cimi> so I don't know :P
[15:10] <Cimi> dunno
[15:13] <Cimi> mterry, you know how the greeter eats events?
[15:13] <Cimi> mterry, I want the hudbutton to eat mouse clicks
[15:13] <Cimi> otherwise when I click the button the app gets the clicks as well
[15:14] <Cimi> maybe greyback knows that too (how to make a component eat events)
[15:14] <mterry>  Cimi, is that due to InputFilterArea ?
[15:14] <greyback> Cimi: what is the context? What do you need  to do?
[15:15] <Cimi> greyback, hud button now stays on screen, so we can click on it to open the hud. Problem: the app gets click (for example when I click the hud with the calendar app opened, I switch to the day below :P)
[15:16] <greyback> Cimi: you need an InputFilterArea, which fills that hud button.
[15:16] <Cimi> greyback, I'm wondering how the launcher works then °_°
[15:16] <greyback> Cimi: InputFilterArea defines a rectangle of the shell where the shell takes the input, and keeps it. Taps on a zone of the screen where no IFA is, go to *both* shell, and the application underneath
[15:18] <Cimi> greyback, right understood!
[15:18] <Cimi> thx
[15:19] <greyback> np
[15:28] <Cimi> tsdgeos, https://code.launchpad.net/~unity-team/unity8/unity8.new_hud-button_interaction/+merge/181829/comments/411800
[15:28] <Saviq> mzanetti, hmm https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/1284/testReport/junit/%28root%29/qmltestrunner/Drag_and_Drop__test_dragndrop/
[15:28] <Saviq> mzanetti, that seems to be a persistent failure
[15:31] <om26er> the failing tests all look like the screen is not able to unlock on the device
[15:31] <om26er> AssertionError: After 10.0 seconds test on Greeter.created failed: False != dbus.Boolean(True, variant_level=1)
[15:32] <Cimi> tsdgeos, I addded a regression / fixing
[15:37] <mzanetti> Saviq: i'll check it out
[15:37] <Saviq> mzanetti, thanks
[15:43] <tsdgeos> Daekdroom: there?
[15:43] <tsdgeos> wops
[15:43] <tsdgeos> Daekdroom: sorry
[15:43] <tsdgeos> dednick_: there?
[15:44] <dednick_> tsdgeos: alo
[15:44] <tsdgeos> dednick_: https://code.launchpad.net/~nick-dedekind/unity8/indicators.menu-items-cleaning/+merge/181410 looks good to me, tested on the phone and all seems to work fine too
[15:44] <tsdgeos> dednick_: so unless you want someone else to have a second view, i'm approving
[15:45] <tsdgeos> dednick_: i guess we'll be getting "signalStrength: strenthAction.valid ? strenthAction.state : 0" soon? so we can uncomment it?
[15:46] <dednick_> tsdgeos: yeah, it's in MP
[15:46] <tsdgeos> oka
[15:46] <dednick_> tsdgeos: ok to approve
[15:46] <tsdgeos> dednick_: so maybe wait for that one? or just go and have a small one later?
[15:46] <dednick_> tsdgeos: it'll probably only come next week. i can delete the section if you prefer.
[15:47] <tsdgeos> no it's fine
[15:47] <mzanetti> Saviq: that fail is really weird... its a line that does tryCompare(draggedItem, "itemOpacity", 1)
[15:47] <tsdgeos> remind us of something has to be done :D
[15:47] <mzanetti> Saviq: and it seems the animation only goes to 0.94...
[15:47] <Saviq> mzanetti, yeah, it's either the easing or an undefined state, I'd say
[15:48] <kgunn> Saviq ping ?
[15:48] <Saviq> kgunn, pong
[15:48] <tsdgeos> Cimi: you moved the hud thing to WIP?
[15:48] <mzanetti> Saviq: ah... dammit I have a feeling... if it moves into the folded area, it gets transparent...
[15:48] <Cimi> tsdgeos, there's a bug
[15:49] <Cimi> tsdgeos, looking into it..
[15:49] <tsdgeos> Cimi: ok
[15:49] <Saviq> mzanetti, right, that might be it, too
[15:49] <kgunn> Saviq: did you happen to think about how long it might take to have a proto for user testing of design new shell navigation...
[15:49] <tsdgeos> Cimi: maybe you can add a comment of what's the bug so i can also check it's fixed once you fix it? :D
[15:49] <mhr3_> mzanetti, can we please get https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/unity-theme-icon-provider/+merge/180805 merged?
[15:49] <kgunn> 3d card deck from right edge for example
[15:49] <Saviq> kgunn, yeah we talked with greyback
[15:50] <Saviq> kgunn, we're thinking 2 man-weeks with screenshots
[15:50] <greyback> yep
[15:50] <mzanetti> mhr3_: not really sure why you're asking me
[15:50] <kgunn> Saviq: mmm....so 3 w/ interrupts :)
[15:50] <Saviq> kgunn, yeah
[15:51] <mhr3_> mzanetti, ehm, because it's friday! :P
[15:51] <mzanetti> mhr3_: I have no clue about that merge proposal
[15:52] <mzanetti> mhr3_: you might want to ask someone from #sdk, no?
[15:52] <mhr3_> mzanetti, yea, i really have no idea why i pinged you about it
[15:52] <Cimi> tsdgeos, I think it's fixed now
[15:52] <Cimi> tsdgeos, was basically the hud not running if you were dragging from the bottom
[15:52] <Cimi> tsdgeos, after enabling it with clicks
[15:53] <Saviq> mhr3_, zsombi and Wellark are on it
[15:53] <tsdgeos> Cimi: i see
[15:53] <tsdgeos> well, i'm calling it a day
[15:53] <Saviq> mhr3_, they wanted tests, though
[15:53] <tsdgeos> see you on monday guys
[15:53] <Cimi> tsdgeos, not fixed yet :D
[15:54] <Cimi> this input filter thing is tricky, it's invisible so you don't know when it's enabled
[15:55]  * Cimi next time I put a visual element to test it
[15:57]  * Cimi should create an alias bzr pysh = bzr push
[15:57] <Cimi> so many typos
[15:59] <Cimi> well it's ready to be reviewed now
[15:59] <mhall119> Saviq: are we going to discuss Unity 8's desktop mode this UDS, or wait until next?
[16:00] <Saviq> mhall119, I'm going on holiday starting tomorrow
[16:00] <Saviq> mhall119, so won't be there for vUDS or the week after that
[16:00] <mhall119> so....no then
[16:03] <Saviq> mhall119, sounds right
[16:03] <mhall119> ok, thankis
[16:04] <dednick_> tedg: will need https://code.launchpad.net/~nick-dedekind/unity8/indicator.multi-icon/+merge/181862 for your cellular data to be in unity8 indicators
[16:05] <tedg> dednick_, Yeah, I understand.  It's not blocking me other than I'd really love to see the icon :-)
[16:06] <dednick_> tedg: ok. i tested ealier. seems to be all good
[16:07] <tedg> dednick_, Woot!
[16:08] <tedg> dednick_, That's what I like to hear on Friday's ;-)
[16:20] <mzanetti> Saviq: _should_ be fixed: https://code.launchpad.net/~mzanetti/unity8/launcher-folding-tweaks/+merge/181208
[16:21] <mzanetti> at least I get 100% success rate locally here
[16:21] <mzanetti> before every 10th run failed here
[16:21] <Saviq> mzanetti, ok cool
[16:40] <kgunn> greyback: jamie's saying the clickpackage download bug is really in mir ?...just wanted your 2 cents...does racarr need to look into that todya ?
[16:41] <fajung> hello, I'm on ubuntu 12.04, my mounted partition isn't display in the luncher bar
[16:42] <fajung> it is mounted under /mnt/partition
[16:48] <greyback> kgunn: I need to chat with him a sec, just to see we're on the same page.
[16:49] <greyback> kgunn: where do I find him??
[16:50] <greyback> kgunn: nevermind
[17:04] <ESphynx> Hey guys... so , we'd *really* like to solve this glitch we get in Unity with our toolkit before the Saucy feature freeze
[17:05] <ESphynx> We end up with a doubled up menu like this: http://ecere.com/tmp/unityBug.png    , bug description: http://ecere.com/mantis/view.php?id=850
[17:06] <ESphynx> The first thing is we'd like to know if our toolkit is doing something wrong, or if it's Unity that's to blame, either way we'd really like the fix to be in before feature freeze
[17:14] <ESphynx> hey redj
[17:16] <redj> hey ESphynx
[17:17] <ESphynx> So what do you think of this bug redj:  http://ecere.com/tmp/unityBug.png ?
[17:19] <redj> ESphynx: I don't know... I have to look at it again... going to do that in a sec...
[17:36] <greyback> Saviq: still around?
[17:44] <Saviq> greyback, yup
[17:44] <greyback> Saviq: this might be familiar: https://code.launchpad.net/~gerboland/unity-mir/fix-click/+merge/181881
[17:45] <ESphynx> Any idea about this bug guys?
[17:45] <Saviq> greyback, approved
[17:46] <greyback> Saviq: thanks!
[17:46] <Saviq> greyback, good I affected unity-mir on those bugs ,then
[17:46] <greyback> Saviq: nah, it took an actual complaint by the click guys to remind me :)
[17:47] <Saviq> lol
[17:47] <greyback> I was expecting the upstart app stuff to be done by the time they would be testing. I was wrong :(
[17:48] <ESphynx> Saviq: Do you think our toolkit is to blame?
[17:49] <Saviq> ESphynx, sorry, I'm not involved in current Unity work, just unity8 - the phone one
[17:49] <Saviq> ESphynx, but, from the top of my head
[17:49] <Saviq> ESphynx, if you mean the double toolbar, then yes - Unity doesn't draw anything in there
[17:49] <ESphynx> Ah... could you please ping whoever would have a clue?
[17:50] <ESphynx> thing is it doesn't happen with any other toolkits
[17:50] <ESphynx> it's the whole maximized thing and decorations size reporting I guess
[17:50] <Saviq> ESphynx, it's Friday afternoon, best email the unity-dev list https://launchpad.net/~unity-dev
[17:51] <Saviq> ESphynx, and/or file a bug against lp:unity, if you find it is actually the culprit
[17:51] <ESphynx> k, thanks salem_
[17:51] <ESphynx> Saviq*
[17:51] <ESphynx> redj: got that? :P
[17:52] <Saviq> ESphynx, but yeah, the double toolbar is in the window's area, so I doubt that unity has anything to do with that
[17:53] <ESphynx> Saviq: well it would be a bad _NET_FRAME_EXTENTS or something
[17:54] <ESphynx> redj: Track these _NET_FRAME_EXTENTS notifications down!
[17:58] <ESphynx> In particular, we're only requesting the frame_extents when 'creating' a window...
[18:04] <redj> ESphynx: got it
[18:18]  * greyback eod
[18:39] <om26er|afk> Saviq, I think the kill ubuntuappmanager workaround didn't change anything, what you say should I remove it ?
[19:00] <Saviq> om26er|afk, yeah, do


[08:05] <LocutusOfBorg> jugmac00, hello, looks like bos02 is still having issues...
[08:05] <LocutusOfBorg> and also lcy02
[08:11] <jugmac00> LocutusOfBorg: As Colin mentioned yesterday, this has been escalated to IS. I will talk to him once he is online, but I am afraid there is not much we can do from our side.
[08:13] <LocutusOfBorg> oh... I saw in the meanwhile britney was able to finish one run, so I was wondering if that was fixed...
[08:13] <LocutusOfBorg> it would be nice to have some sort of automatic notification here so we know when something is ok, and when its not maybe :)
[08:19] <cjwatson> britney being fixed is unrelated.
[08:20] <cjwatson> The cleaning builders on lcy02 aren't a serious problem right now, but I'll do a mass-reset on general principles.
[08:26] <jugmac00> cjwatson: I am not sure whether I understand you correctly. Should I perform the mass reset now?
[08:34] <cjwatson> jugmac00: No, I already did.
[08:34] <cjwatson> "I'll do a mass-reset on general principles"
[08:34] <cjwatson> meant I was doing so right then
[08:34] <cjwatson> if it had been a suggestion to you it would have been "I'd" rather than "I'll"
[08:34] <cjwatson> (though hopefully I'd have been a little clearer than that ...)
[08:35] <jugmac00> cjwatson: thanks for clarifying
[08:35] <cjwatson> I doubt it will do much though
[08:35] <cjwatson> It might have cleared out a bit of noise on lcy02
[08:36] <cjwatson> And sort of vaguely helped a bit temporarily on bos02, but I don't expect it will last
[09:04] <LocutusOfBorg> thanks!
[09:45] <wgrant> I'm in the middle of some heavy maintenance on bos02 to lighten the DB load, but it's a few days away.
[11:55] <juliank> cjwatson: wgrant really need to get the 2022 signing key stuff sorted out, https://answers.launchpad.net/launchpad/+question/703740


[13:56] <xu-help26w> Hello everyone
[13:56] <Alabalistic> hi
[13:56] <xu-help26w> I have a toshiba w100-107 tablet pc
[13:56] <xu-help26w> It's a dual screen tablet
[13:56] <xu-help26w> I want to install Xubuntu on it
[13:56] <xu-help26w> and make it run fine
[13:57] <Alabalistic> you need to consider cpu
[13:57] <Alabalistic> are using arm or x86
[13:57] <xu-help26w> x86
[13:57] <xu-help26w> https://pl.dynabook.com/discontinued-products/libretto-w100-107/ here are the specs
[13:58] <xu-help26w> can it run xubuntu?
[13:58] <xu-help26w> with 2 touchscreens?
[13:58] <Alabalistic> wow
[13:58] <Alabalistic> no idea
[13:59] <Alabalistic> consider raspbian os, it's fast with 1GB RAM
[13:59] <Alabalistic> on the Raspberry pie
[13:59] <Alabalistic> I have no idea
[14:00] <xu-help26w> will it work with two touchscreens?
[22:03] <big_charlie> hello. is there anyway to install WICD w/o compiling it myself?
[23:24] <akko> why do i only have 640x480?
[23:26] <Bashing-om> akko: No telling - yet - what is driving the display ' sudo lshw -C display ' ? in a pastebin .
[23:30] <akko> Bashing-om: ix.io/2pI9
[23:33] <Bashing-om> akko: Complete URL please - no idea which one ^ that is from.
[23:33] <akko> what do you mean?
[23:33] <akko> ix is a pasting service
[23:34] <Bashing-om> Oh ! .. live and learn a new one :P
[23:34] <akko> XD
[23:34] <akko> wgetpaste wasn't on the repos so I just went with ix
[23:38] <Bashing-om> akko: Ouch ! Sis graphics - see if: https://easylinuxtipsproject.blogspot.com/p/sis.html helps .
[23:38] <akko> ouch indeed
[23:39] <akko> its a very old laptop my grandma wants to use, and I wont just install windows 7 or something like that for her
[23:39] <Bashing-om> akko: i have read sometime in the recent past that there was renewed efforts to update the driver - but did not keep track of it.
[23:40] <akko> well i have tried debian before on the same laptop
[23:40] <akko> and i had at least 1024x768
[23:40] <akko> didn't stick to it because the wireless adaptor i use wasn't being recognized
[23:40] <Bashing-om> akko: right now there is no driver loaded :(
[23:41] <akko> oof
[23:42] <Bashing-om> akko: There is old: http://zatherz.cba.pl/sis/ that might be of value.
[23:43] <akko> hmmm
[23:43] <akko> i'll give it a shot
[23:43] <akko> links are 404 though
[23:44] <tomreyn> https://github.com/rasdark/xf86-video-sis671 may work with xserver-xorg in (x)ubuntu 18.04
[23:44] <tomreyn> ...which is xorg 1.19.6
[23:46] <Bashing-om> akko: tomreyn Maybe too xorg.freedesktop.org has a driver - checking.
[23:51] <akko> Bashing-om: your first link worked :O
[23:51] <akko> thanks :)
[23:51] <Bashing-om> akko: Oh updated drivers even! http://xorg.freedesktop.org/releases/individual/driver/ (xf86-video-sis-0.12.0.tar.gz2019-12-03 19:21867K).
[23:52] <akko> well its working so I won't bother updating them I guess :o
[23:52] <akko> but thanks man
[23:53] <Bashing-om> akko: Great ! All's well :)
[23:53] <akko> can't say its the fastest thing ive ever seen, but thats to be expected out of these poopy sis and via chipsets XD
[23:56] <Bashing-om> akko: I am surprised there is still support - http://ubuntuforums.org/showthread.php?t=2144455 <-Links/solutions:I am the author of the how-to at Easylinuxtipsproject
[23:57] <tomreyn> https://gitlab.freedesktop.org/xorg/driver/xf86-video-sis
[23:58] <tomreyn> akko: which xubuntu version are you on? i'm surprised you got it to work this easily


[00:44] <rick_h_> lazyPower: hey there
[00:44] <lazyPower> o/
[00:44] <lazyPower> rick_h_: pong
[00:55] <rick_h_> lazyPower: ty email away :)
[02:16] <lazyPower> jrwren: ping - just got a big MP from foli w/ nagios bits targeted at my namespace charm of logstash
[04:39] <blahdeblah> Any charmers stil awake?  aisrael tells me that as long as "python tests/20-mytest" runs, then any test code should work.  But 20-mytest relies on python modules elsewhere in the charm tree; what's the correct method for including it in the python module path?
[11:06] <marcoceppi> blahdeblah: still around?
[11:10] <blahdeblah> marcoceppi: Sort of; past EOD & dealing with a broken machine at the moment
[11:11] <marcoceppi> you can import sys and patch the pythonpath at the top of the test file if you're unable to import it by normal means
[11:12] <blahdeblah> marcoceppi: Yeah - found that in the latest unit_tests template and used that in my unit_tests.
[11:13] <blahdeblah> Do we have any documentation about the preferred best practice for unit tests at present?
[11:13] <marcoceppi> ah, I figured 7 hours of searching must have yeilded something, sorry we couldn't get you an answer sooner
[11:13] <marcoceppi> blahdeblah: not entirely, no
[11:13] <blahdeblah> np - I know I'm on the wrong side of the planet. :-)
[12:05] <marcoceppi> has anyone run into an issue with local provider and 1.24?
[12:54] <aisrael> marcoceppi: The only problem I had was it wasn't a clean upgrade. I had to destroy and bootstrap my env
[12:54] <aisrael> (1.24-beta1)
[12:55] <aisrael> blahdeblah: Glad you found a solution!
[13:00] <aisrael> The upgrade from 1.24-beta1 to beta2 went smooth
[13:00] <aisrael> ANd we have service-status and workload-status!
[14:06] <lazyPower> woot
[15:24] <jose> 'ello guys, having some troubles over here
[15:24] <jose> `juju bootstrap --constraints "cpu-power=0 mem=512M"` is trying to launch a t2.micro instead of a t1.micro
[15:25] <jose> any idea why?
[15:28] <jrwren> "The t1.micro is a previous generation instance and it has been replaced by the t2.micro"
[15:29] <jrwren> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts_micro_instances.html
[15:33] <jose> jrwren: I've continued using t1.micro instances because they suit me for charming, has the core team decided to deprecate them?
[15:34] <jose> t1.micros can still be launched from the aws console and everything
[16:17] <stokachu> sinzui: have you guys noticed issues with juju trying to create vivid containers?
[16:17]  * sinzui gets bug
[16:18] <sinzui> stokachu, bug 1442308 is our nemesis
[16:18] <mup> Bug #1442308: Juju cannot create vivid containers <ci> <local-provider> <lxc> <ubuntu-engineering> <vivid> <juju-core:Triaged by cherylj> <juju-core 1.24:Triaged by cherylj> <https://launchpad.net/bugs/1442308>
[16:18] <stokachu> sinzui: thanks!
[16:18] <sinzui> stokachu, in the details of the bug, I think we see that the container logic is using upstart :(
[16:20]  * sinzui high fixes Core for getting every branch blessed
[16:43] <sinzui> hi ses
[16:43] <sinzui> I can discuss compatibility tests now
[17:31] <lukasa> Quick question: what's the incantation for deploying the /next branch of a charm?
[17:31] <lukasa> Or do I have to check it out in bzr and deploy it locally?
[17:32] <marcoceppi> lukasa: the latter
[17:33] <lukasa> Ok. =)


[01:23] <scientes> how do i turn off launchpad annoying me with my own bugs?
[01:23] <scientes> nvm
[02:40] <slick666> hello LP team
[02:40] <slick666> I was hoping to get a pointer on how to move a personal branch into a team branch
[02:40] <slick666> I think I'm just googleing the wrong terms and not finding this
[02:41] <thumper> hi slick666
[02:41] <thumper> let me just check
[02:41] <thumper> see if it is still the same
[02:42] <slick666> cool
[02:42] <thumper> slick666: go to the branch
[02:42] <thumper> slick666: on the right hand side, click the change details
[02:42] <thumper> slick666: you can then specify the owner with a drop down select box
[02:42] <slick666> ah I see it and follow
[02:42] <slick666> oh cool
[02:42] <thumper> slick666: I think the reason we didn't have an ajax change button was due to the potential for naming conflicts
[02:42] <thumper> however that isn't really a good reason
[02:43] <thumper> and there is no technical reason why it couldn't be fixe
[02:43] <thumper> d
[02:43] <slick666> actually I was poking at documentation and looking for a command line solution
[02:43] <thumper> oh...
[02:43] <slick666> this is way easier :P
[02:43] <thumper> I think you can do it with launchpadlib too
[02:43] <thumper> I think I got that working...
[02:43] <slick666> I was thinking bzr branch, bzr push something something
[02:44] <thumper> you should just be able to change the owner reference
[02:44] <thumper> and lp_save()
[02:44] <thumper> pushing to a new place works too
[02:44] <thumper> but it doesn't keep the existing subscribers
[02:44] <thumper> or linked bugs or merge proposals
[02:44] <thumper> as the old branch is still around
[02:45] <slick666> yea, thats what I was running into
[02:45] <slick666> thanks thumper, problem solved
[02:45] <thumper> np
[09:00] <mgz> anyone aware of issues with codehosting currently?
[09:00] <mgz> lp:~gz/bzr/2.5_backport_rmbranch_fixes exists over bzr+ssh but not over http
[09:02] <wgrant> mgz: You're the one that's meant to be aware of this now :P
[09:03] <wgrant> mgz: But I believe the HTTP rewriter always uses a slave database, and they're lagging by a bit at the moment.
[09:03] <wgrant> So if it's a new branch it might not be there yet.
[09:03] <jam> wgrant: I'm pretty sure they are served
[09:03] <jam> by the same location now, isn't it?
[09:03] <mgz> wgrant: thanks, now I am becoming more aware.
[09:03] <jam> ah, different pg db
[09:03] <jam> so it doesn't know how to translate URL to path on disk
[09:03] <wgrant> jam: Same location on disk, yeah
[09:03] <mgz> and this means I can blame stub?
[09:03] <wgrant> Pretty much.
[09:04] <wgrant> See the discussion in #-ops
[09:04] <mgz> ace.
[09:04] <wgrant> Well
[09:04] <wgrant> Blame Rosetta
[09:04] <wgrant> and stub
[09:04] <stub> I'm pedalling as fast as I can
[09:09] <czajkowski> poor stub
[09:12] <Nafallo> wgrant: oh hey! can ppas build stuff for debian yet? as in, can I put squeeze in my changelog and the buildfarm will DTRT?
[09:12] <StevenK> Nope
[09:12] <Nafallo> bah
[09:13] <czajkowski> Nafallo: ello
[09:13] <Nafallo> what's the timeline on that feature?
[09:13] <Nafallo> hola czajkowski
[09:13] <wgrant> Nafallo: Not clear if it will ever happen
[09:13] <Nafallo> wgrant: are you saying you've stopped being bored in weekends? ;-)
[09:13] <czajkowski> Nafallo: no it's ok I plague poor wgrant
[09:14] <wgrant> Nafallo: I implemented the necessary code in 2009
[09:14] <wgrant> Nafallo: It's trivial.
[09:14] <czajkowski> he now runs away at weekends to avoid me and my questions
[09:14] <Nafallo> haha
[09:14] <wgrant> Nafallo: Builder and disk resources are more the problem now
[09:14] <Nafallo> czajkowski: he's a clever guy :-)
[09:14] <wgrant> And potentially social considerations
[09:14] <czajkowski> wgrant: your idea of trivial and everyone elsses differs
[09:14] <Nafallo> wgrant: oh. hrm. yeeah... that makes sense to me...
[09:15] <wgrant> Nafallo: Maybe one day when we recruit 1SS into the build farm :)
[09:15] <Nafallo> wgrant: *grins*
[09:15] <wgrant> But it's certainly not feasible now
[10:08] <mpt> There should be a law against assigning bugs or work items to teams ...
[10:09] <geser> mpt: "It is forbidden by law to file bug or work items." something like that?
[10:09] <mpt> geser, no, just to assign them to teams
[10:09] <mpt> filing them is fine
[10:11] <geser> mpt: then file a bug which requests that the assign column gets hidden and assign it to the LP devs :)
[10:12] <mpt> Hiding it wouldn't work, because that would prevent assigning bugs to individuals.
[10:13] <geser> ah, indivuals are ok but just teams not
[10:13] <mpt> right
[10:19] <czajkowski> mpt: are you a happy chappy today!
[10:20] <mpt> I'm a box of birds, czajkowski
[10:20] <czajkowski> mpt: as always :)
[10:20] <czajkowski> mpt: unlike my battery icon which looks like a bee :/
[10:21] <mpt> A bee?
[10:21] <mpt> Screenshot?
[10:21] <davmor2> mpt: that's animal cruelty that is :P
[10:21] <xnox> Is launchpad ok? it has been 'processing' lp:~dmitrij.ledkov/ubuntu/quantal/btrfs-tools/merge for a while. =)
[10:22] <czajkowski> xnox: day downtime should be back up now
[10:22] <xnox> czajkowski: if you say so =)))
[10:22] <xnox> ok.
[10:22] <czajkowski> mpt: http://twitpic.com/9msmw2   http://twitpic.com/9mtp01     http://twitpic.com/9mtqml
[10:22] <czajkowski> xnox: in theory if not poke wgrant or stub
[10:24] <mpt> czajkowski, that is very strange. It looks as if one of the icons is missing, so for just that icon, it's falling back to a different theme.
[10:24] <czajkowski> mpt: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1001229
[10:24] <czajkowski> mpt: aye jut it's randomly changing every 2-3 mins only way to make it behave is to plug in your power supply
[10:50] <tsdgeos> hi guys, i can't change the branch status (the one under Branch Information) in https://code.launchpad.net/~aacid/nautilus/fix_quicklist_underscore even if it's my branch, any idea why? Could i convince you to do it for me?
[10:54] <czajkowski> tsdgeos: you should be able to do this
[10:54] <tsdgeos> i hope i could
[10:54] <tsdgeos> s/hope/wish
[10:54] <tsdgeos> don't see the yellow pencil
[10:55] <jelmer> tsdgeos: there is no yellow icon next to the statu ?
[10:55] <jelmer> *status
[10:55] <tsdgeos> nope
[10:55] <tsdgeos> oh wait
[10:55] <jelmer> tsdgeos: and you're logged in under the right account?
[10:55] <tsdgeos> i'm not logged in
[10:55] <tsdgeos> :D
[10:55]  * tsdgeos hides
[10:55]  * czajkowski peers at tsdgeos :)
[10:55] <tsdgeos> sorry guys
[10:55] <tsdgeos> and gal
[10:55] <czajkowski> tsdgeos: tis grand
[11:13] <xnox> maybe it's just me, but "Updating branch..." feels slow today
[11:13] <xnox> unless there is backlog
[11:35] <czajkowski> xnox: they are working on things atm
[11:36] <czajkowski> so perhaps thats why
[11:36] <xnox> ok
[12:09] <gema> hello, trying to work with the new blueprint work items section. is there a way to assign two people to one task? When I try to put the task twice with different names  against it, launchpad makes all of them the same name
[12:12] <gema> uhmmmm... it seems now it allowed me to, is it me or does it reorder the tasks?
[14:37] <dobey> sinzui: it would be pretty awesome if LP could work correctly in Netscape Navigator 3.04 Gold ;)
[14:41] <sinzui> dobey 3.04 parsed numbers wrong. I suspect that it is imposable for it to ever position content correctly on the screen
[14:42] <dobey> sinzui: it should work fine if you use tables :)
[14:42] <sinzui> Yes. I was pretty angry with how quick tables were subverted to layout tools in 1994
[14:43] <sinzui> I think it took 2 days from the moment Netscape added support for them
[14:43] <sinzui> but I do remember that moment in the Netscape 0.0 beta that I saw an animated GIF. That was really impressive
[14:45] <dobey> CSS is just a complex description of how to draw tables, anyway
[14:47] <sinzui> I don't think so. Positioning and z-index are a very different way of solving layout. Maybe you are referring to display:inline-block which is a really nice way to create a grid without a table
[14:48] <dobey> i mean, for most sites, the end result is the same, and z-order is not necessary.
[15:03] <mgz> the branch <lp:~clint-fewbar/charms/oneiric/statusnet/apparmor> has its stacking borked or similar
[15:07] <dobey> mgz: i guess you should bug SpamapS directly about that?
[15:08] <mgz> checking that no one else is already on the case, it's a known issue with the oneiric charms apparently
[15:14] <mgz> seems like it's currently not being handled, context is:

[15:16] <dobey> stacking looks correct on lp for clint's branch
[15:17] <dobey> it's stacked on lp:charms/oneiric/statusnet
[16:51] <m_3> james_w: ping
[16:52] <james_w> hi m_3
[16:52] <james_w> how's it going?
[16:52]  * m_3 stands around looking guilty :)
[16:52] <m_3> james_w: so... we've got these branches
[16:53] <m_3> james_w: they're frozen still too I think
[16:53] <james_w> yeah
[16:53] <m_3> james_w: any suggestions on who to ask for help here?
[16:53] <james_w> I think that will need a Launchpad change to unfreeze them
[16:53] <czajkowski> m_3: what's up ?
[16:53] <m_3> james_w: and then bzr reconfigure them in a script?
[16:54] <m_3> czajkowski: fundamental problem is that we have a series of branches that're stacked on the wrong bases if I understand correctly
[16:54] <m_3> example:
[16:54] <m_3> lp:~charmers/charms/oneiric/sbuild/trunk
[16:55] <m_3> I try to branch it and it's pointing to the precise branches
[16:55] <m_3> czajkowski: history is... lemme just pastebin the email summary
[16:57] <m_3> czajkowski: http://paste.ubuntu.com/1001230/ summarizes how we got these branches into their current state
[16:58] <czajkowski> ok
[16:58] <jimis> Hello all. Thought you'd like to know: It happens often to me that Launchpad times out when I try to browse big projects. Trying a second time after 30 seconds or so and request succeeds.
[16:58] <m_3> czajkowski: note that I mis-stated what `branch-distro` does in that email... it doesn't just _rename_ the branches
[16:58] <czajkowski> m_3: findibng out how best to help 2 ticks
[16:59] <james_w> ah right
[16:59] <james_w> I don't know if the freezing will mean that we can't fix the stacking
[16:59] <james_w> we can likely get an admin to fix the stacking without having to unfreeze them though
[16:59] <james_w> abentley, hi, I'm sure you will know: how can we fix a branch that is stacked on a non-existent branch due to a rename?
[16:59] <james_w> reconfigure --stacked-on seems to try and activate the fallback, so you have to have a working branch to use it?
[16:59] <m_3> czajkowski: many thanks!!! no particular rush... we need to a.) fix this and b.) make sure we don't do it again next release
[17:00] <czajkowski> m_3: nods just rying to find out as heading away but will get someone first
[17:00] <m_3> james_w: the branches are based on _different_ branches (that also have lp:charms aliases)... not nec non-existent branches
[17:00] <james_w> m_3, for next release an option to branch-distro to set the name to 'trunk' would seem to avoid this?
[17:01] <lifeless> that got wont-fix I think
[17:02] <lifeless> m_3: james_w: Stacking *is not semantic*, it shouldn't matter if oneiric is stacked on precise, as long as it was setup that way using bzr primitives (which will migrate data if needed)
[17:02] <james_w> m_3, for redis-master it is complaining about https://code.launchpad.net/~charmers/charms/precise/redis-master/precise/ which doesn't exist
[17:02] <lifeless> m_3: james_w: The branche should be stacked on +branch/ddddddd urls, not on long path urls.
[17:02] <m_3> james_w: I think that's the target branch for lp:charms/redis-master thought
[17:02] <lifeless> If they are long path urls, something is broken somewhere.
[17:02] <m_3> s/thought/though/
[17:03] <james_w> m_3, no, lp:charms/redis-master points to .../trunk
[17:03] <m_3> james_w: ah, right
[17:03] <james_w> m_3, branch-distro sets up that stacking, so I'm assuming the renaming you did to get /trunk is what broke the stacking
[17:04] <m_3> james_w: right... sounds correct
[17:04] <lifeless> james_w: branch-distro is broken if it set .../trunk
[17:04] <james_w> lifeless, branch-distro is what is broken then
[17:04] <lifeless> james_w: see my prior comment
[17:04] <james_w>     old_location_branch.set_stacked_on_url('/' + new_db_branch.unique_name)
[17:04] <lifeless> it should stack on numeric is
[17:04] <lifeless> *ids*
[17:04] <lifeless> to allow renames to be done.
[17:05] <m_3> lifeless: branch-distro set to /precise... but juju requires /trunk... so we renamed
[17:05] <m_3> lifeless: the rename script is in the email summary (halfway-ish) in http://paste.ubuntu.com/1001230/
[17:06] <lifeless> james_w: yeah, its using unique_name, which is fragile
[17:06] <lifeless> james_w: could you file a bug? Its 5am here...
[17:07] <lifeless> thumper did a project to migrate all existing branches to numeric stacked pointers, and change LP to stack numerically itself.
[17:07] <james_w> https://bugs.launchpad.net/launchpad/+bug/1003016
[17:07] <lifeless> We don't however magically change a symbolic name to a numeric
[17:07] <lifeless> we just provide a good default to bzr's config when it inspects the server
[17:08] <chrisccoulson> who broke armhf? https://launchpadlibrarian.net/105811044/buildlog_ubuntu-quantal-armhf.thunderbird_13.0~b2%2Bbuild1-0ubuntu3_CHROOTWAIT.txt.gz
[17:08] <chrisccoulson> :)
[17:09] <james_w> chrisccoulson, which slave is that?
[17:09] <chrisccoulson> james_w, nihal
[17:10] <james_w> chrisccoulson, cjwatson reported that already, and it's on the list to be hit with a cluebat
[17:10] <chrisccoulson> ah, cool. thanks!
[17:10] <czajkowski> heh
[17:10] <james_w> https://bugs.launchpad.net/launchpad/+bug/1003017
[17:11] <james_w> m_3, do you know if there is a bug about the oneiric branches being frozen?
[17:11] <m_3> james_w: dunno
[17:12] <m_3> james_w: Bug #991980
[17:12] <james_w> thanks
[17:13] <james_w> now that we've filed all the bugs hopefully we can get to fixing the broken branches now :-)
[17:13] <lifeless> james_w: a bug about the wrong stacking location I meant.
[17:14] <james_w> https://bugs.launchpad.net/launchpad/+bug/1003016
[17:14] <lifeless> james_w: we won't fixed the name choice, I don't know the bug number offhand to dupe it.
[17:14] <james_w> already commented with the bug number!
[17:14] <lifeless> james_w: if I'm sloppy right now, its because its 5am ;)
[17:15] <lifeless> james_w: but in this case, I loaded the page before your comment :)
[17:17] <james_w> sure
[17:17] <james_w> how can we fix the stacked on location of these broken branches?
[17:17] <lifeless> re-run the migration script thumper wrote
[17:18] <lifeless> its idempotent
[17:18] <lifeless> need to rename the branches back first.
[17:18] <lifeless> so that it can find and resolve the names
[17:19] <m_3> lifeless: can you point to thumper's migration script?
[17:20] <james_w> m_3, it's in the LP tree, one moment
[17:22] <dobey> is there a way to tell recipes on lp to include the "NubuntuM" part of the version?
[17:23] <james_w> m_3, http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/scripts/update-stacked-on.py
[17:23] <james_w> to be used with http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/scripts/get-stacked-on-branches.py
[17:23] <james_w> dobey, you mean from the changelog?
[17:25] <m_3> james_w: thanks... looking now
[17:25] <dobey> james_w: yes.
[17:26] <james_w> dobey, {debversion}
[17:26] <james_w> dobey, requires format 0.4
[17:27] <dobey> ah ok, cool
[17:27] <dobey> thanks
[17:27] <dobey> james_w: might you also know what LockNotHeld error from bzr means? #bzr seems to be deaf to my cry at the moment :)
[17:38]  * james_w can't hear dobey
[17:38] <james_w> dobey, I don't really know
[17:38] <dobey> heh
[17:38] <dobey> ok
[17:39] <james_w> dobey, possibly that locking isn't being done correctly and the operation in question needs a lock that hasn't been taken, but I think that error is different
[17:39] <james_w> dobey, possibly that the lock on disk isn't the state that bzr thinks it should be
[17:39] <james_w> possibly something else
[17:39] <dobey> hmm
[17:39] <james_w> dobey, getting a backtrace by running with "bzr -Derror" might be useful
[17:40] <james_w> "bzr -Dlock" might be useful too
[17:40] <dobey> james_w: so it's not from bzr the program itself, but from tarmac using bzrlib
[17:40] <james_w> ah, hmm
[17:41] <james_w> dobey, do you have plugins that interact with bzrlib as well by any chance?
[17:41] <dobey> yes
[17:41] <james_w> and is tarmac running on precise?
[17:41] <dobey> yes
[17:42] <james_w> I have no new information for you
[17:42] <james_w> but they are possible sources of the error given that we aren't seeing it without those two things
[17:43] <james_w> class ObjectNotLocked(LockError):
[17:43] <james_w>     _fmt = "%(obj)r is not locked"
[17:43] <james_w>     # this can indicate that any particular object is not locked; see also
[17:43] <james_w>     # LockNotHeld which means that a particular *lock* object is not held by
[17:43] <james_w>     # the caller -- perhaps they should be unified.
[17:44] <dobey> hmm
[17:44] <dobey> that's quite odd
[17:44] <dobey> thanks
[20:09] <milk> howdy. i'm looking to login to my milkmiruku account, but the password reset doesn't work for what i think the address should be. what might my options be?
[20:21] <dobey> what should the address be?
[20:25] <milk_> it should be something @milkmiruku.com. i thought i'd have gone with launchpad@milkmiruku, but it might have been before, but my<EMAIL_ADDRESS>doesn't work either
[20:25] <dobey> milk: perhaps you should check spam folder
[20:28] <milk> och, i tried again with gmail and it worked. prolly pebkac. thanking you.


[07:17] <owaishanif786> hi there
[07:17] <owaishanif786> is there any way to get screenshots via html5 or QML api ?
[07:18] <owaishanif786> "femma"
[07:18] <owaishanif786> "femma1"
[07:19] <owaishanif786> @zzarr
[07:19] <owaishanif786> hi there
[07:19] <owaishanif786> how to use irc :)
[07:26] <kalikiana> hey owaishanif786
[07:26] <kalikiana> from QML you mean programmatically getting a screenshot?
[07:26] <owaishanif786> yes
[07:27] <owaishanif786> whether its QML or javascript I just want to know is there any api access or function for getting screenshots
[07:27] <kalikiana> owaishanif786: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/QtQuick.Item/#grabToImage-method
[07:28] <kalikiana> you basically pass a filename and it gets saved on disk (or memory card)
[07:28] <owaishanif786> thanks let me check it
[11:10] <kalikiana> timp: zsombi zbenjamin: bug 1589903 is the one I mentioned
[13:04] <kalikiana> t1mp: Another one for you: I filed bug 1589982
[13:05] <t1mp> yay..
[13:05] <t1mp> kalikiana: where did the image go?
[13:06] <t1mp> hmm, we have an icon for that now I guess
[13:06] <t1mp> kalikiana: ahh, toolbar. That is not the header. That is the old toolbar at the bottom
[13:07] <t1mp> kalikiana: you are importing 1.1 there, not 1.2
[13:08] <kalikiana> t1mp: there is no MainView in 1.1 :-)
[13:09] <kalikiana> I guess I should mention, for clarity, that the code is the 1.2 version
[13:09] <t1mp> hmm
[13:09] <t1mp> there is a MainView 1.1, but the source is indeed 1.2/MainView
[13:09] <t1mp> .qml
[13:10] <kalikiana> There is no MainView 1.1
[13:10] <kalikiana> not even in qmldir
[13:10] <kalikiana> anyway I updated the description
[13:19] <t1mp> kalikiana: MainView 1.0 1.2/MainView.qml
[13:19] <t1mp> 1.1 falls back to 1.0 which is 1.2 ;)
[13:19] <kalikiana> Yes
[13:20] <kalikiana> 1.1 has no MainView, I stand by that
[13:20] <kalikiana> And it's wonderfully confusing, we should do stuff like that in 1.3, it's too straightforward
[14:26] <sverzegnassi> Elleo: Hi! I'm playing with CuteSpotify sources and I have some doubt about the libQtSpotify branches on GitHub. Could you suggest me which one I should pick?
[18:29] <aldrog> hi
[18:30] <aldrog> can anyone here tell me if it's possible to package a gstreamer plugin within a click package?
[18:31] <aldrog> (considering I don't use gstreamer directly, but through QtMultimedia)
[18:34] <popey> jhodapp: ^ maybe one for you?
[18:57] <jhodapp> aldrog, not that I'm aware of
[18:57] <jhodapp> aldrog, well not sure that it's not possible, but don't believe it's been done before
[18:57] <jhodapp> I would think that it would be possible, but have not tried it myself
[18:58] <aldrog> I'm just completely unfamiliar with click so have no idea what to try
[19:00] <jhodapp> aldrog, yeah and I as well have no experience packaging with click...so sounds like someone who knows click better would be a good person to talk to
[19:00] <jhodapp> aldrog, what exactly would you like to try to do?
[19:01] <aldrog> jhodapp, I'm building a client for streaming service which uses hls
[19:01] <aldrog> jhodapp, and hls is in bad gst plugins, which are not included in UT
[19:01] <jhodapp> aldrog, cool, well we have a story for my team next sprint which will investigate what we can ship by default from gst-plugins-bad...HLS being one of the main investigation points
[19:02] <jhodapp> aldrog, and we'll also be testing out upgrading to gstreamer 1.8.x for the phone image
[19:03] <aldrog> jhodapp, yeah, i've seen gstreamer upgrade being discussed on ubuntu-phone mailing list
[19:04] <aldrog> jhodapp, and it would be really cool if HLS was supported out of the box
[19:07] <jhodapp> aldrog, yeah so I'd say hold off trying to package in a click for now and hold tight while we try and resolve these issues in the backend itself
[19:07] <jhodapp> aldrog, I'd recommend joining #ubuntu-media as well...we media guys hang out in there
[19:09] <aldrog> jhodapp, thanks for info and advices :)
[19:10] <jhodapp> np
[19:48] <Guest94099> hi


[03:21] <mcasadevall> lool, mesa built successfully in launchpad-buildd on babbage 2
[03:21] <mcasadevall> lool, I believe I can officially say argh
[04:17] <Sarvatt> 10 hours mcasadevall?
[04:18] <mcasadevall> Build needed 03:44:36, 1393092k disk space
[04:18] <mcasadevall> Nope
[04:18] <mcasadevall> SOmething has got seriously wrong on the actual buildds ...
[04:19] <Sarvatt> ahh was like 12:30 my time when we were talking about it so thought it might have actually taken the 10+ hours
[09:17] <lool> mcasadevall: Could you bring this up with IS?
[09:56] <ogra> hmm, doesnt look if i gained much with more ram for debootstraps second stage ... its simply the lack of CPU making it slow
[10:08] <ogra> hmm, ok, the unpacking surely is faster
[10:37] <ogra> wow, locale-gen is gotten a lot faster
[10:40] <ogra> real	51m49.350s
[10:40] <ogra> user	48m31.682s
[10:40] <ogra> sys	0m21.285s
[10:40] <ogra> not to bad for an ubuntu-minimal
[10:41]  * ogra comments all the swap stuff and runs it again
[11:37] <ogra> real	51m9.016s
[11:37] <ogra> user	47m42.963s
[11:37] <ogra> sys	0m22.133s
[11:37] <ogra> hmm, no significant difference
[11:38] <ogra> so guess i'll leave the swap part in but dont add the ugly bits that make it be used *before* debootstrap runs
[11:39] <ogra> since that requires to unpack busybox-static in the choot before switching to VM to have swapon available before a system exists
[11:47] <ogra> meh /me wants a --to-the-rim option for dd so it only fills a file up to the max available space on the target device
[11:57] <lool> ogra: What's the status of the banshee bug?
[11:58] <ogra> dyfet, is looking into it atm
[11:58] <lool> ogra: Why are you assigned?
[11:59] <lool> dyfet: hey what's the status of the banshee bug?
[11:59] <ogra> should i reassign ?
[12:00] <lool> ogra: What do you think?
[12:00] <ogra> well, i felt responsible for it even though dyfet looks into it atm
[12:07] <lool> ogra: If you're responsible for it, could you please give me a more detailed status update?  There's nothing in the bug
[12:07] <lool> I don't know what's being investigated, what are the current results etc.
[12:08] <lool> The fact that dyfet is looking into it is mentionned nowhere
[12:08] <ogra> well, i asked dyfet to take a look and pointed him to the vorbis error
[12:09] <lool> ogra: When was that?
[12:09] <lool> ogra: Could you please document that in the bug itself?
[12:10] <ogra> that was two days ago, i'll add info to the bug
[12:11] <lool> ogra: Thanks
[12:11] <lool> ogra: What about the debian-cd specs (subarches and mx51 changes); will this happen for Alpha 3?
[12:12] <ogra> i'd really like to have a prototype but without the HW its not that easy to work out a uboot layout
[12:14] <lool> ogra: Did you test Uboot on the lange?
[12:15] <lool> ogra: I don't think the subarch changes need any hardware though
[12:15] <lool> ogra: Are the Uboot packages ready?
[12:15] <ogra> i tested the binary image we had
[12:15] <ogra> but that didnt work
[12:15] <lool> Ok
[12:15] <ogra> was waiting until NCommander has his binary through NEW
[12:15] <lool> So it's in NEW? good
[12:15] <ogra> he told me tue. its sitting there
[12:16] <lool> ogra: So what about the armel -> armel+mx51 changes?
[12:16]  * ogra sighs ... calling cleanup on 0 1 2 3 9 11 13 15 has intresting sideeffects
[12:17] <ogra> lool, i want to have uboot-install separately
[12:17] <lool> Yes?
[12:17] <ogra> so i'm blocking on the layout as i mentioned above
[12:17] <lool> Well you could rename the script first
[12:17] <lool> That makes room for the Marvell stuff in parallel
[12:18] <ogra> grmbl, why is cleanup called multiple times now
[12:18] <ogra> lool, ok, i'll do the renaming this week
[12:19] <lool> Ok thanks
[12:37]  * ogra slaps forhead
[12:37]  * ogra removes "exit 0" from the end of cleanup() and goes to a corner to cry
[12:45] <ogra> grmbl now it doesnt exit properly
[12:46]  * ogra curses, it was all working before
[12:47]  * ogra re-adds the cleanup acll at the end of the script
[12:48] <ogra> trapping on 0 is simeply not working right
[13:24] <kod-e> hi all
[14:06] <lool> dyfet: Hey when you come up, could you update the banshee bug with your findings?
[14:06] <lool> ogra: trap 0 works fine for me   :-)
[14:07] <dyfet> lool: yes...but I dont have update yet...I was fighting hw part of yesterday to get karmic setup on it :)
[14:07] <ogra> lool, i have massive probs with all the traps here
[14:08] <ogra> if i trap out of run_vm it essentially does nothing
[14:08] <ogra> well, it prints the "Cleaning up..." but exists immediately
[14:11] <ogra> everywhere else trapping works fine
[14:12] <ogra> well, thats not actually right, trapping works in run_vm if the vm actually runs but not while wget runs or the vm is just starting up
[14:12] <Sarvatt> so is marvell support going to be kept in karmic?
[14:13] <ogra> kept ?
[14:13] <ogra> its being added
[14:14] <Sarvatt> ah, new kernel flavor? i just meant the armv5, didn't know if it was going to go v6 or v7 only during karmic
[14:14] <ogra> it will be v6
[14:15] <Sarvatt> oh wow, i should have read up more on sheeva
[14:17] <lool> Sarvatt: Right, Sheeva wont work
[14:17] <lool> Sarvatt: We didn't support any marvell flavour last cycle
[14:18] <lool> I find it unfortunate that we're not supporting v5, but we're targetting high end ARMv7 netbooks/hardware so it makes sense to rip the benefits of the new instructions
[14:19] <ogra> lool, swap stuff pushed btw, feel free to edit away
[14:23]  * ogra builds a desktop image to see how swap affects it
[14:24] <rjune_wrk> Morning ogra
[14:24] <ogra> grmpf, why does it die now
[14:24] <ogra> hmm, swapsizes above 1G seem to be no good idea
[14:33] <Sarvatt> i'm so confused, marvell says "It contains advanced three-level branch prediction, a variable stage pipeline, and an integrated memory controller, providing unmatched high-end performance and low-power requirements. Compliant with the Cortex A8, Sheeva also supports both the ARMv6 and ARMv7 instruction sets, making it the world's first dual ARM ISA compatible CPU." but the docs for the sheevaplug say its a Sheeva 88SV131 ARM v5TE Pro
[14:33] <Sarvatt> cessor Core with MMU and L1/L2 Cache
[14:34] <ogra> the docs are right
[14:41] <Sarvatt> so moral of the story is, if i buy one make a copy of the archive now before things move to armv6? :D
[14:41] <suihkulokki> the moral of the story is to switch to debian \o/
[14:42] <suihkulokki> Sarvatt: marvell is saying that sales stuff that they can produce ARMv6/ARMv7 cpu's based on sheeva tehnology, but their current cores are are ARMv5
[14:44] <suihkulokki> s/sales stuff that//
[14:46] <Sarvatt> yeah for armv5 i guess thats the best option, i really would like to get a v7 to play with instead but the sheevaplug looks like a better option for me for the price right now vs a beagleboard and i'm starting to get convinced other platforms arent going to come out anytime soon at a decent price :D
[15:15] <lool> ogra: Hmm you seem to assume all vars aren't set in the env
[15:15] <lool> ogra: You should be init-ing things like SWAPFILE or NOSWAP
[15:16] <ogra> with ="" ?
[15:16] <ogra> hmm
[15:16] <ogra> thats a lot of extra empty lines ...
[15:16] <lool> They are not "extra"
[15:16] <ogra> heh
[15:16] <ogra> yeah
[15:16] <ogra> i'll add them
[15:16] <lool> ogra: Since the script is so young you could still consider set -U
[15:17] <rjune_wrk> what does set -U do?
[15:17] <lool> sorry set -u
[15:17] <lool> rjune_wrk: It errors out if you use an undefined var in an expansion
[15:17] <rjune_wrk> Ahhh
[15:17] <rjune_wrk> IOW, a very good habit.
[15:18] <lool> A bit hard to retrofit in some pieces of code
[15:18] <rjune_wrk> I believe that.
[15:18] <Sarvatt> ogra: what cpu was rootstock (well qemu-arm) using by default before the cortex-a8 change?
[15:19] <ogra> Sarvatt, the default versatile one
[15:19] <ogra> it didnt specify -cpu before
[15:20] <ogra> arm926 i belive
[15:20] <Sarvatt> guess it uses "any" if you dont specifiy?
[15:20] <Sarvatt> ah
[15:22] <Sarvatt> its just nuts how much faster it is doing the second stage in a chroot in the android qemu (like 5 minutes there)
[15:22] <ogra> what cpu is that ?
[15:22] <ogra> (specifically at what speed does it run)
[15:23] <ogra> i havent gotten qemu to do more than 200MHz here
[15:23] <ogra> (on arm)
[15:30] <Sarvatt> checking, battery about to die brb
[15:40] <Sarvatt> http://sarvatt.com/downloads/emulator.txt
[15:41] <ogra> BogoMIPS	: 736.22
[15:41] <Sarvatt> thats on my faster pc that took almost 5 hours with rootstock the other day, will check what it is on the one i just built it on in a sec (atom cpu) :D
[15:43] <Sarvatt> BogoMIPS	: 85.40
[15:43] <ogra> right, thats a bit of a differentce
[15:43] <ogra> *difference
[15:43] <Sarvatt> its QEMU PC emulator version 0.8.2
[15:44] <Sarvatt> but it builds fast on this 85 bogo mips one which is the weird part
[15:44] <ogra> do you see the cpu speed in dmesg ?
[15:46] <ogra> i'd really love to speed up debootstrap ... the rest runs totally fine, but the --second-stage processing is awful
[15:46] <Sarvatt> http://sarvatt.com/downloads/emu-dmesg.txt
[15:47] <Sarvatt> sorry, I had 512mb memory when I did it
[15:48] <ogra> hmm
[15:48] <Sarvatt> only 96 in that dmesg
[15:48] <ogra> right, that means their qemu is hacked up i guess
[15:49] <Sarvatt> yeah it is quite alot, thats why they havent upgraded it since theres so many changes against the old version
[15:51] <Sarvatt> http://android.git.kernel.org/?p=platform/external/qemu.git;a=summary
[15:52] <Sarvatt> doesn't help they do most of the development in a private perforce vcs and just import it in batches every now and then
[15:53] <ogra> yeah
[15:53] <ogra> not very clean
[15:53]  * ogra rolls a qemu with lool's 512M patch and checks if that changes anything
[15:54] <ogra> i was trying to add a gig of swap today, but that didnt make any speed difference
[15:55] <ogra> (using awful hacks that added the swapspace before debootstrap runs)
[15:57] <lool> Sarvatt: Oh Google also patches qemu for 512MB of RAM?  interesting
[15:58] <Sarvatt> they have a custom platform that allows it I think?
[15:58] <Sarvatt> not using versatile
[15:58] <ogra> ah
[15:59] <ogra> lool, did you notics any speed improvement with your patch
[16:00] <lool> ogra: For what?
[16:00] <ogra> qemu debootstrapping
[16:00] <lool> I didn't load qemu with heavy workloads, so no
[16:00] <ogra> ah
[16:00] <lool> I don't think 256M or 512M make any difference for a debootstrap
[16:01] <ogra> it might make a difference to the dpkg database processing
[16:01] <ogra> it hangs endelss in the preprocessing in rootstock
[16:01] <ogra> *endless
[16:03] <Sarvatt> neat, XenARM has a paravirtualized goldfish platform from android qemu
[16:34] <ogra> lool, hmm, your qemu patch doesnt work if applied against our package it seems :/
[16:34] <ogra> DEBUG registered size=10000000 SDRAM at 0x0 with offset (nil)
[16:34] <ogra> Not enough memory (requested_size = 268435456, max memory = 268435456)
[16:49] <ogra> hmm, there seems to be a bunch of stuff missing in the patch
[17:09] <ogra> lool, do you remember against which 0.10 version you made the qemu patches ?
[17:22] <ogra> hrm, i suspect we apply some patch that breaks it
[17:31] <lool> ogra: Against tip
[17:31] <ogra> oh, i thought you did it against 0.10.x
[17:31] <lool> ogra: No, it wont work against 0.10
[17:32] <ogra> yes, i see that
[17:32] <lool> memory management was redone and didn't allow for split memory banks in <= 0.10.x
[17:32] <ogra> aaahh
[17:43] <lool> ogra: Is it you or NCommander working on the gnome-keyring bug?
[17:44] <ogra> on my list
[17:44] <lool> NCommander: hey when do you usually roll the wiki page for next meeting?
[17:44] <ogra> i need some more deskspace for the B1 though
[17:44] <lool> NCommander: I'd like to add a couple of topics early in the agenda
[17:44] <ogra> lool, i think he does it 10mins before the meeting :P
[17:53] <lool> NCommander: Ah it would be cool if you could roll the pages now; otherwise I can send you topics by email
[18:08] <NCommander> lool, I'll roll it a little later today (I usually do it a day or two after the meeting)
[18:09] <NCommander> lool, just shoot me an email and I'll amend the pages
[18:09]  * NCommander has to add somethinge sel as well
[18:13]  * ogra wasnt aware NCommander speaks french
[18:15] <lool> NCommander: sent
[18:15]  * ogra just remembered that sel is salt in french :)
[18:16]  * NCommander knows no human language expect English
[18:16] <ogra> lol
[18:16] <ogra> partially at least :)
[18:17] <NCommander> *grumble*
[18:17] <ogra> wow, the tip qemu just trashed my filesystem in the image completely
[18:17] <NCommander> o____o;
[18:18]  * ogra takes another img ...
[18:18] <ogra> after the last two days i have plenty of them
[18:18] <ogra> /etc/init.d/rc: line 74: /etc/default/rcS: No such file or directory
[18:18] <ogra> error: '/etc/init.d/rc' exited outside the expected code flow.
[18:18] <ogra> init: rc-sysinit main process (379) terminated with status 1
[18:18] <Sarvatt> wow yeah i'm doing a second stage in 256mb ram and its alot slower
[18:18] <ogra> geeez
[18:18] <NCommander> o]______-o;
[18:21]  * ogra sees no difference with 512M in qemu yet
[18:25] <ogra> still sitting there ... doesnt move
[18:25] <ogra> but i wasnt really expecting a difference through more ram
[18:26] <ogra> that would have shown with the swap this morning already
[18:27] <Sarvatt> i have the gui up this time too though, thats eating alot of the cpu time. 13% phone 11% alarm clock 9% google apps 21% dpkg kernel time 7% user 34% debootstrap user 14% kernel
[18:28] <ogra> well, you are bootstrapping from a running system
[18:28] <ogra> tahts a bit different anyway
[18:33] <Sarvatt> hmm 141mb ram inactive, really doesnt need more ram.. its quite nice how in depth the android debugger is for profiling
[18:35] <Sarvatt> ahhh i think the android environment tries to keep 50% ram free
[18:45] <mcasadevall> lool, ogra, 13563 mcasadev  20   0  372m 367m   64 R 69.6 72.9   7:14.26 lzma
[18:45] <mcasadevall> Looks like lzma is sucking down the machine's resources
[18:45] <mcasadevall> and is paging out
[18:49] <NCommander> wait a tick
[18:49] <NCommander> never mind
[19:08] <lool> mcasadevall / NCommander: You said yesterday it was working fine?!
[19:08] <NCommander> lool, on my boards, I didn't build on rimu
[19:08] <NCommander> lool, but the build passed on both rimu w/ dpkg-buildpackage, and under launchpad-buildd on my B2
[19:08] <lool> So on rimu it's slow but on our boards it's not
[19:08] <NCommander> lool, it passed though, 4 hours, no hang
[19:08] <NCommander> (the build took 3:40 on my boards)
[19:08] <lool> 4 hours is about the same you got and shorter than on the buildds
[19:08] <NCommander> Right
[19:09] <lool> NCommander: Chase IS to see what is different?
[19:09] <NCommander> lool, infinity just went WTF when I told him it passed
[19:09] <NCommander> since it shouldn't
[19:09] <NCommander> rimu is setup the same way as the buildds expect access permissions, and it doesn't have launchpad-buildd