[02:21] <Trevinho> jaytaoko: I sent the merge request...
[02:21] <Trevinho> However with latest Nux I can't run compiz...
[02:23] <Trevinho> I meant unity....
[02:24] <Trevinho> I guess the problem is one of the most recent changes, since I pull just few new changes and compiz didn't load at all (keeping my CPU at 100%)
[03:25] <jaytaoko> Trevinho: I will review your branch with an up to date Nux branch. I will pull all the latest changes to Nux and Unity.
[05:53] <didrocks> good morning
[06:01] <jaytaoko> didrocks: bonjour!
[06:02] <didrocks> salut jaytaoko! ça va ?
[06:02] <jaytaoko> didrocks: yeah, no problem...
[06:03] <jaytaoko> didrocks: but it is time for bed now! cheers
[06:04] <didrocks> jaytaoko: have a good night!
[06:57] <MacSlow> greetings
[07:00] <oSoMoN> good morning
[08:39] <andyrock> good morning
[09:01] <apw> am i expecting to have lost ctrl-alt-T as a keybinding in oneiric
[09:01] <apw> am i expecting to have lost the Reboot option from the power menu in oneiric
[09:08] <ephan> apw, no you're not. I think those maintan
[09:11] <didrocks> apw: reboot will be when dx will implement the new shutdown dialog from design
[09:11] <didrocks> apw: ctrl-alt-T is because there is no moe integration and such shortcuts in GNOME3
[09:11] <didrocks> you can still set that manually in ccsm though, in the "gnomecompat" plugin
[09:12] <apw> didrocks, you'd think we could have kept the reboot option on the menu till we had the new functionality
[09:12] <apw> least supprise and all that
[09:13] <didrocks> apw: seems the new indicator-session release landed before that
[09:13] <apw> didrocks, or we could have pointed the Shutdown... to the same thing that the power button opens
[09:13] <apw> as that has all the options one might want even if its as ugly as an ugly thing
[09:14] <didrocks> apw: not sure as you have all the others options there as well, what we really need is the new dialog
[09:15] <apw> hmmm, perhaps some coordination then if we arn't going to try and make this thing easy to use for people
[09:15] <didrocks> apw: btw, while you are there, I have a recurrent issue (like 50% of the time), having no network at startup, seems to be the iwl3945 river not being correctly loaded. I have to unload it and load it again. There is a bug, but no activity (see dx isn't the only one)
[09:15] <didrocks> also, there is this dkms not working with nvidia-current for each kernel upgrade
[09:16] <apw> didrocks, binary drivers luckily arn't my problem :)
[09:16] <apw> didrocks, whats the bug number for the iwl problem
[09:16] <didrocks> apw: you are quite lucky. However, dkms not being executed is, isn't it?
[09:16] <seb128> apw, it's only an unstable cycle and it's not like it was hard to restart
[09:16] <apw> didrocks, not being run would be indeed
[09:17] <didrocks> and rebooting without any graphic isn't nice for our user, that's the kinf of transition user are list as well :)
[09:17] <seb128> apw, log out and restart from the login screen, or switch to a vt and ctrl-alt-del
[09:17] <apw> seb128, i don't have any working buttons on my login screen, i am told i'll get those back eventually
[09:17] <seb128> apw, should be fixed with yesterday's update
[09:17] <apw> didrocks, whats the bug number for the dkms not running one
[09:17] <seb128> works for me at least
[09:18] <apw> seb128, cool i'll do more updating
[09:18] <didrocks> apw: not sure about the dkms, I didn't report it, let me look for the wifi driver one first
[09:19] <didrocks> apw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/803815
[09:19] <RAOF> didrocks, apw: You're looking for bug #812979
[09:20] <didrocks> RAOF: thanks :)
[09:21] <apw> RAOF, ahh so that was a dkms issue?  new kernel version number the cause ?
[09:21] <RAOF> apw: No.  It doesn't try to parse the kernel version number, it just totally ignores it.
[09:22] <RAOF> So you say ‘build me the module for 3.0.0-7-generic’ and it happily goes ahead and says ‘I see you're running 3.0.0-6-generic, and the nvidia-current module is already built for that kernel.  My work here is (silently!) done!”
[09:23] <RAOF> I'm not sure how it was ever supposed to work; presumably someone did something that was frightfully clever recently and accidentally broke it.
[09:28] <ephan> So if I got it, GNOME 3 does not support shortcuts?
[09:28] <ephan> I'm probably confused, as this can't be right
[09:29] <didrocks> ephan: there is no shortcut you can tweak in g-c-c, so no way to integrate and such them in compiz
[09:30] <ephan> ah I see didrocks
[09:31] <ephan> I personally haven't tried the Alpha 2 to check for bugs, but I feel like I have to
[09:31] <ephan> in a few days
[09:45] <apw> RAOF, heh that is top quality, glad it gotten fixed, might explain the random failures of it we have had in the past too
[09:54] <snadge> that could explain why i've had to manually force dkms rebuilds
[10:08] <snadge> id also like to randomly say .. good job for improving the linux desktop with some much overdue changes, and actually doing it, despite the overlap problems with gnome etc
[10:19] <apw> didrocks, next time you hit this iwl3945 problem could you just rmmod the driver and re-modprobe it, it should not be necessary to restart nm if this is a driver issue; i do this with a problem brcm device often
[10:19] <didrocks> apw: oh ok, will try that
[10:19] <didrocks> apw: it appeared with -3 I would say
[10:59] <andyrock> njpatel, around?
[11:02] <njpatel> andyrock, hey
[11:03] <andyrock> njpatel, i was reading dood tweet about eject/safely remove stuff
[11:03] <njpatel> yep
[11:04] <andyrock> njpatel, for safely remove we use g_drive_stop and we use also the GAsyncReadyCallback
[11:04] <njpatel> right
[11:04] <andyrock> but the GAsyncReadyCallback is not useful since we don't read the result of the operation :)
[11:05] <njpatel> andyrock, that's fine, we can just not send it then :)
[11:06] <andyrock> so, we don't need the GAsyncReadyCallback and we can remove it?
[11:06] <andyrock> njpatel, or we can make it useful adding logging information...
[11:07] <njpatel> andyrock, logging information would be good
[11:08] <njpatel> andyrock, is it done inside the device-icon or the devices manager?
[11:08] <andyrock> njpatel, P.S.: according to me "eject" item for usb drives is a gnome bug
[11:08] <andyrock> njpatel, device-icon
[11:08] <njpatel> ah, nice
[11:08] <njpatel> andyrock, okay, makes sense
[11:09] <andyrock> njpatel, you want port devices manager (and favorites one) into unity core?
[11:11] <njpatel> andyrock, hmm, not sure what unity-2d use
[11:12] <njpatel> andyrock, i'm not sure they use gio at all
[11:12] <njpatel> andyrock, favorites store would be good, yes
[11:12] <njpatel> andyrock, also, having another look at the favourites store tests would be good, maybe porting to the gtest suite
[11:13] <andyrock> nerochiaro, gtest suite?
[11:14] <andyrock> njpatel, ^^^
[11:14] <andyrock> nerochiaro, sorry :)
[11:14] <nerochiaro> andyrock: no problem
[11:15] <njpatel> andyrock, yeah, the test-gtest binary that uses google test instead of glibtest
[11:15] <andyrock> njpatel, ok ok
[11:15] <njpatel> andyrock, (see any of my mere proposals that are pending for how to do it)
[14:33] <h_> hi there
[14:35] <ephan> hey h_
[14:36] <h_> hi ephan, dont know if this is the place to ask but.....
[14:36] <h_> do you have any experience on writing appindicators for Natty?
[14:36] <ephan> For Natty? No
[14:37] <ephan> Only for the good old gnome-panel
[14:37] <h_> ok
[14:38] <h_> anyways, do you know if it was possible to display other gtk widgets than a classic dropdown menu?
[14:39] <h_> like buttons, maybe a container box, etc
[14:39] <h_> because it seems that it's not possible in Natty
[14:40] <ephan> If it isn't and you'd like it, go to launchpad.net and add that to the wishlist in Unity or Ubuntu (not sure on which one)
[14:40] <ephan> But I do not know if you can
[14:41] <h_> ok
[14:42] <h_> and one more question, what is ayatana ?
[14:44] <ephan> The Ayatana Project is the collective project that houses user interface, design and interaction projects started by Canonical.
[14:44] <ephan> https://launchpad.net/ayatana More information there
[14:46] <h_> good
[14:51] <h_> ephan, how to i access any of this irc channels http://live.gnome.org/GnomeIrcChannels#GNOME_Software_Development?
[14:52] <ephan> h_, not sure if that question should be posed in this channel. Nevertheless, I'll answer you. Those servers are irc.gnome.org. #ayatana is on FreeNode. You need a new server tab and connect to irc.gnome.org.
[14:54] <h_> thanks
[19:04] <c10ud> so, oneiric features a new messaging menu or whatever, is there some docs about it?
[19:04] <c10ud> thanks :D
[19:05] <c10ud> (people have been asking emesene support, i guess you changed something from natty...)
[19:14] <jcastro> c10ud: I think the -me menu stuff was just merged with the messaging menu
[19:14] <jcastro> afaik you don't need to do anything
[19:14] <jcastro> tedg: right?
[19:14] <c10ud> i really hope people at least tried before opening the bug :p
[19:15] <jcastro> heh, or ask them to try to reproduce it
[19:15] <c10ud> they even posted a screenshot .p
[19:15] <jcastro> link?
[19:15] <tedg> c10ud, I ported over the old code, but I didn't test it.
[19:15] <c10ud> sure, sec
[19:15] <tedg> c10ud, It might be that the module isn't loaded, the different backends are loadable now.
[19:16] <jcastro> maybe it's a bug
[19:16] <c10ud> tedg, out of curiosity, any reason on why the thing can't be done backwards (?) i mean, memenu throws a signal and apps behave accordingly
[19:16] <jcastro> because ted knows that if we were going to force every app author to update their apps (again), that I would kill him.
[19:16] <c10ud> yeah well i mean like...when it was engineered
[19:17] <tedg> c10ud, Well, you can just the telepathy-mission-control to get that... it sends all those signal.
[19:17] <c10ud> anyway, jcastro: https://github.com/emesene/emesene/issues/745
[19:17] <tedg> c10ud, I don't remember, but I think that the gnome-session interface does as well.  Though, I'm not sure if we're tied into that yet.
[19:17] <c10ud> i see, it just came up to my mind when i suddenly remembered ubuntu code was modified to support emesene as well
[19:18] <jcastro> who ported it the first time around, was it cando?
[19:18] <c10ud> iirc, yes
[19:21] <tedg> This is the new package: indicator-status-provider-emesene
[19:21] <c10ud> thank you, so basically we just have to tell our ubuntu packagers to add a dep on that
[19:22] <jcastro> oh that's easy, that's not even an emesene issue
[19:22] <jcastro> kenvandine: heya, can you put this on the desktop team volunteer queue?
[19:22] <tedg> No, if you guys want, you can pull that code into emesne so that it gets maintained there.
[19:22] <tedg> Not sure what makes sense, but it doesn't have to be in the indicator source anymore.
[19:23] <c10ud> mh, i don't know how it is done, but we wanted to rel a new version this month and we were trying to put support for oneiric
[19:24] <c10ud> src is some c-lib i guess?
[19:24] <tedg> c10ud, Yup, one file though.
[19:25] <c10ud> well, for oneiric i'll just ask our debian packager to put some hard dep on the already-avail package, then we'll see, maybe we could do it backwards in future, who knows :p
[19:25] <c10ud> thanks for the fast replies tedg jcastro
[19:26] <jcastro> rock.
[19:26] <jcastro> c10ud: is the package maintained in ubuntu or just synced from debian, do you know?
[19:26] <c10ud> no idea, last thing i remember about it is cando patching the memenu and the patch being accepted upstream
[19:27] <c10ud> (i'm still with lucid :p)
[19:27] <jcastro> ok if I see cando around I'll holla at him
[19:28] <jcastro> but I suspect fixing it in debian will just require a sync from our end and we'll be good to go
[19:30] <c10ud> jcastro, i think you meant emesene package, not indicator-*-emesene
[19:31] <c10ud> if that's the case, i don't know, sometimes i got the ubuntu package sooner than debian
[19:31] <c10ud> but i know for sure who the debian packager is (devfil) so i'll take care of it
[19:32] <c10ud> thanks again
[20:30] <ephan> Ubuntu 11.04 Dash, how to force it to hide?
[20:31] <ephan> It just won't hide
[21:06] <jcastro> Trevinho: heh, someone was complaining about the chromium bug again
[21:12] <ephan> which bug jcastro ?
[21:14] <czajkowski> the fact it eats memory
[21:19] <Trevinho> jcastro: who? :)
[21:19] <Trevinho> jcastro: who? :)
[21:19] <jcastro> it was on the omg post for the last unity report
[21:19] <jcastro> do you have any new information to add?
[21:19] <Trevinho> However If I've enough time before leaving for the holideys I'd like to work on that too
[21:19] <jcastro> I basically was like "yeah, we know"
[21:20] <Trevinho> The right answwer was: we fixed, but then DBO reverted it not to fix a side-effect seg-fault :D
[21:20] <Trevinho> lol
[21:20] <Trevinho> No, really we'd like to get a proper fix for chromium again
[21:21] <Trevinho> I should ask them in google code to change something that they changed for us
[21:21] <DBO> ?
[21:21] <DBO> what?
[21:21] <DBO> the chromium thing is currently unmerged?
[21:21] <Trevinho> DBO: just jocking....
[21:21] <DBO> im confused
[21:21]  * DBO goes back to his corner
[21:21] <Trevinho> It was, but you had to revert something which lead to a segfault
[21:22] <Trevinho> There's something that must be fixed properly
[21:22] <Trevinho> However jcastro  the main issue is related to the fact that libwnck that we use doesn't give us all the wm_class informations we need
[21:22] <Trevinho> I've already sent to their bugzilla a patch to fix this, but they only reviewed and I'm still waiting for the merge
[21:23] <DBO> Trevinho, do you want I to just write you a X call instead?
[21:23] <Trevinho> so I guess we should use a temporary X call
[21:23] <DBO> I dont mind us using raw X calls
[21:23] <DBO> yes
[21:23] <Trevinho> I already done that
[21:23] <Trevinho> (but in my private branch)
[21:23] <Trevinho> So, this is not a problem...
[21:24] <Trevinho> However since we didn't get the proper informations by chromium, we asked them to wrongly use the WM_CLASS
[21:24] <Trevinho> and so now they use this parameter in a non-standard way
[21:25] <Trevinho> and we should ask them to revert what they've done...
[21:26] <ephan> By the way guys, do we have an option for the time the dash takes to appear, so how quickly it pops out?
[22:20] <ephan> jcastro, you're the one who made the new Alt+TAB right? either way my question is, do you speak portuguese?
[23:03] <RAOF> DBO: Oh!  Was that dash bug the same problem as Jay's clipping thingy on older radeons?
[23:04] <DBO> RAOF, which clipping thingy?
[23:04] <DBO> where only the background and maybe one icon would show?
[23:04] <DBO> yes
[23:04] <DBO> that bug
[23:04] <RAOF> Oh, hurray!
[23:05] <DBO> as I was working on the blur effect
[23:05] <DBO> it just became clear what was happening
[23:05] <DBO> so hows your back?
[23:06] <RAOF> Annoying.
[23:07] <RAOF> Even more so because it happened while I was sleeping.  What the hell!
[23:08] <DBO> i've done that
[23:09] <DBO> I've also done it picking up a towel
[23:09] <DBO> and attempting to jump into a pair of pants (I deserved that one)
[23:10] <RAOF> Sorry?  *Jump* into a pair of pants?
[23:10] <DBO> yeah you know
[23:11] <DBO> hold the pair of pants with two arms
[23:11] <DBO> lift both legs off the ground
[23:11] <DBO> land with pants on
[23:11] <RAOF> No.  No, I don't know.
[23:11] <DBO> you cant tell me you were never curious as a kid to know if it were possible
[23:11] <DBO> well I figure, Im an adult now, and I get to decide what mature means to me
[23:11] <RAOF> I am curious about many things, but whether or not I can jump into pants has never been one of them.
[23:11] <DBO> long story short
[23:12] <DBO> no, you cannot easily jump into a pair of pants
[23:12] <RAOF> Not the winner that it so clearly appeared to be? :)
[23:13] <DBO> no, it's not a big time saver actually
[23:14] <DBO> in fact you'll probably spend the better part of the day wondering if you back could possibly hurt more