=== rsalveti` is now known as rsalveti [07:25] duflu: hey, about bug 927168, should I send it upstream to the mesa guys, or is it a compiz bug? [07:25] Launchpad bug 927168 in Compiz "compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry()" [Critical,In progress] https://launchpad.net/bugs/927168 [07:27] tjaalton: Still not 100% but seems very likely a compiz bug. I just approved a potential compiz fix [07:28] duflu: oh cool, I could give it a try as well, easy to reproduce :) [08:04] om26er_, about bug 1052345, I don't have unity-window-decorator running but gtk-window-decorator. Is it the process I should kill ? [08:04] Launchpad bug 1052345 in unity (Ubuntu) "Windows operations in Unity become sluggish after a few days of usage" [Undecided,New] https://launchpad.net/bugs/1052345 [08:14] jibel, yeah, sorry that was meant to be gtk-window-decorator [08:15] there is a leak in gtk-window-decorator so i thought your issue maybe the same [08:15] om26er_, np, I commented on the report. The desktop is more responsive again. [08:58] hiya [08:58] do we have some docs for how to "integrate a program into the HUD"? [08:58] http://daniel.holba.ch/blog/2012/09/ubuntu-dev-hangouts/#comment-653338925 [09:05] popey: FYI: https://bugs.launchpad.net/shotwell/+bug/1052375 [09:05] Ubuntu bug 1052375 in unity-scope-gdocs (Ubuntu) "The g-c-c interface doesn't support i18n" [Undecided,New] [09:05] * popey clicks [09:08] popey: it's just a FYI, I just spent some time to sort that out between the different team [09:08] thanks [09:25] popey: do you have a status on compiz release/migration? [09:25] popey: also, I think it will be good to backport latest commits from compiz as distro cherry-picks [09:26] didrocks, ted kindly had a deep look at the migration issue, and identified some interesting stuff but not a conclusion, he's offered to look further [09:27] didrocks, I agree.. [09:27] ^ Mirv :) [09:27] popey: thanks! [09:38] I've already cherry-picked the two additional compiz bug fixes that are targeted to beta-2. PPA (and packaging url) at https://launchpad.net/~timo-jyrinki/+archive/compiz-quantal-testing2 [09:39] or the other compiz bug fix is to a bug fix in unity that is targeted to beta-2, so essentially needed [09:39] Mirv: excellent! [09:40] Mirv: so rev 377 and rev 3376 are in? [09:40] Mirv: I think rev 3374 is interesting as well [09:40] so maybe better to merge tip on top of your content? [09:42] thanks Mirv [09:42] 3372 and 3376. tip would be nice, but as usual creates a risk of detecting late regressions when testing everything at once, and then we might miss beta 2 if we end into a loop of finding new bugs, trying to get them fixed etc, while 0.9.8.2 + cherry-picks have already been successfully tested [09:44] there'll always be time for 0.9.8.4 [09:44] (3368 and 3373 are also in the packaging branch) [09:50] Mirv: rev 3376 is fixing a critical bug for beta2 [09:50] Mirv: so we need at least this one [09:51] yep, it's in, although apparently needs more than just that commit [09:51] Mirv: ok, I'll let you decipher this :) [10:07] Mirv: You mean 3374, not 3373? [10:07] 3374 is getting lots of duplicate crash reports === mmrazik is now known as mmrazik|lunch [10:49] no, 3373 since it prevents unity from building. [10:50] 3374 can be picked up as well === MacSlow is now known as MacSlow|lunch === MacSlow|lunch is now known as MacSlow === doko_ is now known as doko === _salem is now known as salem_ === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === yofel_ is now known as yofel [14:14] I'm going the "tip" route... [14:15] Mirv: sounds safe to me [14:56] popey: Mirv: any news from ted on the migration? [14:56] popey: Mirv: I think we won't have time to deal with those with tomorrow's release, so better to have that tackled before [15:03] didrocks, sorry, was afk. just catching up [15:08] didrocks, no movement yet [15:08] * popey hugs tedg [15:08] * didrocks starts to be concerned [15:08] really concerned [15:13] not sure who else we can recruit/press-gang into helping tbh [15:13] not sure, everyone is really busy… [15:13] tedg: no time for that? [15:14] popey: you have 4 people in your team, nobody can help Mirv? seems blocking on a transitional issue for 2 weeks shouldn't happen [15:15] I am reaching out to tedg because he seems to have the knowledge to help. others do not. === dandrader is now known as dandrader|lunch [15:54] didrocks, Yeah, unfortunately I end up in meetings :-) [15:55] tedg: tell that your mic is broken dude! :-) [15:55] didrocks, Heh [15:55] tedg: did you find anything yesterday? [15:55] didrocks, BTW, why is this a blocker? Can we just say "eh, new configuration, you get defaults"? [15:55] tedg: I didn't test is on my machine, so can't really tell [15:55] didrocks, There's some oddities, but I haven't found a final "this is what it is" [15:55] tedg: well, gold rule is to keep user config [15:56] tedg: like, if they tweak switching ws [15:56] and it's reset to the default [15:56] didrocks, It seems the writer is going later than we'd like. [15:56] this shows a bad quality product [15:56] didrocks, Sure, and we wouldn't touch their old config :-) [15:56] well, we do with the gconf -> gsettings transition :) [15:56] didrocks, It seems like a "nice to have" and a "should do" but not a blocker. [15:57] tedg: so, at worst, the user has the default config? [15:57] didrocks, Yes [15:57] tedg: no binary corruption of the gsettings blob? [15:57] like if there is a writing and a revert [15:57] (this is what happens, right?) [15:57] It seems like there is a write and a revert, but the revert goes back to the default value. [15:58] I haven't seen any corruption, but I'd double check with Mirv to be sure he hasn't. [15:58] no, I haven't seen any corruptions at any point [15:59] well, ok, I think at this point we can keep as it is then [15:59] let's keep the migration script [15:59] tedg: did you talk to desrt? [15:59] tedg: maybe he would have some inputs [15:59] as it's clearly a dconf issue :) [15:59] didrocks, I asked him a couple of questions, but haven't pulled him in completely :-) [16:00] It is a bit odd that the gsettings migration tool doesn't force a sync, but I added that and it didn't help. [16:00] Well, it didn't solve it. [16:00] tedg: you can tell him that you have so many "desrt" files and path on your system that he has to do the support now :p [16:00] I blame him for every bug in GTK+ [16:00] oh gsettings-data-convert doesn't force a sync? [16:00] tedg: you sure probably do :) [16:01] didrocks, Nope. I've got a patch, but it didn't solve this problem. [16:01] Not sure if we should add it just because it makes sense though. [16:01] tedg: probably, well, no hurry though [16:01] tedg: if you can get more info at some not that crazy time point from desrt, I would be interesting [16:01] tedg: thanks for checking [16:02] Mirv: popey: so I think we can go on, with the migration, as we are [16:02] Mirv: popey: let's forget about the corner case, we will be blame, but seeing the unity release coming… [16:12] ok. the new compiz snapshot packaging branch is at lp:~timo-jyrinki/ubuntu/quantal/compiz/ubuntu.0982bzr3377 [16:12] it's a shame it can't be released without a unity rebuild which cannot be done without updating unity and libunity... [16:12] Mirv: libunity as well? [16:12] Mirv: unity is because of at-spi2, right? [16:12] but libunity? [16:13] didrocks: the unity version that brings at-spi2 (if not cherry-picking) happens to also require newer libunity [16:13] Mirv: can we cherry-pick the unity at-spi2 commit only? [16:14] didrocks: we could, although then that combo should be also tested [16:14] and the whole stack will need testing tomorrow as well [16:14] I can prepare such a PPA anyway which has compiz + unity 6.4+at-spi2 [16:15] Mirv: no need I guess, if we are confident that the whole stack would be ready by tomorrow [16:15] Mirv: how many additional commit is compiz trunk? [16:16] Mirv: compared to latest tests [16:17] didrocks: well I'll prepare. I'm not 100% confident of all of this, but I tend to be on the cautious side. 14 commits since latest was tested. [16:18] Mirv: yeah, 14 is a lot [16:19] at least I'll check if unity 6.4 + a11n cherry-pick + latest compiz would be one functional combination [16:19] Mirv: so, let's get one stack tested [16:19] ok :) [16:19] thanks Mirv [16:19] no prob [16:27] mpt: have some minutes to talk about https://bugs.launchpad.net/dbusmenu/+bug/541472? [16:27] Ubuntu bug 541472 in libindicator "Menu icons should not be 16x16 px" [Low,Confirmed] [16:28] conscioususer, hey! I'm in a meeting, but in about 30 min [16:28] mpt: ok, I'll stay around === dandrader|lunch is now known as dandrader [17:06] ok unity 6.4 + a11n cherry-pick alone was not successful unfortunately https://launchpadlibrarian.net/116530817/buildlog_ubuntu-quantal-amd64.unity_6.4.0-0ubuntu7~test1_FAILEDTOBUILD.txt.gz [17:08] conscioususer, yo [17:08] mpt: hi [17:09] mpt: hope the meeting went well :) [17:09] no comment [17:09] but seriously, it was good [17:09] ah, you got me worried for a moment there [17:10] so, icons! [17:10] if I understood correctly, you guys want to invest in auto-resizing according to font size? [17:13] mpt: how would the approach to scaling be, considering there is a set of discrete sizes? [17:14] conscioususer, I don't know, but I imagine it would be choosing the nearest discrete size up to a certain level, and thence scaling the scalable/largest [17:14] So graphed, like a staircase followed by a ramp [17:14] mpt: the nearest *larger* than the font, I suppose [17:15] I don't know [17:15] mpt: hmm, or maybe the smaller one, so it's aesthetically better to keep all items with the same height [17:15] maybe [17:16] mpt: anyway, IIRC one problem with your proposal on the report is that changing the constant (supposing that is even possible) will not auto-update the icons [17:16] mpt: I think the size is read when the pixbuf is read, and never again [17:18] conscioususer, could you comment about that in the bug report? I don't really know what a pixbuf is. :-) [17:18] mpt: will do [17:18] thanks! [17:19] mpt: the GNOME HIG (leaving aside the fact that it needs a new version) simply says "menu icons should be 16x16" and leaves it at that http://developer.gnome.org/hig-book/3.5/icons-types.html.en [17:19] mpt: so I'm not sure what is the position of GNOME/GTK devs on this [17:19] mpt: but leaves me pessimistic as to how easy it will be to reach the goal [17:19] conscioususer, desrt is going to report it upstream for starters [17:20] mpt: current version of polly resizes icons, but I use exact sizes instead of restricting itself to the discrete ones... that ended up in blurring disaster, won't keep that for the gtk3 port [17:21] What do you mean by "instead"? The discrete sizes are exact sizes, no? [17:25] mpt: I meant I don't necessarily choose one of the discrete ones... so it's possible to have 20x20, 21x21, 23x23, 25x25, etc. [17:26] mpt: wrote on the report [17:26] thanks === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [19:08] Hallo, this is my live session of quantal today build amd64, running on amd2800+, 1,6 GHz, 2Gram, Geforce 6100 onboard, http://www.youtube.com/watch?v=bC-9OZmI4XI&feature=youtu.be [19:10] is this compiz, unity, gtk or whatelse ? [19:15] this machine before was working well on 2D, not fast but working. [19:17] before I mean 12.04 === ike_ahloe is now known as StevieB === StevieB is now known as HelloMannn === salem_ is now known as _salem