[00:09] <bmcorser> nn
[00:19] <bschaefer>  /msg hey jay
[00:19] <bschaefer> ops
[00:19] <thumper> :)
[00:19] <bschaefer> thumper, also think I found a good fix for the last problem :)
[00:20] <bschaefer> the ibus, not the alt+f1 (will get to that soon)
[00:22] <thumper> cool
[00:22] <thumper> looking forward to all this landing in trunk
[00:23] <bschaefer> me too! The korean bug has been bothering me for sometime and im happy this will get fixed :)
[00:24] <bschaefer> thumper, also the fix is when the dash is about to hide it has to SetKeyFocusArea to NULL so the end key nav focus signals fires
[00:24]  * bschaefer is hoping that is a correct way to do this
[00:25] <thumper> bschaefer: double check with jaytaoko
[00:25] <bschaefer> will do!
[02:31] <tgm4883> Is there any documentation on working with the new videos lens in 12.04?
[02:32] <mhall119> tgm4883: what kind of documentation are you looking for?
[02:32] <tgm4883> mhall119, along the lines of what kind of data the videos lens is expecting
[02:33] <mhall119> tgm4883: same thing any lens is expecting, url, image, name, description
[02:33] <tgm4883> Looking at the screenshots, it still seems short of working really well with episodic content, but it's a start
[02:33] <mhall119> tgm4883: the videos lens isn't the same as what was designed for Ubuntu TV
[02:33] <tgm4883> mhall119, right
[02:34] <mhall119> you're right that it's not designed to handle episodic content
[02:36] <tgm4883> mhall119, will that be making it's way into the videos plugin? or is there plans for a separate plugin for UTV
[02:36] <mhall119> I'm not sure how you'd successfully navigate heirarchical data like that in the dash
[02:37] <mhall119> tgm4883: you can probably add a "series" category to the video lens, but how to get a list of episodes form that, I'm not really clear on
[02:37] <tgm4883> mhall119, you'd have to have a lens that showed top-level content (just show title), then be able to click on that and list all shows with that title
[02:37] <tgm4883> would be similar to a search I guess
[02:38] <tgm4883> catagories and sources are defined in the lens though, not the scope right?
[02:38] <mhall119> categories are
[02:38] <tgm4883> Not something I can add on the fly
[02:38] <mhall119> no
[02:39] <tgm4883> cause that would be another way of doing it
[02:39] <tgm4883> allowing to add 'catagories' that were just the show title
[02:39] <mhall119> unfortunately categories aren't allowed to change dynamically like that
[02:40] <mhall119> or fortunately, depending on your perspective
[02:41] <tgm4883> and sources doesn't really make sense for show titles
[02:43] <mhall119> like I said, the Dash isn't really designed for browsing heirarchical data like this
[02:43] <mhall119> if you have an application that can, you can have the Dash search for the series, then open the series in that app
[02:44] <mhall119> like how the music lens will list albums, but opens the albums in the music app, not the dash
[02:47] <tgm4883> mhall119, doesn't really work well for my use case
[02:48] <mhall119> what is your use case?
[02:48] <tgm4883> although really, it makes more sense to wait for UTV, although I'm unsure of how that will be implemented
[02:48] <tgm4883> I'm making a MythTV lens
[02:48] <tgm4883> err, scope
[02:48] <mhall119> what is your user story I mean, as a user what do you want to be able to do
[02:50] <tgm4883> so I'm sitting at my desktop and want to watch a show while doing some work (just something in the background). MythTV doesn't really support opening up to a series like that (and I'd rather just have it open the particular show in the video player anyway)
[02:51] <tgm4883> although I suppose there isn't really a need to drill down in that scenario. I guess I was mixing that with my UTV plan for a MythTV scope
[05:26] <snadge> anyone here know anyone from amd.. specifically the fglrx team?
[05:27] <snadge> do they even bother to test it with ubuntu? .. theres an option to --builpkg Ubuntu/precise
[09:14] <tsdgeos> can i unload/load the unityshell compiz plugin?
[09:14] <tsdgeos> unity --reset ?
[09:16] <tsdgeos> no that kills compiz altogether
[09:29] <greyback> tsdgeos: maybe using ccsm?
[09:29] <tsdgeos> greyback: unity --advanced_debug worked for what i wanted
[09:30] <greyback> tsdgeos: new to me, will remember that
[09:30] <tsdgeos> greyback: well, basically starts starts gdb instead of compiz :D
[09:30] <greyback> :)
[09:31] <tsdgeos> but with the "correct options"
[09:31] <tsdgeos> doing gdb compiz did not bring up a full unity session for me
[10:24] <didrocks> right, hence the option ;)
[10:24] <didrocks> greyback: btw, so no release this week
[10:24] <didrocks> will be next week
[10:25] <greyback> didrocks: thanks for confirming
[10:33] <rye> Hello, I was wondering whether all the pop-up menus are supposed to be dark in Ambiance? I see mixed results and could not figure out whether that's correct from the bug reports
[12:13] <rye> hi, i wanted to install chromium-browser via dash/software center but dash was keep giving me adobe flash player instead
[12:27] <rye> can I somehow help if currently one of my windows on current workspace has an empty triangle as if it was on another workspace?
[12:28] <om26er> rye, screenshot please?
[15:27] <rye> om26er, http://ubuntuone.com/1MiPjEC2429h56eUzkqPrL - look at the launcher, below gimp there is an app that is at the front
[15:28] <rye> om26er, if i minimize all windows then unity finds this window too, it is not listed in alt+tab switcher
[15:28] <om26er> yeah I face it too
[15:28] <om26er> if you switch to a different workspace and come back it will fix ;-)
[15:28] <didrocks> mhall119: hey, aroudn?
[15:29] <om26er> we have it reported somewhere I was looking for the bug number a few hours ago didn't find it :/
[15:29] <om26er> rye, ^^
[15:29] <mhall119> didrocks: yup
[15:29] <didrocks> mhall119: so, I'm looking at your quickly template
[15:30] <didrocks> mhall119: nice work, I think you got it quite easily :)
[15:30] <mhall119> didrocks: the packaging bits may change, I'm waiting on the ARB to decide how they're going to handle lenses/scopes
[15:30] <rye> om26er, hm, yep - it does fix it, ok :)
[15:30] <mhall119> didrocks: can you help me turn this template into an installable package?
[15:31] <didrocks> mhall119: sure, so the python module needs to be in /opt, isn't it?
[15:31] <mhall119> didrocks: for the ARB, but they may end up maintainging lens packaging themselves, in which case I'll change it to use normal system paths
[15:32] <jokerdino> guys, just a quick check. is the white sub menus in ambiance a bug or feature?
[15:32] <rye> om26er, sorry about the picture, i was too involved translating the top part that i failed to understand it has an english equivalent
[15:32] <rye> unpublishing
[15:33] <om26er> uuh I didn't notice looks kinda cool :p
[15:34] <didrocks> mhall119: ok, let's see how quickly package goes in it
[15:35] <didrocks> mhall119: so, you shouldn't import the upgrade method from the application template (they have nothing in common)
[15:37] <mhall119> I was wondering about that...
[15:38] <didrocks> yeah, this command is really template specific
[15:39] <tsdgeos> greyback: https://code.launchpad.net/~aacid/unity-2d/unity-2d_fix_starting_size_problem/+merge/94007
[15:39] <greyback> tsdgeos: looking
[15:39] <tsdgeos> greyback: i'm not really happy with the fix, but I can no longer reproduce it, so that makes me happy :D
[15:40] <mhall119> didrocks: I'm struggling with what to do about "quickly run"
[15:40] <mhall119> since you'd have to copy your .lens file into /usr/share/unity and "unity --replace" in order for it to show up
[15:40] <didrocks> mhall119: I really thing that unity should pick on the fly the new lenses :/
[15:40] <didrocks> but yeah, I was sure it was an issue there
[15:41] <didrocks> first, looking in a local ir
[15:41] <mhall119> didrocks: there's a bug for it, and njpatel says it should be do-able
[15:41] <didrocks> dir*
[15:41] <didrocks> and running "unity"
[15:41] <didrocks> (no need for --replace as my warning it telling :p)
[15:41] <mhall119> I'd like to have that working for 12.04
[15:42] <didrocks> I'm wondering
[15:42] <didrocks> something sudoish is not great
[15:42] <didrocks> so copying in a local dir
[15:42] <didrocks> and running unity is maybe doable
[15:42] <didrocks> I can maybe try to have a look at that
[15:43] <didrocks> if we can't do it, we will require sudo :/
[15:43] <didrocks> mhall119: quickly package seem to do what you expect it to do, isn't it?
[15:44] <mhall119> yes
[15:44] <didrocks> so as release, share
[15:44] <didrocks> edit, doesn't show .service and .lens, but I think it's better that way
[15:45] <didrocks> quickly configure only shows the command that are relevant to the derived template
[15:45] <mhall119> didrocks: FYI https://bugs.launchpad.net/unity/+bug/606277 is the bug for recognizing new lenses without restarting
[15:46] <mhall119> yeah,  I thought about adding .service and .lens, but it's not really something that should be modified regularly
[15:46] <didrocks> mhall119: yeah, unfortunatly, this bug is not a high prio
[15:46] <didrocks> quickly debug still works \o/
[15:46] <mhall119> didrocks: yeah, I've asked for it's priority to be changed
[15:47] <didrocks> mhall119: we have 80 precise release critical bug before getting to anything else unfortunatly :/
[15:47] <didrocks> mhall119: but looking at a local folder, I can maybe handle it in the unity code
[15:47] <didrocks> that would at least enable developping a lens without using sudo
[15:47] <didrocks> or hum
[15:48] <didrocks> we can maybe be smarter
[15:48] <didrocks> like, first time, requiring copying the file
[15:48] <didrocks> then, you don't need to
[15:48] <mhall119> if I was any good with C, I'd commit the patches myself
[15:48] <didrocks> mhall119: it's C++, not C ;)
[15:48] <mhall119> even worse :(
[15:48] <mhall119> I've at least taken classes on C
[15:48] <didrocks> would that be acceptable?
[15:48] <mhall119> didrocks: what you mean "first time, requiring copying the file"
[15:49] <didrocks> well, the .service and .lens files are needed to unity to know that, at some point, a lens can connect
[15:49] <didrocks> then, you can kill a lens
[15:49] <didrocks> start it again
[15:49] <didrocks> without restarting unity
[15:49] <mhall119> technically only the .lens is needed, you don't need the .service if you run the process manually
[15:49] <didrocks> indeed, even
[15:49] <didrocks> so, what we can do
[15:50] <didrocks> is quickly create … copying the lens file
[15:50] <didrocks> restarting unity
[15:50] <didrocks> and then, you're ready to roll
[15:50] <mhall119> ew
[15:50] <didrocks> "quickly run" run the daemon
[15:50] <mhall119> restarting unity is a horrible user experience
[15:50] <didrocks> you can ctrl + C
[15:50] <mhall119> you lose all of your window placement
[15:50] <didrocks> and run it again
[15:50] <mhall119> not something that you'd expect to happen when you run "quickly create"
[15:51] <didrocks> mhall119: I think we should ask for a confirmation
[15:51] <didrocks> or first quickly run
[15:51] <didrocks> I have no strong opinion, but it can be a way to deal with it as we won't have to autoload support for 12.04 I guess
[15:51] <mhall119> I'm thinking maybe add a "quickly install" that requires sudo
[15:51] <mhall119> much like how Singlet did it
[15:52] <didrocks> and "quickly run" telling "you need to "quickly install at least once?"
[15:52] <mhall119> yeah
[15:52] <didrocks> yeah, that can work
[15:52] <mhall119> and "quickly install" can restart Unity, I think that's acceptable (though still not ideal)
[15:53] <didrocks> so, back on quickly package, it works. If the ARB need to intall the python module in /opt, I need to check that the support I added is still working (it even compiles py to .pyc in /opt/extra…)
[15:53] <mhall119> i need to learn more C/C++ so I can be more helpful here
[15:53] <didrocks> mhall119: it's not that complicated, the thing that will take time it the autopilot test
[15:53] <didrocks> (and the bunch of other issues we have ;))
[15:53] <mhall119> didrocks: my setup.py tells dh_python to install  to /opt/, is that the right way to do it?
[15:54] <didrocks> mhall119: you don't ask that for the module, isn't it?
[15:54] <mhall119> what do you mean?
[15:55] <didrocks> ./usr/lib/python2.7/dist-packages/foo/__init__.py -> ../../../../share/pyshared/foo/__init__.py
[15:55] <didrocks> this is not in /opt
[15:55] <didrocks> you can do it in setup.py as well though, that would be better than my hack through the distro back in karmic time (that shouldn't be supported by dh_python2 even)
[15:57] <mhall119> didrocks: is my template packings putting things in ./usr/lib?
[15:58] <mhall119> I thought it put it all into /opt/
[15:58] <didrocks> not the "python module" for the lens
[15:58] <didrocks> only the bin/ stuff
[16:00] <mhall119> didrocks: oh, so it does, I need to fix that then
[16:00] <didrocks> mhall119: also, you need to add: http://paste.ubuntu.com/851509/
[16:00] <didrocks> to the binary, where there is my code for symlink and such
[16:01] <didrocks> to import the module from /opt
[16:01] <greyback> sdgeos: what should that fix again, the general view size, or the panel
[16:01] <didrocks> mhall119: the only downside of this not being managed at the system level (as what i did in the python-central time), is that you don't get the compilation from .py to .pyc
[16:02] <greyback> ignore that :)
[16:02] <greyback> tsdgeos: I'm still getting the same problem
[16:02] <tsdgeos> greyback: are you?
[16:02]  * didrocks looks at the quickly ubuntu-application template are really miss this time where he had to to hack on this fun project (but so much stuff I'm seeing right now should be broken due to lib/tools evolution…)
[16:03] <greyback> tsdgeos: yep :(
[16:03] <tsdgeos> greyback: i can't reproduce it anymore with that change :-/
[16:03] <greyback> tsdgeos: in fact, I've got it the last 3 times in a row
[16:03] <tsdgeos> lol
[16:03] <greyback> so it's bad timing
[16:03] <tsdgeos> greyback: i have another much more invasive fix, i can push that if you prefer, basically it seems that something in Qt is borked
[16:04] <tsdgeos> that more invasive fix will fix it for sure
[16:04] <tsdgeos> let me push that one
[16:04] <greyback> tsdgeos: yeah let me try it
[16:06] <didrocks> mhall119: as well, drop the import from the "upgrade" command as told
[16:06] <didrocks> mhall119: if you need any help/review on the template, please ping me
[16:06] <didrocks> mhall119: seems you caught it quite easily how the (simple) inheritance works :)
[16:07] <didrocks> mhall119: do you need packaging for the template itself?
[16:07] <mhall119> didrocks: in a meeting in -community-team atm
[16:08] <mhall119> but yes, I'll ned packaging for the template itself
[16:09] <didrocks> mhall119: will propose a branch shortly then
[16:09] <mhall119> thanks
[16:12] <tsdgeos> greyback: pull again
[16:21] <didrocks> mhall119: just a question, shouldn't we move your template to a subdir? and then create the other scope/templates as other dirs? (just one source, multiple binary packages)
[16:21] <mhall119> didrocks: yeah, I just wasn't thinking of that when I started
[16:21] <mhall119> I'll mkdir and bzr move everything
[16:22] <didrocks> mhall119: no worry, I'll bzr mv while doing the setup.py
[16:22] <didrocks> (as needed for packaging
[16:22] <didrocks> I'll propose you a branch then :)
[16:22] <mhall119> cool
[16:32] <tsdgeos> greyback: is that better?
[16:34] <greyback> tsdgeos: yes actually
[16:34] <greyback> tsdgeos: yes actually
[16:34] <greyback> stupid multi-monitor :D
[16:34] <tsdgeos> greyback: note that i'm doing one of the "Qt donts" that is setting the size from a resizeEvent
[16:35] <greyback> tsdgeos: yeah I noticed that
[16:37] <tsdgeos> greyback: but should be "safe"
[16:37] <tsdgeos> "famous last words" TM
[16:38] <greyback> Yeah :) I'm not so keen on it tho, could you run it by saviq/kaleo in case they have alternative idea?
[16:39] <greyback> I admit I'm stumped by it
[16:43] <tsdgeos> greyback: added them to the MR
[16:43] <tsdgeos> greyback: i've been tracing it inside Qt, basically there's something that sometimes happens in the wrong order,
[16:44] <tsdgeos> though can't say why it does not if oyu have the panel already started
[16:44] <greyback> tsdgeos: is there a bug in the Qt bug tracker about it?
[16:44] <tsdgeos> haven't looked
[16:45] <tsdgeos> but i don't think you'd be able to reproduce it with something small
[16:45] <greyback> if that's the only possible workaround, then it'll be good to log it with qt people
[16:45] <greyback> of course
[16:47] <tsdgeos> greyback: if you think it's worth the time i can strip off things until i end up with two codebases as small as possible that reproduce the bug
[16:49] <greyback> tsdgeos: that could take some time. No I think you can be more useful in other ways right now :)
[16:50] <greyback> tsdgeos: I'll check in with Sam tomorrow to see where he is with the Metacity work, and get you to continue working on the MM stuff
[16:50] <tsdgeos> cool
[17:01] <kklimonda> hey, I have a problem with some applications disappearing from alt+tab - any idea what that may be about?
[17:01] <kklimonda> (other than it being a bug ;))
[17:02] <Daekdroom> kklimonda, do they also appear in the launcher with a hollow arrow, as if they were in another workspace?
[17:02] <kklimonda> Daekdroom: yeah
[17:02] <Daekdroom> kklimonda, try pressing Super + S twice and see if it persists.
[17:02] <kklimonda> Daekdroom: thanks, that fixed it
[17:03] <kklimonda> Daekdroom: is that another bug related to windows being placed between two workplaces? I remember seeing bugs related to that around 11.04
[17:04] <Daekdroom> I don't know.
[17:08] <elopio> greyback: ping. I need some help with the testability driver.
[17:08] <elopio> do you have time?
[17:13] <Andy80> what kind of sourcery is this http://www.ubuntu.com/devices/android :D ????????
[17:13] <mhr3> greyback, heads up - there's a small abi break coming to unity-core
[17:13] <mhr3> but just abi
[17:14] <kancerman> thank you to whoever un-defaulted hiding the launcher :D
[17:17] <racarr> :p
[17:17] <racarr> Err. whoops. middle click error...
[17:31] <kklimonda> Andy80: no idea but it actually looks interesting
[17:32] <kklimonda> I wonder how usable it is going to be though when most phones have only 512MB of ram
[17:34] <Andy80> kklimonda: if I understand correctly is not something you could install on your own phone.... (even if it was a powerfull Galaxy Nexus), it requires some customization to integrate it with Android. I think it's just an idea, a good one, but nothing available yet.
[17:35] <kklimonda> Andy80: from what I can tell it's more than that
[17:35] <kklimonda> Andy80: they talk about how you can run both at the same time
[17:36] <kklimonda> ah, it uses google apps (docs, calendar) for most stuff - maybe that's how they are going to fit it in 512MB ram
[17:37] <Daekdroom> So it's an Android device you connect to a monitor and WHAM! You have Ubuntu as a PC and Android as a phone at the same time.
[17:37] <kklimonda> yeah
[17:37] <kklimonda> which would actually be pretty coo
[17:37] <kklimonda> cool*
[17:37] <kklimonda> if my phone had like 2GB+ ram ;)
[17:38] <Daekdroom> Well, if they put the RAM requirement at 512, then it must work with that little..
[17:40] <kklimonda> I'm not convinced - especially that they want you to "forget the office PC"
[17:41] <kklimonda> stupid TB uses well over 150MB of ram and I have really small collection of emails
[17:42] <kklimonda> but I love the idea itself
[18:26] <greyback> elopio: hey, I'm here now. How can I help?
[18:26] <greyback> mhr3: ok. When it gets merged, it should trigger a unity-2d build too so all should be well
[18:28] <DebolazW> Meh, I'm a sad panda. Application titles still look weird on 12.04 :(
[18:30] <elopio> greyback: I wasn't able to see the application on the visualiser, but now I can.
[18:30] <elopio> greyback: so, I'll probably bother you again some time in the future. :)
[18:30] <greyback> elopio: you're welcome to :)
[18:31] <elopio> greyback: oh, and here I think that rubygems is also a requirement. https://wiki.ubuntu.com/Unity2DTestability
[18:32] <greyback> elopio: yeah it is, but I unless I've a bug in the package, it should've been installed
[18:32] <elopio> greyback: then you have a bug in the package. It wasn't installed here.
[18:33] <greyback> elopio: ok, thanks for telling me
[18:34] <elopio> greyback: np. Thanks to you, your talk has been really useful for us.
[18:34] <DebolazW> Someone remind me, what was the command I used to submit bug data, and what application do I specify for problems in drawing application titles correctly? (Compiz?)
[18:34] <greyback> elopio: I'm glad. Any (more) problems, let me know
[18:34] <elopio> ok.
[18:35]  * DebolazW was told to do this earlier here, but havent had access to the computer in question until now.
[19:11]  * DebolazW pokes people.
[20:25] <mhall119> Debolaz: ubuntu-bug perhaps?
[22:05] <balloons> anyone else having there launcher non appear with set to autohide? this is on multimonitor setup in precise, running up to date as of now
[22:05] <thomi> balloons: are you using an nvidia chipset?
[22:05] <balloons> thomi, yes, this is on nvidia
[22:05] <thomi> balloons: there's a bug in the latest nvidia drivers that stops autohide working
[22:06] <balloons> great, do you know the number? I'll subscribe to it
[22:06] <thomi> hmmm, no. jason was following it up with the nvidia people.
[22:06] <thomi> let me check LP quickly
[22:06] <balloons> ok, thanks
[22:08] <thomi> balloons: ok, it seems there's not a bug for it yet
[22:08] <thomi> I'll ask jason when I next see him online
[22:08] <balloons> would you like me to create.
[22:08] <balloons> ?
[22:08] <balloons> i'm looking to open another bug as well.. I get x crashes occasionally when crossing my mouse across the 2 monitors
[22:09] <balloons> it's happened enough to be a real bug.. always the same way
[22:09] <thomi> balloons: if you like
[22:12] <balloons> k, doing it.. thanks for your help thomi
[22:42] <balloons> thomi, fyi if your interested lp:938227
[22:42] <balloons> i can never get that syntax right.. bah  lp:938227
[22:43] <balloons> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/938227
[22:43] <thomi> Cheers