[01:55] robert_ancell, just FYI, i got an answer to my gir from vala sources question... you can generate the GIR from valac [01:55] instead of using g-ir-scanner [01:55] which works much better for vala sources [01:55] :) [02:18] ./c === asac_ is now known as asac [02:46] kenvandine, awesome [02:46] kenvandine, what version of vala? [02:46] the 0.12 series [02:46] pass --gir [02:46] or can do it with autotools nicely [02:47] of course now i am beating myself up trying to generate decent docs [02:47] i think i need to package valadoc [02:47] which generates gtk-doc style docs for vala [02:50] kenvandine, oh, that's something I was looking for this morning - has anyone got a gir -> documentation program working? [02:50] no [02:51] there is someone that seems to have gotten something going [02:51] using seed and JS [02:51] but nothing that seems usable yet [02:51] until we get that, the docs we generate won't be all that good [02:52] at least from what i have found, nobody has gotten there yet === almaisan-away is now known as al-maisan [08:41] pitti: hi, so we are switching to LibreOffice for Natty, right? [08:44] Good morning [08:44] bryceh: apport crashes> not from my side [08:44] evilvish: yes, the upload already happened [08:44] pitti: neat! thanks.. :) === tkamppeter_ is now known as tkamppeter === al-maisan is now known as almaisan-away === smspillaz is now known as SmSpillaz [09:48] hey === SmSpillaz is now known as smspillaz [09:50] good morning seb128 [09:50] morning [09:54] lut didrocks [09:54] hey rodrigo_ [09:54] sorry I'm a bit late today [09:54] hi seb128 [09:56] didrocks, rodrigo_: how are you? [09:56] seb128, fine, and you? [09:56] seb128: I'm fine, thanks, you? [09:56] same ;-) [09:56] hey rodrigo_ ;) [09:56] everything is alright [09:56] running the new unity ;-) [09:56] :) [09:56] salut didrocks [09:57] seb128, does it work ok for you now? [09:57] yes [09:57] didrocks, is the right corner not working for you as well? [09:57] the session indicator doesn't open if I'm really in the corner [09:57] ok, known bug [09:58] just reading my bug emails [09:58] seb128: no, I see some bug reports about it, but can't reproduce it, I'm still not on the new indicator stack though, just need a reboot [09:58] ok [09:58] hmm, new indicator stack, I guess that should fix the invisible menus problem I was seeing? [09:59] rodrigo_: yes, if what you what is no menu at all :) [09:59] I had no menu at all, so I want my menus back :-D [09:59] dist-upgrade should be fine now [10:03] ok, let's reboot the session with the new stack, brb [10:05] excellent, all is working well [10:05] … apart from the stacking issue [10:05] so, restarting compiz [10:05] seb128: so yeah, confirming now the top-left corner dead zone [10:06] k [10:09] didrocks, yeah but sladen set the bug as incomplete asking for a screenshot for some reason [10:09] seb128: let me confirm it [10:09] thanks [10:09] I will comment as well [10:10] thanks :) [10:10] french cabale \o/ [10:12] seb128: groovy if you can, I couldn't reproduce it---I was wondering if it was theme-dependent [10:13] sladen, do you run the current unity version? [10:13] it makes 3 people getting it since the upgrade it seems [10:13] seb128: I can't change the importance in launchpad, can you try to do it? [10:14] seb128: FSVO latest; last update was yesterday afternoon(?), but there could have been an upload since then [10:14] I have the javascript popup, but clicking on it has no effect [10:14] didrocks, works on the ubuntu task [10:14] I don't have permissions on the upstream bug [10:15] seb128: thanks, not that important in any case… [10:15] sladen, right, there was an upload on thursday night as every week [10:15] sladen, the version is included in the apport infos [10:42] rodrigo_, did you see my ping on https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/649809? [10:42] Launchpad bug 649809 in gnome-settings-daemon "Meerkat (10.10) does not apply theme properly" [Low,Confirmed] [10:42] it's a weird bug but quite some users get it [10:42] they get [10:42] "** (gnome-settings-daemon:1641): WARNING **: You can only run one xsettings manager at a time; exiting [10:42] ** (gnome-settings-daemon:1641): WARNING **: Unable to start xsettings manager: Could not initialize xsettings manager." [10:43] but don't have another settings manager running [10:43] seems most people having it get it on session start on i7 with ssd config [10:43] seems a race on modern hardwares [10:43] do you have a clue what could be going on there [10:43] ? [10:53] seb128: comment #100 makes it sound like g-s-d is racing against gdm's g-s-d exiting [10:56] seb128, no, looking [10:57] ebroder, hum, but gdm is not running g-s-d for the same user [10:57] it's weird [10:57] seb128: but they both share an x server, no? [10:59] ebroder, not sure what gdm is doing, if it's opening a new xorg session or reusing the gdm one for the session [10:59] pitti, ^ do you know? [11:56] seb128, hmm, about bug #649809, I think I know what it is [11:56] Launchpad bug 649809 in gnome-settings-daemon "Meerkat (10.10) does not apply theme properly" [Low,Confirmed] https://launchpad.net/bugs/649809 [11:56] rodrigo_, is that what ebroder suggested? [11:56] seb128, desrt had that problem, on very fast machines, the g-s-d from gdm is still running when the user's g-s-d is running [11:56] yes, ebroder's right [11:56] ok [11:56] how do we solve that? [11:57] hmm, let me find the bug in b.g.o [11:57] it's going to be hitting higher number of users over time [11:57] yeah [11:57] since new machines will not likely go slower [11:57] rodrigo_, thanks [12:01] seb128, https://bugzilla.gnome.org/show_bug.cgi?id=634988 [12:01] Gnome bug 634988 in xsettings "my computer is too fast" [Normal,New] [12:01] seb128, https://bugzilla.gnome.org/show_bug.cgi?id=634988 [12:01] a gdm bug [12:11] seb128, https://bugzilla.gnome.org/show_bug.cgi?id=634988 [12:11] Gnome bug 634988 in xsettings "my computer is too fast" [Normal,New] === MacSlow is now known as MacSlow|lunch [12:11] seb128, looking at gdm, to see if I can cook a quick fix [13:15] seb128: do you have some time today for the release meeting? I'll be travelling at that time [13:15] good morning [13:15] hey cyphermox [13:15] hey didrocks [13:16] bonjour cyphermox, what's the expected timetable of network manager 0.9? [13:17] Riddell, I was once told shortly after christmas, but from the looks of things, it might still be a few weeks. I'll ask [13:18] cyphermox: hmm, so are you expecting it for natty? [13:18] pitti, hey [13:19] pitti, ok, no problem, did you have time to update the wiki? [13:19] Riddell, I thought so, but I'm not holding my breath now [13:19] pitti, is there anything I should know about? [13:19] seb128: I didn't update the wiki yet, sorry [13:19] seb128: the main problem is the LibO CD overflow, I didn't get to know another one [13:19] let me look it up properly and maybe I can make the call today [13:19] cyphermox: hmm, but it's an API change right, so it'll almost certainly break the kde frontend [13:19] right [13:20] seb128: I discussed that with doko; he'll upload a new version in time for a2 for dropping the recommends [13:20] so far though, there is only wimax added [13:20] seb128: and the balooning of -common is a known problem which we'll hopefully fix in time for release (we need the humanity icons back) [13:22] pitti, ok [13:22] pitti, do you want me to update the wiki or will you do it before travelling? === MacSlow|lunch is now known as MacSlow [13:22] seb128: if you could, that'd be great [13:22] I'd still like to wrap up some things here [13:23] ok, will do [13:23] pitti, was the week a productive one? [13:23] seb128: merci [13:23] seb128: absolutely, yes; I'll blog about it next Monday [13:23] great ;-) [13:25] Riddell, what happened to your patch piloting day this week? [13:26] the queue got quite some easy sponsoring which nobody picked this week it seems [13:27] seb128: it was unfortunate enough to land on my swap day and now I'm busy with KDE SC 4.6.0 [13:27] I hope to do some patch piloting next week [13:28] Riddell, ok, I figured you might have been not working that day, I'm wondering if we should trying to swap piloting in those cases or whoever is not there should find someone to swap with or something [13:28] will talk to dholbach about that [13:29] Riddell, I think I rather stay with 0.8, unless there is something really good and 0.9 gets tagged before FF; the indicator patch is big enough a change for me I think [13:29] seb128: yes I think I should have done that [13:30] Riddell, ok, next time then ;-) [13:31] cyphermox: I expect that using 0.9 would result in breaking Kubuntu so I'd strongly support keeping 0.8 (this happened during the switch to 0.8 and it wasn't pleasant) [13:41] ok, then that's good enough of a reason to wait until next cycle... and if 0.9 gets released early, I'll put it in a PPA === oubiwann is now known as oubiwann_ === oubiwann is now known as oubiwann_ [13:54] hmm.. seems like stuff like menus (and notifications) are still painting behind windows or the desktop... distracting ;) [13:55] yes, known bug [13:55] didrocks, what's the bug number? [13:56] cyphermox: don't have it handy for now :) [13:56] cyphermox: it's a compiz bug, stacking issue [13:56] ah ok :) === james is now known as Guest58598 [14:21] anyone else having weird mouse input issues? [14:22] kenvandine, like not being able to click a rectangular area in the top-left corner of the screen? [14:22] Hmm... How do I access the "preferred handlers" configuration thingamajig in Natty? [14:22] Or "preferred applications" or whatever it was called before. [14:22] like in evolution, i can click on the scrollbar in the message and scroll it but in the mailboxes scrollbar i can't do anything with it? [14:23] and i can't select text in gnome-terminal [14:23] soren: gnome-default-applications-properties ? [14:23] pitti: Yeah, that's the one. Thanks. [14:24] pitti: Is it in the UI anywhere? [14:24] very frustrating :) [14:24] This is the first time I've used unity :) [14:24] soren: we don't have the main menu back et [14:24] "yet" [14:24] kenvandine, if that only occurs in the top left area of the screen, try opening and closing places briefly ;) [14:24] it happens to me too, and that's what gord recommended [14:24] pitti: Alrighty. np. [14:24] pitti: I'll stop searching for it, then :) [14:24] chrisccoulson, ah ha! [14:24] that did it [14:25] that is weird [14:25] so weird to be able to use one scrollbar in an app but not another one in the same app [14:25] chrisccoulson, i also couldn't click on any tabs in firefox, but i could bring up the big tab view thing and select them [14:26] but now it can [14:26] gord, is there a bug filed on that? [14:31] I can't push to bzr right now? Is that expected [14:32] huh is LP down? [14:32] i can't push to bzr [14:33] oh "Launchpad: code host offline" in #launchpad [14:34] chrisccoulson, i got confused too. Odd that they don't update their identi.ca status page on such thing [14:34] s [14:34] mterry, oh, they don't? i have to admit, i didn't check that ;) [14:36] chrisccoulson, well, they didn't this time. I'll have to remember to check #launchpad first then [14:37] mterry, i think they might have fixed it already. i just tried again, and it seemed to work [14:37] chrisccoulson, yah, yup [14:37] yay \o/ http://bazaar.launchpad.net/~chrisccoulson/globalmenu-extension/trunk/revision/73 [14:37] it worked :) === almaisan-away is now known as al-maisan [14:45] bratsche, https://code.launchpad.net/~mterry/gtk/ubuntu-f10/+merge/47044 [14:46] bratsche, for that branch to work like normal F10, we'd also want to patch indicator-appmenu to dismiss menus when it gets the right accel press [14:47] mterry, hey [14:47] mterry, let me know if that should land today [14:47] seb128, it's not urgent, would rather have it well reviewed than not [14:47] I was about to push and upload to other pending patch but got blocker due to launchpadcode being down [14:48] mterry, ok, so I will upload the other patch and we can get that in the next upload [14:48] seb128, sure [14:53] hmmmm, i wonder if i need to handle F10 in firefox too [14:53] i can't remember what it did before ;) [14:58] oh, it does nothing [15:01] mterry_: Awesome! [15:02] hmm, anyone else not able to install gstreamer0.10-plugins-bad? synaptic wants to remove the rest of gstreamer to install it, can't figure out why though [15:02] bratsche, I looked into the java thing too. Seems like SWT isn't emitting the 'realize' signal? I asked upstream about it [15:03] mterry_: Awesome * 2! [15:03] :) [15:21] good day everyone [15:23] hey bcurtiswx [15:23] so build didn't work still... [15:23] seb128, correct [15:24] bcurtiswx, try asking to cjwatson maybe he knows about that new error [15:24] seb128, OK will do [15:25] or build it with --no-as-needed as a workaround [15:26] ok, time to catch the train, good bye and have a nice weekend! [15:27] pitti, ok, have fun [15:27] pitti, just wanted to discuss disabling the apport code which prevents filing bugs for assertions without a message [15:27] but we can do that next week ;-) [15:28] seems people keep running into crashes and can't report them because of that [15:28] seems we should not confuse users but rather see on launchpad if they are useful or not [15:33] enjoy your week-end pitti [15:35] hey didrocks , thanks for the quick reviews [15:37] cyphermox: you're welcome, just wanting for code hosting to be up again to push the branches [15:38] I'm looking at another small thing though, looks like one plugin may have been dropped from 2.32, trying to figure out whether it's the case or if it's just no longer built [15:38] * kenvandine twiddles thumbs waiting for bzr to work again :/ [15:38] didrocks, so yeah, the face plugin appears to be missing, I'd like to push that too in the evo stuff I did [15:39] cyphermox: I've already sponsored the package, that will be for next upload :) [15:39] ah, ok ;) [15:47] seb128: as regards bug #660417 I guess we don't need the patch anymore since we no longer set the virtual resolution in the gnome-settings-daemon, right? [15:47] Launchpad bug 660417 in gnome-desktop3 "the load_desired_settings patch needs to be upstreamed and updated" [Low,Triaged] https://launchpad.net/bugs/660417 [15:47] tseliot, what do you call virtual resolution? [15:47] seb128: the "Virtual" option in xorg.conf [15:48] was is what this patch was about? [15:48] seb128: IIRC pitti dropped that patch [15:49] this patch was useful only because we needed to restart X in order to apply the virtual resolution [15:49] oh ok [15:49] right, so it's deprecated, thanks! [15:49] np [16:06] tseliot, I will drop it gnome-desktop as well in the next upload [16:06] seb128: sounds good to me === mterry_ is now known as mterry [16:11] yeah, launchpad code is back! [16:14] \o/ [16:14] excellent :) [16:14] yay [16:30] seb128 - can you approve stuff in new? [16:31] chrisccoulson, yes [16:31] or ping jdstrand, it's his archive day ;-) [16:32] seb128 - ah, i could do that ;) [16:41] Riddell, do you know about this one? [16:41] bug #684704 [16:41] Launchpad bug 684704 in qmf "qmf MIR or qtmobility change needed" [High,Confirmed] https://launchpad.net/bugs/684704 [16:42] seb128: hmm no, I've added a kubuntu tag and will take a look when I can [16:42] thanks [16:56] will we have libreoffice equivalents of the -hyphenation*, -thesaurus* and -style-human that oo currently has? === dbarth__ is now known as dbarth [17:04] seb128: thanks for the compizconfig-python sponsoring [17:04] didrocks, you're welcome [17:12] kenvandine, could you review and sponsor lp:~om26er/ubuntu/maverick/empathy/empathy-fix-666288 if it's ok? [17:13] yup === al-maisan is now known as almaisan-away [17:15] kenvandine, thanks [17:18] micahg, hey [17:18] hi seb128 [17:18] micahg, could you do a debdiff for the sur on bug #695728? [17:18] Launchpad bug 695728 in gnome-python-extras "python-gtkmozembed should depend on xulrunner" [High,Fix released] https://launchpad.net/bugs/695728 [17:18] micahg, the only thing to sponsor is for natty it seems? [17:18] seb128: both natty and maverick were uploaded [17:18] ok, I'm fixing the bug status then, thanks [17:19] unsubscribing sponsors as well [17:19] seb128: err, maverick wasn't accepted yet [17:19] micahg, right, but you need ubuntu-sru, not ubuntu-sponsors [17:19] micahg, the sponsors do the upload, the sru team review the queue [17:20] right, I think my sponsor forgot to do that, fixing now [17:20] micahg, ok, I did fix it [17:20] so don't bother [17:20] thanks ;-) [17:21] seb128: thanks [17:21] im adding almost every .c/.h file in empathy to chat_SOURCES.. seems like i shouldn't have to [17:22] bcurtiswx, well are those used by the empathy-indicator source? [17:22] bcurtiswx, you should basically have to add the same list that was in the hand written section [17:22] seb128, i am plus some.. i'll keep going until i can't add any more i guess [17:25] rickspencer3, kenvandine: I pushed lp:~bratsche/libgrip/python-fixage-wip but it's still behaving kind of strangely. Normally it doesn't work, but when I set a breakpoint at the program startup and hit continue then it seems to work. [17:25] seb128, can i link empathy_handwritten_sources to empathy_chat_sources before empathy_handwritten_sources is defined? [17:26] bcurtiswx, no and you should not do that [17:26] rickspencer3, kenvandine: Do you guys know anyone who might have time to peek into this? I need to be focusing on some webkit and maybe a little gtk stuff now. [17:26] seb128, OK [17:26] i didn't but i was curious [17:26] bcurtiswx, what I mean is that you should probably add the same sources that were in the 2.32 patch [17:27] bratsche, i can try, is there any signal handling done? [17:28] we just figured out that currently GI expects you to do the signal handling with pygobject instead... which i can't see how that could possible work [17:28] bratsche, how can i test it without the hardware? [17:29] kenvandine: I'm not sure what you mean. [17:29] Oh, right. [17:29] Uhh. [17:29] I'm not sure. [17:30] right now you need to provide some gesture to trigger it right? [17:31] seb128, in 2.32 version there is no empathy_chat_SOURCES [17:31] well that's why I said in the "handwritten" [17:31] what happened to libgrope? that was a much better name ;) [17:31] kenvandine: Yeah. [17:32] seb128, finally... [17:32] seb128, its back to how it _should_ be.. webkit issues because we don't ahve the most recent webkit in gnome3 ppa [17:32] kenvandine: Let me find out if there's a way to force geis to generate an event. Hang on. [17:33] * bcurtiswx has a new respect for tediousness [17:34] bratsche, ok, i am stepping away to eat... but will read scrollback [17:34] bcurtiswx, great [17:34] kenvandine: Okay sounds good. I should do the same thing. [17:34] bcurtiswx, natty has webkit 1.3.10 [17:35] bcurtiswx, seems the gtk3 binaries are still in NEW [17:35] but once they are NEWed you can use this one [17:36] seb128, will do. for now i'm going to see if it build with --disable-webkit and then push to GNOME3 PPA if it works [17:37] great [17:38] kenvandine, do you think you could fix gtk2 for the same issue than you just fixed in gtk3? [17:38] the gir stacked probably changed or something, the gtk2 upload I just did failed in a similar way to what gtk3 was doing [17:39] cyphermox, impressive work on the eds and evo updates! [17:40] cyphermox, btw subscribe ubuntu-desktop to your merge requests rather than didrocks [17:40] seb128, i'll have to check into it more, but if empathy-2.91.5.1 deps are fulfilled in natty (non gnome 3) would it go into natty? [17:41] cyphermox, robert_ancell updated the version tracking to show ubuntu-desktop merge requests [17:41] so they would show there [17:41] he's also doing quite some sponsoring for things showing on it [17:41] cyphermox, could you also check on https://bugs.launchpad.net/ubuntu/+source/evolution-rss/+bug/688776, there is a merge request which seems to require some tweaks [17:41] Launchpad bug 688776 in evolution-rss "evolution-rss broken in Natty" [Medium,Triaged] [17:41] bcurtiswx, no [17:42] OK just wondering [17:42] bcurtiswx, natty will not have gtk3 on the CD [17:42] ah, i'll remember that [17:42] we would need empathy to build with gtk2 to update [17:42] it won't, so case solved :) [17:43] seb128, worked disabling webkit for not.. changlog editing and PPA bound.. thanks :) [17:43] kenvandine: utouch-evemu I think will let you fake events from hardware. [17:51] seb128, how do i merge https://code.launchpad.net/~gnome3-team/empathy/ubuntu with what i have in my own bazaar ? [17:51] bcurtiswx, bzr get lp:~gnome3-team/empathy/ubuntu [17:52] cd ubuntu [17:52] bzr merge ../your_own_dir [17:52] bzr commit [17:52] bzr push [17:52] OK thx [18:04] Laney, could someone from the cli team review the merge request from bratsche on gtk#? the depends on gtk probably needs to be updated to the version shipping the grip patch as well [18:06] libgnome-keyring-dev is now libgcr-dev ? [18:08] nvm\ [18:09] bcurtiswx, afaik, there's no more libgnome-keyring [18:10] rodrigo_, OK thx [18:12] cassidy, the dep of KEYRING_REQUIRED is not libgnome-keyring-dev right? [18:14] bcurtiswx, wait, sorry, there's libgnome-keyring, but it's its own module now, so we are missing a GNOME3 package for it indeed [18:14] * rodrigo_ adds to TODO list [18:15] rodrigo_, i was just going to go package it [18:15] bcurtiswx, ah, cool [18:15] bcurtiswx, submit it to the GNOME3 PPA then, when ready [18:15] will do [18:15] ok :) [18:18] rodrigo_, wait.. so http://ftp.acc.umu.se/pub/gnome/sources/libgnome-keyring/2.32/ isn't it anymore [18:22] kenvandine, oh, seems that empathy update was already uploaded [18:22] kenvandine, the bug and request where just not updated [18:25] tedg, where you talking about how you weren't sure if about-to-show made sense? === artix_ is now known as artix [18:25] (in dbusmenu) [18:26] mterry, Well, it makes some sense, but it's kinda difficult to do the blocking of the menu in GTK. It's not really built to do that. [18:27] tedg, I see. I'm trying to solve an empathy issue where they construct the menu dynamically, and I was looking into adding support to appmenu-gtk for it [18:29] mterry, Ah, that'd be cool. Really it needs dbusmenu support as well. [18:29] mterry, appmenu support will only get you the first layer :) [18:29] mterry, The submenus need support too. [18:29] tedg, agreed, that's next, because empathy dynamically removes/adds submenus to items [18:30] tedg, explain about dbusmenu support? [18:30] ugh! [18:30] seb128, i should have looked on launchpad i guess... [18:30] doesn't that already work in dbusmenu now? (i'm using it in firefox, as it dynamically builds most of its menus) [18:30] mterry, It just needs to track the menu opening and block it before it gets the signal or a timeout. [18:30] rmadison didn't show it [18:30] chrisccoulson, it'll work in that they'll update and send the signal, but it won't block the building of the menu for the reply. [18:31] oh, you're talking about blocking it too :) [18:32] tedg - btw, i uploaded the extension to the archive today, but it's still sat in new. you can get it from my PPA already though if you want to use it: https://launchpad.net/~chrisccoulson/+archive/ppa ;) [18:32] kenvandine too ;) [18:32] tedg, so it works, there's just a race condition? [18:33] tedg, if I add support to appmenu-gtk, what does the return boolean of about-to-show callbacks mean? [18:33] so I'm future compatible with dbusmenu support [18:33] * kenvandine jumps on that [18:33] mterry, i think i just always return the same value for that ;) [18:33] chrisccoulson, yeah, dbusmenu just throws the value away currently [18:35] yeah, i always return false: http://bazaar.launchpad.net/~chrisccoulson/globalmenu-extension/trunk/view/head:/extensions/globalmenu/components/src/uGlobalMenu.cpp#L60 [18:38] chrisccoulson, how do i enable it? [18:38] kenvandine, once it's installed, you should just need to restart firefox [18:38] chrisccoulson, and what should be the default for tabs? tabs on top? [18:38] kenvandine, tabs-on-top should be default [18:39] enjoy your week-end everyone! [18:39] damn [18:39] you too didrocks [18:39] thanks :) [18:39] chrisccoulson, i thought so... you had me change that last week to tabs on top... [18:39] it reverted [18:39] hmmm, that's odd. do you have any other extensions installed? [18:40] i doubt it...i hate extensions :) [18:40] lol [18:40] i restarted firefox and this menu extension isn't enabled [18:40] and i have no enable button [18:40] tedg, sorry but I just uncleaned your indicator-application list by adding upstream tasks for the ubuntu bug ;-) [18:42] kenvandine, hmm, does it show in the addons manager? [18:42] yes [18:42] as disabled [18:42] does it give a reason for being disabled? [18:42] what firefox version are you using? [18:42] oh [18:43] incompatible with 4.0b9 [18:43] oh? [18:43] that's odd ;) [18:43] that is what it says :) [18:43] * kenvandine couldn't make this shit up [18:43] it should be compatible with that. i'll check what happened with the build [18:43] :) [18:44] kenvandine, oh, actually, which version of the extension is it? is it 0.1 or 0.2? [18:44] perhaps it still hasn't published yet ;) [18:45] 0.2 [18:45] oh [18:45] i see whats happened [18:45] my PPA pulled in b10pre from the mozilla-daily PPA ;) [18:45] ok, i'll fix that [18:45] ugh :) [18:45] ok [18:47] * kenvandine builds locally for the new hotness [18:47] kenvandine, ok, reuploaded. that will hopefully work now [18:47] ok... local build failed [18:47] as long as my PPA pulls in the right package [18:48] oh? what was the failure? [18:48] http://pastebin.ubuntu.com/556612/ [18:49] further up it looks like missing build depends [18:49] kenvandine, oh, it's because you have xulrunner-1.9.2 installed. could you run "update-alternatives --config xulrunner" and set the link to point to xulrunner-2.0? [18:49] it should work then [18:49] ok [18:50] better [18:50] tjx [18:50] thx even [18:50] cool [18:51] oh the hotness! [18:51] * kenvandine high fives chrisccoulson! [18:51] yet another reason not to use chromium [18:51] nice :) [18:51] jcastro, take that! [18:51] now go fix OOo :) [18:52] * kenvandine ducks [18:52] lol [18:52] heh [18:54] :) [18:55] jcastro, now you go port chromium :) [18:55] I don't really use the menus often [18:56] jcastro, likely excuse [18:56] jcastro, oh... been meaning to ask you [18:56] you use gmail and all in appmode right? [18:56] launch speed > menus for me [18:56] do you get the "a plugin crashed" error banner at the top everytime you launch it [18:56] ? [18:56] yes, that's a compiz bug [18:56] if you can believe that [18:56] chromium isn't any faster to launch anymore [18:57] firefox is just as fast, and it actually uses less memory than chromium [18:57] which is hard to believe... [18:57] not many things are more bloated than firefox [18:57] lol [18:58] chrisccoulson, funny how i can praise firefox and insult it in like the same sentence huh? [18:58] :) [18:58] just remember i hate all web browsers :-D [18:58] pedro_, hey [18:58] i expect firefox will use as much memory as chromium once electrolysis lands ;) [18:58] pedro_, if you want to clean some crash listed seems gnome-settings-daemon has quite some duplicates [18:58] or policykit-1-gnome [18:59] chrisccoulson, there we go... firefox won't let me down huh? [18:59] lol [19:01] bratsche, i might just run over to best buy and pick up one of those apple magic touch thingies [19:04] seb128, ok will have a look at both [19:04] pedro_, thanks [19:05] pedro_, how are you otherwise? [19:05] np :-) [19:05] seb128, I'm good, thanks. just finishing with the kernel sru testing for lucid [19:05] seb128, what about you? [19:05] ok right, kernel testing for you now ;-) [19:05] pedro_, I'm fine thanks [19:05] yeah yeah... [19:06] good :-) [19:07] bratsche, where can i get utouch-evemu ? [19:08] bratsche, and is there a package for libgrip yet? [19:09] kenvandine: Yeah, they're both in ppa:utouch-team/unstable I think. [19:09] ok [19:09] bratsche, would it be a was of money to get a magic trackpad for testing purposes? [19:11] s/was/waste [19:11] kenvandine: I dunno.. if you're thinking you might end up doing any more stuff with gestures then it's a good device to have. And if nothing else, we'll have gesture-enabled Unity this cycle. :) [19:12] if it takes to long for me to figure out how to fake it maybe i'll go pick one up and hope my wife doesn't yell too loud for me getting more toys :-D [19:13] hehe [19:13] kenvandine, cf other channel [19:14] seb128, and i'll fix up gtk2 too [19:14] thanks! [19:14] ok, dinner time [19:14] bbl [19:14] enjoy! [19:14] thanks [19:18] seb128, thanks, looking at the merge request now... as for the merge requests I do, I only subscribed didrocks directly because he had prior knowledge -- we discussed these merges before [19:19] with evo and e-d-s done I still need to look at all the other evo- packages, especially evo-exchange which appears to be totally borked [19:33] ok... while gtk builds and tries to overheat my laptop, i am going to run out to get that touchpad :) [19:33] bbs [19:33] bratsche, ^^ [19:35] heh [19:35] bratsche: hey [19:36] bratsche: any idea why the huge resize grabbers would show up on panel applets? [19:46] dobey: Yeah.. those are derived from GtkPlug and I guess it's not disabling the resize grip yet. [19:46] dobey: If you have time, it's a 1-line patch. Otherwise just file a bug and assign it to me and I can do it later. [19:46] weird. it's only on some of them, not all, and it's not at the bottom right on the ones it is on. it's closer to the middle [19:47] Oh, weird. [19:47] I dunno. [19:47] well i just saw it on my laptop, but i am not seeing it on my workstation [19:47] but i'm upgrading the laptop right now [20:02] bratsche: hrmm, seems gone now, so i guess the update fixed it [20:06] dobey: Awesome [20:06] yeah. though i had to switch back to metacity on my workstation :( [20:23] dobey: Suckfest [20:24] dobey: Why? video problem or something? [20:24] because i'm damned tired of having all my compiz settings get completely wiped out when i update [20:24] and alt+drag stopped working [20:29] bratsche, https://code.launchpad.net/~ken-vandine/libgrip/packaging-with-gir/+merge/47096 [20:29] bratsche, added the packaging for the gir stuff [20:29] Awesome, thanks! [20:30] bratsche, also, do we need the overrides? [20:30] if so can you give me that? [20:31] Let me find it.. I can't remember where it is or what's in it now. [20:34] ok empathy builds, but fails to run (testing now) .. so using gdb i run empathy then backtrace http://paste.ubuntu.com/556655/ [20:35] am I supposed to see the crash here? [20:37] kenvandine: Found it.. emailing now. [20:38] thx [20:38] Sent [20:40] what does "fails to run" mean exactly? [20:40] bcurtiswx: ^^ that is [20:41] dobey, sorry, segfaults [20:41] Maybe "fails to run for very long" :) [20:42] bcurtiswx: what's above the "(gdb) backtrace" bit? if it crsahed it should have spit some info out first before dropping to console [20:44] dobey, Program received signal SIGSEGV, Segmentation fault. 0x00007ffff57153b8 in XSendEvent () from /usr/lib/libX11.so.6 [20:47] bcurtiswx: ok, then yes that's the backtrace [20:48] dobey, where would I go from here? [20:48] bcurtiswx: install the debug symbols for everything in the stack, starting with libX11.so.6 [20:50] x11-dbg ? [20:51] i don't know what the package name is [20:51] -dbgsym seems to be the commonly used appendage to the package names though [20:56] dobey, http://paste.ubuntu.com/556660/ [21:00] ok [21:00] it could well be a bug in gtk+ or empathy or X or something else. you need to install the debug packages, reproduce the crash, and debug it [21:01] cassidy, http://paste.ubuntu.com/556660/ have you seen this before? [21:01] i mean the file doesn't exist on my system.. a find / -name ... didn't come up with anything === bjf is now known as bjf[afk] [21:17] where would I search to see if XSendEvent is deprecated ? [21:32] bratsche: can that patch go upstream? [21:34] bratsche, https://code.launchpad.net/~mterry/appmenu-gtk/misc-fixes/+merge/47114 too [21:34] bcurtiswx: pretty sure it's not and that is being called inside gtk+ [21:34] kenvandine, are you the guy to talk about libindicate/messaing menu ? [21:35] dobey, http://bazaar.launchpad.net/~gnome3-team/empathy/ubuntu/view/head:/debian/patches/31_really_raise_window.patch [21:35] its the XSendEvent in ther [21:35] bcurtiswx, more likely tedg [21:35] Laney: Which one? [21:35] gtk# (and gnome-do I suppose) [21:35] but... feel free to complain to me, and i'll complain to tedg... i rather enjoy that [21:35] Laney: No. [21:35] tedg, http://bazaar.launchpad.net/~gnome3-team/empathy/ubuntu/view/head:/debian/patches/31_really_raise_window.patch the XSendEvent is causing empathy to Segfault [21:35] could you take a look when u get a minute or two? [21:36] oh, weird [21:36] Laney: So, this is new API in gtk+ 3.0 but we've backported it to 2.x for Natty. [21:36] Laney: So I guess whenever there is a gtk# for 3.0 then it will get pulled in. [21:37] kenvandine, ^^ at my last post [21:37] I really feel that really_raise_window should go away. [21:37] mterry: Thanks.. looking now. [21:37] tedg, remove the patch entirely? [21:37] I think it's an abomination. [21:37] tedg: i was just about to say the same thing [21:38] bcurtiswx, Well, then you need to patch Compiz to remove focus-stealing prevention. And I can't convince seb128 of that. [21:38] tedg, so is there something else needed for that XSendEvent [21:38] bcurtiswx, yeah, don't listen to tedg about that... :) [21:39] bcurtiswx, so this is just for the gnome3 ppa? you could remove it there for now... but ideally figure out why XSendEvent is causing a crash [21:39] mterry: I haven't looked through the patch yet, but are you sure about changing the separator mode stuff? That was added in to fix a bunch of bugs we had due to uimanager's separator mode stuff. Are you sure this won't break those things? [21:39] bcurtiswx, Not sure, I'm guessing the window is invalid at the point it's being called? [21:39] well, i don't get what that patch is supposed to do anyway, other than implement gtk_window_present incorrectly [21:39] bratsche, ok... so what exactly is wrong with libgrip and the pygrip example? [21:39] mterry: I don't remember specific examples anymore thoughl [21:39] bratsche, nope! I was hoping you could tell me more [21:39] tedg, http://paste.ubuntu.com/556665/ [21:40] bratsche, it fixed separators for me in empathy. that's all the history I know. Looking at gtk's code makes it seem like UIManager does the right thing, but I don't have a bunch of test cases to try [21:40] grip has a library and python bindings? [21:40] dobey, "incorrectly" for some definition of that... it makes it raise the window when you as for the window :) [21:40] dobey, with gir [21:40] kenvandine: When I run it without setting a breakpoint, I never see anything printed to the console (which is in the callback). But if I set the breakpoint that's right before register_window() and then hit "c" to continue.. everything works fine. [21:40] apparrently it is broken [21:40] ah... i need to remove that breakpoint then to see that breakage [21:40] gotcha [21:40] :) [21:40] bratsche, at the least, the existing code never updated separator visibility. In an attempt to fix that, I realized that all I needed was to watch widget visibility status [21:41] kenvandine: Yeah, without the breakpoint it appears to never get triggered. [21:41] kenvandine: https://launchpad.net/grip ? [21:41] ah, racy... [21:41] no [21:41] dobey: libgrip [21:41] gesture stuff [21:41] dobey: It's a multitouch gesture library. [21:42] mterry: I doubt I left enough useful information in bzr log to figure out which apps were breaking without that. :) [21:42] bratsche: i can still make fun of the poor naming choice :) [21:42] dobey: My original name was libgrope, but Mark didn't like this. :) [21:43] So I had a new name forced on me. [21:43] DBO had a good suggestion after that, which was libTSA. But sadly, I had already renamed it to libgrip. :/ [21:44] fwap would have been more awesome [21:44] heh [21:45] tedg, gtk_window_present was mentioned on gimpnet to use [21:45] yes of course it was [21:46] which amounts to "don't apply the patch" [21:46] Well, it doesn't really work is the problem. [21:46] it was already doing gtk_window_present [21:46] and sjoerd mentioned we should chat with them about moving it all upstream, but i have no idea about policies here so i refrained [21:46] And gtk_window_present_with_time would be better. [21:46] * tedg would love for all of it to be upstream [21:46] tedg: i don't see how that would be different [21:47] _present() and _present_with_time(GDK_CURRENT_TIME) are the same [21:47] no? [21:47] dobey, Because I think the only reasonable way to do focus stealing prevention is to match user events to timestamps. And, they're not as this event is coming through DBus, much delay. [21:49] void [21:49] gtk_window_present (GtkWindow *window) [21:49] { gtk_window_present_with_time (window, GDK_CURRENT_TIME); [21:49] } [21:50] tedg: why does dbus matter? [21:50] tedg, the change from gtk_window_present to empathy_window_present could potentially be ok, the other hunk is just bad (all according to upstream) [21:51] dobey, Because the event timestamp from X is getting send to the messaging menu. It's then pulling that timestamp and passing it along. So the event that is causing the present is the messaging menu one. [21:51] dobey, If you do GDK_CURRENT_TIME that'll be the time that the dbus message is processed. [21:52] tedg: the patch *IS* doing GDK_CURRENT_TIME [21:52] bcurtiswx, That's fine if it works. I'd be happy to drop it. [21:52] dobey, Oh. :-/ [21:52] It shouldn't do that. [21:53] it's just calling the XSendEvent directly instead of going through gtk+ [21:53] which seems silly [21:53] sorry if i seem lost, but what was wrong with removing the patch all together? [21:53] i think what you really want is to raise the window, but not focus it, right? [21:54] bcurtiswx: supposedly compiz sucks so the window doesn't get raised properly [21:54] Yup. It just won't come forward. I think even with the patch it won't switch desktops. [21:54] It's not a compiz thing really. Metacity does the same stuff. [21:55] what behavior do you want? [21:55] Someone clicks on the menu item in the messaging menu and that chat window is shown to them. [21:56] and without that patch, what will happen? [21:57] I don't remember entirely, but I think the Empathy issue was that it'd only call for attention. [21:57] that's what should be happening without the patch. so if it's not working i think there's some other problem? [21:58] dobey, Yes, the WM is blocking the present. It's focus stealing prevention. You turn it off, the world is a happy place :) [21:58] tedg, well for now, i'll remove the patch, build, see if it doesn't crash, and work from there.. i'll keep the patch but remove it from series... that sound OK to you? [21:59] bcurtiswx, Yup. If you're up for it, taking the event timestamp from libindicate should improve things some. [22:01] tedg, i had tried doing that when you first added it and it didn't really solve the problem [22:01] * kenvandine shakes fist at window managers [22:02] no, it wouldn't [22:02] GDK_CURRENT_TIME would be best [22:04] tedg: do you have the XID of the indicator's window? [22:05] dobey, No [22:05] dobey, In many cases clicking on an indicator will cause a window to be created as well. [22:05] sure [22:05] And, I really don't want to be a pager. That seems broken even more. [22:07] so the big problem is if it's on another workspace, right? [22:08] That's one. I believe they didn't raise at all at one point, but that was less reproducible. Might have been a mutter issue, I don't remember. [22:09] tedg, sjoerd from upstream has mentioned a few times he'd like us to do less workaround patches and work with them to do things right.. just passing with word on tho [22:10] well i should quote "right" because i know it's suggestive that we don't .. and i know we do. [22:11] bcurtiswx, Yes, that's a touchy point on both sides of the coin :) [22:12] tedg, yup :) [22:12] well [22:12] this patch is clearly not right :) [22:14] tedg: hrmm, so yeah, it seems to be a larger issue, though i'm not sure it's a WM one yet [22:15] tedg: i just reproduced the "not raising/focusing the window" issue with ubuntuone-preferences though [22:15] hrmm, i take that back. it raises, but doesn't focus [22:15] and it doesn't switch to that workspace, or move the window to current [22:17] I've heard that GEdit supposedly has some very nice code for this, but I haven't looked for it. [22:18] Probably should go into GTK as gtk_window_present_no_i_really_mean_it() :) [22:19] tedg, a bigger issue and one that I wouldn't know better is that the other patches are mixed gtk2 gtk3 and cause gtk3 aborts. i think the patches need to be gtk3-ified... who would be able to do that? [22:19] well i mean the patches haven't been gtk3-ified while empathy has and empathy complains [22:19] bcurtiswx, I think that for GTK3 we're going to have to drop it anyway as Empathy is changing a bunch. Don't we need the approver for Empathy 3, right kenvandine? [22:20] tedg, i think so [22:20] darn.. [22:21] so basically all the libindicate patches for empathy will need to be completely re-written? [22:21] probably not completely [22:22] the indicator patch didn't look too invasive in the empathy code itself. it just adds a few new files which are self-contained pretty much, which might need some gtk3-ification [22:23] anyway, it is time for the weekend. later all :) [22:23] dobey, thanks for all the assistance.. :) later [22:24] well kenvandine, until the libindicate stuff gets fixed up, do you think it would be against anything to just have a source only empathy built for the GNOME3 PPA ? [22:25] yeah, that would be fine for the gnome3 ppa [22:25] it won't be in the messaging menu for those who use the PPA [22:25] :/ [22:25] it's fine for the ppa [22:26] kenvandine, OK then I will do that. Who would I request to put on their long-term to-do list ? [22:26] i.e. no rush until next cycle [22:26] it's already on mine [22:26] telepathy-approver [22:26] :) [22:28] kenvandine, OK, a source empathy will go into the PPA then. I guess lemme know if I can take some easy tasks with that for empathy when you start on it. [22:33] Have a good weekend everyone. CYA!! [22:59] bratsche, hey... so grip_gesture_manager_register_window should actually be the constructor for GestureManager right? [23:00] kenvandine: No. [23:01] kenvandine: Take a peek in ../rectangle-mover/gesture.c [23:01] You acquire a reference to GestureManager, and then you call register_window() [23:01] ok, so GestureManager will be a singleton right? [23:02] Yes. [23:02] kenvandine: Did you get it to print events by setting the breakpoint and continuing? [23:05] yes [23:09] bratsche, i have some ideas, i'll work on it tonight