[01:24] <jalcine> Hey guys!
[01:24] <jalcine> I'm working on possibly adding a nifty feature into Unity.
[01:25] <jalcine> Now, after reading http://developer.ubuntu.com/resources/technologies/unity/lenses-and-scopes/, I noticed something about filters in scopes.
[01:25] <jalcine> Is it possible to perhaps implement a means of opening another dialog perhaps, or a silent notification whilst the filter's activated?
[01:26] <jalcine> I'm looking to adding speech recognition into the filter.
[01:31] <mhall119> jalcine: to the filter?
[01:31] <mhall119> or to the search?
[01:32] <jalcine> Well, I'm not sure how specifically how it'd work. I'd like to provide the ability to speak and have the user's text be used as a search query.
[01:32] <jalcine> search, sorry.
[01:32]  * jalcine is still learning
[01:32] <mhall119> ok, that would go into the Dash itself then
[01:32] <mhall119> and some common library so it can be mostly shared between unity and unity-2d
[01:34] <mhall119> that's a pretty big task you've picked to work on, it might be a good idea to send your ideas to the mailing list so they can be discussed by more people to see what would need to be done
[01:35] <mhall119> also to make sure that you're not missing any preliminary work/designs/discussions that have been done around voice recognition in Unity
[01:35] <jalcine> Heh, I managed to get dictation working with my application so I'm pretty confident.
[01:35] <jalcine> Alrighty then, I'd search the archives for anything interesting then.
[01:35] <jalcine> Thanks
[01:36] <mhall119> jalcine: these docs are still very much under construction, but http://unity.ubuntu.com/getinvolved/development/unity/ might be helpful to you
[01:37] <mhall119> I'd like to see speech recognition built into both the Dash and HUD
[01:39] <jalcine> Only real concern I have is focusing, but I'd need some to familiarize myself with Unity's inner workings.
[01:39] <jalcine> See you in a week or so.
[01:43] <mhall119> that's what i was suggesting to bring to the ML, one the one hand having it automatically accept voice input would be nice, I can see it being undesirable, and having to press a button to activate voice might seem to defeat the point of not typing
[01:44] <jalcine> Well, the way it works, it'd only recognize whenever it detects input.
[01:45] <jalcine> recognition could occur only when the user focuses within the input field (changing the placeholder text to "type or speak to search" or something)
[01:46] <jalcine> the tech's decent enough to know when you sneezed, coughed or made some kind of "white-space" noise (like uhm, and er)
[01:46] <jalcine> The only real danger that I can foresee is that the code's largely written in Qt.
[01:47] <jalcine> We're working on Python bindings so that could probably fare better, but I'd have to see.
[02:04] <mhall119> jalcine: if it's already using Qt, try implementing it in http://unity.ubuntu.com/getinvolved/development/unity-2d/ first
[07:29] <smb> didrocks, Do you know more about the current state of bug 963633? I saw this just yesterday with fresh installs on i915 based hw. One of those was via orchestra, so that even installed latest archive immediately.
[07:30] <didrocks> smb: hum, we never noticed complain on direct install though
[07:30] <didrocks> smb: duflu has almost a fix
[07:30] <didrocks> smb: can take one or more two days
[07:31] <didrocks> the workaround we push for beta 2 "fix" the upgrade case, which is the main one
[07:31] <didrocks> seems nobody notice a blank desktop directly installing beta2 though
[07:32] <smb> didrocks, Ok, yeah I had been thinking it was upgrade only. So I am a bit worried this happened on the new installs. Both alternate. Though one of them from CD and (since I did that late yesterday while watching TV) I am not sure whether it was directly after install or after the first complete upgrade after.
[07:33] <didrocks> smb: can be, the most important note is: after a second boot, did it still happen?
[07:33] <smb> The second was alternate 64bit and through orchestra. Btw, both with tha background visible and actually something working as I can launch a terminal with ctrl+alt+t
[07:34] <didrocks> ok, the second is the unityshell plugin removed from the config
[07:34] <didrocks> smb: this is no a new bug, it happened in the past already…
[07:34] <didrocks> smb: I pinged the compiz guys for a year about that one, we never had a great reproducer
[07:34] <didrocks> but the fix that duflu is doing is supposed to avoid it as well
[07:36] <smb> Ok, yeah, I am not sure I really know exactly how that one has been triggered. Just coincidence... ? I guess, when I see the bug going into fixed I will have to run the installs again.
[07:39] <didrocks> smb: right. I can tell you as well :)
[07:39] <didrocks> smb: please keep us in touch, as it's a very tricky behavior ;)
[07:39] <didrocks> (also multiple causes resulting in the same effect, so people mixing)
[07:40] <smb> didrocks, Right, I rather would not want to have this behaviour going into release... ;)
[07:40] <didrocks> same for me :)
[07:40] <smb> Yeah, hard to keep seperate if so similar
[07:40] <smb> At least I never saw a completely black screen
[07:41] <smb> Only the background only (unity not starting) one. But that one across various gfx hw (i915, ati)
[07:44] <smb> didrocks, Oh, btw. Just interested in the expected behaviour here: what should happen when I run "unity --reset" in a gfx terminal/vt (should the command return?). Cause for me it either does not return or segfaults (while still fixing issues)
[07:45] <didrocks> no, it's launching compiz
[07:45] <didrocks> so it's at the end your compiz process
[07:45] <didrocks> (so shouldn't return, or you have a problem ;))
[07:46] <smb> Ok, understood. :) Thanks
[07:46] <didrocks> yw ;)
[09:05] <apw> didrocks, i managed to find a way to 100% reproduce: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/934084
[09:05] <apw> didrocks, simply hit Super+z (or any invalid combo)
[09:05] <didrocks> apw: oh nice, please ping upstream directly when you get reproducers :)
[09:05] <apw> didrocks, found that cause the binding on Super+d moved somewhere else so that is invalid ... and my keyboard has a key for Super+d
[09:05] <didrocks> like sam, gord, thumper ;)
[09:06] <didrocks> apw: maybe linked to another bug we have (but fixed in trunk)
[09:06] <didrocks> anyway, worth a look from upstream directly
[09:06] <apw> didrocks, heard of the panel showing up in the alt-tab thing ?
[09:07] <didrocks> apw: yeah, it's already reported, a known regression of 5.8. Pinged and assigned 1 week and half ago
[09:07] <apw> didrocks, got a bug number so i can me-too it
[09:08] <didrocks> bug #960652
[09:09] <apw> didrocks, ahh thanks ... and the the panel in the alt-tab was that known or shall i file
[09:10] <didrocks> panel in alt-tab?
[09:10] <apw> didrocks, with cirtain application running alt-tab shows both of my panels as windows i can select
[09:10] <didrocks> greyback: unity-2d launcher reveal spot will finally not get in, right?
[09:11] <didrocks> apw: no, not sure about that one, please file a bug and ping om26er, who is dx upstream bug triager and should handle all those :)
[09:11] <apw> will do thanks
[09:17] <didrocks> apw: thanks to you for all this feedback :)
[09:19] <MCR> Hi :) Are there any news about: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/963872 ?
[09:19] <apw> didrocks, heh no problem, this is literally dog-fooding in action.  things i am seeing over long use
[09:20] <MCR> I cannot live without Compiz :'(
[09:20] <didrocks> yeah ;)
[09:20] <apw> didrocks, om26er, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/968088
[09:21] <MCR> Also I would like to compile Unity from source, but I do not know where to get the source for nux which seems to be required to do so. Could anyone point me to some wiki ?
[09:27] <MCR> Now I got everything up-and-running here (on Precise) I need for a productive system except Unity-3d/Compiz and Emerald (which does not compile anymore on 12.04).
[10:07] <MCR> I filed another bug report/regression on Precise I would very much like to see fixed (sorry for that :-D): https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/968112
[10:09] <MCR> * Ignore MCR *
[10:09] <MCR> :-X
[12:56] <mhall119> emerald is still around?
[16:12] <rye> hello, may i ask about bug #943851 - pressing compose key still switches input focus from the widget - you can see it in the terminal or in http://people.canonical.com/~roman.yepishev/blur.html - it gets really annoying when you can't use compose characters e.g. in Picasa (as my wife noticed :) ) you can't rename the photo - it saves the name once you press the compose key
[16:20] <MCR> mhall119: any reason to get rid of the best if nothing is available by far that surpasses emerald in looks or functionality ? ofc it is still around ;)
[16:21] <mhall119> MCR: I just assumed it was swallowed up into Compiz Fusion years ago
[17:55] <krnekhelesh> JohnLea: ping
[17:56] <JohnLea> krnekhelesh; hyia, in a meeting atm
[17:56] <krnekhelesh> JohnLea: oh...alrite sry to disturb, I'll catch with you later
[17:57] <JohnLea> krnekhelesh; can you give me a quick summery of your question? ;-)
[17:58] <krnekhelesh> JohnLea: it is about static quicklist support for gnome control center...if I am able to finish it, is there a chance of inclusion in precise?
[18:01] <JohnLea> krnekhelesh; the person who would make that call would be didrocks in the platform team, he is the best person to ping
[18:02] <JohnLea> krnekhelesh; thanks!
[18:03] <krnekhelesh> JohnLea: thanks, I'll contact him
[18:36] <rye> bug: Windows+Tab - you start going through the windows, but you can't actually start new applications, then any alt+1..n keypresses actually start meaning super+1..n
[18:37] <rye> by the way, is it known that some keyboard hints don't fit the space and get truncated e.g. in Russian translation?
[18:38] <krnekhelesh> rye: 1st question, there is currently a bug with Windows+Tab in Unity 5.8..This will be fixed soon
[18:38] <krnekhelesh> rye: 2nd question, regarding the truncation, please submit a bug report with a screenshot attached..
[18:43] <rye> krnekhelesh: aha, bug #960652
[18:53] <rye> krnekhelesh: sorry, i forgot, when design decision is required, what tags should be added? - bug #968494
[18:59] <krnekhelesh> rye: needs-design
[19:00] <krnekhelesh> rye: can you also add a screenshot..will be very helpful
[19:02] <rye> krnekhelesh: done and done, i wonder why nobody noticed it before
[19:03] <rye> krnekhelesh: another question - is it knownw that sometimes windows started in fullscreen leave the 29px gap at the bottom as if they haven't full-screened properly
[19:04] <rye> e.g. shotwell
[19:04] <rye> and virt-manager
[19:19] <krnekhelesh> rye: I have that with shotwell...I thought it was just me imagining stuf...I dont know about virt-manager since i do not use it
[19:19] <krnekhelesh> rye: do you want to report it...I am in for support :)
[19:22] <rye> krnekhelesh: already reported, though it may be something that shotwell and virt-manager do to open with the same geometry - bug #968518
[19:46] <zyga> hi
[19:47] <zyga> anyone with radeon up for a very simple and quick test
[19:47] <zyga> open the dash
[19:47] <zyga> switch to app scope (or was that lens?)
[19:47] <zyga> and type something that returns no matches
[19:47] <zyga> say, 'cpufreq'
[19:47] <zyga> for me the first letter of the localized "does not exist" message is corrupted
[19:48] <zyga> anyone?
[19:49] <sil2100> zyga: radeon driver or fglrx?
[19:49] <zyga> sil2100, fglrx, radeon was unbearably slow for me (in the dash and hud)
[19:50] <zyga> sil2100, still, if you have radeon that's fine too, I'm interested to check if this is gpu related
[19:50] <sil2100> zyga: cannot reproduce it here
[19:50] <zyga> note: when I mean 'corrupted' I mean the first two pixels are
[19:50] <sil2100> zyga: I'm using fglrx right now
[19:50] <zyga> let me screenshot that
[19:50] <sil2100> zyga: ah, I think I know what you mean
[19:50] <sil2100> zyga: I actually experienced this bug in the past, a few weeks ago for sure
[19:51] <sil2100> zyga: what compiz/unity version are you running right now?
[19:51] <jussi> had a strange thing today, cant seem to reproduce it. was in chromium, hit alt, started to type but the focus stayed in chromiums address bar, even after clicking the hud input bar.
[19:51] <zyga> sil2100, latest precise
[19:51] <zyga> http://ubuntuone.com/19jrHrMtvgvFFrIO0VxkLe
[19:51] <zyga> (still uploading)
[19:52] <zyga> oh, I've got another one
[19:52] <zyga> font corruption in the thing that covers most of the screen on meta
[19:52] <zyga> (how do we call that element?)
[19:52] <sil2100> zyga: you mean, while holding? The help dialog?
[19:53] <zyga> yes
[19:53] <sil2100> zyga: yea, I had this bug some time ago, not sure when it disappeared
[19:53] <sil2100> zyga: hmm, I'm using compiz 1:0.9.7.2-0ubuntu4 and unity 5.8.0+bzr2172ubuntu0+677 right now, and it seems to be fine
[19:54] <zyga> 1:0.9.7.2-0ubuntu4 and 5.8.0-0ubuntu2
[19:54] <sil2100> zyga: I also saw the 'first letter corruction' in the panel, where the title of the active window was
[19:54] <zyga> sil2100, another screenshot on the way
[19:55] <sil2100> zyga: ok, so maybe it was an unity bug - which has been fixed in some staging unity version
[19:56] <sil2100> zyga: you can try the unity-team ppa if it fixes the issue
[19:56] <sil2100> Those might introduce more bugs, but you can always revert to the previous one
[19:57] <zyga> http://ubuntuone.com/6kXxBB5RoPk33pie70vra5
[19:57] <zyga> that's the one in the help screen
[19:57] <zyga> I cannot right now, I'm running a graphical app for the past 8 hours
[19:57] <zyga> I cannot exit it
[19:57] <zyga> (sucking all CPU during that time)
[19:58] <sil2100> zyga: polski ;)
[19:58] <zyga> yeah
[19:58] <sil2100> zyga: na szczęście to już najprawdopodobniej naprawione
[19:58] <sil2100> zyga: just give it a shot once you'll be able to
[19:58] <zyga> ok
[19:59] <zyga> on free drivers I had different issues
[19:59] <sil2100> At least we'll know for sure if it's fixed or just something specific for my system
[20:00] <zyga> sil2100, also occurs in the hud, type ł
[20:00] <zyga> sil2100, <space>ł looks good
[20:00] <zyga> sil2100, but initial ł is corrupted
[20:02] <sil2100> zyga: actually, then this might have been a bug in nux
[20:02] <zyga> sil2100, shall I report any of them?
[20:02] <sil2100> zyga: I would first check the unity-team/staging ppa's
[20:03] <zyga> ok
[20:03] <sil2100> Not to waste time on filling the bug report for something that might have been already dealt with - if it would be still not fixed for you, please report a bug
[20:04] <sil2100> I'm currently using 2.8.0+bzr606ubuntu0+326 of libnux-2.0-0, from unity-team staging
[20:06] <zyga> sil2100, do you think the gpu type is important (apart from just the gpu vendor?)
[20:08] <sil2100> zyga: I don't think so, not regarding this problem I think - fglrx has many specific quirks just by itself
[20:53] <mhall119> woot!  Got an app indicator for my python/gtk app working!
[21:06] <bschaefer> thomi, ping
[21:06] <thomi> bschaefer: yo
[21:06] <bschaefer> soo would you know why self.hud.toggle_reveal() doesn't feel like doing anything in test_ibus.py?
[21:07] <thomi> does unity log anything?
[21:07] <bschaefer> theres no error, it just doesn't open anything
[21:07] <thomi> bschaefer: it's better to use the ensure_visible / ensure_hidden
[21:07] <bschaefer> I tried visible too
[21:07] <thomi> bschaefer: also, make sure you set unity to log at DEBUG level
[21:07] <bschaefer> for the autopilot tests?
[21:08] <thomi> yeah, look at how we do it in the launcher tests
[21:08] <bschaefer> o my...I tried the test_hud.py and my system crashed one sec
[21:08] <thomi> :)
[21:09] <bschaefer> I swore I checked that before I bugged you! haha
[21:09] <thomi> no worries - I'm waiting for nux to build on a VM....
[21:10] <bschaefer> yeah i saw that...jenkins is not a nice person
[21:10] <bschaefer> also saw I messed up space tab/indention in TextEntry.cpp Thanks for fix those :)
[21:14] <thomi> bschaefer: oh, that's automatic for me. I suggest you use an editor that takes care of trailing whitespace & tab/space indentation for you
[21:15] <bschaefer> I have my tabstop set to 2
[21:15] <bschaefer> which I thought was the standard
[21:17] <bschaefer> thomi, I see that you use logger = logging.getLogger(__name__) in the launcher test
[21:17] <bschaefer> are you saying you want me to add some logging info in the hud?
[21:17] <thomi> bschaefer: no, that's for the autopilot logging
[21:17] <thomi> umm, hang on
[21:18] <bschaefer> or when I compile unity set it to debug mode
[21:18] <thomi> sorry, dash tests
[21:18] <thomi> line 20 & 21
[21:18] <thomi> self.set_unity_log_level("unity.shell", "DEBUG")
[21:18] <thomi> but to start with, I'd just try:
[21:19] <thomi> self.set_unity_log_level("unity", "DEBUG")
[21:19] <bschaefer> oo
[21:21] <thomi> bschaefer: whatever unioty logs while your test is run will be attached to the test.
[21:21] <thomi> I suspect the issue is that you're running AP from within a VM, and the tap times are too long.
[21:21] <thomi> (I assume you're still using a VM for development?)
[21:22] <bschaefer> thomi, hmm odd, now it says it doesn't know what self.hud is!
[21:22] <bschaefer> and yes
[21:22] <bschaefer> I just got a laptop yesterday though, soon Ill have real hardware :)
[21:22] <bschaefer> well ordered it
[21:23] <thomi> cool
[21:25] <bschaefer> thomi, if only I had let the test finish it would have told me no hud exist! I thought python would tell me as soon as it it self.hud...
[21:25] <bschaefer> as I just have to add hud to __init__.py
[21:25] <thomi> ahhh, ok
[21:33] <bschaefer> thomi, hmm so it looks like Ill have to make a 'class Hud' in the emulator, pretty much like the dash.py emulator
[21:33] <bschaefer> so the __init__ function can see it, so I can use self.hud
[21:33] <thomi> bschaefer: why's that? You shouldn't need to
[21:34] <thomi> bschaefer: which __init__ function? The one for AutopilotTestCase?
[21:34] <bschaefer> the __init__.py under test
[21:34] <Breetai> In Ubuntu 3d I can change virtual desktops with ctrl-alt <direction key> is there some way to do that in unity2d?
[21:34] <bschaefer> when I try to import hud
[21:35] <bschaefer> this wont work self.hud = Hud() as there is no Hud class in the hud.py emulator
[21:38] <bschaefer> thomi, unless I just so self.hud = HudController
[21:38] <thomi> bschaefer: yes, do that :)
[21:38] <thomi> eventually someone will make a Hud class
[21:50] <bschaefer> thomi, so more problems...yay. So the HudController takes 2 arguments and when I give it KeybindingsHelper, it then gives me this error
[21:50] <bschaefer> AttributeError: type object 'KeybindingsHelper' has no attribute 'iteritems'
[21:50] <thomi> bschaefer: ahhhh yes
[21:50] <thomi> ok, you know what? The simplest way may be to amke a Hud class.
[21:51] <bschaefer> haha :) alright
[21:51] <thomi> inside the class, set the controller. TO get the controller, call HudController.get_all_instances()
[21:51] <thomi> that returns a list, whose length should be 1
[21:51] <bschaefer> self.controller = DashController.get_all_instances()[0]
[21:52] <bschaefer> pretty much like that?
[21:52] <bschaefer> so, Im guessing the class Dash is going to be pretty similar to what Ill have to do with the class Hud
[21:55] <thomi> yeah
[21:55] <thomi> bschaefer: you may want to do that in more than one step though, and assert that len(controllers) really is 1
[21:55] <bschaefer> alright!
[22:14] <Will123456> hey guys. i'm seeing how easy it'd be to fix https://bugs.launchpad.net/unity/+bug/959339 , but i'm not familiar with the codebase. is there any documentation, or do you just have to dive in?
[22:26] <bschaefer> thomi, sweet, had to a bit of re working, but the hud works now with a self.hud. I have to go make sure I didn't mess up any test_hud.py test though
[22:26] <thomi> bschaefer: ok. Feel free to poke me when you have a MP up and running
[22:26] <thomi> I will be offline for lunch in a bit though, so feel free to email me
[22:26] <bschaefer> thomi, will do! Ill try to get the hud class looking a lot like the dash, with the property and stuff
[22:27] <thomi> Will123456: the best way is to get the code and ask questions here if/when you get stuck.
[22:27] <thomi> sweet
[22:27] <bschaefer> thomi, alright will do! Have a good lunch
[22:41] <Will123456> thomi: thanks, i'll give it a go
[23:29] <Will123456> thomi: i've got the code and i've identified where i think the changes need to be made. beyond that i'm really not sure what to do
[23:30] <bschaefer> Will123456, have been able to compile/run the code from trunk?
[23:31] <Will123456> bschaefer: i've just downloaded the tools needed to do that, so i'll read through the readmes and try it
[23:31] <bschaefer> Will123456, here is a good one. http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source
[23:32] <bschaefer> Will123456, after your able to get unity compiled then you can start messing with the code :)
[23:33] <Will123456> bschaefer: thanks! looks like that's just what i need
[23:33] <bschaefer> Will123456, your welcome, let me know if you get stuck
[23:34] <Will123456> i'm hoping the fix to that bug'll get in before the 12.04 release
[23:34] <Will123456> it seems like a pretty major regression and at least in my case totally ruins my workflow :P
[23:35] <bschaefer> looks like a fun bug :)
[23:35] <Will123456> have you not had any problems with it?
[23:35] <Will123456> unity-2D follows the spec exactly, so it's only the 3D version that is wrong
[23:36] <bschaefer> i usually just live in a terminal, and don't use the launcher much haha
[23:36] <bschaefer> and usually only have 1 window type per workspace
[23:37] <Will123456> bschaefer: maybe that's why it's not been a problem for you. i'm surprised how little it's been noticed
[23:37] <bschaefer> ie, 1 terminal for each workspaces, so I don't run into that problem
[23:37] <bschaefer> that would annoy me though!
[23:38] <Will123456> i had this irc terminal window full screened, so clicking from gedit (reading the readmes) to the terminal (to compie unity) was impossible because the full screen irc window kept appearing instead :(
[23:39] <bschaefer> that seems like a very big regression!
[23:42] <Will123456> i'm desperately hoping that someone will take it on before the final release, since i'm getting no where fast :P
[23:43] <bschaefer> I should be able to take a look at that next week, if you don't fix it :)
[23:43] <Will123456> i'll hold you to that :P and i'll try my best to make sure you don't have to!
[23:44] <bschaefer> well that bug only got reported 10 days ago, sometimes it takes  while to get some attention. Im sure if I don't someone will!
[23:45] <bschaefer> Will123456, o and it has a Milestone attached to it, so it'll get attention!
[23:45] <Will123456> bschaefer: i'm pretty new to all this - what does an attached milestone imply?
[23:46] <bschaefer> it means the next by the next release we want it fixed! ie. we want it fixed by Unity 5.10
[23:46] <bschaefer> if you click on it up by the bug you'll see a list of bugs
[23:48] <Will123456> ah, gotcha :)