[05:33] <RAOF> smspillaz: What is GLTexture->priv->mipmapSupport meant to be used for?  In particular, why does the texture code generate mipmaps regardless of that value?
[07:06] <kvalo> morning
[07:17] <coz_> ok I am going to assume that Amber1  has booted into the live cd
[07:17] <coz_> I am off to bed
[07:41] <smspillaz> RAOF: I suppose it's used to check if there is mipmapping support? although if that is false and we are generating mipmaps then it is a bug in compiz
[07:41] <didrocks> good morning
[07:42] <kvalo> didrocks: good morning
[07:42] <didrocks> hey kvalo
[07:43] <RAOF> smspillaz: Ok, then the follow up to bug #682327 involves a bug in compiz; the TfpTexture has mipmapSupport = false and SIGSEGVs while generating a mipmap.
[07:44] <RAOF> (That particular bug is fixed-ish in mesa git - now, rather than assert(), it SIGSEGVs :))
[08:18] <MacSlow> hey folks
[08:24] <didrocks> guten morgen MacSlow
[08:24] <didrocks> hey RAOF
[08:25] <kamstrup> didrocks: I just merged https://code.launchpad.net/~unity-team/unity/mmaped-icons/+merge/37634 and there is definite SRU potential there
[08:26] <didrocks> kamstrup: SRU? for maverick?
[08:30] <didrocks> kamstrup: if you talk about a potential issue is natty, does it put https://code.launchpad.net/~mterry/unity/683735/+merge/42406 obselete?
[08:30] <didrocks> oupsss, not that one
[08:30] <didrocks> one sec
[08:30] <didrocks> https://code.launchpad.net/~robert-ancell/unity/lp682345/+merge/42432
[08:30] <didrocks> kamstrup: ^^
[08:31] <kamstrup> didrocks: It's for M. I think Unity trunk isn't using the old pixbuf cache
[08:31] <didrocks> kamstrup: oh ok :)
[08:32] <kamstrup> didrocks: it works well here, and njpatel confirmed it as well
[08:33] <didrocks> kamstrup: yeah, but we are in freeze right now dude
[08:33] <didrocks> kamstrup: and tomorrow there will be a release
[08:34] <kamstrup> didrocks: oh, it was not because I wanted to rush it in. It was just to put it on your radar if updates for M where darwing near
[08:34] <didrocks> kamstrup: heh, ok, nice! I'll keep an eye on it :)
[08:54] <kamstrup> Is the workspace button in the swicther supposed to do something? Or is it just a place holder?
[08:55] <kamstrup> s/switcher/launcher/
[08:59] <njpatel> Morning
[09:02] <MacSlow> hey njpatel, kamstrup
[09:03] <njpatel> hey MacSlow
[09:03] <njpatel> MacSlow, how's it going with th event-dispatcher bits?
[09:04] <MacSlow> njpatel, at least it's compiling... but not ready for merge yet.
[09:04] <njpatel> coolio
[09:05] <njpatel> MacSlow, are you expecting to merge today/tomorrow, or later?
[09:05] <MacSlow> njpatel, I try today of course (btw... it's running and showing something too)
[09:06] <njpatel> MacSlow, nice!
[09:06] <MacSlow> njpatel, but since I need to go to the doc after lunch (and don't know how long that'll take) it's 50:50
[09:06] <MacSlow> njpatel, dBusmenu critical-warning bugging me atm
[09:21] <njpatel> smspillaz, duuuuuude
[09:24] <smspillaz> njpatel: uuuuude ?
[09:24] <smspillaz> njpatel: what's up?
[09:24] <smspillaz> (and don't say the sky since I will punch this wall next to me)
[09:24] <njpatel> smspillaz, I could say something else but maybe not for this channel
[09:24] <njpatel> smspillaz, aaaaaanyway
[09:25] <njpatel> smspillaz, Compiz knows where the mouse is? Yes or No?
[09:25] <smspillaz> njpatel: yes and no
[09:25] <njpatel> smspillaz, touché
[09:25] <smspillaz> njpatel: it only tracks MotionNotify where we have a grab otherwise pointerX and pointerY are updated on button, enter and leave events
[09:26] <smspillaz> njpatel: but for plugins which don't want to grab the screen we have a mouse polling plugin
[09:26] <njpatel> oh, so you need to just do polling too
[09:26] <smspillaz> (basically tracking the mouse position == lots of useless wakeups, no need for that)
[09:26] <njpatel> (which makes sense, but I was led to believe they was magic here)
[09:26] <dbarth__> you guys know about the glib::source issue, right?
[09:26] <smspillaz> dbarth__: which ones is this?
[09:26] <smspillaz> *one
[09:26] <njpatel> didrocks, what happened about the GLib::Source issue?
[09:27] <njpatel> dbarth__, we were discussing it just now
[09:27] <didrocks> njpatel: hum? it should be fixed
[09:27]  * smspillaz would like to know what it is!
[09:27] <didrocks> first, everyone ensure that you have:
[09:27] <didrocks> 1:0.9.2.1+glibmainloop2-0ubuntu4
[09:27] <didrocks> then, let's rediscuss it :)
[09:27] <dbarth__> finding the bug
[09:28] <smspillaz> (you'd be so much cooler if you kompiled from source like me)
[09:28] <dbarth__> i just filed it, grrr
[09:28] <njpatel> smspillaz, i pinged you yesterday about it, boost::function is null
[09:28] <didrocks> smspillaz: I'm compiling from source :)
[09:28] <smspillaz> njpatel: I am pretty sure I fixed that like 2 days ago
[09:28] <njpatel> didrocks, riight, there's a new compiz :)
[09:28] <didrocks> smspillaz: and I have the distro defaults + patch at least :p
[09:28] <smspillaz> njpatel: and I also tried launching g-a-p with the glibmm branch - no sigabrt
[09:28] <njpatel> smspillaz, right, you were wondering if didrocks had the patch in ubuntu or not (are you a goldfish? :)
[09:29] <didrocks> njpatel: it's a distro-patch lovely taken from the git repo :)
[09:29] <smspillaz> njpatel: I think I was wondering that (it was at 2AM, not guarunteed to remember)
[09:29] <njpatel> smspillaz, :)
[09:29] <smspillaz> njpatel: also I'm sammy the salmon
[09:29] <njpatel> heh
[09:29] <smspillaz> njpatel: http://www.youtube.com/watch?v=IVu2cX0jEYk
[09:30] <njpatel> smspillaz, so, mouse position. Any way we can add something to Xorg to get it without it taking weeks and it being somewhat stable?
[09:30] <smspillaz> njpatel: you can do it already by registering for MotionNotify on every single window
[09:30] <smspillaz> njpatel: prepare to murder your battery life though
[09:30] <njpatel> smspillaz, i really don't want to do that
[09:31] <smspillaz> njpatel: well you want to track the mouse position right ?
[09:31] <smspillaz> the only way to do that is to get tons of updates about the position
[09:31] <njpatel> smspillaz, I'm saying, could we write a module for X that let's you register a area that your interested in, and only pings you when the mouse moves into that area?
[09:31] <dbarth__> crap, LP ate my bug report or what?!
[09:31] <smspillaz> njpatel: X already has that
[09:31] <smspillaz> njpatel: XSelectInput (dpy, w, EnterMask | LeaveMask);
[09:32] <smspillaz> njpatel: see xev
[09:32] <njpatel> smspillaz, I'm saying "area on screen", not "a window"
[09:32] <dbarth__> https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/684038
[09:32] <njpatel> smspillaz, so we can do proximity without screwing applications
[09:32] <dbarth__> ah, of course it says it's invalid, since it cannot retrace it
[09:33] <smspillaz> njpatel: you could do it like we do it in the wall plugin
[09:33] <njpatel> smspillaz, how is that?
[09:33] <dbarth__> and yet, i had all debug packages installed, and that was from a package install, not from source...
[09:33] <didrocks> dbarth__: you don't have the latest compiz
[09:33] <didrocks> dbarth: the one which should fix that
[09:33] <smspillaz> njpatel: compiz uses little windows on the edge of the screen -> when we enter them you get an event and then we can unmap them straight away once the user has entered
[09:33] <dbarth> ah, it's really fixing that one?
[09:34] <smspillaz> njpatel: and from there poll the mouse to determine if we have left
[09:34] <smspillaz> njpatel: it's a bit of a work-a-round, but it is far better than writing a whole new X extension to handle this
[09:34] <njpatel> smspillaz, urgh
[09:34] <smspillaz> njpatel: it's a bit workaroundish but I don't think writing new X extensions is really a good way to go
[09:35] <didrocks> dbarth: I guess so, please upgrade and keep us in touch
[09:35] <njpatel> smspillaz, but that is clever I guess, unless the mouse is left in that area and your continuously polling
[09:35] <njpatel> smspillaz, I'd like to figure out a clean way of doing it so it's just solved once and for all...I feel like we're going to have this problem a lot
[09:35] <smspillaz> njpatel: if it is proximity and your window is larger than something by 1px then you can be a little smarter about it
[09:35] <dbarth> didrocks: but seriously, there is something wrong here: i had the dbg packages, and still apport couldn't retrace it
[09:36] <smspillaz> njpatel: like, you can shape the window so that it is only the "edges" of the proximity window
[09:36] <didrocks> dbarth: apport is retracing it in a chroot on launchpad
[09:36] <smspillaz> njpatel: and then while inside that proximity window poll
[09:36] <didrocks> dbarth: not related to you having the dbgsym or not
[09:36] <dbarth> didrocks: plus, as i'll be using the dailies (as most contributors who want to help will) and so apport is also going to complain about my version of the packages or waht?
[09:36] <njpatel> smspillaz, could you take a deeper look tomorrow to see what the cost would be for an extension, and even if it's possible?
[09:36] <didrocks> dbarth: and it can't retrace because he has a newer version than you
[09:37] <didrocks> dbarth: yes
[09:37] <didrocks> dbarth: I really think that most contributors won't use the daily
[09:37] <njpatel> smspillaz, yeah, that's what I was thinking, but there's always a chance that the user left their mouse there while typing or something
[09:37] <dbarth> so explaining to me again why we should use it?
[09:37] <smspillaz> njpatel: I'll have a look into it when I get time (still gotta finish your decoration stuff and fix a truckload of bugs and also do jason's stacking stuff)
[09:37] <smspillaz> njpatel: also writing X extensions is hard
[09:37] <didrocks> dbarth:
[09:37] <njpatel> smspillaz, and for that time, we're just polling continuously
[09:37] <didrocks> 1. you merge once a week, before the release, most of the time
[09:37] <smspillaz> njpatel: there is a very small chance of that happening
[09:37] <didrocks> 2. we see that a lot of ubuntu contributors give patch against current release version (like maverick)
[09:37] <smspillaz> njpatel: you'd basically have to be in a 1px by 1px area
[09:38] <dbarth> didrocks: we can bring that offline; i'm complaining, but i really want to see what we need to change to make that useful; at the moment, it's not
[09:38] <smspillaz> njpatel: actually I know a way to remove the polling alltogether too
[09:38]  * dbarth restarts with the newest unity/compiz
[09:38] <smspillaz> njpatel: I'll need to draw a diagram and scan it and send it to you
[09:38] <didrocks> dbarth: well, it is if we don't have to upload each new commit (that's why apport isn't set by default right now, things are moving too fast)
[09:38] <njpatel> smspillaz, sounds like a plan, thanks
[09:39] <njpatel> smspillaz, okay, I'll leave you alone now :)
[09:39] <dbarth> njpatel: hey dude, so you have some magic tricks for the proximity effect?
[09:40] <njpatel> dbarth, maybe, need to try out a couple of things and also see what's in smspillaz's head
[09:40] <njpatel> dbarth, for now, though, just normal roll-over
[09:40]  * njpatel doesn't need phoronix showing Unity with zero battery life
[09:40] <smspillaz> njpatel: just so I can get this right - what exactly are you checking proximity to?
[09:40] <didrocks> doesn't mousepool have a bad effect on battery life?
[09:41] <njpatel> didrocks, yes, no way we're using that
[09:41] <didrocks> ok, same concern about polling continuously then :)
[09:41] <didrocks> njpatel: we already have it activated
[09:41] <dbarth> njpatel: ;)
[09:41] <didrocks> by another plugin IIRC
[09:42] <njpatel> didrocks, urg
[09:42] <didrocks> njpatel: ezoom
[09:42] <njpatel> didrocks, oh, but that's only when it's active (the plugin)
[09:42] <njpatel> i think that's fine, it's the only way it's ever going to work
[09:42]  * njpatel ->tea
[09:42] <didrocks> you mean when the zoom effect is active?
[09:42] <didrocks> (I hope so :))
[09:42] <didrocks> I just hope it doesn't send signals everytime which are lost
[09:42] <didrocks> smspillaz: can you confirm? ^^
[09:43] <smspillaz> didrocks: yes, but only when ezoom asks for it
[09:44] <smspillaz> didrocks: when you are not zoomed, no polling occurrs
[09:44] <didrocks> smspillaz: ok, sounds good then :)
[09:44] <didrocks> smspillaz: I have some weird artifacts something when moving the mouse btw (or switching ws)
[09:45] <didrocks> hard to describe, like if you had a magnet
[09:45] <didrocks> and the electrons would move, making the image to distort
[09:45] <didrocks> (less than 500 ms I would say)
[09:45] <didrocks> I think it's related to nvidia driver
[09:45] <smspillaz> is this with ezoom actually zoomed in?
[09:46] <smspillaz> software cursor is notoriously broken on nvidia
[09:46] <didrocks> no, ezoom not used
[09:46] <didrocks> I didn't get that with 0.8, but it can the driver as well…
[09:46] <didrocks> it's something like twice a day
[09:47] <didrocks> I don't want to have gtkrecordmydesktop recording for a all day :)
[09:48] <didrocks> whole*
[10:09] <didrocks> dbarth: can you add the reproduceable steps to bug #683273?
[10:10] <didrocks> dbarth: that will help smspillaz, I still got it once, but closing the wrong app and launching it again doesn't have the same behavior :/
[10:38] <kamstrup> can't wait to try out the new Dee. It's going to be *so* much more efficient in all kinds of ways
[10:47] <ronoc> good stuff
[11:40] <didrocks> dbarth: did yo usaw my comment about getting reproduceable setps for bug #683273?
[12:25] <kvalo> kamstrup: about making review through email. does lp require gpg signed mail for the commands or is it just really slow today?
[12:27] <kvalo> ah, now found the error reply. yeah, it needs the gpg signature :/
[12:28] <didrocks> dbarth: did you saw my comment about getting reproduceable setps for bug #683273? (2) was disconnected, not sure you answered ;)
[12:37] <njpatel> smspillaz, awake
[12:37] <njpatel> ?
[12:37] <smspillaz> njpatel: yes
[12:37] <njpatel> smspillaz, still hasn't been merged lp:~canonical-dx-team/unity/unity.remove-io-from-pl what are we doing with it?
[12:39] <kamstrup> njpatel: I think that merge is for me, no?
[12:40] <njpatel> daaaamit
[12:40] <njpatel> smspillaz, ignore me
[12:40] <njpatel> no, hold up
[12:40] <smspillaz> njpatel: io-from-pl is me
[12:40] <smspillaz> and I bzr merged i
[12:40] <smspillaz> *it
[12:40] <smspillaz> and it said it was already merged
[12:40] <njpatel> right
[12:40] <njpatel> thanks
[12:40]  * njpatel stops for a second and gathers his thoughts
[12:40] <smspillaz> njpatel: check unity.cpp it should have a ::getWindowPaintList function
[12:41] <njpatel> it doesn't
[12:41] <njpatel> smspillaz,  I just bzr branch lp:unity; cd unity; bzr merge lp:~canonical-dx-team/unity/unity.remove-io-from-pl and it shows that it requires a merge
[12:41] <njpatel> kamstrup, stop confusing me!
[12:42] <kamstrup> njpatel: do you want napalm with your muffins sir?
[12:42] <smspillaz> njpatel: could you merge it then? merging is a pain for me since I have to do it in dbarth's netbook due to my broken install
[12:42] <njpatel> kamstrup, heh, that's just like you ;)
[12:42] <njpatel> smspillaz, sure
[12:43] <smspillaz> njpatel: thanks
[12:43] <njpatel> done
[12:44] <ronoc> kamstrup, got a minute ?
[12:44] <njpatel> ronoc, I approved your ayatana-dev message but it doesn't seem to have come through :(
[12:45] <ronoc> hmm
[12:45] <ronoc> njpatel, I subscribed to the list before sending it, weird ?
[12:45] <njpatel> yeah
[12:46] <njpatel> maybe it takes a bit of time
[12:46] <njpatel> this is launchpad
[12:46] <ronoc> njpatel, :)
[12:48] <ronoc> njpatel, for now I'm going to get this working by being blatant, watch for each client that I know works, just for the short term to get this port going
[13:01] <ronoc> njpatel_, match rules are in the pipline for vala so this should only be a temporary solution
[13:16] <kamstrup> ronoc: sorry, I am already overflowing my brain capacity with this DeeModel porting
[13:16] <kamstrup> ronoc: so unless it's urgent i'd rather wait
[13:18] <ronoc> kamstrup, nws
[14:10] <njpatel> ronoc, sounds good, but just make a bug and milestone for A2 if nothing else, so we don't forget
[14:18] <janimo> jaytaoko: hi, in a LP bug report it was suggested that calling abort() would work without need for asm level hw breakpoint code. Regardless of the solution you pick if it fixes the build I am ok :)
[14:19] <jaytaoko> janimo: so abort() should do ?
[14:20] <janimo> that is what sladen said
[14:20] <janimo> but I have only checked the build and never got to running nux let alone debug it :)
[14:30] <ronoc> njpatel, will do
[14:41] <jcastro> so njpatel
[14:41] <jcastro> tell me about quicklists
[14:41] <njpatel> jcastro, so you did get my ping!
[14:42] <jcastro> wait, what ping?
[14:42] <jcastro> all I heard is that you were selling me out -- continue.
[14:42] <njpatel> like last week
[14:42] <njpatel> twice
[14:43] <njpatel> jcastro, In any case, we're thinking hard about detaching quicklists from the appindicators
[14:43] <jcastro> njpatel: I am up to speed on places now, I chatted with john for a bit
[14:43] <njpatel> jcastro, and building a proper API into libunity for apps to control the launcher icon + quicklists
[14:43] <njpatel> jcastro, as am I, now ;)
[14:44] <jcastro> ok so what does this buy me as an app developer that I don't get with libappindicator?
[14:44] <MacSlow> re
[14:45] <njpatel> jcastro, lets you set up your ApplicationIcon in the launcher to do things like message count/progress
[14:45] <njpatel> jcastro, let's us give an API that reflects the features of the quicklists instead of allowing the clients do things at one end (submenus, custom items) and then not fulfulling at the other end (unity)
[14:46] <njpatel> jcastro, and it means that we start to build a library that you can link to for most tasks in Unity (places, application-icon, message menu (future), soundmenu (future)) etc etc
[14:46] <jcastro> ok, so I get more bling for my app
[14:46] <jcastro> so I can do more things
[14:47] <njpatel> yes, and the API is contract that we can actually fulfill, rather than letting you down when you create a complex gtk-menu and we can't show it
[14:47] <jcastro> Is it possible to do this and keep the appindicator bits though? Say I'm an app author, and I've already ported, but I don't need/want the bling
[14:47] <njpatel> jcastro, the appindicator bits rarely work well, for instance the tomboy one has two quit items
[14:47] <jcastro> like, you're not going to break existing appindicator quicklists things?
[14:47] <njpatel> jcastro, there is only two, one in gwibber and one in tomboy
[14:48] <jcastro> njpatel: right, but what happens when we blacklist the top panel to only show system ones?
[14:48] <njpatel> jcastro, we're hoping we can just make those two use libunity instead of appindicator if it's available
[14:48] <jcastro> where are the other apps going to go?
[14:48] <njpatel> jcastro, appindicator is still there
[14:49] <jcastro> ok, so let's say I write Transmission
[14:49] <jcastro> what changes do I need to make
[14:49] <njpatel> jcastro, nothing right now, I've barely had time to think this through :)
[14:50] <njpatel> jcastro, there are so many things to work out still, like fallbacks etc
[14:50] <njpatel> I'll send a mail to ayatana-dev when I have a good idea whether this is feasible or not
[15:15] <ronoc> world cup announcement coming up
[15:15] <ronoc> njpatel, ^
[15:17] <tedg> ronoc, I'll bet you 10:1 that they're going to disallow touching the ball with your hands.
[15:19] <ronoc> tedg, what, for goal keepers ?
[15:19] <tedg> ronoc, No, I was just being silly.  I have no clue what they'd even be announcing.
[15:19] <tedg> Location?
[15:19] <ronoc> tedg, yup for 2018 and 2022
[15:19] <ronoc> england are looking likely for 2018
[15:19] <tedg> Why two at the same time?
[15:20] <ronoc> tedg, don't know, this is the way they usually do it, so they double up the bribes :)
[15:20] <ronoc> *can
[15:20] <didrocks> ok, with the connect/disconnect spam, sorry if I asked a question twice :)
[15:20]  * tedg needs to get in on that board of directors
[15:20] <didrocks> smspillaz: is there a known issue about alt + tab which can be veryyyyyyyyy slow on some system? (I get that when a ws has… let's say, more than 5 windows)
[15:21] <didrocks> smspillaz: not sure what you need for debugging
[15:21] <didrocks> njpatel: will you release today or tomorrow, btw?
[15:23] <ronoc> tedg, apparently platini is very swayable given the right whiskey
[15:24] <smspillaz> didrocks: intel?
[15:24] <didrocks> smspillaz: no, nvidia
[15:24] <smspillaz> weird
[15:24] <smspillaz> didrocks: does the cpu usage of compiz skyrocket?
[15:24] <didrocks> let me see
[15:24] <tedg> ronoc, All I know is that when going to the bar, not wise to take klattimer, or at least don't follow his lead :)
[15:25] <didrocks> smspillaz: in general, X CPU is high
[15:25] <klattimer> oi tedg!
[15:25] <klattimer> :P
[15:26] <ronoc> tedg, advise noted, although I have been known to enjoy my poison ...
[15:26] <ronoc> apparently england went out in the first round
[15:26] <ronoc> shame, its been a while
[15:26] <ronoc> '66
[15:27] <smspillaz> didrocks: the nvidia driver is doing something stupid then
[15:28] <smspillaz> X CPU skyrocketing is a definite way to tell
[15:28] <didrocks> smspillaz: I can believe you, I'll nag RAOF about that, because end user doesn't care who is doing wrong :)
[15:28] <njpatel> didrocks, later today probably
[15:28] <njpatel> ronoc, was on a call, what happened?
[15:28] <didrocks> and 2 seconds here for an alt+tab is just horrible to live with
[15:29] <ronoc> njpatel, just been announced right now
[15:29] <ronoc> njpatel, http://www.fifa.com/worldcup/bidders/live/index.html
[15:31] <didrocks> smspillaz: well, alt+tab if I don't show the staticswitcher is fine, it's only when I use it
[15:34] <njpatel> ronoc, sweet, thanks
[15:35] <smspillaz> lets see, probably not australia
[15:37] <smspillaz> russia!
[15:37] <njpatel> bastards
[15:38] <smspillaz> njpatel: the iron curtain rises again ;-)
[15:38] <ronoc> russians my god
[15:39] <ronoc> well they know how to pay bribes up there
[15:40] <jaytaoko> It is russia!
[15:40] <smspillaz> ronoc: LOL
[15:40] <smspillaz> ronoc: this is exactly what I was thinking
[15:40] <smspillaz> ronoc: soon there will be something about this on http://uncomfortablemomentswithputin.tumblr.com/
[15:40] <jaytaoko> i think they won fairly!
[15:41] <smspillaz> jaytaoko: probably
[15:41] <njpatel> ronoc, and they aren't English.
[15:41] <ronoc> smspillaz, funny considering all the current wikileaks Russian stuff  and the bribery allegations within Fifa
[15:41] <smspillaz> ronoc: ahahaha
[15:41] <ronoc> njpatel, well there is that aswell
[15:41] <smspillaz> ronoc: have you read some of the diplomatic cables? they sound like gossip girl
[15:42] <smspillaz> "hey I heard that bellersconi had another affair and is too lazy to do anything about it unamed xoxo"
[15:43] <ronoc> smspillaz, just some headlines, I know it does sound like a load of gossip but still is great considering the mass the white house is giving it which in turns makes it all the more seemingly credible for the media,
[15:43] <smspillaz> ronoc: indeed
[15:44] <didrocks> njpatel: "We're clever like that."… that can only be one of you comment :)
[15:44] <njpatel> didrocks, hells yes
[15:44] <ronoc> brb
[15:46] <lamalex> ok so compiz/unity doesn't play so well with dual monitors?
[15:48] <lamalex> jaytaoko, can you fix your line endings so I can sanely review this/
[15:48] <jaytaoko> lamalex: sure
[15:48] <kenvandine> tedg, are we going to need to version indicator-application-service separately for gtk3?
[15:48] <lamalex> thank you
[15:48] <kenvandine> i am assuming so....
[15:48] <kenvandine> which kind of sucks...
[15:48] <njpatel> kenvandine, dbus is effected by gtk3?
[15:49] <kenvandine> no
[15:49] <njpatel> what are they up to in GNOME? ;)
[15:49] <tedg> kenvandine, No, we shouldn't if we don't need a GTK2/3 version of the libapplication.so
[15:49] <kenvandine> but it links against the lib
[15:49] <tedg> kenvandine, Which, honestly, I think we will at some point....
[15:49] <tedg> kenvandine, It doesn't link against libappindicator
[15:49] <njpatel> okay, tea
[15:50] <kenvandine> indicator_application_service_LDADD = \
[15:50] <kenvandine>         $(INDICATOR_LIBS) \
[15:50] <kenvandine>         libappindicator.la
[15:50] <kenvandine> maybe that isn't needed
[15:50] <kenvandine> that's a relief :)
[15:50] <kenvandine> i'll drop that
[15:50] <tedg> kenvandine, I don't think so, that's a bug I think.
[15:50] <kenvandine> we'll find out :)
[15:50] <kenvandine> thx
[15:51] <tedg> kenvandine, They need to share a couple of files, but I think those can just be linked in as .o files.
[15:51] <tedg> (and probably are)
[15:51] <kenvandine> ok, cool it doesn't need that
[15:51] <kenvandine> great
[15:52] <kenvandine> however... of course GIR scanning breaks on natty, even for gtk2 :/
[15:52] <kenvandine> need to tweak it, which i am pretty familiar with now :)
[15:52] <kenvandine> and for gtk3 it doesn't build... seems some api differences in GtkImage
[15:54] <tedg> kenvandine, Uhg
[16:02] <oubiwann> johnlea: you around?
[16:02] <johnlea> oubiwann; yes, but just about to go into a meeting
[16:03] <oubiwann> johnlea: okay, this is fairly urgent... but for after your meeting :-)
[16:03] <oubiwann> johnlea: can you respond to the request here? https://bugs.launchpad.net/utouch/+bug/674958
[16:04] <didrocks> DBO_: FYI, I'm starting working on support of Type=link .desktop file. What do you prefer, keeping them as a bamf_application and don't add a new type (so reading in unity only) or hacking in bamf? (not telling that bamf will recognize it for now)
[16:04] <johnlea> oubiwann; cool, just heard that mark will be 5min late for our meeting so I'll answer it now
[16:04] <oubiwann> johnlea: awesome, thanks!
[16:05] <DBO_> didrocks, what?
[16:05] <didrocks> DBO_: look at /etc/skel/examples.desktop for instance
[16:06] <didrocks> DBO: this is a desktop file with Type=link, unity doesn't handle them right now (and crash… but that's another question)
[16:06] <DBO> oh
[16:06] <didrocks> DBO: I was wondering if you prefer that bamf get a new type like "system/web/link"
[16:06] <johnlea> oubiwann; use case 4.5 is a shortcut to copying and pasting with touch.  The long (and more discoverable) method is 4.6 http://use-case-mapper.canonical.com/specifications/0AU5sFuLRpCpBZGZra2pqY2pfMTU3MmhwbXczcWQ1/use_cases/4_6
[16:06] <DBO> I thought bamf just ignored .desktop files without an exec string
[16:06] <DBO> if it doesn't it should
[16:06] <didrocks> DBO: well, unity is crashing, not bamf
[16:06] <DBO> didrocks, how is Unity crashing?
[16:07] <oubiwann> johnlea: yup, understood
[16:07] <didrocks> DBO: there is no icon associated and so on
[16:07] <johnlea> oubiwann; my meeting is starting now, I'll have to update the buy afterwards
[16:07] <didrocks> DBO: the question there is to add support for them
[16:07]  * oubiwann nods
[16:07] <oubiwann> johnlea: thanks
[16:07] <DBO> didrocks, I should ask
[16:07] <DBO> didrocks, how is unity even involved with that .desktop file?
[16:07] <didrocks> DBO: njpatel agree with adding support
[16:07] <DBO> I mean as far as I can reason, Unity is goign to flat out ignore .desktop files like that
[16:08] <didrocks> DBO: my importer import every desktop file in ~/Desktop
[16:08] <DBO> as a favorite?
[16:08] <didrocks> setting the gsetting key to it
[16:08] <didrocks> right
[16:08] <DBO> ah yeah that might puke...
[16:08] <DBO> okay
[16:08] <didrocks> I would prefer avoid reparsing the desktop file on launch :)
[16:08] <DBO> will make it happen
[16:08] <njpatel> DBO, so what I was saying is that at some point, if we can figure out what URI nautilus is showing, we can make use of desktop files like this
[16:09] <njpatel> DBO, but that's in the future and so for now, we should ignore them
[16:09] <njpatel> otherwise it'll just sit on the launcher doing nothing
[16:09] <didrocks> njpatel: DBO: I have some time to work on this, just tell me if you want a new bamf application type like web/system or a new class or nothing :)
[16:10] <DBO> nothing is fine
[16:10] <DBO> no need to change .desktop files for this
[16:10] <DBO> didrocks, are we okay shipping  patch to nautilus to export URI information over dbus?
[16:11] <didrocks> DBO: you mean, I should reparse it in OpenInstance() ?
[16:11] <didrocks> DBO: hum… that will be needed for nautilus, not sure about others apps :)
[16:11] <DBO> nautilus is the bigger use case
[16:11] <didrocks> like the link can be an OOo file
[16:11] <didrocks> yeah
[16:12] <DBO> nautilus can be a tab provider no different from chromium or firefox
[16:12] <DBO> fuck I should have started with nautilus
[16:12] <DBO> SO much easier
[16:12] <DBO> god I am retarded
[16:12] <njpatel> you are
[16:12] <didrocks> DBO: oh, that's how you do it for chromium and firefox? you expose the tabs over dbus?
[16:12] <DBO> right
[16:12] <didrocks> njpatel: DBO: I really can and want to work on this if you don't mind :)
[16:13] <didrocks> sounds cool and no hurry on it
[16:13] <DBO> okay so short term plan... make it not crash
[16:13] <didrocks> DBO: yeah, jaytaoko made a patch yesterday, do you want to review it?
[16:13] <DBO> yes
[16:13] <didrocks> but the icon is empty, so not the right solution
[16:13] <didrocks> one sec
[16:14] <DBO> then nevermind
[16:14] <DBO> the right solution is this
[16:14] <DBO> in BamfMatcher.c (for libbamf)
[16:14] <didrocks> yep
[16:14] <DBO> there is a method to get a BamfApplication for a desktop file
[16:14] <DBO> you pass true to create one if one does not exist
[16:14] <didrocks> I saw that
[16:14] <DBO> in the creation step
[16:14] <DBO> if the passed .desktop file is not valid for bamf
[16:15] <DBO> (aka the one you showed me)
[16:15] <DBO> return out a null
[16:15] <DBO> then make unity do the null check and move on to the next favorite
[16:15] <didrocks> ok, to just ignore it for now
[16:15] <DBO> then as bamf learns how to handle those types of link .desktop files
[16:15] <DBO> we can enable it
[16:15] <didrocks> ok, let me have a try
[16:15] <DBO> sure :)
[16:16] <didrocks> DBO: btw, can you review https://code.launchpad.net/~didrocks/unity/fix683444/+merge/42493? it's linked to the subject :)
[16:16] <DBO> reviewing
[16:16] <didrocks> oh wait, I didn't push the g_error_free
[16:16] <didrocks> one sec
[16:17] <didrocks> waow, bzr push stucked
[16:17] <didrocks> done
[16:17] <DBO> +1
[16:17] <didrocks> thanks :)
[16:18] <DBO> yeah forgot to free the error but everything else looks good
[16:18] <didrocks> http://bazaar.launchpad.net/~didrocks/unity/fix683444/revision/653
[16:18] <didrocks> is the additional commit :)
[16:18] <didrocks> (I added it to your function as well)
[16:21] <DBO> gratzi
[16:24] <didrocks> thanks to you :)
[16:34] <njpatel> didrocks, I thought it's time to introduce DBO  to Ubuntu Starter Edition https://bugs.launchpad.net/ubuntu/+source/unity/+bug/683623 :)
[16:34] <didrocks> oh yeah, DBO didn't know that :)
[16:34] <DBO> what?
[16:35] <didrocks> DBO: this week release, you planned to add a "donate to DBO to unblock that feature" :)
[16:35] <njpatel> haha
[16:35] <DBO> THAT AWESOME
[16:35] <didrocks> exactly :)
[16:35] <DBO> okay I know what caused this
[16:35] <DBO> kinda...
[16:36] <DBO> bamf has very complex logic for ref/unref with sticky
[16:36] <DBO> its got a bug it seems
[16:36] <didrocks> I just can't believe it when confirming the bug :)
[16:36] <DBO> what?
[16:36] <DBO> that it only works 4 times
[16:37] <DBO> this isn't the first time I have seen this
[16:37] <didrocks> first time I noticed it :)
[16:37] <njpatel> same here
[16:37] <DBO> yeah
[16:37] <DBO> its due to changes in libbamf for pin/unpin
[16:37] <DBO> im looking at it
[16:39] <DBO> I actually have an even better
[16:39] <DBO> and rarer bug
[16:39] <DBO> seems that if you wait long enough
[16:39] <njpatel> DBO, there are some move here https://launchpad.net/unity/+milestone/3.2.4. Basically try and nail as many as possible, so we can get them into this weeks release
[16:39] <DBO> the launchers will randomly switch to launching a different application
[16:39] <DBO> I know what causes this too
[16:39] <DBO> but its just awesome
[16:40] <didrocks> oh, that's an easter egg :)
[16:40] <DBO> its about as rare
[16:40] <DBO> I got it to happen one time
[16:40] <DBO> suddenly clicking devhelp summoned gnome do
[16:40] <htorque> DBO, i thought that's part of that bug (added it to the bug information)
[16:41] <htorque> DBO, for me it suddenly launched gnome-screenshot which i previously started via a terminal (don't have it in my launcher)
[16:41] <DBO> htorque, only if you are lucky
[16:41] <DBO> you are getting a name collision over dbus
[16:41] <DBO> its a 1/1000 chance for every newly opened application
[16:42] <DBO> erm
[16:42] <DBO> 1/10000
[16:42] <htorque> time to win the lottery! \o/
[16:42] <DBO> exactly
[16:42] <DBO> also its probably lower
[16:42] <DBO> rand () is not perfect
[16:51] <lamalex> is it possible to merge chunks?
[16:53] <jaytaoko> lamalex: https://code.launchpad.net/~canonical-dx-team/unity/unity.quicklist-introspection/+merge/42494
[16:53] <lamalex> jaytaoko, thanks :)
[16:54] <jaytaoko> lamalex: let me know if it is ok to merge
[16:57] <lamalex> jaytaoko, looks good, just add tooltip text/quicklist item text to props
[16:57] <jaytaoko> lamalex: ok doing it now...
[17:08] <jaytaoko> lamalex: I made the correction... I will merge with trunk if it is ok with you
[17:09] <lamalex> go for it
[17:15] <vish> tedg: hi.. there was once a discussion here regarding adding a delay before opening the adjacent indicator-menu, similar to the gtk-menu.. was that fixed?
[17:15] <vish> i cant seem to find the bug..
[17:15] <vish> either..
[17:16] <lamalex> dbarth, we have introspection
[17:18] <njpatel> woohoo
[17:26] <dbarth> lamalex: awesome! thanks for taking care of that
[17:28] <dbarth> alt-tabbing furiously here, and the mipmap tip seems to work
[17:36] <tedg> vish, Yeah, we talked about it -- but I think we decided that was a GTK issue.  I don't believe that anyone fixed it.
[17:36] <vish> tedg: do you happen to remember the bug# ?
[17:37] <vish> or the bug title..
[17:37] <tedg> vish, No, I can't remember if it was a bug or not.
[17:38] <vish> tedg: np.. there was a bug , thats why it was discussed..  i just forgot where it got transferred  :p
[17:42] <johnlea> oubiwann; I've updated the bug, Cody is looking at it now
[17:42] <johnlea> btw, thx for the blueprint updates ;-)
[17:53] <oubiwann> johnlea: thanks!
[17:53] <oubiwann> johnlea: and you're welcome :-)
[17:53] <oubiwann> johnlea: I only updated the ones where I actually got info back from folks
[17:54] <oubiwann> johnlea: there were a few where stuff is pending (e.g. details on work items)
[17:54] <johnlea> oubiwann; when you have a moment cast your eyes over the launcher prototype attached to bug #676579
[17:55] <njpatel> Reeevvvviiiiewww https://code.launchpad.net/~unity-team/unity/installation-instructions/+merge/42511
[17:57] <seb128> njpatel, "Dependancies"?
[17:58] <seb128> njpatel, typo there
[17:58] <seb128> njpatel,  do you still need libgconf2-dev?
[17:59] <njpatel> seb128, fixed
[17:59] <njpatel> seb128, erm, no
[17:59] <njpatel> :)
[17:59] <lamalex> what the heck does ￼ mean?
[17:59] <DBO> htorque, thank you for the bug report, it is fixed in rev 365 of bamf
[17:59] <htorque> DBO, great, thanks!
[18:08] <didrocks> no more starter edition :/
[18:27] <htorque> DBO, should it work when only updating bamf? i'm now getting a compiz crash when closing an application
[18:27] <DBO> htorque, how are you closing the application?
[18:28] <htorque> "x" button
[18:28] <DBO> htorque, please get a backtrace
[18:28] <DBO> but you should update compiz
[18:28] <DBO> I gotta run out now
[18:28] <DBO> dentis appointment
[18:28] <DBO> htorque, if you get a backtrace for me
[18:28] <DBO> email it to jason.smith@canonical.com
[18:28] <DBO> as well as making a bug
[18:29] <htorque> will try, good luck ;)
[18:29] <DBO> I meant to say update unity
[18:29] <DBO> I put a small crash fix in
[18:29] <DBO> but it should be unrelated
[18:29] <htorque> ok, will do
[19:45] <kenvandine> tedg, didn't you have a indicator-datetime ready to release?
[19:46] <tedg> kenvandine, Uhm, I never pulled all the tarball together.
[19:47] <tedg> kenvandine, But there's no reason it couldn't be.
[19:47] <kenvandine> :)
[19:47] <kenvandine> also... is that bug where it doesn't change the date fixed?
[19:47] <tedg> kenvandine, Can we do that tomorrow when the archive opens?
[19:47] <kenvandine> sure
[19:47] <tedg> I believe it is fixed.
[19:47] <kenvandine> good
[19:47] <tedg> Are you still seeing it?
[19:47] <kenvandine> yes
[19:47] <tedg> :-/
[19:47] <kenvandine> mine has been telling me it was the 1st
[19:48] <kenvandine> i was just schooled by my wife about what day it really is
[19:48] <kenvandine> :-D
[19:48] <tedg> Oh no!  A wife bug!
[19:48] <tedg> :)
[19:48] <tedg> Hmm, it's working for me.
[19:48] <kenvandine> i shouldn't have insisted it was the first
[19:49] <kenvandine> that's what i get for trusting software written by tedg :-D
[19:49] <tedg> kenvandine, You're the one that insisted the username thing was broken too.... hmm, I think it's all your fault!
[19:49] <kenvandine> :-D
[19:49] <kenvandine> my name was not ted!
[19:50] <tedg> Implying it is now?
[19:50] <kenvandine> hehe
[19:50] <kenvandine> maybe this is a different bug
[19:50] <kenvandine> if i click on a date it gets selected
[19:50] <kenvandine> let the calendar close
[19:50] <kenvandine> and open it again
[19:50] <kenvandine> the date i previously selected is still selected
[19:51] <kenvandine> so maybe this morning i had accidentally clicked on the 1st
[19:53] <kenvandine> tedg,  so that should reset the selected date to the current one right?
[19:53] <tedg> kenvandine, That was the design in Mavrick.  There's a TODO item in the new spec for designing a way to go back to the current date.  A "home" button or some such.
[19:54] <kenvandine> humm
[19:54] <kenvandine> ok
[19:54] <tedg> kenvandine, Is the date in the desensitized menu item correct?
[19:54] <kenvandine> yes it is
[19:54] <kenvandine> but of course you can't see it
[19:54] <tedg> kenvandine, Ah, okay.  That's all I have control over ;)
[19:54] <kenvandine> love that about our theme.... hehe
[19:55] <tedg> I just put the date on the panel... that works as well.
[19:57] <kenvandine> tedg, these gir changes between maverick and natty are a real pita
[19:57] <kenvandine> getting a bunch of <type name="" c:type="AppIndicator*">
[19:58] <tedg> kenvandine, Yeah -- hopefully they'll be worth it to drop all the bindings next release :-/
[19:58] <lamalex> oh wow I didn't even notice that desensitized label in the clock
[19:58] <kenvandine> lamalex, love that about our theme :-D
[19:59] <kenvandine> tedg, this is all in the metadata that wasn't even generated in the maverick version
[19:59]  * kenvandine finds something else to hack on for 30m or so to clear his head 
[20:00] <tedg> kenvandine, Yeah, I worry about some of that stuff, as there seems to be no good way to debug if it's right or not as well :-/
[20:00] <tedg> I think we're going to end up with leaks
[20:02] <kenvandine> tedg, i just can't see what it is doing to cause that, it seems to be getting everything else right
[20:03] <kenvandine> but all instances of AppIndicator as a c:type is not getting the type name
[20:03]  * dbarth is making the nick dance to try to be noticed by lamalex ;)
[20:03] <kenvandine> haha
[20:03] <lamalex> haha
[20:03] <lamalex> the pm never said you were back :P
[20:04] <tedg> kenvandine, Perhaps it's a namespace issue?
[20:04] <tedg> kenvandine, It can't find the types?
[20:04] <kenvandine> that was my thought
[20:04] <kenvandine> but i can't see why
[20:05] <kenvandine> unless it doesn't like that the gir namespace is the same as the object name in c
[20:05] <kenvandine> but i can't imagine that is uncommon
[20:08] <tedg> kenvandine, Yeah, but AppIndicator is funny in the case that it doesn't really have a namespace.
[20:09] <kenvandine> maybe that is the problem
[21:09] <jcastro> tedg: when do you plan to go Natty?
[21:09] <jcastro> tedg: there are a few scrubbing issues with indicators
[21:17] <tedg> jcastro, Hmm, I don't have a specific plan for switching -- but most of the scrubbing issues would be in Unity.
[21:19] <tedg> jcastro, For the record, installing test drive, none of my Natty installs today worked. :-/
[22:48] <ztefn> is this C# example supposed to work? i don't see anything showing in the indicator applet (using MonoDevelop on Ubuntu 10.04): https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#C#%20Example