[00:36] <vadi2> Is anyone else extremely bothered by 2D unity refusing to hide from the mouse if there is a pending notification - forcing you to click on the notification first if you want to see the content the panel is hiding?
[10:56] <BerndSch_> hi, what's the best way to debug Lenses? Where can I find which lenses are loaded? Where can I find why the search signal don't trigger for my lens?
[14:02] <mhr3> BerndSch_, debug prints + running the lens from console works fine
[15:02] <Petko10> hey guys , I don't see too much action going on , but I'll guess I'm in the right place . I want to get some feedback on my idea for the calendar applet here : http://brainstorm.ubuntu.com/idea/29130/
[15:02] <Petko10> if anyone would be kind enough to review it
[15:07] <mhall119> Petko10: I've been wanting an indicator for notes/tasks for a while now
[15:07] <mhall119> I'm not sure the clock applet is the right place for it though
[15:18] <BerndSch_> mhr3: no, sadly not. The lens+scope works fine. I see the debug output in the init method. But I see no lens (no icon) and there is no debug output from my search method (enabled global search)
[15:19] <BerndSch_> mhr3: I think this all has something to do with the apparmor stuff I integrated in my source because I submitted my lens to the Software Center. This all works fine with 11.10, but don't work now with 12.04
[15:24] <Petko10> mhall119: well the applet now has some sync with mail clients (frankly I haven't tried it :?) so I guess it has some functionality like that . all I really want is to make it big , so it's more usable than a pocket calendar (and that one could annotate in it)
[16:17] <mhr3> BerndSch_, if you dont see the lens in the bottom bar of unity that's pretty bad
[16:33] <BerndSch_> mhr3: yes, and so I would like to know how I can debug wich lenses are loaded at startup and how I can debug the search behaviour. My lens connects to the search signal, but why the callback method get never called?
[16:34] <mhr3> BerndSch_, running unity itself in console might reveal something
[16:34] <BerndSch_> mhr3: I think debugging lenses and scopes are a mess at the moment?! Why is there now documentation how to debug them? Gnome it's easier with this think. There you can see why an extensions isn't loaded and it's easier to see the debug output
[16:35] <BerndSch_> mhr3: I think it's the apparmor think that blocks my lens, but how I can debug that?!
[16:35] <mhr3> sorry i know nothing about apparmor
[16:42] <BerndSch_> mhr3: ok, no problem
[20:24] <thumper> morning
[20:25] <Saviq> thumper, it's monday already?
[20:25] <Saviq> jeez
[20:25] <Saviq> you guys have it tough...
[20:29] <thumper> Saviq: yes... yes it is
[20:30] <smspillaz>  thumper morning
[20:30] <smspillaz> (night)
[20:30] <smspillaz> Saviq: its uh
[20:30] <thumper> smspillaz: hi
[20:30] <smspillaz> early here
[20:30] <smspillaz> hey hey
[20:52] <thumper> bschaefer: feel free to chat about normal untiy stuff here :)
[20:53] <bschaefer> thumper, alright
[20:53] <thumper> :)
[20:54] <bschaefer> thumper, so sam and andyrock both reviewed the alt+f1 nav mode bug so I would say that bug looks fixed
[20:54] <thumper> awesome
[20:55] <bschaefer> thumper, and the ibus problem is slightly weird. I am not sure how far I should be going on it
[20:55] <thumper> is it unity specific?
[20:55] <thumper> or ibus in ubuntu in general?
[20:56] <bschaefer> thumper, well if setting IBUS_ENABLE_SYNC_MODE causes the problem but the problem is that the IMs can't handle all the input
[20:56] <bschaefer> so it gets sent to gtk then it commits the letter but there is still preedit left around so that is a bug in the IM
[20:57] <thumper> IMs?
[20:57] <bschaefer> input method
[20:57] <bschaefer> like hangul or pinyin
[20:58] <bschaefer> umm so if the IM cant handle an input char such as space it returns FALSE and lets gtk handle it; the bug is it leaves the preedit around
[20:59] <bschaefer> It is not unitys problem; but im not sure who to blame
[21:00] <bschaefer> because I don't know the specs for what an IM should do. Should it be able to handle all the input? Or is that ibus problem? Or should ibus not even offer IBUS_ENABLE_SYNC_MODE
[21:02] <bschaefer> thumper, sorry, spent a while digging though ibus, ibus-hangul and libhangul code. I was able to get the space working correctly though; in libhangul
[21:03] <thumper> hmm...
[21:03] <thumper> I'll escalate this through the distro
[21:04] <bschaefer> thumper, alright. I just wish ibus and unity could be friends :)
[21:04] <bschaefer> I need to talk with jay about how far he has gotten on the TextEntry in nux. With ibus support
[21:05] <thumper> bschaefer: do you have the bug number to hand?
[21:05] <bschaefer> 880876
[21:05] <bschaefer> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/880876
[21:06] <bschaefer> there is more info from me in there too
[21:06] <thumper> ta
[21:09] <bschaefer> thumper, also to prove this isn't unitys fault you get the same results in GNOME if you set the env var
[21:10] <bschaefer> or force ibus to set it to true. So it is a bug with that env var and ibus and the specific IM engine being used
[21:10]  * thumper nods
[21:10] <thumper> I've asked for some distro help on the ibus stuff
[21:11] <bschaefer> if it isn't in unity fault should I set the bug to invalid for unity of leave it? As it does effect unity but it isn't unitys fault
[21:11] <bschaefer> thumper, and thanks
[21:41] <bschaefer> hey mhr3
[21:41] <mhr3> sup bschaefer
[21:41] <bschaefer> mhr3, I did some testing
[21:42] <bschaefer> and when you kill the say the applications daemon and then search (it restarts it self) the init does nothing
[21:42] <bschaefer> it still has a problem when you kill the lens and then your next search does nothing
[21:42] <mhr3> bschaefer, init?
[21:42] <bschaefer> it comes up empty
[21:43] <bschaefer> sorry, umm in LensView the initial_activation_ bool
[21:43] <bschaefer> that is used when a lens connects and it calls Search("");
[21:43] <bschaefer> but that Search(""); does not actually reset the lens
[21:43] <mhr3> yea, there's something odd
[21:44] <mhr3> i'll have to look at it closer
[21:44] <bschaefer> alright, because that line of code causes a problem with my branch for the no-results-hint
[21:45] <bschaefer> but cool, let me know if you find something. Another thing I noticed was unity --reset does not cause the problem. Only on a fresh login or reboot
[21:46] <bschaefer> mhr3, with the Search (""); call emitting OnSearchFinished with 0 results.
[21:46] <mhr3> i also noticed some problem with models, when lens restarts they sometimes dont see to work properly
[21:48] <bschaefer> mhr3, let me know if you find something :). Ill leave my branch as is because I still need to wait for mikkel to finish the new home view.
[21:48] <bschaefer> also it is looking a lot nicer, the home view
[21:50] <mhr3> bschaefer, sure, i hope we'll merge his branch soon, the diff is becoming too huge
[21:50] <bschaefer> mhr3, haha. Yeah. I  might want to split mine up into one for LensView/DashView and one for the HomeView...
[21:50] <bschaefer> I dont like getting the diff to large
[21:53] <bschaefer> mhr3, I also added a manual test for it in unity. Not sure how you would test for this else where...
[21:54] <mhr3> yea, good idea, the lens tester will probably test it too, but sending the hint doesn't mean that unity is displaying it, right? :)
[21:54] <bschaefer> mhr3, correct :) It sends it when it is == 0 then unity does a check because the lens might not have a no-result-hint
[21:55] <bschaefer> mhr3, but if you emit the OnSearchFinished with 0 results unity should always display something