[03:56] <thomi> bschaefer: pong from earlier... although it's a holiday for me :)
[03:56] <bschaefer> yeah I looked it up :)
[03:57] <bschaefer> thomi, no worries, I just got done with class.
[03:57] <bschaefer> I can talk to you tomorrow if you want a day off ;)
[03:57] <thomi> it's cool - I'm about to start hacking on some personal projects
[03:57] <bschaefer> cool!
[03:58] <thomi> So, Ctrl+Space isn't activating ibus in the VM huh?
[03:58] <thomi> that's odd
[03:58] <bschaefer> Im excited to start one up soon
[03:58] <bschaefer> yeah
[03:58] <bschaefer> if you look at the error messge
[03:58]  * bschaefer goes to get it...
[03:58] <thomi> bschaefer: heh, if you're looking for something to do I can suggest several projects for you :P
[03:59] <thomi> bschaefer: I wonder if we can get a test system that's closer to the one that jenkins runs on - maybe we can reproduce some of these intermittently failing tests as well.
[03:59] <bschaefer> thomi, well I might be writing a compiler this summer, or using nux to make a maze solver/generator
[03:59] <thomi> ahh, cool
[03:59] <bschaefer> thomi, AssertionError: After 10 seconds test on SearchBar.im_active failed: True != dbus.Boolean(False, variant_level=1)
[03:59] <bschaefer> so
[03:59] <bschaefer> fails on this line AssertionError: After 10 seconds test on SearchBar.im_active failed: True != dbus.Boolean(False, variant_level=1)
[03:59] <bschaefer> opps
[03:59] <bschaefer> didn't copy haha
[04:00] <bschaefer>   self.assertThat(widget.im_active, Eventually(Equals(True)))
[04:00] <thomi> yeah, so either ibus isn't being activated, or we're not getting the signal
[04:00] <bschaefer> yeah
[04:00] <thomi> I wonder if there's anything we can do to narrow down the cause?
[04:00] <bschaefer> I was thinking maybe a key is getting held down but I couldn't find a key that you could hold downt o cause that
[04:00] <bschaefer> yeah I was wondering that too
[04:00] <thomi> you should be able to see the timings in the test log
[04:01] <bschaefer> so it fails on waiting for ibus to be true
[04:01] <thomi> it logs a line every time it presses and releases a key
[04:01] <bschaefer> hmm
[04:01] <thomi> maybe the delay is too long or something?
[04:01] <bschaefer> well I wanted to add some debuging messages in but I guess you need to merge it to trunk for that
[04:01] <bschaefer> thomi, but it works locally
[04:01] <bschaefer> well
[04:01] <bschaefer> let me try a super long wait
[04:01] <thomi> good idea
[04:02] <bschaefer> ooo thomi hold down ctrl+space
[04:02] <bschaefer> just hold it down and look at the indicator
[04:02] <thomi> I don't get an indicator... hang on
[04:03] <bschaefer> hmm well it toggles on/off
[04:03] <bschaefer> and I got a random crash doing that...
[04:03] <thomi> yeah, I see
[04:03] <bschaefer> very odd that it doesn't fail on the local build though
[04:04] <bschaefer> I tried it in my VM today also
[04:04] <thomi> can you do some subtraction from the trimestamps in the test log and see if the timings are unreasonable?
[04:04] <bschaefer> lowering the ram to like 300 mb
[04:04] <bschaefer> well it hold it for 0.2
[04:04] <bschaefer> which I think is like 200 ms?
[04:04] <thomi> yeah
[04:05] <bschaefer> that seems fast to me
[04:05] <thomi> that doesn't seem unreasonable to me
[04:05] <bschaefer> yeah
[04:05] <bschaefer> I wonder
[04:05] <thomi> heh, I was going to say it's on the slow side :)
[04:05] <bschaefer> if the VM is just slow
[04:05] <bschaefer> though
[04:05] <thomi> that's 1/5 of a second.
[04:05] <bschaefer> yeah haha, but I/O is always slow haha
[04:06] <bschaefer> hmm
[04:06] <bschaefer> Ill see what happen is I just set it to 0.0
[04:06] <bschaefer> or maybe 0.05 haha
[04:07] <bschaefer> thomi, we should have a dx-autopilot-test-jenkins
[04:07] <bschaefer> not being able to debug the VM is not very nice
[04:08] <thomi> bschaefer: if you want to set it up I'm sure we can make it happen
[04:08] <thomi> ... or even set it up on our own jenkins instance.
[04:08] <bschaefer> thomi, Ill have to look into that but that would be awesome
[04:08] <bschaefer> I also need to show you how I set up a VM for unity 3d
[04:08] <bschaefer> thomi, also do you know when the last time the VM was reset?
[04:09] <thomi> I have a jenkins instance for my own projects. I'll talk to people and see how hard it'll be to get running on the PA jenkins machine
[04:09] <bschaefer> like just rebooted
[04:09] <thomi> it gets reset each run
[04:09] <thomi> the dx-autopilot-build-nfsroot job reboots the machine and boots it with a clean image
[04:09] <thomi> ...but that's not the case if we just trigger the dx-autopilot-run job directly
[04:10] <bschaefer> hmm good
[04:10] <bschaefer> I just want to eliminate as many possible problems as possible
[04:11] <bschaefer> thomi, hmm it seems to work at 0.05
[04:11] <bschaefer> ill push it 0.0
[04:12] <thomi> ...assuming the issue is that it's too slow. Worth a shot though
[04:13] <bschaefer> yeah
[04:13] <bschaefer> and 0.0 works fine locally
[04:13] <bschaefer> thomi, there are also some debugging messages in nux I could uncomment....
[04:13] <bschaefer> but I don't want to push just debugging messages to nux trunk
[04:14] <thomi> bschaefer: hmmmm. It'd be nice if there was a copy of the jenkins job we could customise...
[04:14] <bschaefer> yeah I know...all I want is to be able to reproduce this problem
[04:14] <bschaefer> ALL of the test are failing
[04:14] <bschaefer> but I cant get 1 to produce anything jenkins says...
[04:14] <bschaefer> and it is very constant
[04:15] <thomi> hmmm
[04:15] <bschaefer> im just trying to think of anything that could cause that
[04:15] <thomi> if you were feeling brave you could recreate the jenkins config on your local machine
[04:15] <bschaefer> sure, I can set up a VM haha
[04:15] <bschaefer> I actually have a  VM I can toast
[04:15] <thomi> do you have access to the private jenkins instance?
[04:15] <bschaefer> no :(
[04:16] <bschaefer> I could walk you through how to setup a VM sometime soon
[04:16] <bschaefer> though I use windows for my VM
[04:16] <thomi> OK, I can grab the job details and paste them somewhere for you
[04:16] <bschaefer> ok cool
[04:23] <bschaefer> thomi, ugg my schools internet is crap
[04:23] <thomi> :(
[04:24] <bschaefer> just randomly kicked off, anyway did I miss anything?
[04:24] <thomi> nope
[04:24] <bschaefer> cool
[04:24] <thomi> I made fun of you, but that was it
[04:24] <bschaefer> Im happy I missed that then
[04:25] <bschaefer> hmm should I push these ibus test with the time press set to 0.0?
[04:25] <bschaefer> im also wondering if I could use nux to time the inbetween im_active gets active
[04:25] <bschaefer> and deactive
[04:26] <bschaefer> but that might not even be the problem :(, you would think it would work at lease once if it was a timing issue
[04:27] <thomi> bschaefer: I think ideally we'd be able to reproduce the issue before pushing random changes to trunk.
[04:27] <thomi> bschaefer: maybe push 0.1 or 0.05 instead? seems like a more sensible change
[04:28] <bschaefer> thomi, and guess what I did :)
[04:28] <bschaefer> I set the time to 1.0
[04:28] <bschaefer> and it seem to mimic those that problem
[04:28] <thomi> oooh, that's interesting
[04:28] <bschaefer> let me run the Ignore test to see if that works
[04:29] <bschaefer>     self.assertThat(widget.im_active, Eventually(Equals(True)))
[04:29] <bschaefer> AssertionError: After 10 seconds test on SearchBar.im_active failed: True != dbus.Boolean(False, variant_level=1)
[04:29] <bschaefer> :)
[04:29] <bschaefer> both failed
[04:30] <thomi> cool!
[04:30] <bschaefer> ok
[04:30] <thomi> would be interesting to see where the cutoff point is
[04:30] <bschaefer> so, why does 0.2 work for us but not jenkins?
[04:30] <bschaefer> yeah
[04:30] <bschaefer> Ill start going closer to 0.2
[04:30] <thomi> bschaefer: probably because the jenkins instance is slow, so it's closer to 0.4 or somthing
[04:32] <bschaefer> thomi, ooo you were sooo close
[04:32] <bschaefer> it is 0.5
[04:32] <bschaefer> that is start failing fo re
[04:32] <bschaefer> for me*
[04:32] <bschaefer> could be 0.4 on a different machine
[04:33] <bschaefer> thomi, but to be honest that seems like a bug in nux to me
[04:33] <bschaefer> I don't think it should toggle like that...
[04:33] <thomi> bschaefer: probably to do with the tap detection code
[04:33] <bschaefer> yeah, or lack of
[04:33] <bschaefer> im not sure if there is one
[04:33] <thomi> better not say that too loud, the compiz guys will ragequit
[04:33] <bschaefer> haha
[04:33] <thomi> bschaefer: ok, so maybe push a branch that sets it to 0.05 or so
[04:34] <bschaefer> alright, hopefully that helps!
[04:34] <thomi> ping me when you have a MP to review
[04:34] <bschaefer> ok
[04:40] <bschaefer> thomi, https://code.launchpad.net/~brandontschaefer/unity/ap-ibus-shorten-timer/+merge/103407
[04:41] <bschaefer> also what were some other side projects were you doing?
[04:41] <thomi> bschaefer: approved
[04:41] <thomi> bschaefer: right now I'm working on http://launchpad.net/sloecodfe
[04:41] <bschaefer> cool, this should fix 32 failures!!
[04:41] <thomi> *sloecode
[04:42] <bschaefer> thomi, that looks awesome
[04:42] <bschaefer> I actually need to learn something about networking
[04:43] <thomi> bschaefer: we have a todo list that's insanely long :)
[04:43] <thomi> so uhh... "patches welcome" :)
[04:43] <bschaefer> thomi, I might take a look :)
[04:43] <thomi> we hang out in #sloecode
[04:43] <bschaefer> I also might have to wait until I graduate
[04:44] <bschaefer> I do to many things atm haha, being a TA/Tutor takes  a lot of time along with classes and working here
[04:45] <thomi> yeha
[04:45] <thomi> *yeah
[04:46] <bschaefer> Ill stop by that irc room when I get a chance
[04:47] <bschaefer> it is getting a bit late here and I should go eat
[04:47] <bschaefer> thomi, do you know when the next jenkins test should run?
[04:47] <bschaefer> I suck at waiting..
[04:47] <thomi> bschaefer: nope, shouldn't be too long though
[04:48] <thomi> if you're running indicator-jenkins you can get a helpful popup :)
[04:48] <bschaefer> cool, Ill check after dinner
[04:48] <bschaefer> oo
[04:48] <bschaefer> i should install that
[04:49] <bschaefer> well im off to relocate back home, have fun programming :)
[07:12] <tsdgeos> didrocks: ping-y
[07:20] <didrocks> tsdgeos: hey hey
[07:21] <tsdgeos> didrocks: was wondering, might it be that the merger thingy gets confused when a branch name is a subset of another?
[07:21] <tsdgeos> yesterday we merged https://code.launchpad.net/~aacid/unity-2d/load_24bit_pixbuf_icons_2
[07:21] <tsdgeos> and https://code.launchpad.net/~aacid/unity-2d/load_24bit_pixbuf_icons was incorrectly set to merged, Gerry had to put it back to needs review
[07:21] <didrocks> tsdgeos: it's not the merger it's launchpad AFAIK
[07:22] <tsdgeos> ah
[07:22] <didrocks> if it sees commits that are in trunk, it triggered the status to "merged"
[07:24] <tsdgeos> ok :-/
[09:07] <nik90> hi, I am reading a bug report where a user's application and music daemons are not running
[09:07] <nik90> how do I ask him to start them?
[09:07] <nik90> so basically unity-applications-daemon and unity-music-daemon not running as background processes
[09:17] <davidcalle> mhr3, hey
[09:17] <mhr3> davidcalle, hey, awesome you here, wanted to ask you something :)
[09:18] <davidcalle> mhr3, ok, you first :)
[09:18] <mhr3> davidcalle, https://bugs.launchpad.net/bugs/953871
[09:18] <mhr3> is the lens doing something it shouldn't?
[09:18] <mhr3> or is that us?
[09:18] <mhr3> or perhaps it's not doing something it should ;)
[09:20] <davidcalle> mhr3, should be invisible... I don't remember, is there an entry in the .lens for this? Because it's not set, so that may be the issue here.
[09:20] <mhr3> davidcalle, yea, it should have Visible=false
[09:21] <davidcalle> mhr3, ok, fixed. People will have it in a few hours.
[09:21] <mhr3> ultimately we should be clever there, but we ain't so lenses need to provide this info :)
[09:22] <davidcalle> mhr3, I feel like it's the third time I'm fixing this o_o Must be forgetting to push it each time.
[09:22] <mhr3> heh :)
[09:22] <davidcalle> mhr3, is it possible to reload only one filter, without changing the state of the others?
[09:23] <mhr3> it *should*
[09:23] <mhr3> last time i was talking about it with ken, he said that unity doesn't react to the changes
[09:23] <davidcalle> mhr3, I see.
[09:23] <mhr3> and i don't remember anyone fixing it on unity side
[09:24] <mhr3> davidcalle, try removing the filter and then re-add it
[09:24] <davidcalle> mhr3, ok.
[09:24] <mhr3> although that will change the order i guess :/
[09:26] <mhr3> davidcalle, still, i think it should be possible to even remove all the filters and re-add them (if you keep the original references the state wouldn't change iirc)
[09:27] <davidcalle> mhr3, yeah, that's what I was going to do.
[09:43] <nik90> mhr, can you please look at https://bugs.launchpad.net/bugs/987689
[09:43] <nik90> its regarding the application and music lens daemon not running
[09:45] <davidcalle> nik90, if the icons are missing, the lens have probably been uninstalled for some reason. Do you have unity-lens-music installed?
[09:45] <nik90> davidcalle, apparently the user states that both are installed but the daemons are not running for some reason
[09:46] <nik90> davidcalle: he checked the existence of the package using apt-cache policy unity-lens-application
[09:48] <davidcalle> mhr3, what do you think ? ^
[09:49] <nik90> maybe I should ask him to just try unity --reset and see if it solves his problem??
[09:50] <mhr3> starting the lens daemons manually will probably spit some error
[09:51] <mhr3> would be nice to know what kind of
[09:51] <mhr3> nik90, ^^
[09:52] <nik90> mhr, how do you start the daemon manuall?
[09:52] <nik90> manually*
[09:54] <mhr3> /usr/lib/unity-lens-applications/unity-applications-daemon
[09:54] <davidcalle> /usr/lib/unity-lens-music/unity-music-daemon
[09:55] <nik90> mhr, davidcalle..nice synchronisation :)
[09:55] <nik90> I'll inform the user
[09:55] <nik90> thnx
[13:55] <mhall119> more Hello Unity updates: http://mhall119.com/2012/04/hello-unity-episode-3-4/
[14:10]  * mfisch just gave a presentation on Singlet
[14:10] <mfisch> it was well received
[14:10] <mhall119> mfisch: awesome@
[14:10] <mhall119> !
[14:10] <mfisch> mhall119: they wanted to know if singlet was here for the long haul, and I said yes, but of course have no proof
[14:11] <mfisch> mhall119: the best part is that I presented it as "Singlet" and "The Old Way"
[14:13] <mhall119> mfisch: it's here at least as long as I am, which I certainly hope is long haul :)
[14:13] <mhall119> "The Old Way" isn't quite accurate
[14:14] <mfisch> mhall119: true
[14:14] <mfisch> mhall119: the "traditional way"
[14:15] <mhall119> it's also the only way for non-Python lenses and scopes, or anything more complex
[14:44] <seb128> mhr3, hey, do you know if bug #915203 is a lens side issue? a design decision?
[14:44] <seb128> mhr3, i.e having limited number of songs and albums listed
[14:45] <mhr3> seb128, i'm sure would like to put 20 thousand items in the lens, people who implemented the lens didn't
[14:45] <mhr3> ..design would like...
[14:46] <seb128> mhr3, ok, so unity-lens-music is the right component? i.e it's coming from the backend side?
[14:46] <mhr3> yes, its implemented to list only up to 100 items
[14:47] <seb128> mhr3, thanks
[15:15] <hyperair> any lightdm devs around?
[15:15] <hyperair> how does lightdm find out what wallpaper the user is using?
[15:17] <mdeslaur> hyperair: it asks accountsservice IIRC
[15:17] <hyperair> mdeslaur: i see. is it possible to get lightdm to pull the entire wallpaper image through this as well?
[15:18] <hyperair> mdeslaur: if you use a custom wallpaper in your $HOME (i don't see where else you would put it) and chmod o-r $HOME, lightdm refuses to log in.
[15:18] <hyperair> not getting the wallpaper is one thing, but not being able to log in is ridiculous
[15:18] <hyperair> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/987614
[15:18] <hyperair> we have this bug here
[15:18] <mdeslaur> hyperair: well, that's a bug. It should be able to obtain the wallpaper so it doesn't bypass permissions, but shouldn't fail either
[15:18] <mdeslaur> s/should/shouldn't/
[15:19] <hyperair> it looks like background.vala:138 loads it directly in the unity greeter process
[15:19] <mdeslaur> hyperair: I'm not a lightdm developer, can't help you any further
[15:20] <hyperair> ah, okay thanks anyway
[15:51] <mfisch> mhall119: do you have a simple example of something too complex for singlet?
[15:58] <mhall119> mfisch: the video lens would be one
[15:58] <mfisch> mhall119: whats the reason?
[16:02] <mfisch> mhall119: trying to think of an example to tell people and explain why
[16:04] <mhall119> mfisch: mostly just because Singlet only covers simple cases
[16:04] <mhall119> you can do more complex stuff using Singlet, but you don't get any real benefit from using Singlet at that point
[16:05] <mhall119> it's like Quickly, good for small fast development, but once you reach a certain size it doesn't do you much good anymore
[16:21] <mfisch> got it
[18:19] <bschaefer> lamalex, hey, so thomi and I might have figured out why the ibus test don't work
[18:20] <lamalex> nice!
[18:20] <bschaefer> I pushed some changes last night, but it didn't seem to fix it
[18:20] <bschaefer> it seems when you hold ctrl+space down, ibus toggles on/off
[18:20] <lamalex> ok
[18:21] <lamalex> are we turning it off?
[18:21] <bschaefer> I think it is how fast we detect tabing
[18:21] <bschaefer> for the hud
[18:21] <bschaefer> so events come through faster, so holding it down
[18:21] <bschaefer> will push that event through nux multiple times
[18:23] <bschaefer> I have a different solution but Im not sure how much I like it :(
[18:24] <bschaefer> lamalex, o yeah to reproduce the problem on a local machine. Go into test_ibus.py and under def activate_ibus change the press/release time to 0.5
[18:25] <lamalex> so it's purely timing issue?
[18:26] <lamalex> yarrr
[18:26] <bschaefer> that is what it looks like...
[18:26] <bschaefer> but that is the only way I can reproduce it on a local machine...
[18:27] <bschaefer> I changed the time to 0.05 last night, but it still fails so I think a fix is to iterate from 0.2 to 0.9 and try and press/release ctrl+space
[18:28] <bschaefer> if it activates its the go, else it will drop out and fail on an assert
[18:28] <lamalex> bschaefer, after doing that- now it fails without setting the time for me
[18:28] <bschaefer> hmm really?
[18:29] <bschaefer> what test are you running?
[18:29] <lamalex> autopilot.tests.test_ibus.IBusTestsPinyin.test_simple_input_dash
[18:29] <bschaefer> ok, ill see if I can get the same
[18:33] <bschaefer> lamalex, hmm mine works after setting it back to default
[18:33] <lamalex> odd
[18:33] <bschaefer> yeah...
[18:34] <bschaefer> I have a branch that should find the correct time for presssing ctrl+space...
[18:34] <bschaefer> which should find a correct time, if the timing is the issue
[18:37] <lamalex> odd that this is the only place where key press timing is an issue
[18:37] <lamalex> so you think you understand the root cause of this?
[18:37] <bschaefer> I think it has to do with ctrl+space getting pushing into ibus multiple times in nux
[18:38] <bschaefer> yeah, the problem is Ctrl+Space can change to anything...
[18:39] <bschaefer> also gnome seems to toggle it
[18:39] <bschaefer> but just not as much
[18:40] <bschaefer> well not on pinyin...it really is up to ibus engine then
[18:42] <bschaefer> lamalex, this is one possible fix...https://code.launchpad.net/~brandontschaefer/unity/ibus-ap-test-range-time/+merge/103544
[19:09] <lamalex> bschaefer, this is such a hack :\
[19:10] <bschaefer> lamalex, I know....Ill spend today looking into fixing this in nux
[19:58] <lamalex> thomi, review my branch when you're back! https://code.launchpad.net/~alexlauni/unity/unity.ap-switcher-emu/+merge/103338
[19:59] <gema> hey , wondering if unity is supposed to show the launcher bar and the top bar on all of my screens (3 of them)
[20:00] <gema> and also if the mouse is supposed to get stuck when moving from one to the next (which I find rather annoying)
[20:00] <seb128> gema, yes and yes, and both can be changed in the system settings
[20:00] <gema> seb128: you are a lifesaver
[20:01] <seb128> gema, well the top bar can't, but the display configuration dialog has a combo to select if the launcher should on one screen, which one in that case, or on all screens
[20:01] <seb128> gema, it has a config to turn off the stickyness between screens as well (which is there so you can easily get to a scrollbar against the border)
[20:02] <gema> seb128: already much more usable for me
[20:02] <gema> seb128: thanks
[20:06] <seb128> gema, yw!
[20:10] <bschaefer> thomi, ping
[20:13] <thomi> bschaefer: pong
[20:13] <thomi> lamalex: ok
[20:13] <bschaefer> hey
[20:14] <bschaefer> soo that fix didn't work :I(
[20:14] <bschaefer> :(
[20:14] <lamalex> wah
[20:15] <bschaefer> thomi, ill see if this is a possible fix in nux. The problem is there are multiple keys to activate/deactivate ibus and you can add/subtract from that list
[20:15] <thomi> bschaefer: I saw - odd huh?
[20:15] <bschaefer> yeaah
[20:15] <thomi> lamalex: is there any way to run an identical environment to the one the jenkins instance uses locally?
[20:15] <bschaefer> so it must have a min slow time, ie it is always 0.5 or higher
[20:15] <bschaefer> if it is a timing issue
[20:16] <seb128> thomi, hey
[20:16] <lamalex> thomi, i mean it should be possible to run the nfsbuild root script stuff locally
[20:16] <lamalex> but im not sure how you'd boot the overlayfs image. you'd need a second machine to pxe boot
[20:16] <thomi> lamalex: hmmm
[20:16] <seb128> thomi, lamalex, bschaefer: is there any chance one of you help writing a test for https://code.launchpad.net/~mvo/unity/usc-launcher-fix-982921/+merge/102257
[20:16] <lamalex> i guess really you need a jenkins master and slave set up in your apt
[20:17] <bschaefer> VirtualBox has pxe
[20:17] <seb128> it will not make into the first SRU otherwise
[20:17] <seb128> i.e mvo is maintaining software-center but is not familiar with the unity test framework and he's busy with the precise release (he's looking at i.e upgrade bugs as well)
[20:18] <thomi> lamalex: ok, another idea - do you think we could duplicate the autopilot-run job into another jenkins job that we fire off manualkly? We could point it at a custom unity branch, so we can try things out and run the tests in an identical environment without having to merge with trunk.
[20:18] <lamalex> thomi, yah for sure
[20:18] <lamalex> just make a new job and copy from dx-autopilot run and change the branch ha
[20:18] <thomi> lamalex: we can just go ahead and do that, or do we need to ask someone?
[20:18] <lamalex> thomi, on it
[20:18] <thomi> lamalex: thanks!
[20:19] <thomi> bschaefer: now we can try some wacky fixes and not have to merge with trunk :)
[20:19] <bschaefer> sweet!
[20:19] <thomi> seb128: looking into it...
[20:19] <seb128> thomi, thanks ;-)
[20:19] <bschaefer> I have a bad hack to check if it is a timing issue
[20:20] <bschaefer> thomi, https://code.launchpad.net/~brandontschaefer/unity/ibus-ap-test-range-time/+merge/103544
[20:20] <bschaefer> we should be able to use that to check if/what is the timing problem
[20:21] <thomi> bschaefer: you want to at least sleep before that if statement. It will take a while for unity to update
[20:21] <thomi> you could use wait_for, but then you'd be sleeping 10 seconds each time it didn't work
[20:21] <thomi> also, the more I think about this, the less I think it's a timing issue
[20:21] <bschaefer> hmm yeah,
[20:21] <thomi> The times seem similar to what works for me locally
[20:21] <thomi> and we're seeing 100% failure rate
[20:22] <thomi> so I suspect it's something a bit more basic.
[20:22] <bschaefer> yeah
[20:22] <thomi> bschaefer: a vlue might be to look at what changed when they all started failing?
[20:22] <bschaefer> im hoping...
[20:22] <bschaefer> Ill look through the logs
[20:23] <lamalex> thomi, where do we want this branch
[20:23] <lamalex> lp:~unity-team/unity/ibus-tests
[20:23] <lamalex> sound good?
[20:23] <thomi> yup
[20:23] <thomi> lamalex: we can always tweak the jenkins job config to point it elsewhere, right?
[20:23] <lamalex> yah
[20:24] <lamalex> also going to change the ap run command to just run ibus tests
[20:24] <lamalex> save time
[20:24] <bschaefer> lamalex, awesome, thanks!
[20:24] <lamalex> (will do a test run to make sure we're still seeing same fails this way)
[20:25] <bschaefer> thomi, man, im looking at these test and it has been failing to activate ibus for a while...
[20:25] <thomi> bschaefer: yeah
[20:28] <lamalex> ok should be set to build on every commit
[20:35] <bschaefer> thomi, the first build to not activate ibus correctly
[20:35] <bschaefer> though that is for pinyin only
[20:35] <bschaefer> https://jenkins.qa.ubuntu.com/job/dx-autopilot-run/695/#showFailuresLink
[20:36] <thomi> bschaefer: ok, so what changed in that build? can you see the bzr revno?
[20:36] <thomi> look in the console output for the default configuration
[20:36] <bschaefer> yeah, I started looking for where they ALL started failing
[20:36] <bschaefer> goes to do that
[20:37] <bschaefer> thomi Now on revision 2206.
[20:37]  * bschaefer goes to look at that rev
[20:37] <thomi> uh oh - dx-autopilot-run build just failed.
[20:37] <lamalex> i might have cancelled it
[20:38] <lamalex> i forgot to change the downstream job to the ibus job
[20:38] <lamalex> s/might have//
[20:39] <bschaefer> thomi, http://bazaar.launchpad.net/~unity-team/unity/trunk/changes/2206
[20:40] <bschaefer> im just going to dig until if find anything useful haha
[20:44] <bschaefer> thomi, ugg so a problem, a problem happen between rev 2120 - 2206...since the jenkins test fail for a while
[20:44] <bschaefer> unity rev 2120-2206
[20:45] <thomi> hmmmm
[20:45] <thomi> bschaefer: it could also be a change in the autopilot infrastructure branch that caused it
[20:45] <bschaefer> Ill see if I can find where ALL start failing as that doesn't help at all
[20:45] <thomi> ...or a change oin nux.
[20:45] <bschaefer> yeah
[20:48] <thomi> lamalex: I take it you didn't want to go the extra step and use the Eventually() matcher in your switcher refactor branch?
[20:48] <thomi> I guess it makes sense to do that in a separate branch
[20:49] <lamalex> thomi, where? i thought i did
[20:49] <thomi> oh, ok, there are some, I didn't get to them yet
[20:49] <thomi> I'll add a note in my review
[20:49] <lamalex> there are some places where I couldn't use it- for instance the mode property isn't from introspection
[20:50] <lamalex> i added a card to extend wait_for so that you can use it on properties not added by introspection
[20:51] <bschaefer> thomi, wow even more odd things. What happen to jenkins dx ap builds 723-763?
[20:51] <bschaefer> because after that is were all start to fail
[20:52]  * thomi looks
[20:52] <bschaefer> and it could have happened in unity form 2228-2275
[20:52] <bschaefer> :(
[20:52] <lamalex> erm well, good news- all the tests fail
[20:52] <bschaefer> haha
[20:52] <lamalex> good news in that we get the same results as in the normal AP env with only running ibus tests
[20:52] <thomi> \o/
[20:52] <bschaefer> yeah
[20:53] <lamalex> but you know, still bad news
[20:53] <lamalex> :P
[20:53] <thomi> it'd be funny if they all passed :)
[20:53] <bschaefer> I would .... idk
[20:53] <bschaefer> haha
[20:53] <bschaefer> that would be very inconsistent
[20:53] <thomi> bschaefer: let me finish this review for alex, do the standup, then I'll investigate - will you be around still in 20 minutes?
[20:53] <bschaefer> yup!
[20:53] <bschaefer> Ill dig some more
[20:54] <lamalex> bschaefer, thomi i would just say screw it and have a seperate ibus job
[20:55] <thomi> ibus job?
[20:55] <bschaefer> I ment to dig through nux and the ibus api those logs aren't going to be very helpful :(
[20:56] <lamalex> thomi, as in we'd have two AP test jobs, one for most of the tests one for the ibus tests
[20:57] <lamalex> of course that's moot becuase they failed
[20:57] <lamalex> but had they passed...
[20:57] <bschaefer> or if we can get them to pass :)
[20:59] <thomi> lamalex: https://code.launchpad.net/~alexlauni/unity/unity.ap-switcher-emu/+merge/103338/comments/223103  just a few small tweaks needed :)
[20:59] <thomi> looke awesome otherwise
[20:59] <lamalex> sick
[20:59] <lamalex> will fix now
[21:01] <lamalex> damn i thought i changed that docstring about the tuple
[21:01] <lamalex> wth
[21:03] <gema> can you guys help me add a console based app to the launcher?
[21:10] <gema> nevermind, got it already
[21:10] <NotALamer> hey how does unity figure out what icon and title to use for alt-tab
[21:10] <NotALamer> having trouble getting an application to show up properly
[21:11] <NotALamer> unity is calling it win0 and giving it a generic icon
[21:11] <NotALamer> but xwininfo gives the correct title
[21:14] <thomi> bschaefer: still around?
[21:17] <bschaefer> thomi, yeah
[21:18] <thomi> ...just looking for clues as to the ibus failures...
[21:18] <bschaefer> thomi, was just pulling/compiling that unity-team/ibus-tests branch
[21:18] <bschaefer> yeah, the logs don't seems to help besides a general time line
[21:18] <bschaefer> do you want to push a test in to see if we can find a press/release time that works?
[21:19] <bschaefer> worst case is we can show it is'nt a timing issue
[21:20] <bschaefer> thomi, what if we hold Ctrl, then tab space very fast
[21:21] <bschaefer> instead of having it be "Ctrl+Space"
[21:21] <thomi> bschaefer: worth a shot, although it shouldn't make any difference.
[21:21] <bschaefer> i know :(
[21:21] <thomi> I suspect this is an environmental thing.
[21:21] <bschaefer> ok
[21:22] <bschaefer> dam I wonder if ibus ever gets activated at all
[21:22] <bschaefer> we should start with push some debugging changes I suppose
[21:25] <bschaefer> thomi, can we print out 'ps aux' on that VM?
[21:25] <bschaefer> ps aux | grep ibus
[21:26] <thomi> bschaefer: sure, if you use subprocess and log it in a test
[21:26] <thomi> now that we have a junk branch to push to that's easy :)
[21:26] <thomi> good idea BTW :)
[21:26] <thomi> bschaefer: you want me to set that up?
[21:26] <bschaefer> haha that is true, sure!
[21:26] <thomi> ok, I'm on it
[21:26] <bschaefer> I can look it up, but Ill start trying to figure out how this could happen w/o a timing issue
[21:27] <bschaefer> very odd
[21:27] <bschaefer> and thanks, I like being able to debug things manually haha
[21:30] <bschaefer> thomi, sweet also found a good spot in put a print statement in SearchBar.cpp to see if im active gets set
[21:31] <thomi> cool
[21:31] <bschaefer> did you want to throw it in your branch when you get a chance?
[21:33] <thomi> bschaefer: I just pushed a new revision of that testing branch
[21:34] <thomi> bschaefer: also, your print statemnt won't work, since we're not compiling unity from the branch, only running the autopilot tests
[21:34] <bschaefer> oo
[21:34] <bschaefer> ok
[21:34]  * bschaefer goes to look up some python ibus api
[21:35] <bschaefer> maybe we can add some ibus stuff in the emulator for debugging
[21:35] <thomi> sure
[21:35] <thomi> ok, i just kicked off a new run of the debugging jenkins job
[21:36] <bschaefer> cool
[21:37] <bschaefer> also got that jenkins indicator it is awesome
[21:37] <thomi> thanks :)
[21:38] <bschaefer> o you made it? haha
[21:38] <thomi> yeah,. one of my side projects
[21:39] <thomi> there's several things that I need to fix in it, but it's useful at least
[21:39] <bschaefer> awesome, didn't check who pushed it to launchpad, just pulled it and ran it
[21:39] <bschaefer> yeah!
[21:39] <thomi> bschaefer: there's a PPA as well
[21:40] <bschaefer> O, well it worked from launchpad haha
[21:46] <tiredGeek> On Pangolin, desktop is blank when trying to use vncserver for a remote session.  Can Unity be redirected to another X display?
[21:52] <thomi> hmmm, the ibus test jenkins jobs eems to be hanging
[21:53] <bschaefer> yeah, Im trying to see if we can push the trigger signal through ibus
[21:54] <bschaefer> instead of pressing ctrl+space...
[21:54] <bschaefer> I know how to get the list of shortcuts but need to look more
[21:59] <thomi> bschaefer: hmmm, tht's odd. My debug test fails in a strange way on the server
[21:59]  * bschaefer looking
[22:00] <bschaefer> thomi, so hud doesn't want to show now?
[22:00] <thomi> ok, I made it even simpler
[22:00] <bschaefer> odd
[22:01] <thomi> pushing a version that just does the 'ps' command without trying to show or hide the hud
[22:02] <thomi> re-running it now
[22:02] <bschaefer> alright, also I wonder what would happen if you ran "ibus-setup", isn't it taking a video the whole test?
[22:02] <bschaefer> so we could in a sense have a video of the test, screen shots of ibus-set if anything is wrong with it?
[22:02] <bschaefer> setup*
[22:02] <thomi> sure, except you'd only see the first tab.
[22:03] <bschaefer> yeah
[22:03] <thomi> let's see what this produces first
[22:03] <bschaefer> agree
[22:03] <thomi> brb
[22:04] <bschaefer> ok
[22:04] <mhall119> mhr3: are global search strings still stored in .props.search_string?
[22:04] <mhall119> mhr3: I'm trying to help with http://askubuntu.com/questions/125121/unity-lens-not-included-in-global-search/125186#125186
[22:06] <mhr3> mhall119, i dont think there was such property... ever :)
[22:07] <mhall119> uh...
[22:08] <mhr3> mhall119, not on scopes anyway
[22:09] <mhr3> oh... it is on the LensSearch instance of course
[22:09] <mhall119> yeah
[22:09]  * mhr3 needs time to process stuff this late :P
[22:09] <mhall119> which gets passed to the function listening to search-changed signals, right?
[22:10] <mhr3> yep
[22:14] <mhall119> mhr3: so, Singlet sets search_in_global=False all the time, is it possible that it would still get a search_changed signal on a gloabl search, but with an empty search string?
[22:15] <mhr3> mhall119, are we talking strictly 12.04?
[22:16] <mhall119> I assume, since Singlet only works at all in 12.04
[22:16] <mhr3> cause there was a race in unity4 were that could happen
[22:16] <mhr3> but afaict i fixed it :)
[22:16] <thomi> bschaefer: OK, did you see the results?
[22:17] <bschaefer> looking at it right now
[22:17] <bschaefer> and comparing
[22:17] <thomi> looks good to me
[22:17] <bschaefer> thomi, I have ibus-daemon --xim
[22:17] <bschaefer> and that log has
[22:17] <bschaefer> ibus-daemon -d --xim
[22:17] <bschaefer> I need to look up what that -d does
[22:17] <thomi> -d = daemonise
[22:18] <bschaefer> yeah
[22:18] <bschaefer> hmm
[22:18] <mhr3> mhall119, so, no it shouldn't, and if it does sound alarms :)
[22:19] <mhall119> mhr3: ok, I'll see what responses I get from my current comments, thanks
[22:20] <mhr3> mhall119, i feel bad when i chat with you, you don't make mistakes and you put commas where they should be :P
[22:21] <mhr3> not to mention the capital I :)
[22:22] <mhall119> lol
[22:23] <mhall119> my mother was a paralegal, taught me to write on one of those old smash-the-keys typewriters
[22:23] <mhall119> I still put two spaces after a period, despite all my subsequent English teachers yelling at me for it
[22:24] <bschaefer> thomi, ugg, so im still not sure what could cause this besides that toggling problem.
[22:24] <mhall119> I still make typos though, if you're paying attention
[22:24] <bschaefer> thomi, when I had ibus set to press/release at 0.5 it was failing consistently for me
[22:25] <thomi> bschaefer: hmmm
[22:25] <bschaefer> thomi, hmmm, should we just go ahead and eliminate a timing issue by seeing if the ibus can get active?
[22:26] <thomi> bschaefer: if you look at this: https://jenkins.qa.ubuntu.com/job/dx-autopilot-fix-ibus/3/label=1EBEE0FF-DAC9-11DF-BBDA-64A98C34D485/testReport/autopilot.tests.test_ibus/IBusTestsAnthy/test_simple_input_dash_user_commit_j_/?
[22:26] <thomi> it looks to me like the tap is taking just less than 200mS
[22:26] <thomi> ...which seems reasonable?
[22:26] <mhr3> mhall119, good, otherwise i'd have to assume you installed some clever autocorrect in your irc client :)
[22:26] <bschaefer> thomi, it says 50 ms doesn't it?
[22:26] <bschaefer> for ctrl+space
[22:27] <bschaefer> thomi, also how accurate are those times? it seems like it just prints the var you push into the function
[22:28] <thomi> bschaefer: nope, 201 ms
[22:28] <bschaefer> thomi, wait where are you looking?
[22:28] <bschaefer> Pressing keys 'Ctrl+Space' with delay 0.050000
[22:29] <thomi> oh nuts - I'm being an idiot
[22:29] <thomi> was looking at the Ctrl+a :(
[22:29] <thomi> right, so 23mS for the space key
[22:29] <bschaefer> how are you getting 23ms?
[22:29] <bschaefer> 23mS?
[22:30] <thomi> 22:03:54.965 DEBUG X11:194 - Sending press event for key:
[22:30] <thomi> 22:03:55.017 DEBUG X11:197 - Sending release event for key:
[22:30] <bschaefer> oo
[22:30] <bschaefer> ok yeah duh
[22:30] <thomi> :)
[22:30] <bschaefer> hmm that is very odd
[22:31] <bschaefer> this would be funny. So you can kill the ibus daemon and the ap test starts a new one when you open an engine
[22:32] <bschaefer> so I think a new daemon is getting started each test...nevermind that idea does no where...
[22:32] <davidcalle> jono, poing
[22:32] <jono> hey davidcalle
[22:32] <thomi> hmmmm
[22:33] <jono> davidcalle, nice work on the lens!
[22:33] <jono> davidcalle, I responded to your mail on the list
[22:33] <bschaefer> thomi, so, what could we be missing that we have but jenkins doesn't
[22:33] <bschaefer> could we have*
[22:33] <jono> davidcalle, also, we have #ubuntu-accomplishments if you ever want to hang out there
[22:33] <bschaefer> ugg that is worded very badly...
[22:33] <thomi> bschaefer: possibly an engine, but they should be installed, and the tests should skip if it can't find the engine
[22:33] <bschaefer> or I just can't read right now haha
[22:34] <bschaefer> thomi, yeah, we could print out all engines
[22:34] <davidcalle> jono, thanks. I've seen your answer, when are you going to push your API changes to the PPA ?
[22:34] <jono> davidcalle, the PPA has now been updated
[22:34] <jono> davidcalle, so you should be good to go
[22:34] <davidcalle> Oh, cool
[22:35] <jono> when you have updated the lens I will install the PPA and test too :-)
[22:36] <thomi> bschaefer: hmmm, I'm going to try some things...
[22:36] <bschaefer> thomi, alright...
[22:36] <bschaefer> ill try to think of something...
[22:36] <bschaefer> haha
[22:42]  * thomi kicks off another jenkins run
[22:43] <bschaefer> ugg I have to leave in 20 min
[22:43] <bschaefer> thomi, what are you testing?
[22:43] <thomi> I added a bunch more debugging statements, and made the sleep after we restart the ibus daemon a bit more sensible
[22:44] <bschaefer> cool!
[22:44] <bschaefer> I like the graph, Test Results Trend, all red
[22:44] <thomi> heh
[22:46] <bschaefer> thomi, I don't think it's an engine problem. I removed hangul and those test just reported back as no test taken
[22:46] <bschaefer> so it seem to skip them :(
[22:46] <thomi> good
[22:47] <bschaefer> well yeah
[22:47] <bschaefer> haha
[22:47] <thomi> I'm getting virtualbox set up to PXE boot the remastered CD, so I should have anidentical setupo
[22:47] <thomi> *seup
[22:48]  * thomi waits for CD to download...
[22:48] <bschaefer> yeah, I'll end up doing that when I get back form this seminar I have to go too...
[22:48] <bschaefer> to*
[22:52] <bschaefer> thomi, ugg well I have to go for a bit. Ill be back in a couple hours, good luck!
[22:54] <thomi> cheers