[00:04] <TheMuso> RAOF: You're probably just used to autotools.
[00:04] <RAOF> I'm also used to being able to do an in-tree build :P
[00:04] <TheMuso> heh
[00:05] <TheMuso> But make distcheck does out of tree builds. :)
[00:06] <RAOF> For convenience, yeah.  But it's generally happy to do in-tree builds!
[00:09] <TheMuso> yeah
[00:11] <RAOF> Well, unity's building and the espresso machine has warmed up.  Time to make coffee!
[00:12] <TheMuso> heh
[00:59] <Omega> What do you guys think about the recent removal of the Maximize and Minimize buttons in GNOME Shell?
[01:00] <nhaines> It's good for them to experiment as long as they put it back.  ;)
[01:00] <Omega> Personally, I think they might be on to something.
[02:10] <RAOF> Ok.  I'm now freaked out.
[02:26] <chrisccoulson> RAOF, me too, but that's probably because it's nearly 2.30 am ;)
[02:29] <RAOF> Heh.
[02:29] <RAOF> I'm freaked out by something suddenly being null when I want to relayout the shell.
[02:30] <ScottK> Null is nothing, so no problem, right?
[02:33] <RAOF> It's getting set up correctly at init time, and I can't see where it's getting set anywhere else, so I'm mystigofied.
[03:32] <RAOF> Damn you unity folks and your flagrant disregard for method signatures!
[03:46] <RAOF> Ok.  Well, that now kinda works.
[03:52] <dylan-m> Hey, two quick design questions: is the name “Me menu” strictly a development code name, or can I use that name for users, too?
[03:53] <dylan-m> Also, do we have a rule for capitalizing these, like “Messaging Menu?”
[07:17] <dylan-m> Oh well, I have to turn in for the night. I took a guess that it's how I wrote it already (“Me Menu” and “messaging menu”). Hopefully it's right. Will try to clarify tomorrow. Good night / day / whichever! :)
[07:24] <Aeronaut> I loaded Ubuntu 10.4 Netbook edition and hated the Unity interface.
[07:24] <Aeronaut> The reason is that:
[07:24] <Aeronaut> - a lot of space is wasted by permanent icons you can't conceal
[07:25] <Aeronaut> - every panel is maximised, to take up  the entire space on the screen
[07:25] <Aeronaut> - there are no minimise, maximise and close buttons on each panel
[07:26] <Aeronaut> - the minimise, maximise and close functions are moved up to a panel at the top of the screen, that is muddy and difficult to see.
[07:27] <Aeronaut> - the "place markers" for each panel don't have pop-out legends, individual icons or explanatory texts
[07:27] <Aeronaut> So I wiped it and installed 10.4 Desktop instead.
[07:30] <Aeronaut> I hope that the Unity interface is only offered as an option - the xfce interface works perfectly on my Acer Aspire One.
[07:31] <Aeronaut> Of course, I would like to express my admiration and gratitude for all the work that Canonical and others have put into Ubuntu.
[07:31] <Aeronaut> End of message =
[07:37] <didrocks> good morning
[08:05] <RAOF> DBO: By the way, I hate you and your broken unity/nux multihead code :).  It kinda sorta ish works here, though.
[08:06] <DBO> RAOF, what multihead code?
[08:06] <DBO> we never did any multihead code
[08:06] <RAOF> Ok.  The lack of multihead code, then.
[08:07] <DBO> RAOF, expect to get double renders of nux on the left monitor
[08:07] <DBO> dont try to fix that
[08:07] <DBO> I know what the problem is
[08:07] <RAOF> What would double-renders look like?
[08:07] <DBO> transparency is suddenly less transparent
[08:07] <RAOF> Ah.
[08:07] <DBO> why?
[08:07] <RAOF> Well, I don't have anything transparent on my left monitor.
[08:08] <didrocks> RAOF: the version in natty is "broken" in the way we forcec double transparency :)
[08:08] <didrocks> force*
[08:08] <DBO> wherever the launcher is
[08:08] <didrocks> like 0.8 instead of 0.9 for the dash
[08:08] <RAOF> Apart from the launcher's tooltips, which are where they would be if the launcher was on the left monitor ;)
[08:08] <didrocks> (it's reverted in trunk, blame mr Patel :))
[08:08] <DBO> wait he really did that?
[08:08] <DBO> what a tart...
[08:08] <didrocks> DBO: yeah, he was thinking the value was inaccurate :)
[08:08] <DBO> RAOF, oh well then
[08:09] <didrocks> DBO: so it was a last minute commit before alpha3 :)
[08:09] <DBO> didrocks, yeah I can fix that as soon as I get this event processing shit done
[08:09] <RAOF> Nux almost handles resizing crtcs, too.
[08:09] <didrocks> then saw it was because of the double painting in multihead
[08:09] <didrocks> it's reverted in trunk :)
[08:09] <didrocks> DBO: heh, you have time, next release is Monday
[08:09] <DBO> no I mean the double painting thing
[08:09] <didrocks> right, I konw
[08:09] <didrocks> know*
[08:09] <DBO> i think you overestimate how quickly I can rip out an entire event system of a toolkit
[08:09] <DBO> I mean I am good
[08:09] <didrocks> DBO: just no need to hurry, you still have until Monday
[08:09] <DBO> but I am not jesus
[08:10] <didrocks> heh :)
[08:10] <didrocks> you are dude!
[08:10] <RAOF> I've got the hair, he's got the beard :P
[08:10] <DBO> I imagine nux as a medium sized mammal
[08:10] <DBO> and what I am doing right now is akin to cutting it open with a chainsaw
[08:10] <didrocks> DBO: if you can't get it rewrote for this release, aren't you afraid of ETOOMANYCONFLICTS when merging?
[08:10] <DBO> ripping out its spine
[08:10] <DBO> grabbing some GTK mammal spine, and sloshing it in there
[08:11] <oSoMoN> good morning
[08:11] <DBO> didrocks, i am seriously considering bzr pushing to lp:nux and then cutting it off half way through
[08:11] <DBO> didrocks, jay wont figure that out for weeks
[08:11] <DBO> and then nux trunk is frozen!
[08:11] <didrocks> DBO: please, don't break nux trunk ;)
[08:11] <DBO> its not broken
[08:11] <didrocks> DBO: there are crashes to fix!
[08:11] <didrocks> a lot of them :)
[08:11] <DBO> I'll just be holding the lock file
[08:12]  * didrocks fires bzr break-locks
[08:12] <didrocks> or whatever it is :)
[08:12] <DBO> didrocks, so my plan to avoid too many merge issues is to insert the new spinal system for nux alongside its existing mechanisms
[08:12] <DBO> then just switch it over in WindowCompositor
[08:13] <DBO> if I only add code I can A) make your life a living hell
[08:13] <DBO> and B) avoid merge conflicts
[08:13] <didrocks> DBO: waow, sounds more work though
[08:13] <RAOF> So, I also discovered today that unity kinda-sorta has dynamic multihead code already hooked up, in that it watches the monitors-changed signal.
[08:13] <didrocks> to ensure both system are working
[08:13] <DBO> RAOF, are you saying between the two of us we are Jesus?
[08:14] <DBO> RAOF, because I always thought of you as the romance novel anti-hero
[08:14] <didrocks> RAOF: yeah, just came with that release (thanks cyphermox)
[08:14] <didrocks> but the magic is really elementary though :/
[08:14] <DBO> RAOF, i told you that
[08:14] <didrocks> and introduce design issues
[08:14] <didrocks> like, if you primary monitor is the right one
[08:14] <DBO> didrocks, i'll make it work
[08:14] <didrocks> the launcher is there :)
[08:14] <DBO> thats crap
[08:14] <didrocks> so, quite funny to not have any "resistance" :)
[08:14] <didrocks> right
[08:14] <RAOF> Yeah, but the monitors-changed signal triggers the setting of the needsRelayout variable, which then isn't used anywhere.
[08:15] <DBO> MacSlow, keynav is my problem from now on
[08:15] <DBO> that okay with you?
[08:15] <didrocks> 09:14:03     didrocks | RAOF: yeah, just came with that release (thanks cyphermox)
[08:15] <didrocks> s/thanks/blames
[08:15] <didrocks> :)
[08:15] <MacSlow> DBO, hey there
[08:15] <DBO> I am ripping out all of nux's spinal system (ProcessEvents is dying a terrible death) and replacing it with something sane
[08:15] <MacSlow> DBO, yeah
[08:15] <RAOF> Also, the signal is hooked up backwards, so if you actually tried to use the UnityScreen that it gets passed in you'll immediately SIGSEGV :)
[08:16] <DBO> RAOF, SIGSEGV is for manly men
[08:16] <DBO> manly men with chest hair
[08:16] <RAOF> Actually… it's a bit worse.
[08:16]  * DBO tries to think of whats worse than sigsegv
[08:16] <DBO> deadlock?
[08:16] <MacSlow> DBO, I'm atm doing desperate things like starting timers upon opening ql with calling SetInputFocus() at the end in the hope to get it back working :)
[08:16] <RAOF> You *won't* necessarily SIGSEGV, but you *will* set some byte of the GdkScreen to TRUE.
[08:16] <RAOF> Who knows what that'll do later ;)
[08:17] <DBO> MacSlow, dont bother, I already implemented the global grab thing I talked about
[08:17] <DBO> MacSlow, your grabs were racing, now they dont
[08:17] <DBO> MacSlow, I am further implementing input grabs with nux
[08:17] <DBO> SetInputFocus is a worthless method for us now
[08:17] <DBO> :)
[08:17] <DBO> I hate to kill all your fun
[08:17]  * RAOF can push a branch with these fixes if you like.
[08:17] <MacSlow> DBO, but why only on the ql and not on the launcher... I still don't see that... the difference between launcher and ql
[08:18] <DBO> MacSlow, ql isn't mapped when you call SetInputFocus
[08:18] <DBO> you just *requested* it be mapped
[08:18] <DBO> but its not yet mapped
[08:18] <DBO> hence why the timer sometimes fixes the issue
[08:18] <DBO> again, leave this one to me
[08:18] <DBO> I got it from here on
[08:18] <didrocks> morning MacSlow :)
[08:19] <DBO> RAOF, you sexy devil, lets run away together and live in a pine studded bungalow (thats what australians live in right?)
[08:19] <MacSlow> DBO, but I added the ability to hook up to MapNotify in GraphicsDisplay::GetSystemEvent() and ::ProcessXEvent()
[08:19] <DBO> yeah I saw that, it looked nasty...
[08:19] <MacSlow> DBO, and that didn't help much
[08:19] <MacSlow> salut didrocks btw :)
[08:19] <MacSlow> hey RAOF
[08:19] <RAOF> Hey MacSlow :)
[08:19] <DBO> MacSlow, dont worry, we dont need it anymore, really :)
[08:20] <RAOF> Going to complain about mesa at me? :)
[08:20] <MacSlow> RAOF, no... but do you want me to? :)
[08:20] <MacSlow> RAOF, I mean I can think of something I bet ;)
[08:20] <RAOF> Not particularly :)
[08:20] <DBO> RAOF, if it wasn't clear, my last message to you roughly translated to "please upload your branch"
[08:20] <RAOF> DBO: I'll clean it up and push.
[08:20] <didrocks> RAOF: if MacSlow doesn't complain, can I complaing about my nvidia magnetic issue again?
[08:21] <DBO> RAOF, mesa is a terrible name, we should change its name in a distro patch
[08:21] <didrocks> RAOF: I tried some vodoo without any chance
[08:21] <RAOF> Obviously, it also needs nux to not suck.
[08:21] <RAOF> But that's a one-liner.
[08:21] <MacSlow> didrocks, "magnetic issue" ??
[08:21] <didrocks> I was obviously really helpful :)
[08:21] <didrocks> hopeful*
[08:21] <MacSlow> oh and hi there everyone
[08:21] <didrocks> MacSlow: yeah, you don't want to see that
[08:21] <didrocks> it's ugly :)
[08:21] <didrocks> imagine that you monitor was still a lcd, with electrons
[08:22] <didrocks> and you bring a magnetic next to it
[08:22] <MacSlow> didrocks, you mean CRT?
[08:22] <didrocks> then, some part of the display is distored
[08:22] <didrocks> yeah
[08:22] <didrocks> that's what I have there :)
[08:22] <didrocks> loicm has some too
[08:22] <MacSlow> didrocks, wow... you got that with and LCD?
[08:22] <didrocks> only with unity (think that nux is guilty)
[08:22] <didrocks> MacSlow: right…
[08:22] <didrocks> compiz only don't get it
[08:22] <MacSlow> didrocks, spooky!
[08:22] <didrocks> and the more "interesting"
[08:23] <didrocks> is that I get it when I only have one display
[08:23] <didrocks> if I use the twinview mode, no issue at all
[08:23] <didrocks> (even on the screen having it)
[08:23] <DBO> didrocks, turn of lighting in compiz
[08:23] <DBO> off*
[08:23] <MacSlow> didrocks, uff... when did that happen first?
[08:23] <DBO> didrocks, i am 99% sure this is a compiz setting needing tweaking
[08:23] <DBO> I saw it once...
[08:24] <MacSlow> DBO, you mean GL-lighting so the cube looks nicer upon rotatino?
[08:24] <MacSlow> rotation
[08:24] <didrocks> DBO: I think it's already turned off, let me check
[08:24] <didrocks> MacSlow: mid-november IIRC
[08:24] <DBO> MacSlow, yeah that
[08:24] <DBO> it causes some issues with other shiz right now
[08:25] <DBO> seems nux messes up the lighting for compiz somehow
[08:25] <didrocks> let me check lightning again
[08:25] <DBO> im not sure why to be honest
[08:25] <DBO> didrocks, if its not that start messing around with other settings
[08:25] <DBO> its something in there I am like 99% sure
[08:25] <didrocks> I turned it off already
[08:25] <didrocks> DBO: ok, will try some config change
[08:26] <DBO> 80% sure
[08:40] <MacSlow> didrocks, do you still get this issue LP: #727890
[08:44] <didrocks> MacSlow: when I added the ql items, I checked for that
[08:44] <didrocks> it didn't happen
[08:44] <didrocks> (tried 5 times to ensure)
[08:44] <didrocks> has I was afraid of it
[08:45] <didrocks> I think it's a race
[08:45] <MacSlow> didrocks, hm
[08:46] <didrocks> as*
[08:48] <RAOF> Man, bzr is awesome.  “bzr lp-open” is love.
[08:51] <RAOF> DBO: Eat hot lp:~raof/unity/multihead-fixes
[08:58] <seb128> RAOF, you know about bzr lp-submit?
[09:06] <didrocks> (I have to use it everytime with -R unity-team though)
[09:11] <RAOF> Hm.  While I'm at it, I should probably see if it's trivial to fix the layout with DPI≠96
[09:11] <didrocks> RAOF: DBO is changing a lot in the Layout code
[09:11] <didrocks> RAOF: maybe worth to wait for a week?
[09:31] <RAOF> DBO: Do you actually want the a nux branch?  It contains exactly the one-line change you suggested.
[10:12] <rye> hi, this is still annoying me. Is there anything known about libappindicator failing to pick up changes for the underlying menu in case the menu has been modified by appending/inserting the entries at runtime?
[10:12]  * rye meant that it is again him, "annoying rye"
[11:04] <rodrigo_> is unity supposed to work on intel graphic cards?
[11:05] <aruiz> rodrigo_, if there's a class of graphics card where it should work, that's intel's
[11:05] <aruiz> unless it's poulsbo
[11:05] <rodrigo_> aruiz, any idea what package do I need to install for the intel drivers? it seems to not work at all here
[11:07] <aruiz> xserver-xorg-video-intel
[11:07] <aruiz> robtaylor, try removing /etc/X11/xorg.conf if you happen to have one
[11:07] <aruiz> oops
[11:08] <aruiz> that's not rodrigo_
[11:08] <aruiz> :-)
[11:08] <rodrigo_> ok, I think I already have that one, checking
[12:47] <klattimer> seb128, didrocks, kenvandine, I just pushed a branch here; lp:~karl-qdh/indicator-datetime/recurring-and-gsettings-fixes which fixes a whole bunch of issues - we get correct recurrence times and a few small gsettings fixes, I'm battling through to get colours added to the menu items too which seems to at least be feasible now
[12:47] <klattimer> would you like me to file a merge request?
[13:00] <klattimer> seb128: didrocks https://code.launchpad.net/~karl-qdh/indicator-datetime/recurring-and-gsettings-fixes/+merge/52059
[13:00] <didrocks> klattimer: hey, will get over it if I find some time today, otherwise, kenvandine and seb128 knows more about it than I :)
[13:01] <klattimer> ok
[13:01] <seb128> hey
[13:02] <seb128> klattimer, hi, I meant to talk to you today about your way to work, nice that you bring it on
[13:02] <seb128> klattimer, could you try to get merge requests happening on a regular basis for fixes and incremental changes
[13:03] <seb128> klattimer, like ideally you would have your work of the day landing to trunk every day in small diffs
[13:03] <klattimer> seb128: I'd love to, but there are a lot of bits of evolution which are taking time to get the hang of
[13:03] <seb128> stacking one week of work makes review not as easy and means that if that doesn't land we have nothing to land in natty
[13:04] <seb128> klattimer, well it seems some of the gsettings watching and update issues could have landed as separated fixes during the week
[13:04] <klattimer> well you can also see there's a lot of testing that's needed to go back and forth to try and tame eds into this indicator
[13:04] <seb128> you seem to stack refactoring and simple bug fixes in the same vcs
[13:04] <klattimer> seb128: agreed those smaller changes should have been in a separate branch
[13:05] <seb128> we want at least the few liners fixed to land
[13:05] <seb128> even if you still fight eds for other things
[13:05] <seb128> but in any case today is tarball day so yeah please do a merge proposal with what you have
[13:05] <seb128> then we can talk to ted and others about helping you to fix remaining issues so we can roll a tarball
[13:06] <klattimer> seb128: it's already done, link above
[13:06] <seb128> great
[13:07] <seb128> kenvandine and ted should review that when they will be online
[13:20] <MacSlow> hey andreasn
[13:23] <coz_> hey all
[13:50] <klattimer> seb128: I have a new branch which fixes colours
[13:50] <klattimer> seb128: lp:~karl-qdh/indicator-datetime/fixed-appointment-icon-colours
[13:50] <klattimer> how would you like me to merge these
[13:51] <klattimer> would you like a merge request to the previous branch or to trunk?
[13:51] <klattimer> actually hang on, I need to do a small fix in there still
[13:56] <mpt> ronoc, hey, do you have a list of all the players that have integrated with the sound menu so far?
[13:57] <ronoc> hmm lets see, banshee, rb, xnoise, spotify, symphony, amarok, mpd, apparently xmms, clementine
[13:57] <ronoc> mpt ^
[13:57] <ronoc> did I leave any out ?
[13:57] <mpt> wow, that's a lot
[13:57] <mpt> that's cool :-)
[13:57] <ronoc> yup
[13:58] <ronoc> mpt, moving over to the mpris only registration in December has removed unnecessary hurdles
[13:59] <mpt> ah, of course
[13:59] <ronoc> the weather is beautiful in Ireland
[13:59]  * ronoc is surprised
[14:00] <didrocks> ronoc: in Frebruary? Waow! The only time I really saw in my 6 months in dubin was April
[14:00] <didrocks> February*
[14:01] <didrocks> ok, March in fact :)
[14:01] <ronoc> didrocks, clear skies, really really bright. really calm. great skies at night (i'm down the country on the south coast)
[14:01] <ronoc> the air is so clean
[14:01] <didrocks> ronoc: where are you btw?
[14:01] <didrocks> (I visited a lot the country)
[14:01] <ronoc> didrocks, makes me realise what the hell am i doing in smelly london
[14:01] <didrocks> heh ;)
[14:02] <ronoc> didrocks, a small town called Dungarvan in Co. Waterford
[14:02] <didrocks> ok, I went to Wateford :)
[14:02] <didrocks> Waterford*
[14:02] <ronoc> didrocks, http://mjcurran.com/home/store_finder
[14:02]  * didrocks can't type today
[14:02] <ronoc> didrocks, i'm like that every day ;)
[14:03] <didrocks> ronoc: heh :) I probably went not near from Dungarvan as I drove from Waterford to Cork
[14:04] <ronoc> didrocks, around the bypass I would imagine
[14:04] <didrocks> ronoc: exactly :)
[14:05] <ronoc> didrocks, its where i grew up
[14:05] <aruiz> ronoc, are you in Dublin atm?
[14:05] <ronoc> aruiz, nope -> http://mjcurran.com/home/store_finder
[14:05] <aruiz> ah yeah
[14:05] <aruiz> weather bust me better there most def
[14:05] <didrocks> ronoc: oh nice! the south coast is beautiful :)
[14:06]  * aruiz never went to the south coast
[14:06] <ronoc> didrocks, yeah its nice alright.
[14:06]  * ronoc is wondering if he could move back here ...
[14:07]  * ronoc back to bug fixing
[14:15] <kenvandine> klattimer, in case you missed my comment yesterday, your indicator-datetime branch is MUCH better
[14:16] <kenvandine> klattimer, it still doesn't get the timezone's right for events
[14:16] <kenvandine> but it does show me the next 5 reliably :)
[14:16] <klattimer> kenvandine: have you used todays?
[14:16] <klattimer> the timezone stuff still needs playing with a bit
[14:16] <klattimer> but I'm getting there
[14:16] <klattimer> I've just added a new branch which even has colours for the events
[14:17] <kenvandine> woot
[14:17] <kenvandine> same branch?
[14:17] <klattimer> well, the one which works well is
[14:17] <kenvandine> i want to get your current fixes at least uploaded today
[14:17] <klattimer> the colours are in a separate branch I'm working on
[14:17] <kenvandine> ok
[14:18] <kenvandine> i had to remove a g_debug line to get it to build yesterday, casting to an int or something
[14:18] <klattimer> oh yeah, sorry
[14:18] <klattimer> I have a delay sometimes when I save :/
[14:18] <kenvandine> no worries :)
[14:18] <klattimer> it causes a few minor glitches when I push
[14:19] <kenvandine> ok, didn't look at your changes yet... but after pulling i am getting mostly dupes in the menu
[14:19] <kenvandine> which i didn't get before
[14:20] <kenvandine> oh... but it got the timezone right :)
[14:20] <klattimer> hmm
[14:20] <kenvandine> it's showing my 1:1 with jasoncwarner 4 times, but displaying it in my timezone not Australia like it had been
[14:20] <klattimer> for me I get recurring appointments with the right date/time and no repeats
[14:21] <klattimer> kenvandine: can you run the indicator on its own with no watchers and send me a copy of the output
[14:22] <kenvandine> you mean in the indicator loader?
[14:22] <kenvandine> and without the service running?
[14:22] <klattimer> no just the datetime service
[14:23] <kenvandine> ok, what do you mean with no watchers?
[14:24] <klattimer> INDICATOR_ALLOW_NO_WATCHERS=1
[14:24] <kenvandine> ah, ok
[14:25] <klattimer> I think I might have a buffer overflow somewhere but not sure where
[14:26] <kenvandine> klattimer, http://pastebin.ubuntu.com/574992/
[14:29] <klattimer> kenvandine: wait 10 minutes
[14:29] <klattimer> I want to see if it increases in size
[14:29] <kenvandine> ok
[14:30] <klattimer> looks to me like old items haven't been removed
[14:33] <klattimer> kenvandine: http://dl.dropbox.com/u/889043/Screenshot-ecalindicator.png - this is what I see on my testing machine
[14:35] <kenvandine> klattimer, yeah, your's looks sane
[14:36] <kenvandine> not sure if other events would show multiple times like that... i am only seeing the dupe on the one event
[14:36] <kenvandine> but since i see it 4 times, no room to see if i get dupes for others
[14:38] <klattimer> kenvandine: as far as I can tell they all have different comps
[14:38] <klattimer> so maybe your duplicate calendar problem is interfering with it
[14:38] <kenvandine> not this one, this event is on one of my google calendars
[14:38] <klattimer> hmm
[14:38] <kenvandine> and it is only on one of them
[14:39] <kenvandine> klattimer, note before i pulled your changes a few minutes ago, it was displaying it only once
[14:39] <klattimer> kenvandine: what I see is 3 completely different ecal components
[14:39] <klattimer> all with the same data
[14:39] <klattimer> so there's got to be something up in eds
[14:40] <kenvandine> weirder is that there are 4 of them displayed :)
[14:40] <klattimer> kenvandine: try evolution --force-shutdown then start evolution and restart the indicaotr
[14:41] <kenvandine> klattimer, no difference
[14:43] <klattimer> kenvandine: I'm adding in a toggle to prevent an overlap occurring
[14:44] <klattimer> if that's happening then it *might* cause your problem
[14:44] <klattimer> but I need to make sure things don't get overwritten
[14:45] <klattimer> this should also fix some quirks I'm seeing in the colours
[14:45] <ronoc> kenvandine, i'll have a release for you in a bit
[14:45] <kenvandine> ronoc, cool
[14:46] <kenvandine> ronoc, bug fix only right?
[14:46] <klattimer> kenvandine: lp:~karl-qdh/indicator-datetime/fixed-appointment-icon-colours
[14:46] <ronoc> kenvandine, yup
[14:46] <klattimer> kenvandine: if you can try the above branch
[14:46] <klattimer> I think it might fix your trouble and some of mine
[14:46] <klattimer> if so we can work out the merge path from here ;)
[14:48] <kenvandine> ah ha!
[14:48] <kenvandine> so having the colors helped a lot
[14:49] <kenvandine> it is on other calendars which i don't have enabled
[14:49] <klattimer> :)
[14:50] <klattimer> right
[14:50] <kenvandine> so hadn't you fixed that before so it didn't display the disabled calendars?
[14:50] <klattimer> now checking a calendar is enabled in evo is a different challenge
[14:50] <klattimer> because evo stores this in gconf or gkey files
[14:50] <kenvandine> didn't you do that with gconf?
[14:50] <klattimer> kenvandine: nope not yet
[14:50] <kenvandine> humm
[14:50] <klattimer> because I'm not sure which method evo is using atm
[14:50] <kenvandine> so why wasn't this happening earlier?
[14:51] <klattimer> kenvandine: because it was borked in many other ways
[14:51] <klattimer> there was no generate instances in the earlier version
[14:51] <klattimer> and getting objects is not the same as generating instances
[14:51] <jcastro> DBO: https://code.launchpad.net/~cando/unity/fix_692444/+merge/48767
[14:51] <klattimer> even though the manual says its a combination of that and generate recurring
[14:51] <jcastro> hook that up yo
[14:52] <klattimer> I'll dig into evolution enabled/disabled calendars
[14:52] <klattimer> see if I can get a handle on doing it
[14:56] <kenvandine> cool
[14:56] <kenvandine> klattimer, good progress... :)
[14:56] <kenvandine> klattimer, can you propose this for merge so we can get the current bug fixes in today?
[14:56] <klattimer> kenvandine: in a little while I'm just trying to fix a small bug
[14:57] <kenvandine> ok, just want to make sure we do it in time for tedg to review and get released today :)
[14:59] <rye> hi, people. May I talk to somebody from the libappindicator team?
[14:59] <rye> in particular I am interested in why the following test - http://paste.ubuntu.com/575010/ - does not actually work for dynamic gtk.MenuItem()s
[15:01] <kenvandine> rye, let me look
[15:02] <klattimer> kenvandine: https://code.launchpad.net/~karl-qdh/indicator-datetime/fixed-appointment-icon-colours/+merge/52080
[15:03] <kenvandine> rye, so the problem is that the dynamic item doesn't change label or get removed right?
[15:04] <rye> kenvandine, after dynamic item is added, everything gets broken, so no changes to menu are seen for all the entries.
[15:05] <rye> kenvandine, in that test after I add new gtk.MenuItem() i change its label (not working), change the static item label (also not working) and then hide and remove the dynamic item from the menu (which is not working as well)
[15:06] <lamalex> seb128, is there a policy for bugs  filed by apport with a failed trace?
[15:06] <lamalex> it's pretty hard to figure out what went wrong without a stack trace :(
[15:07] <seb128> lamalex, no, there is stock replies on the wiki you can use to ask the submitter to use gdb and get a stacktrace
[15:08] <lamalex> ah ok
[15:08] <seb128> or close the bug saying that apport didn't work and that he should submit a new report using apport again if that's still an issue
[15:08] <seb128> when I do that I tend to add a comment saying that the versions changed and it might be fixed so we close the bug but that he should open a new bug if he gets a crash again with the current version
[15:20] <kenvandine> rye, your code looks like it should work... i am betting there is either a appindicator or dbusmenu bug here
[15:20] <jcastro> cyphermox: you still looking after multimonitor?
[15:21] <jcastro> andreasn:  Man, this is a thing of beauty: https://mozillalabs.com/messaging/messaging-menu
[15:22] <rye> kenvandine, well, i did dbus-monitor and found no requests after i added the dynamic item, don't know where to direct the bug report in this case. Is that a responsibility of libappindicator to call dbusmenu methods?
[15:23] <kenvandine> libappindicator
[15:23] <rye> kenvandine, ok, thanks!
[15:24] <kenvandine> rye, i had it drop to a debugger for me and i tried setting the label then used get_label to test it
[15:24] <kenvandine> it got the new label
[15:24] <kenvandine> but the indicator wasn't getting updated
[15:25] <kenvandine> so yeah, it looks like it isn't listening anymore
[15:28] <lamalex> I wish I could bind everything to super like osx keybindings
[15:28] <lamalex> I keep hitting super-tab for alt-tab :P
[15:32] <rodrigo_> is there a unity key shortcut to select the indicators?
[15:32] <jcastro> it was super-s in the last release
[15:32] <jcastro> but I think it's conflicting with compiz stuff right now, there's a few cases where we need to sort that
[15:38] <rodrigo_> yeah, seems super-s does nothing on trunk
[15:48] <cyphermox> jcastro, no, Mirco and Sam merged a branch based on mine to lp:unity, according to the bug report's linked branches. I think it's time I update the bug report :D
[15:48] <jcastro> ok
[15:48] <jcastro> MacSlow: so, upon logging in it seems my panel is now fixed in multimonitor mode, but notify-osd still doesn't
[15:49] <cyphermox> jcastro: how does notify-osd show up... on the last monitor?
[15:49] <kenvandine> what happens with appmenus in multimonitor mode?
[15:49] <jcastro> MacSlow: so I guess my question is, does notify-osd care about where the panel is or is this a pure notify-osd bug?
[15:49] <kenvandine> does it display the menu on the appropriate screen?
[15:49] <jcastro> cyphermox: shows up, just off by itself on the 2nd screen
[15:49] <cyphermox> kenvandine, no, it shows on primary.
[15:49] <jcastro> kenvandine: no, there's a bug report on that, currently I have to mouse all the way over
[15:49] <MacSlow> jcastro, isolated to notify-osd
[15:50] <kenvandine> ugh
[15:50] <jcastro> MacSlow: ok weird, that's been working for years until unity. :)
[15:50] <MacSlow> jcastro, where does it show up... and where would you expect it?
[15:50] <kenvandine> glad i don't have two displays :)
[15:50] <cyphermox> jcastro, link the bug? I'd be interested to try my luck if nobody else is working on it
[15:50] <jcastro> I would expect it to show on the primary monitor
[15:50] <MacSlow> kenvandine, I don't like the "forest" of possible multi-monitor setups :)
[15:50] <kenvandine> jcastro, i would expect it on the monitor that has the focused window
[15:51] <jcastro> what? no
[15:51] <jcastro> it should never move around
[15:51] <kenvandine> that is most likely where you are looking
[15:51] <cyphermox> kenvandine, ah, but then there would be no consistency on where it shows up :/
[15:51] <kenvandine> indeed
[15:51] <jcastro> cyphermox: looking
[15:52] <jcastro> https://bugs.launchpad.net/unity/+bug/683084
[15:52] <cyphermox> even the primary monitor for osd doesn't necessarily feel "right", since it would be in the middle of some setups, or sometimes at the far end, etc.
[15:52] <jcastro> right, so put it where the panel is
[15:52] <jcastro> that's what the user designates as their primary monitor is
[15:52] <kenvandine> cyphermox, right... and... the primary monitor might be the one least likely to be used... like on a laptop with a second display plugged in
[15:53] <kenvandine> jcastro, oh... you can set that?
[15:53]  * kenvandine hasn't used multimonitor in years
[15:53] <cyphermox> kenvandine, do you mean when the laptop has its lid closed?
[15:53] <jcastro> yep
[15:53] <MacSlow> jcastro, my second lcd just "died" two days ago so I can't re-test although the fix that went in 0.9.30 seemd good when I ran it
[15:53] <kenvandine> cyphermox, no... i used to leave it open and have my big monitor on next to it
[15:53] <kenvandine> and mostly focus on the big monitor
[15:53] <cyphermox> kenvandine, well, that's how I work in the office ;)
[15:53] <jcastro> MacSlow: ok, want me to keep an eye on it and make cyphermox fix it?
[15:54] <jcastro> err, I mean, give him valuable input. :)
[15:54] <MacSlow> jcastro, yes... and I'd like to be CC'ed at least
[15:54] <cyphermox> kenvandine, but they both have a different use -- one ends up being bigger than the other in terms of character sizes and all, due to different resolutions... so one is better for a particular use than another
[15:54] <cyphermox> jcastro, the what make me what?
[15:54] <jcastro> ok, let me get this in a bug report
[15:54] <kenvandine> to me i think the lesser of the evils is display it on the screen that has the window which is currently focused
[15:55] <kenvandine> but i know then it varies...
[15:55] <jcastro> no way dude
[15:55] <MacSlow> jcastro, work on n-osd is only possible on weekends for me atm... and there aren't many weekend-slots left over before 11.04 :/
[15:55] <kenvandine> no perfect solution to that problem :/
[15:55] <jcastro> MacSlow: k, I'll bitesize it then, is it complicated?
[15:55] <MacSlow> jcastro, yes
[15:55] <jcastro> ok so don't bitesize it then?
[15:56] <MacSlow> jcastro, due to the nature of setups and tasts people can have
[15:56] <kenvandine> at least then it is displayed in the familiar location on the monitor i am currently looking at
[15:56] <cyphermox> MacSlow, how do you forsee it working?
[15:56] <MacSlow> jcastro, but the behaviour (any change) has to go through design
[15:56] <jcastro> sure sure
[15:56] <rye> or display the notification on all the monitors :)
[15:56] <MacSlow> cyphermox, I do whatever I get told from design... that's the way it works... otherwise I'm in trouble
[15:56] <kenvandine> :)
[15:56] <cyphermox> rye, huh, I don't agree with that ;)
[15:57] <jcastro> https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/331369
[15:57] <jcastro> aha!
[15:57] <cyphermox> MacSlow, then do you want to bring it up with them and CC me or something?
[15:57] <rye> cyphermox, well, i am using laptop screen as a main one and push windows I am not immediately interested to the big external screen... so primary monitor is laptop one. and if notifications are there then it is ok for me
[15:58] <cyphermox> rye, then afaik it's already ok for you, no?
[15:58] <MacSlow> cyphermox, until there isn't a flood of complains on LP it'll not be addressed... as n-osd isn't the focus this cycle
[15:58] <jcastro> kenvandine: looks like it's supposed to be where the panel is
[15:58] <jcastro> kenvandine: so now I pull out my regression card!
[15:58] <cyphermox> I honestly don't see so much of an issue with it being on the primary monitor, even if it ends up being in the middle of the logical X screen
[15:59] <cyphermox> (at least for me, I just don't see an annoyance with it showing up there, others may disagree)
[16:00] <rye> cyphermox, let me test, since last time i tried (yesterday) the panel was in the middle of my laptop and was not really nice to use...
[16:00] <rye> cyphermox, looks like it does not respect the primariness of the display at all :-/
[16:01] <MacSlow> rye, the panel was in the middle of your screen?!
[16:03] <rye> MacSlow, omigod, it is now even more messier :http://ubuntuone.com/p/fx9/
[16:04] <MacSlow> rye, are... twin-view
[16:04] <rye> MacSlow, yes, that's twin-view, has not yet re-enabled multiple screen mode
[16:04] <MacSlow> rye, that's laptop with exteranl screen I guess from the look of the nvidia-settings tool
[16:05] <rye> MacSlow, yep, laptop screen part is at the left and external screen is at the right
[16:06] <MacSlow> rye, and it's in "classic desktop"-mode too
[16:06] <rye> MacSlow, no, in classic mode panel is located on the top of my primary display
[16:06] <tedg> klattimer, Your datetime patch for the colors is conflicting with kenvandine's update to the query.  I'm not sure of the API there, can you take a look?
[16:07] <MacSlow> rye, hm... a bug with unity then
[16:07] <klattimer> tedg can you reverse kenvandines query change it's no longer needed
[16:07] <rye> MacSlow, what's interesting is that panel in this case accepts clicks on the top of the screen (basically if i click the ubuntu logo now i will switch the focus to firefox running)
[16:07] <MacSlow> rye, but hard to say if unity doesn't set the struts right... or twin-view is lying to us (unity)
[16:07] <rye> MacSlow, os yes, unity bug with multiple screens in twinview mode
[16:08] <MacSlow> rye, yeah... input-window and drawing-window are two seperate things
[16:08] <tedg> klattimer, Ah, K
[16:08] <MacSlow> rye, I guess if you "blindly" navigate to the top of the screen you'll be able to access the menus... and they open up at the top of the screen?!
[16:09] <rye> MacSlow, in case i can do anything to help testing that, debug or something like this - feel free to ping me (#canonical/#ubuntuone - rye)
[16:09] <rye> MacSlow, yes, they open on top
[16:09] <rye> MacSlow, more thing, in case launcher is displayed it accepts clicks with the same offset
[16:09] <MacSlow> rye, don't know if that's filed already or not... but if not please file it
[16:10] <MacSlow> rye, you're running last weeks release or trunk?
[16:10] <rye> MacSlow, the latest natty package, is there a ppa i can try?
[16:11] <MacSlow> rye, nope... only trunk (from source) or whatever is in natty's repo
[16:12] <MacSlow> rye, I'll try to get my second screen fixed/replaced... I'm not sure about other DX-team-members with a similar setup
[16:12] <rye> MacSlow, well, then i am running 3.6.0-0ubuntu2
[16:13] <MacSlow> rye, I know it works a lot better with intel :-P
[16:13] <rye> MacSlow, hm, let me test this :)
[16:13] <rye> MacSlow, i can even provide VNC to this machine if somebody wants to have a look how that works... if it works with compiz
[16:14] <MacSlow> rye, pfff... never tried that.
[16:16] <rye> okay, plugging intel netbook w/ unity
[16:17] <cyphermox> MacSlow, that looks like how unity should show up in some cases with my multimonitor patch  -- e.g. resolution changes didn't always get done properly
[16:18] <cyphermox> rye, I bet if you restart unity it displays fine, after you enabled twinview
[16:18] <MacSlow> cyphermox, there are fixes in unity that deal with res-changes now
[16:18] <cyphermox> MacSlow, ah, ok
[16:19] <MacSlow> cyphermox, I think I reviewed and updated your patch even so it could move in
[16:19] <cyphermox> yeah
[16:19]  * MacSlow hopes he doesn't mix up names and patches now
[16:19] <MacSlow> :)
[16:19] <cyphermox> no, I'm Matt ;)
[16:20] <MacSlow> resolution- and screen-changes should be handled correctly now
[16:20] <MacSlow> but in rye's case it doesn't seem to work
[16:20] <cyphermox> also notice how the panel gets drawn at the offset of the screen where it should be drawn, assuming the bottom of the primary screen was flush with the bottom of the secondary.
[16:21] <MacSlow> which let's one assume nvidia's driver is lying to us :)
[16:21] <cyphermox> maybe ;)
[16:22] <rye> MacSlow, well, i plugged in intel box and, it shut down internal screen and enabled external one at a quite low resolution, with unity components completely missing
[16:23] <MacSlow> I hope xrandr 1.4 support comes to nvidia's binary driver at some point
[16:23] <MacSlow> read something about this on phoronix in jan
[16:23] <MacSlow> rye, bummer :/
[16:24] <rye> MacSlow, that deserves another screenshot
[16:24] <MacSlow> rye, make sure to attach them to bugs please
[16:25] <cyphermox> MacSlow, smspillaz's idea of using onScreenChangeNotify to set the resolution seemed to work better, except that it would always be lagging behind and set your stuff to the *previous* resolution you had :)
[16:25] <didrocks> ogra: agateau: I got some overwrite issue in libunity-2d-private
[16:25] <MacSlow> cyphermox, yikes
[16:26] <rye> MacSlow, with intel i have unity on a primary screen, but nautilus and _tooltips_ from unity icons appear on a second screen :-/
[16:26] <ogra> didrocks, oh ?
[16:26] <didrocks> ogra: agateau: /usr/lib/qt4/imports/Unity2d/qmldir is libunity-2d-0 s well
[16:26] <ogra> what did you overwrite
[16:26] <MacSlow> rye, :(
[16:26] <cyphermox> rye, screenshot?
[16:26] <agateau> didrocks: that's quite old, libunity-2d-0 is supposed to be replaced with the -private one
[16:26] <MacSlow> rye, file bugs please
[16:26] <didrocks> agateau: seems it didn't on my system :)
[16:27] <didrocks> agateau: just dist-upgrade here
[16:27] <ogra> didrocks, that was never in ubuntu
[16:27] <nmarques> good afternoon everyone
[16:27]  * didrocks checks, maybe I got a ppa
[16:28] <ogra> ubuntu had libuqpanel0 and thats being replaced by libunity-2d-private0
[16:28] <didrocks> ogra: yeah, local install, so probably the ppa
[16:28] <didrocks> nevermind then :)
[16:28] <didrocks> thanks!
[16:28] <ogra> :)
[16:28] <rye> MacSlow, and unity on intel loses some if its icons (blank spaces remain and running app pointers too) after a while for some reason, ok, will revert to a single monitor setup and start filing bugs
[16:28] <didrocks> rye: this one is already filed
[16:29] <didrocks> rye: just ensure looking at duplicates first :)
[16:29] <MacSlow> rye, thank!
[16:29] <rye> didrocks, sure, it is just not that comfortable to user a browser with a panel in the middle :)
[16:29] <MacSlow> rye, thanks!
[16:30] <didrocks> rye: really? who would have guess? :-)
[16:34] <nmarques> didrocks, when you have some spare (if there's such a thing) let me know, I have all the stuff ready, and I could use some guidance :)
[16:34] <nmarques> didrocks, and fire up Unity for the first time ;)
[16:35] <didrocks> nmarques: just drop the question, I'll answer them little by little :)
[16:35] <nmarques> didrocks, this is what I've done so far
[16:36] <nmarques> didrocks, I've used your patch on gnome-session and it has GNOME (gnome3), classic gnome and Unity
[16:36] <didrocks> excellent!
[16:36] <nmarques> didrocks, I have built compiz from your sources and patches (and it's working cool)
[16:36] <nmarques> didrocks, I have one doubt
[16:37] <nmarques> didrocks, 65compiz_profile-on-session you place it on a spot I don't have
[16:37] <nmarques> didrocks, I've given it executable bits and dropped it on /etc/profile.d (not sure if it's the best option)
[16:37] <didrocks> yeah, you need it
[16:38] <nmarques> also tweaked it for a session called Unity and not xgnome
[16:38] <didrocks> well, anyway, all you need is the env to be exported before gnome-session run
[16:38] <didrocks> (so that compiz is picking the right profile)
[16:39] <nmarques> didrocks, ok, then I have a problem :)
[16:39] <nmarques> because it's only loaded after user logs in
[16:39] <nmarques> let me fix that :)
[16:40] <didrocks> :)
[16:41] <m_conley> hey all - I just got alpha 3, and it rocks.  Great job everyone!
[16:45] <andreasn> jcastro, ah, yeah! cool to see it in action!
[16:47] <nmarques> didrocks, done, it's not properly set
[16:47] <nmarques> didrocks, this makes compiz load unity.ini, right ?
[16:47] <didrocks> nmarques: no, that's where it's misleading! :)
[16:48] <didrocks> so, basically, there are two "profiles" notion in compiz
[16:48] <nmarques> I've seen them in your package
[16:48] <nmarques> normal.profile and extra.profile If I'm not mistaken
[16:48] <didrocks> hum? not that :)
[16:49] <didrocks> so, basically you set an env variable to a profile
[16:49] <didrocks> this profile is retrieved in /etc/compizconfig/config
[16:49] <nmarques> didrocks, it's blank :/
[16:49] <didrocks> then, it's adding general_
[16:50] <didrocks> nmarques: that would we easier for you running ubuntu I guess as well :)
[16:50] <didrocks> and this one refers a profile = unity
[16:50] <didrocks> with the chosen backend
[16:50] <didrocks> (gconf in our case)
[16:51] <nmarques> sec I'll locate it
[16:52] <nmarques> strange thing
[16:53] <nmarques> libcompizconfig is placing a blank config file :/
[16:53] <nmarques> let me take a look, I'll get back to you soon once I sort this out
[16:55] <nmarques> ok, fixed
[16:55] <nmarques> didrocks, http://susepaste.org/40941685
[16:55] <nmarques> didrocks, those are the contents of /etc/compizconfig/config
[16:57] <didrocks> nmarques: please install ubuntu in a VM, I had to tweak that to get it working, will be easier for you to see what's needed :)
[16:57] <didrocks> hard to explain, better when looking at it :)
[16:57] <didrocks> ok
[16:57] <nmarques> sec
[16:57] <didrocks> so yeah
[16:57] <didrocks> that should take unity.ini
[16:57] <bcurtiswx> U1 daemon revolving door has commenced again.. woo
[16:57] <nmarques> I will run a VM
[16:59] <nmarques> didrocks, I have a daily built fro 2 days ago (Natty), but the installer fails for a real install, hopefully will go better on a VMN
[16:59] <didrocks> nmarques: anyway, your config looks fine
[17:00] <nmarques> didrocks, I can use gconf if that makes it easier
[17:00] <nmarques> didrocks, I've also packaged and installed gconf backend :)
[17:00] <didrocks> nmarques: ok, just ensure to set the default plugin list in it as I'm doing :)
[17:02] <nmarques> didrocks, http://susepaste.org/78994653
[17:02] <nmarques> didrocks, I know you can't see them all, but they are all there ;)
[17:03] <didrocks> nmarques: just ensure that you have an "unity profile" (look at the debian/*gconf* list)
[17:05] <nmarques> I do have a unity profile, though I did had to create it
[17:05] <didrocks> nmarques: I mean, in gconf
[17:08] <nmarques> didrocks, /apps/compizconfig-1/profiles/unity
[17:08] <nmarques> didrocks, thats what you mean right ?
[17:08] <nmarques> on gconf
[17:08] <didrocks> nmarques: exactly!
[17:08] <nmarques> I don't have  ;)
[17:08] <nmarques> I'm going to populate it now
[17:08] <didrocks> you should if you want to use the gconf backend :)
[17:09] <nmarques> with the data from the compiz-gnome.gconf-defaults from your package
[17:09] <didrocks> you can't imagine how long it took me to figure out this profile stuff
[17:15] <nmarques> didrocks, lame question... how do you create those keys? gconftool-2 ?
[17:15] <didrocks> nmarques: yeah, on debian, we have a system doing that, I think it's using gconftool-2
[17:15] <didrocks> oh right, it is
[17:18] <nmarques> didrocks, done and documented ;) I need the RPM to do this for me
[17:18] <didrocks> nice :)
[17:19] <nmarques> next step will be ?
[17:20] <didrocks> well, should be working
[17:31] <nmarques> didrocks, no valid session found popup :/
[17:31] <nmarques> leaves me with a cursor and a background
[17:32] <didrocks> nmarques: so, you made a mistake in the sessions in /usr/share/gnome-session/sessions/<file> reference from /usr/share/xsessions/*desktop
[17:34] <nmarques> the /usr/share/gnome-session/sessions/unity.session contents are: http://susepaste.org/82939856
[17:35] <didrocks> nmarques: sounds correct, do you reference to it in a session file from /usr/share/xsessions/ ?
[17:40] <nmarques> http://susepaste.org/65865377
[17:40] <nmarques> thats the contents of the file unity.desktop on /usr/share/xsessions
[17:40] <didrocks> --session=unity not Unity with your setup
[17:40] <didrocks> it's the filename
[17:40] <nmarques> --session=unity.desktop ?
[17:40] <didrocks> no
[17:40] <didrocks> just --session=unity
[17:40] <didrocks> as told above :)
[17:40] <nmarques> brb :/
[18:14] <nmarques> didrocks, not much fun :/
[18:14] <didrocks> nmarques: there is something not running it? try looking at ~/.xsession-errors and such
[18:16] <nmarques> didrocks, http://susepaste.org/85945309
[18:16] <didrocks> VirtualBox -> no opengl it seems
[18:17] <didrocks> lspci: command not found
[18:17] <didrocks> so yeah, try on real hardware
[18:17] <didrocks> and look at this file :)
[18:17] <nmarques> nah
[18:17] <nmarques> gnome-session[14926]: WARNING: Cannot use session '/usr/share/gnome-session/sessions/unity.session': no 'GNOME Session' group.
[18:17] <didrocks> nmarques: did you check the file and compared to the one we use on ubuntu?
[18:18] <didrocks> (the warning isn't in the pastebin)
[18:18] <nmarques> didrocks, I don't have a ubuntu install at the moment :/
[18:18] <nmarques> didrocks, it's from an older log
[18:18] <didrocks> nmarques: that would make things far easier for you and I
[18:18] <didrocks> sorry, but I'm really busy :/
[18:18] <nmarques> np
[18:18] <didrocks> and I can't look at every mistake in config file :/
[18:23] <hytreem> guys im disappointed
[18:23] <hytreem> i just read the blog posts on the new scrollbars and you used eclipse as an example, but eclipse isn't supported for the global menubar
[18:41] <lamalex> these kinds of bugs blow my mind, https://bugs.launchpad.net/unity/+bug/723936
[18:41] <lamalex> how is this happening?
[18:59] <lamalex> Cimi__, congrats on landing those scrollbars!
[19:00] <Cimi> lamalex: thanks :)
[19:00] <bcurtiswx> lamalex, i didn't realize people would hate not having the beep :-\
[19:00] <lamalex> bcurtiswx, so that is intentional?
[19:01] <bcurtiswx> i doubt it was intentional AFAIK
[19:01] <lamalex> oh, I thought you were saying "I did this"
[19:01] <bcurtiswx> oh.. lol.. i'm not that smart :P
[19:01] <lamalex> :P
[19:02] <lamalex> so it should be marked wontfix and called a feature :P
[19:02] <bcurtiswx> if i had my way, definitely
[19:02] <lamalex> Cimi, on the page to install it says "you may need to export LIBOVERLAY_SCROLLBAR"
[19:03] <lamalex> may
[19:03] <lamalex> ?
[19:06] <Cimi> lamalex: LIBOVERLAY_SCROLLBAR=true evince
[19:06] <Cimi> or export LIBOVERLAY_SCROLLBAR=true
[19:06] <Cimi> and evince
[19:06] <lamalex> Cimi, right, but it says "may" it should say "will"
[19:06] <lamalex> may means maybe
[19:06] <lamalex> might
[19:07] <lamalex> it's confusing, you should update the page
[19:07] <Cimi> ok
[19:07] <jcastro> anyone getting invisible boxes in the top left again?
[19:07] <jcastro> I can't click in a box-like area on mine
[19:07] <Cimi> lamalex: where's that?
[19:07] <Cimi> ppa?
[19:08] <lamalex> yeah, on the ppa page
[19:09] <Cimi> lamalex: did, anyway you're now a member too
[19:10] <lamalex> oh.. really?
[19:10] <lamalex> hm
[19:10] <lamalex> I had no idae
[19:11] <lamalex> so Cimi will apps launched from the launcher have the scrollbar?
[19:11] <lamalex> or only apps launcher from the terminal
[19:12] <Cimi> lamalex: now, only from the terminal
[19:12] <Cimi> lamalex: on natty it will be totally different
[19:13] <lamalex> k
[19:13] <lamalex> cool
[19:13] <lamalex> the video looks really cool
[19:14] <nhaines> Cimi: Ooh, neat.  Is this available in Alpha 3?
[19:16] <coz_> hey all
[19:18] <Cimi> nhaines: no, PPA, but stay tuned
[19:23] <lamalex> does anyone know what part of the stack the kinetic scrolling is from? oubiwann is that a MT modification?
[19:24] <oubiwann> lamalex: you're talking GTK, right?
[19:24] <oubiwann> lamalex: utouch hasn't done any touch/gestures+physics yet
[19:25] <oubiwann> bratsche looked into it, but anything that you'
[19:25] <oubiwann> re seeing should be in the toolkit
[19:25] <lamalex> maybe it's touchpad driver
[19:25] <oubiwann> lamalex: ah, that could be too
[19:25] <oubiwann> lamalex: cnd had to take off, otherwise we could ask him
[19:25] <lamalex> the way it's implemented is horrible, but I'm not sure where it is so I don't know where to file a bug
[19:26] <oubiwann> lamalex: go ahead and file it in utouch for now... we can sort it out
[19:26] <oubiwann> (if you give enough specifics about the context, etc. ;-)
[19:26] <hytreem> will the appmenu be good in 11.04?
[19:26] <lamalex> hytreem, everything will be good in 11.04
[19:27] <oubiwann> lamalex: assign it to LP id chasedouglas
[19:27] <hytreem> will it support eclipse and libreoffice?
[19:27] <lamalex> it just keeps sending the scroll event, so if you do a hard scroll on a tab, then ctrl+w, it sees ctrl+scroll and zooms/out really fast then closes your tab
[19:27] <lamalex> or if you alt-tab it scolls what you switch to
[19:27] <lamalex> it's driving me nuts
[19:32] <lamalex> oubiwann, what package should I apport-collect on?
[19:32] <oubiwann> ugh... that's a good question
[19:32] <oubiwann> what package is the synaptics x evdev driver in?
[19:33] <lamalex> k
[19:33] <lamalex> thanks
[19:33] <lamalex> xserver-xorg-input-evdev
[19:35] <lamalex> oubiwann, I can't assign chase
[19:35] <oubiwann> lamalex: got a bug number?
[19:35] <lamalex> i don't know why but he doesn't show up
[19:35] <lamalex> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/728643
[19:36] <oubiwann> lamalex: no worries
[19:36] <oubiwann> taking care of it now
[19:43] <lamalex> Jeeze how many bugs do I need to tag before needs-design gets autocompleted.
[19:43] <oubiwann> hehehe
[19:44] <nhaines> Cimi: aww... well, I'm already having fun with Unity anyway.  I may or may not try the PPA but the video definitely excites me.  I'm looking forward to it.  :)
[19:55] <mhall119> okay, question about the new scrollbar design
[19:55] <mhall119> how will that work on touch displays, where you don't really have a cursor hover?
[19:56] <mhall119> or will it automatically behave like an iphone/android scroll area?
[19:56] <cyphermox> mhall119, afaik, you still do get *something* to scroll with, but I guess it would be different than say, android and iphone because the movement would be reversed
[19:57] <mhall119> I meant, will it rely on scroll events on the view pane, rather than click and drag events on the scrollbar itself
[19:58] <cyphermox> I don't know, I wasn't involved in the implementation or design :)
[19:59] <cyphermox> but thinking about it now, and thanks for you for bringing it up, if it just reacts as it does now, and afaik it already would work for touch, the movement is reversed (as I wrote above)
[20:06] <lamalex> mhall119, on a touch device you wouldn't be using a scroll bar
[20:07] <lamalex> you'd just be dragging the content
[20:07] <mhall119> ok
[20:07] <mhall119> that makes sense
[20:07] <lamalex> :)
[20:12] <jcastro> m_conley: chrisccoulson: seems people are getting mixed up a bit about the messaging indicator, like pointing people to the other guy's earlier PPA, etc.
[20:12] <jcastro> perhaps we should clear up something on the add on page or something
[20:12] <jcastro> throwing in a thanks to the guy for the intial work, etc.
[20:12] <chrisccoulson> jcastro, yeah, possibly. i thought that might happen :(
[20:13] <m_conley> jcastro: ah, very good point - I forgot to acknowledge him.
[20:13] <m_conley> jcastro: I'd forgotten all about that, and didn't consider the mixup
[20:13] <jcastro> this is a great example of someone "just hacking it to make it work" inspiring upstream projects to take the idea and run with it
[20:13] <jcastro> or something like that
[20:13] <m_conley> jcastro: mmhmm - sounds good
[20:24] <lamalex> Woo just had the first 'fix released' for the NEW queue cleaning
[20:24] <lamalex> that always feels good
[20:26] <m_conley> jcastro: alright, the project page and add-on page have been updated.  thanks for the heads up.
[20:27] <jcastro> woo, thanks!
[20:27] <jcastro> high fives all around!
[20:40] <Daekdroom> Can anyone else check if they're having problems in latest natty unity regarding minimizing banshee and rhythmbox?
[20:40] <Daekdroom> Whenever I minimize them, the workspace doesn't lose focus on the window.
[20:43] <mainerror> works well for me
[20:52] <jcastro> mine's fine
[20:54] <mainerror> oh hey jcastro, I'm almost setup for the expo hide/unhide bug :)
[20:54] <jcastro> oh nice dude
[20:54] <jcastro> lmk when you submit the branch so I can get someone to review it
[20:54] <mainerror> cool cool
[21:01] <lamalex> vish, is there a tag for a regression?
[21:15] <lamalex> Who is around, anyone?
[21:16] <lamalex> I need someone with autohide enabled to confirm https://bugs.launchpad.net/unity/+bug/726907 for me
[21:16] <lamalex> there's a bug with enabling/disabling autohide that prevents me from just enabling autohide and testing myself
[21:16] <lamalex> id have to restart unity and whatnot
[21:16] <lamalex> jcastro, ^^
[21:16] <jcastro> there's a regression tag
[21:17] <jcastro> click on adding a tag and start typing it, it will autocomplete
[21:17] <jcastro> lamalex: looking
[21:19] <jcastro> lamalex: yep, I can confirm that
[21:19] <didrocks> lamalex: this is a dup, the issue is in nux
[21:19] <lamalex> didrocks, can you find the dupe and mark it?
[21:19] <didrocks> there were a bug filed for that IIRC
[21:20] <lamalex> or give me a hint of the title
[21:20] <didrocks> lamalex: quite busy there, I don't know, it's been filed a week ago IIRC
[21:20] <jcastro> lamalex: you can tag it "likey-dupe" or something
[21:20] <jcastro> there's a tag they made for "this is a dupe I am sure of it I just can't find it right now"
[21:20] <lamalex> haha
[21:21] <jcastro> https://wiki.ubuntu.com/Bugs/Tags
[21:22] <jcastro> "likely-dupe"
[21:22] <lamalex> didrocks, is this the bug? https://bugs.launchpad.net/unity/+bug/726248
[21:22] <didrocks> lamalex: right!
[21:23] <lamalex> :) thanks
[21:23] <didrocks> well done ;)
[21:23] <jcastro> autohide in general seems worse than last unity release
[21:23] <lamalex> Let me say again how much I hate autohide
[21:23] <didrocks> lamalex: btw, some people just answered on some bug you set as incomplete, think to recheck them! (I closed my email client for the noise to focus :))
[21:24] <didrocks> jcastro: oh please, I fix a bunch of bugs spending a whole afternoon on it :/
[21:24] <lamalex> following up on incompletes is the hardest part of this whole thing for me
[21:24] <lamalex> I still don't have a workflow for it really
[21:24] <didrocks> lamalex: rely on bugmail for that
[21:24] <didrocks> it's the easiest
[21:24] <jcastro> lamalex: talk to pitti or bryce or jfo
[21:25] <jcastro> they have awesome bugmail workflows
[21:25] <didrocks> I proposed my script to the dx team more than once :)
[21:25] <didrocks> it's triaging all emails in right directory from assignee/subscribe by team/project
[21:25] <didrocks> jcastro: can you get reproducible false positive testcase for autohide?
[21:25] <lamalex> i can has?
[21:25] <lamalex> didrocks, where does it run? on the server?
[21:26] <jcastro> didrocks: no, I've been messing with it for a while, "weird"
[21:26] <didrocks> lamalex: yeah, on the server: mail.canonical.com for me
[21:26] <didrocks> maildrop
[21:26] <jcastro> is all I can come up with
[21:26] <didrocks> jcastro: hum, I still see a false positive due to drag and drop, nothing else :/
[21:26] <didrocks> jcastro: but I think I'll add some keybinding, like "false positive there? hit this!"
[21:26] <jcastro> this one alex just duped for example
[21:26] <jcastro> I can reproduce it once
[21:26] <jcastro> now I can't anymore
[21:27] <didrocks> and that will spew all internals :)
[21:27] <jcastro> then my lancher was "stuck" open
[21:27] <jcastro> now it works again
[21:27] <lamalex> didrocks, will it create the  folders for me?
[21:27] <didrocks> jcastro: right, this is not due to autohide, this is nux :)
[21:27] <didrocks> lamalex: yeah
[21:27] <lamalex> effin a
[21:27] <didrocks> lamalex: I can help you to setup that tomorrow if you want
[21:27] <didrocks> and just explains how it works
[21:27] <lamalex> yes please
[21:27]  * didrocks wishes launchpad was not so complicated to triaged X-Launchpad-Rationale
[21:28] <didrocks> jcastro: yeah, so I'll add a debug tab with a keybinding for this
[21:28] <didrocks> jcastro: when you have a false positive, you will just have to hit this
[21:28] <didrocks> jcastro: the thing is that design is changing the spec every week, so I refactor all 5 times :/
[21:28] <didrocks> to avoid having 50 variables
[21:28] <didrocks> right now, we have 15, which is already too much
[21:28] <jcastro> right, so like, I am not sure what it's supposed to do
[21:29] <jcastro> like it started kind of 50% transparenting for me when I hovered over the bfb
[21:29] <didrocks> jcastro: yeah, that's part of it :)
[21:29] <jcastro> and then DBO told me that was on purpose
[21:29] <didrocks> jcastro: 25% exactly
[21:29] <jcastro> !
[21:29] <didrocks> it's going from 25 -> 75%
[21:29] <jcastro> ewwww
[21:29] <lamalex> sometimes I just want to delete bugs, because they're so poorly reported that I don't know what to do
[21:29] <didrocks> then, when you hit 0x0 (to 1x1), it translates that as "time event"
[21:29] <lamalex> https://bugs.launchpad.net/ubuntu/+source/unity/+bug/724477 what?
[21:29] <didrocks> and go very fast from 75 -> 100%
[21:30] <didrocks> jcastro: also, there are lot of different cases, like, you click on an launcher icon,
[21:30] <didrocks> then if you don't move the mouse
[21:30] <didrocks> it hides
[21:30] <didrocks> if you move the mouse
[21:30] <didrocks> it's locked again
[21:31] <didrocks> you hit super, you move the mouse over it, it locks
[21:31] <jcastro> also, I get confused with the super keyboard shortcuts
[21:31] <jcastro> and launcher/dash
[21:31] <didrocks> and the latest one (not yet implemented), you hit super, you don't move the mouse, it should hide when you release super
[21:31] <didrocks> jcastro: super is:
[21:31] <jcastro> like, sometimes I want the launcher, but sometimes I want the dash
[21:31] <didrocks> tab super -> show the dash
[21:31] <didrocks> tap*
[21:31] <didrocks> press super (more than 250ms) -> show the launcher
[21:32] <jcastro> yeah I am not used to that
[21:32] <jcastro> I'm sure we'll nail the timing down
[21:32] <didrocks> jcastro: seems you don't like everything I did: fade over bfb, super handling and autohide :p
[21:32]  * didrocks will go and cry in the corner :)
[21:32] <jcastro> I like autohide
[21:32] <didrocks> not all autohide behavior ;)
[21:32] <jcastro> I was just getting used to "mouse to bfb, then launcher comes out automagically"
[21:33] <didrocks> yeah
[21:33] <didrocks> not my call :)
[21:33] <didrocks> just implemented it
[21:33] <jcastro> heh
[21:33] <didrocks> but I got used to it
[21:34] <didrocks> jcastro: also, you should try "slide only"
[21:34] <jcastro> I can get used to it
[21:34] <mainerror> me too I just throw my cursor to the upper left corner and the launcher appears :D
[21:34] <jcastro> yeah I turned it to slide only
[21:34] <didrocks> maybe you will it better :)
[21:34] <didrocks> so, slide is:
[21:34] <didrocks> 0% -> 45%
[21:34] <didrocks> hit the corner -> transform in timing mode (45% -> 100%)
[21:35] <lamalex> christ you know what would be amazing? Something that when a bug status changed, like from incomplete -> confirmed, it marked the bugmail in your incomplete folder as read
[21:36] <didrocks> lamalex: the thing is that you don't have "history" in the bugmail, but yeah, that would be sweet :)
[21:37] <lamalex> didrocks, what do you mean yo don't have history?
[21:37] <lamalex> the bug number is in the email, right? So there is a way to link them
[21:38] <didrocks> lamalex: yeah, but that would be quite heavy, a real X-Launchpad* header will be better :)
[21:38] <didrocks> lamalex: btw, at least, we have automagic revert on design bugs :)
[21:38] <didrocks> incomplete -> triaged
[21:40] <lamalex> didrocks, is the bug number not in any lp header?
[21:40] <lamalex> it's in the subject..
[21:41] <didrocks> lamalex: it is, when then, you need to get a script connecting to Launchpad library…
[21:41] <didrocks> lamalex: what would be sweet is a:
[21:41] <didrocks> X-Launchpad-OldStatus
[21:41] <lamalex> what? why would it need a script connecting to lp
[21:41] <didrocks> and X-Launchad-NewStatus
[21:41] <didrocks> to put some bugs in another folder
[21:42] <didrocks> like "bug status changed"
[21:42] <lamalex> It wouldn't need to connect to lp, it could just have an sqlite db with it
[21:42] <didrocks> lamalex: I was reacting on your "lamalex | christ you know what would be amazing? Something that when a bug status changed, like from incomplete -> confirmed, it marked the bugmail in your incomplete folder as read"
[21:42] <lamalex> I know
[21:42] <didrocks> hum… depends, for instance, I deactivate my own bugmail
[21:42] <didrocks> like, I don't receive my emails
[21:42] <didrocks> (for launchpad)
[21:42] <didrocks> so it can go out of sync
[21:42] <lamalex> well then this script wouldn't work
[21:43] <lamalex> but you would just turn that off
[21:43] <didrocks> yeah
[21:43] <didrocks> not really fan to sync the status locally, but yeah… why not
[21:44] <lamalex> ugh an update just changed my caplocks binding to ctrl
[21:45] <didrocks> lamalex: switch to azerty! we don't have those issues :)
[21:45]  * didrocks tries to convince
[21:45] <lamalex> well didrocks that means buying a new keyboard
[21:45] <lamalex> or prying the keys off of this and rearranging them
[21:45] <didrocks> lamalex: heh :)
[21:45] <didrocks> that doesn't really work
[21:45] <didrocks> like 1 is &
[21:46] <didrocks> and 1 is Shift + &
[21:46] <didrocks> and a lot of other "fun stuff" like that :)
[21:46] <lamalex> well then there you go
[21:46] <lamalex> 1 more reason I'm not going to do that :P
[21:46] <didrocks> lamalex: shouldn't I avoid mentionning that? ;)
[21:47] <lamalex> no because I would be pissed at you after I went through all of that effort and then found that out :P
[21:48] <lamalex> figuring out what release a bug was fixed in is kind of a pain in the ass if the  commit that fixed it was not explicitly marked
[21:48] <didrocks> heh :-)
[21:49] <didrocks> yeah
[21:49] <didrocks> totally +1
[21:49] <lamalex> and when you use trunk sometimes you say, uh wait is this fixed released?
[21:49] <didrocks> heh :)
[21:50] <didrocks> yeah, being aware of what's in trunk is important for that kind of task
[21:50] <didrocks> hence the fact, I pester people to put them as "fix committed"
[21:50] <didrocks> and milestone to next target
[21:50] <didrocks> with the script doing all the changelog for us, it's nice (closing, retargeting to next target if not closed) :)
[21:50] <didrocks> win almost 2 hours a week of donkey work
[21:53] <lamalex> ah ok
[21:53] <lamalex> ill do that then
[21:53] <didrocks> thanks!
[21:53] <didrocks> ok, time to go to bed
[21:53] <didrocks> see you guys
[21:55] <nhaines> Huh, since Alpha 3, I get two network manager indicators in my panel.
[21:58] <lamalex> hmm.. does API get email sent to the dx list?
[22:01] <Daekdroom> nhaines, that happens every once in awhile since Alpha 2, iirc
[22:03] <coz_> hey guys
[22:06] <nhaines> Daekdroom: restarting unity-panel-service clears it right up.
[22:06] <nhaines> coz_: hiya  :)
[22:06] <coz_> nhaines,  hey guy :)
[22:19] <mainerror> I have a quick question regarding this bug https://bugs.launchpad.net/unity/+bug/718889
[22:19] <mainerror> expo is the workspace switcher right?
[22:22] <a3Dman> how to make overlay scrollbars default?
[22:23] <zekopeko> lol, I just came to ask the same question
[22:24] <a3Dman> zekopeko, ;)
[22:25] <RAOF> Just export the variable system-wide.
[22:25] <RAOF> See, for example, /etc/X11/Xsession.d/80appmenu
[22:26] <zekopeko> RAOF, mark pointed me to /etc/X11/Xsession.d/80appmenu  as an example
[22:26] <zekopeko> lol
[22:26] <zekopeko> but where do I put the variable?
[22:27] <RAOF> What do you mean?  You'd create a file, let's call it /etc/X11/Xsession.d/80overlay-scrollbar, and in it put the line “export LIBOVERLAY_SCROLLBAR=foo”
[22:28] <zekopeko> just what I was thinking but wasn't sure
[22:29] <zekopeko> thanks! be back in a minute
[22:30] <RAOF> (When we do this in the packaging we'll guard that export with a test to make sure the overlay-scrollbar is available, but that's the idea)
[22:32] <kenvandine> whew... DX uploads are done :)
[22:34] <tedg> kenvandine, Woot!
[22:34] <kenvandine> tedg, see your IM though :)
[22:35] <kenvandine> found a bug, but gotta jet now
[22:53] <lamalex> https://bugs.launchpad.net/unity/+bug/727524
[22:53] <lamalex> what the heck is a digitizer?
[22:53] <lamalex> is that some kind of a11y device?
[22:55] <nhaines> lamalex: it's a touch-sensitive display.  *maybe* a digitizer tablet like a Wacom tablet.
[22:55] <coz_> wacom tablet
[22:55] <lamalex> ah ha
[22:56] <coz_> although last I tried wacom on natty it was very jittery :(
[23:02] <nhaines> Some of the fancy tablets have Wacon digitizers in the display.  :)
[23:05] <nhaines> In fact, since Wacom tablets usually let you move the stylus over the surface of the tablet to move the cursor, maybe it is a touch screen mentioned in that bug.
[23:06] <RAOF> Yeah, they're talking about a touch-screen there.
[23:06] <RAOF> Or the stylus-equivalent.
[23:25] <coz_> __yhvh__,   <a3Dman> how to make overlay scrollbars default?
 lol, I just came to ask the same question
 zekopeko, ;)
 Just export the variable system-wide.
 See, for example, /etc/X11/Xsession.d/80appmenu
 RAOF, mark pointed me to /etc/X11/Xsession.d/80appmenu  as an example
 lol
 but where do I put the variable?
[23:25] <coz_> * rodrigo_ has quit (Quit: Leaving)
 What do you mean?  You'd create a file, let's call it /etc/X11/Xsession.d/80overlay-scrollbar, and in it put the line “export LIBOVERLAY_SCROLLBAR=foo”
[23:26] <RAOF> UTF-8 fail :)
[23:26] <coz_> :)
[23:27] <coz_> __yhvh__,  thats what you wanted to know ...yes?
[23:27] <__yhvh__> coz_: yeah cheers, was just reading the wiki before asking :P
[23:27] <coz_> ah ok
[23:27] <__yhvh__> coz_: thanks
[23:27] <coz_> __yhvh__,  you should really thank RAOF
[23:27] <coz_> :)
[23:36] <Omega> coz_: Do the prefixed numbers mean anything?
[23:36] <coz_> Omega,  i would speak to DBO
[23:36] <Omega> DBO: ping
[23:37] <RAOF> The numbers prefixed on the things in /etc/x11/Xsession.d?  They're used for lexographical ordering.
[23:38] <Omega> Ah.