[04:52] <hikiko> hi
[05:09] <qengho> hikiko: good morning to you.
[05:09] <qengho> You never taught me how to say that in greek.  :(
[05:46] <hikiko> qengho, good morning (you just say kalimera καλημέρα) :p
[05:57] <hikiko> Trevinho, hi! could you also review this: https://code.launchpad.net/~hikiko/unity/unity.menus-anim-lowgfx/+merge/298859 later? (skips some fade/animations in u7 by only changing settings)
[06:47] <seb128> jbicha, you have some xenial SRUs that are in proposed for a while and not verified, could you try to do that or find somebody to help you doing it (abiword, gnome-taquin, gnome-documents)
[07:24] <willcooke> o/
[07:29] <didrocks> good Friday willcooke
[07:29] <jbicha> seb128: sure, I feel bad verifying my own SRUs but I didn't get any response when I asked the u-gnome list a week ago either
[07:58] <willcooke> hey didrocks, are you free to help me with that new launcher this morning?
[08:03] <Laney> morning!
[08:03] <willcooke> hi Laney, how was climbing?
[08:03] <seb128> jbicha, can try on the IRC channel maybe? but it's fine verifying it's own SRUs if nobody else does
[08:03] <seb128> hey willcooke, Laney, happy friday!
[08:04] <Laney> willcooke: ahoy, it was goooooooooooood
[08:04] <Laney> new competition circuit
[08:04] <Laney> what's not to like?
[08:04] <jbicha> seb128: I think the problem for Ubuntu GNOME especially is the kind of people interested in testing stuff are interested in *new* stuff like the GNOME3 PPAs
[08:04] <Laney> then later on I took some rhubarb stalks from the garden and we had fool which was nice
[08:04] <Laney> hi seb128
[08:05] <Laney> how's are you?
[08:05] <Laney> and jbicha too
[08:05] <Laney> up late?
[08:05] <seb128> I'm good thanks!
[08:05] <seb128> a bit tired
[08:05] <seb128> but it's friday, it's ok
[08:05] <seb128> just had some green tea and a croissant
[08:05] <Laney> nice
[08:06] <jbicha> Laney: yeah I was having trouble going to sleep
[08:07] <qengho> I'm happy. I got my laptop display fixed for US$70.
[08:08] <qengho> Someone in repair shop drove it across town to the factory that made laptop and they replaced something.
[08:09] <seb128> lol
[08:15] <didrocks> willcooke: in meetings, but we can try :)
[08:15] <didrocks> willcooke: you have snapcraft 2.12 now?
[08:16] <flexiondotorg> Morning.
[08:16] <flexiondotorg> Can I request a couple of merge proposal reviews please?
[08:16] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/indicator-session/mate-compatibility/+merge/297183
[08:16] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/cheese/caja-compatibility/+merge/298141
[08:17] <seb128> hey flexiondotorg
[08:17] <flexiondotorg> o/
[08:17] <seb128> flexiondotorg, try #ubuntu-devel? pitti is on a patch pilot shift
[08:18] <flexiondotorg> Thanks. Will do.
[08:18] <pitti> I'm here as well :)
[08:18] <willcooke> didrocks, I'm running devel from git, but it's old, gonna switch back to the archive version and update
[08:18] <didrocks> willcooke: normally, it's working as well with 2.11
[08:18] <pitti> flexiondotorg: I'll have a look
[08:18] <didrocks> willcooke: what you need to do is:
[08:18] <willcooke> didrocks, shall we move this to #snappy?
[08:18] <didrocks> willcooke: sure!
[08:19] <pitti> flexiondotorg: indicator-session is being handled via the CI train
[08:19] <flexiondotorg> pitti, Thanks.
[08:19] <jbicha> https://code.launchpad.net/~ubuntu-mate-dev/yelp/mate-compatibility/+merge/297171
[08:20] <flexiondotorg> Yeah, that one ^^^ too.
[08:20] <pitti> although I guess this simple packaging change can be pushed to trunk directly
[08:20] <seb128> I can do a landing for it if you want
[08:22] <pitti> seb128: this doesn't affect touch at all, does that really require the full CI train process?
[08:22]  * pitti is never sure what to do about those
[08:22] <seb128> no, I guess direct upload and commit to trunk is fine
[08:22] <pitti> ah, I can't commit to trunk
[08:22] <pitti> nor even approve the patch
[08:22] <seb128> you should
[08:23] <seb128> aren't coredev having access there?
[08:23] <seb128> bah
[08:23] <pitti> only ~indicator-applet-developers *grumble*
[08:23] <seb128> let me handle it
[08:24] <pitti> well, we can just upload and let them merge afterwards
[08:24] <pitti> seb128: ok, thanks; looking at the other one then
[08:24] <pitti> one"s"
[08:24] <seb128> well, in fact let me check with ted when he gets online
[08:24] <seb128> or not
[08:25] <seb128> k, they have a branch for 16.10 and another for 16.04
[08:25] <seb128> the tricky thing is that some of those component dual land to y/x
[08:25] <Trevinho> morning
[08:25] <seb128> or triple with the overlay
[08:25] <seb128> and in this case better to use the train and land to the different series together
[08:25] <seb128> hey Trevinho
[08:25] <Trevinho> hi seb128
[08:25] <seb128> Trevinho, how are you?
[08:25] <Trevinho> seb128: allright, you?
[08:26] <seb128> good
[08:26] <seb128> thanks
[08:35] <seb128> pitti, in fact please just dput indicator-session, seems you already did that once in yakkety and it makes the CI grumpy
[08:36] <seb128> so I'm going to let somebody from the indicator team sort that out
[08:36] <seb128> like the vcs doesn't have your previous upload
[08:36] <seb128> and the train bark because the archive and vcs are not in sync
[08:36] <pitti> seb128: ack
[08:36] <seb128> thanks
[08:37] <pitti> ah, https://code.launchpad.net/~seb128/indicator-session/correct-systemd-depends/+merge/285454
[08:37] <seb128> yeah
[08:37] <pitti> so (1) they don't review PRs quickly, and (2) make it impossible for ~core-dev to help out, so self-made hardship :)
[08:37] <seb128> I think we just need to manually push those to the vcs
[08:38] <pitti> ... which we can't
[08:38] <seb128> need to check with ted first
[08:38] <seb128> right
[08:38] <seb128> it's a bit annoying
[08:43] <pitti> seb128: btw, I vote for adding jbicha to https://launchpad.net/~ubuntu-desktop/+members again :)
[08:45] <seb128> yeah, it's probably fine, I don't think we had the case before of people leaving and wanting to come back after a while so I said he should probably just do a few sponsor uploads first just for the form
[09:08] <seb128> happyaron, hey :-)
[09:08] <happyaron> seb128: hi
[09:08] <seb128> happyaron, how are you? at debconf yet?
[09:09] <happyaron> no, packing for flight tonight
[09:10] <Laney> hey happyaron
[09:10] <Laney> when do you arrive?
[09:10] <seb128> k
[09:10] <seb128> happyaron, did you get a chance to merge back those missing commits from nmapplet 1.2.2?
[09:11] <happyaron> Laney: 16:30 2nd July
[09:11] <Laney> :-o
[09:11] <Laney> late
[09:11] <Laney> do you have to change plane somewhere?
[09:11] <happyaron> seb128: not yet, will see if I have time after packing, :)
[09:12] <happyaron> Laney: yep, at DXB
[09:20] <seb128> happyaron, in how many hours are you likely to get that done or not?
[09:23] <happyaron> guess need 3 hours to finish packing&dinner
[09:23] <seb128> happyaron, I want to upload today, if you don't get done I'm going to add those back to what you current have and let you deal later with the git format thing and reconciliating the vcs
[09:24] <seb128> happyaron, just let me know if I should wait or not
[09:24] <seb128> happyaron, k, good luck packing and eating dinner, if you don't get to it it's fine but please keep me updated either way with a clear "wait for me or please upload hacking it"
[09:25] <happyaron> if you have bandwidth please go ahead, and let me to do the git homework
[09:25] <seb128> k
[09:38] <ximion> Laney: Debian uses the immutable-suites stuff now, so far, no issues
[09:40] <Laney> hi ximion
[09:40] <Laney> good news
[09:40] <Laney> I'm coming to CPT tomorrow, we can find some time in the week to look at it if you want
[09:42] <ximion> Laney: oooh, awesome!
[09:43] <ximion> I completely forgot to ask if you'd come :)
[09:43] <Laney> it's your lucky day!
[09:44] <ximion> I wrote the immutable suites stuff before and after dinner, so I hope I catched all corner cases (people are distracting - and also, it is pretty much eating things with slight interruptions all day ^^)
[09:45] <Laney> heh
[09:45] <Laney> sounds nice
[09:45] <ximion> I also came up with a plan to implement a proper testsuite / test at least the basic things in asgen - the current test coverage isn't awesome, and I feel a bit uncomfortable with that
[09:46] <ximion> yeah, the food is awesome so far! I hope they will keep this level when more attendants are there...
[09:49] <ximion> bring warm clothes - it's warm enough outside, but the buildings are surprisingly cold inside (unless you have heaters)
[09:51] <andyrock> hey all
[09:52] <seb128> hey andyrock, how are you?
[09:52] <andyrock> fine :D
[09:52] <andyrock> seb128: you?
[09:53] <seb128> good!
[09:58] <seb128> andyrock, what are you working on today?
[09:58] <andyrock> the copy dialog bug
[09:58] <Trevinho> hi andyrock
[09:58] <seb128> andyrock, don't forget to make those SRU bugs compliant, seems like Trevinho is processing with the SRUs but they bugs need the info
[09:58] <seb128> Ah, nice one
[09:58] <andyrock> ah i forgot
[09:58] <Trevinho> hikiko: I've checked the branches, but things don't apply
[09:58] <andyrock> one moment
[09:58] <seb128> I just got annoyed by that again
[09:59] <Trevinho> seb128: you always got ANY bug there, so you're filtered out from the average user stats :-D
[10:00] <seb128> lol
[10:01] <Trevinho> hikiko: settings change don't seem to apply here, but in general I think that we can't just change user settings... since if user toggles the low-gfx value from CCSM then options get not reset... And he has to put things back again... And this case might also happen when an user doesn't specity the setting, but just if, for some reason, is running in
[10:01] <Trevinho> software rendering. So this might be to aggressive.
[10:02] <Trevinho> hikiko: as I said, we should probably just add a compiz screen option that then bypasses some things in every plugin. In this way we can easily just go in normal and llowgfx mode. Without adding other "options" around...
[10:16] <Sweet5hark> Laney, willcooke: You are not alone anymore! Out of solidarity, Austria presidental election was declared invalid and has to be repeated.
[10:16]  * Sweet5hark wonders if its friday yet.
[10:16] <seb128> it was? :-(
[10:17] <seb128> they had the green party winning instead of the far right no?
[10:17] <hikiko> Trevinho, if we do it this way, when lowgfx is selected we'll have to set every option for every plugin
[10:17] <Trevinho> hikiko: no
[10:17] <Sweet5hark> http://www.bbc.com/news/world-europe-36681475
[10:18] <hikiko> I mean let's say we have plugin A, B, C with special options for low gfx
[10:18] <hikiko> unity will set compscreen lowgfx to true
[10:18] <Trevinho> hikiko: it's like how the lowgfx setting is currently working in unity... When it's up to draw, you read the value and then you change things depending on that
[10:18] <Sweet5hark> seb128: yes.
[10:18] <Trevinho> hikiko: yes
[10:19] <Trevinho> hikiko: but, you don't have to change any settinng internally in the plugin
[10:19] <Trevinho> hikiko: you've only to bypass the animation settings
[10:19] <Trevinho> hikiko: when lowgfx is set, you just chose a different drawing path
[10:19] <hikiko> won't it look weird to the user
[10:19] <Sweet5hark> whats the revocation deadline for 2016? I want 2015 back.
[10:19] <hikiko> to see in ccsm that animation is let's say glide
[10:19] <hikiko> and there's no glide?
[10:19] <hikiko> when I change the setting
[10:20] <hikiko> compiz and ccsm and unity show the same
[10:20] <Trevinho> hikiko: it might look weird, but ccsm is not supported anyway... And if user is using a lowgfx-mode is already that way. While he expect not all things to work properly
[10:20] <seb128> hikiko, Trevinho,btw ideally the low graphics would work without option, there is a flag gnome-session sets that is used in GNOME, doing the same there would be nice
[10:20] <hikiko> seb128, Trevinho says another thing
[10:20] <hikiko> currently
[10:20] <hikiko> I check if lowgfx is set
[10:21] <hikiko> and then I set some extra or existing options in some plugins
[10:21] <hikiko> all that from unity
[10:21] <Trevinho> hikiko: no, I'm not saying that
[10:21] <hikiko> Trevinho, says we should have a variable lowgfx
[10:21] <hikiko> in compscreen
[10:21] <hikiko> no?
[10:22] <Trevinho> hikiko: ah, ok yeay...
[10:22] <Trevinho> hikiko: you were saying what you're doing before :)
[10:22] <hikiko> so when this variable is true
[10:22] <hikiko> each plugin draws accordingly
[10:22] <hikiko> but I disagree because the user will see other settings in ccsm
[10:22] <Trevinho> ideally I'd use an enum, more than a boolean, so it might support other levels in future
[10:22] <hikiko> and have different settings on his desktop
[10:22] <hikiko> plus
[10:23] <hikiko> when the option is added
[10:23] <hikiko> I mean
[10:23] <seb128> well unity is already limiting itself in software rendering mode no?
[10:23] <hikiko> in expo
[10:23] <Trevinho> hikiko: yeah, but it's already like that... Currently unity ignores any options about blur or transparency when the lowgfx mode is set.
[10:23] <hikiko> seb128, yes but what you see in settings is the settings you have
[10:23] <hikiko> Trevinho, yes but that's 1 plugin
[10:23] <hikiko> now it will be for every plugin
[10:24] <hikiko> plus
[10:24] <Trevinho> hikiko: ccsm is something we don't care about.. .I mean if the user sees a different setting, it's fine. We only care about settings exposed in unity control center
[10:25] <hikiko> I understand but why to make it misfunction when we can avoid this + also: adding new options (eg: animation: None to expo) will be shown in the plugin card
[10:25] <Trevinho> hikiko: I mean, you can do the way you want to... but it would need more work IMHO. Because we can't really reset the user settings as you're currently doing. So you'd need to copy them somewhere and then reset them back
[10:25] <Trevinho> imho it's more annoying than just bypassing them
[10:25] <hikiko> the user might want to use it
[10:26] <hikiko> for example
[10:26] <hikiko> he might decide
[10:26] <hikiko> that in expo
[10:26] <hikiko> he wants some eyecandy despite the lowgfx
[10:26] <hikiko> so that way
[10:26] <hikiko> he can open ccsm
[10:26] <hikiko> and change it
[10:26] <hikiko> +also
[10:27] <hikiko> the most important which I didn't thought
[10:27] <hikiko> the fade for example is not done in drawing and we skip it
[10:27] <hikiko> it's done in many small redraws (it's a progressive effect)
[10:27] <hikiko> so if you need to skip it
[10:27] <hikiko> you reduce these steps
[10:28] <Trevinho> Well.... I see the thing, but let's focus on why we need such lowgfx mode: we've to ensure unity runs reducing the eyecandy, but keeping things functional in normal mode. Hacking the settings is something we really can't support in this scenario.
[10:28] <hikiko> before drawing!
[10:28] <hikiko> yes, but we were also thinking (willcooke) that we might have different options for eyecandy
[10:28] <hikiko> like
[10:28] <Trevinho> hikiko: I guess you can just read the variable before drawing too...
[10:29] <hikiko> I can I just want to show you that it's not more simple solution :)
[10:29] <Trevinho> hikiko: I'm not against it, eh... It's just that this would need way more work imho, that we can avoid. Since we've not much time before .1
[10:29] <hikiko> imo its better to give a simple and fast DE to the user
[10:29] <davmor2> hikiko: you me real fire from the screen as your laptop ignites?
[10:29] <hikiko> and allow him
[10:29] <hikiko> to add whatever he likes afterwards
[10:30] <hikiko> instead of ignoring his preferences
[10:30] <hikiko> and the work is the same
[10:30] <hikiko> you either check for lowgfx on u7
[10:30] <hikiko> or you use an extra var in compiz
[10:30] <hikiko> and check twice
[10:30] <hikiko> for the same thing :)
[10:30] <Trevinho> hikiko: free to go, but... As I said, in that case we need to figure out a way to set user settings back when he toggles the gfx mode, because he choose it or because enevironment changed
[10:31] <hikiko> also willcooke had this idea: that we could later give different "sets" of unity effects
[10:31] <hikiko> like fast u7, extremely fast, normal, full eyecandy
[10:31] <hikiko> etc
[10:31] <Trevinho> hikiko: so... We can do that, but as I said some time ago, we can't do this by changing the default unity profile
[10:31] <hikiko> yeah
[10:31] <hikiko> but why do all this workaround
[10:31] <Trevinho> hikiko: add a new unity-lowgfx profile in unity settings, and then you can change whatever you want
[10:32] <hikiko> and restrict the user
[10:32] <Trevinho> compiz settings, not unity settings... Sorry
[10:32] <hikiko> yeah that's a good idea for later
[10:32] <hikiko> but I'd prefer to keep the lowgfx outside of compiz
[10:33] <hikiko> besides it's a u7 setting not a compiz one
[10:33] <hikiko> :s/setting/option or restriction
[10:34] <Trevinho> hikiko: later... Well, it's better to do that now if this is the way we want to proceed. Since we really can't land a version of unity that might revert so many user settings when lowgfx mode is set (which also might happen because of a driver/kernel update that temporary broke things).
[10:35] <hikiko> maybe have a meeting with willcooke (ping :D) next week and discuss this?
[10:35] <hikiko> I think that it's not a good idea to add the lowgfx to compiz
[10:35] <Trevinho> So, if you want to play with user settings, make possible that a new unity-lowgfx ccp profile is used in that mode... And then you can modify from unity whathever you want. Otherwise we're breaking stuff
[10:36] <willcooke> wat!
[10:36]  * willcooke reads
[10:36] <Trevinho> hikiko: you can avoid that, as said... You have to add a new settings profile
[10:36] <hikiko> willcooke, warning you have to do a lot of scroll-up
[10:36] <Trevinho> see the unity.ini in compiz and ccsm settings profiles
[10:36] <willcooke> I'm lazy, can we just have a quick hangout to discuss now?
[10:36] <Trevinho> hikiko: but we can't really play with default one in such way
[10:36] <Trevinho> willcooke: ok
[10:36] <hikiko> ok
[10:37] <willcooke> Trevinho, hikiko - https://hangouts.google.com/hangouts/_/canonical.com/will?authuser=0
[10:37] <Trevinho> seb128: if you want to join...
[10:38] <hikiko> sec
[10:41] <hikiko> pff no sound joining from laptop
[10:44] <hikiko> hey guys do you hear me?
[10:45] <seb128> Trevinho, u-s-d deleted from silo
[10:45] <Trevinho> seb128: thanks, and new silo prepared
[10:46] <seb128> thanks
[11:04] <Laney> going to pack + do errands before train
[11:04] <Laney> biab hopefully
[11:10] <seb128> Laney, good luck with the packing!
[11:23] <hikiko> Trevinho, could you paste me the name of the tool?
[11:23] <Trevinho> hikiko: /usr/lib/nux/unity_support_test
[11:24] <hikiko> and the code is part of nux?
[11:24] <hikiko> or another branch?
[11:24] <Trevinho> well, it's in x86_64 now
[11:24] <Trevinho> hikiko: it's nux
[11:24] <Trevinho> hikiko: nux/tools/unity_support_test.c
[11:25] <hikiko> cool :) thanks
[11:26] <hikiko> well I have to go now, I'll be back in 2-3hrs and finish it +also, I might do a quick compiz branch with a low gfx setting to be ready for merge just in case... although I think the profile will be ok :)
[11:26] <hikiko> bbl
[11:49] <Trevinho> bregma: released https://launchpad.net/compiz/0.9.13/0.9.13.0
[12:20] <andyrock> seb128: i know you're going to be happy about this (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1578792) being fixed
[12:20] <andyrock> :D
[12:50] <seb128> andyrock, great, free beer for you next time!
[13:22] <mitya57> seb128, qt uses GtkSettings when the GTK+ platform theme is available.
[13:23] <mitya57> (which on X11 is a wrapper around XSettings)
[13:23] <mitya57> Also other platform themes can add their own code to detect the icon theme.
[13:25] <seb128> mitya57, thanks, and sorry I forgot to unping, we got things working (trying to get snap applications properly themes and the snap was missing the qt svg loader)
[13:25] <mitya57> No problem, and sorry for being not online in the last couple of days ;)
[13:34] <pitti> yummy ice cream
[13:35] <pitti> fit for the remaining few Friday hours :)
[13:35] <desrt> good morning everyone
[13:36] <pitti> heeeey desrt!
[13:36] <desrt> and happy canada day :)
[13:37] <seb128> hey desrt
[13:38] <desrt> it's a holiday to celebrate the fact that even though our current PM is an idiot, at least we don't live in the UK or US
[13:39] <desrt> or in the words of the most patriotic canadian band of all time -- the arrogant worms -- "we won't say that we're better... it's just that we're less worse."
[13:39]  * desrt feels so so... proud?
[13:41] <seb128> lol
[13:42] <qengho> desrt: I went to the party the Canadian AlmostAnEmbassyButNotOfficialBecauseChinaIsBig's Canada Day Party here in Taipei, on Sunday. All the ONAN expats were there. Was kind of weird.
[13:43] <qengho> I only went for the poutine, and came away very very disappointed.
[13:45] <qengho> desrt: I did teach a gaggle of chinese kiddies how to hold a hockey stick.
[13:45] <desrt> i imagine poutine to be the sort of thing that doesn't travel particularly well
[13:45] <desrt> but cool that you checked it out :D
[14:44]  * qengho Zzzz.
[15:31] <Trevinho> hikiko: https://code.launchpad.net/~3v1n0/compiz/unity-lowgfx/+merge/298918
[15:49] <hikiko> Trevinho, just sent an email let me see
[15:50] <hikiko> Trevinho, is this the new profile?
[15:50] <Trevinho> hikiko: yes
[15:50] <hikiko> (thanks :)) I was looking at the tool code (nux)
[15:51] <hikiko> I guess you mean to extend it
[15:51] <Trevinho> apply that on top of your branch
[15:51] <Trevinho> what you mean about extend?
[15:51] <hikiko> Trevinho, this will change the default profile?
[15:51] <hikiko> oh!
[15:51] <hikiko> I just noticed the ini :DD
[15:51] <Trevinho> hikiko: no
[15:51] <hikiko> yes got it!
[15:52] <hikiko> so I ll have to load this at the beginning?
[15:52] <hikiko> at startup*
[15:52] <hikiko> how does .ini work?
[15:53] <hikiko> is it like a startup script?
[15:53] <Trevinho> hikiko: once installed that and the config in /etc/compizconfig/
[15:53] <Trevinho> you can load compiz
[15:53] <Trevinho> with
[15:53] <Trevinho> COMPIZ_CONFIG_PROFILE=ubuntu_lowgfx
[15:54] <Trevinho> or change it at runtime with ccsm, but...
[15:54] <Trevinho> what we want do do is, inside the upstart job to decide what to use
[15:56] <hikiko> yes, so I have to extend the nux/tools/unity_support_test.c to check for low gfx tool too and set the env var in a script in ~/.config/upstart/unity.conf?
[15:56] <hikiko> btw does upstart work with systemd Trevinho ?
[15:57] <Trevinho> hikiko: at user level we use only upstart, so we don't care about systemd
[15:58] <hikiko> and the upstart conf file for unity is that above?
[15:58] <hikiko> or something else?
[15:58] <hikiko> I've found that in the ubuntu forums :p
[15:58] <Trevinho> un unity_support_test.c, you've to ensure that all the checks we do in unityshell.cpp (at the beginning) are present there
[15:58] <Trevinho> in*
[15:59] <hikiko> I just don't understand how that .c is connected with upstart
[15:59] <Trevinho> it's not yet
[15:59] <Trevinho> I'll modify the unity7.conf file so that it launches that script... If it returns an error, we'll use the low-gfx mode otherwise we proceed as normal
[16:00] <hikiko> alright ;) now it all makes clear
[16:00] <hikiko> so, do you prefer a small standalone program that does only that?
[16:01] <hikiko> the u7 checks?
[16:01] <Trevinho> hikiko: we've it, and it's unity_support_test.c
[16:01] <hikiko> lol
[16:01] <Trevinho> hikiko: can you just please check if that does all the right checks?
[16:02] <hikiko> because it does a lot more, alright then
[16:02] <Trevinho> hikiko: well, if you want to simplify it, feel free.. but I think it's still quite light, isn't it?
[16:02] <hikiko> if you like it, it's fine for me
[16:03] <Trevinho> hikiko: I'm fine with that, I just would like you to ensure that all the extensions we care about are in there
[16:03] <hikiko> OpenGL extensions, right?
[16:05] <Trevinho> hikiko: yes
[16:05] <Trevinho> hikiko: then there's thins comment:   // FIXME(loicm): Compiz does a last check to test whether there's a fbconfig
[16:05] <Trevinho>   //     available for the default depth or not.
[16:06] <hikiko> alright I'll check if there's that on u7
[16:12] <Trevinho> hikiko: do we have a bug for this thing? So  I can attach all the branches to that
[16:14] <hikiko> no
[16:14] <hikiko> well
[16:14] <hikiko> yes
[16:14] <hikiko> there's one: Unity is slow
[16:14] <hikiko> somewhere...
[16:14] <hikiko> let me find it
[16:16] <hikiko> https://bugs.launchpad.net/compiz/+bug/1293384
[16:28] <Trevinho> hikiko: mh, not sure that's the same problem, it looks quite generic... but we can add a new one
[16:28] <Trevinho> hikiko: please check and approve https://code.launchpad.net/~3v1n0/nux/support-test-llvmpipe-check/+merge/298926
[16:34] <hikiko> Trevinho, approved
[16:43] <Trevinho> hikiko: thanks, did you give a look to that FIXME statement in unity-support-test?
[16:44] <seb128> ok, calling it a week
[16:44] <seb128> have a nice w.e everyone
[16:45] <Trevinho> seb128: you too
[16:45] <Trevinho> seb128: good luck with those Vulcanic players ;)
[16:46] <seb128> haha
[16:46] <seb128> nice Italia vs Germany tomorrow!
[16:46] <seb128> then it's us
[16:47] <ogra_> seb128, LOL
[16:47] <ogra_> you dont fear iceland at all, eh ?
[16:48] <seb128> less than Italy let's say
[16:48] <seb128> ;-)
[16:48] <ogra_> well ...
[16:49] <Trevinho> Considering how things are going... I expect portugal to get the cup without winning a single match
[16:49] <ogra_> not so sure ... italy are old farts :)
[16:49] <Trevinho> yeah, we'll see...
[16:52] <hikiko> Trevinho, I dont understand what loic means, fbconfig is a program to set the framebuffer device options... if you draw to the /dev/fb0 (we don't) you might use it to find the color depth
[16:53] <Trevinho> ah, ok
[16:53] <hikiko> but I can't understand what "test whether there's an fbconfig available for the default depth or not" means
[16:54] <hikiko> I'll get a look at compiz he might mean something else
[16:56] <Trevinho> hikiko: ok thanks
[16:57] <andyrock> eow
[16:58] <hikiko> maybe the GLX_SGIX_fbconfig extension?
[17:01] <hikiko> maybe "framebuffer configuration"
[17:02]  * Laney wibbles from nearly-LHR
[17:02] <hikiko> but still it doesn't make much sense
[17:03] <hikiko> it also might mean the Xserver fbconfig struct
[17:04] <hikiko> Trevinho, might mean to check that xserver can use 24 and 32 bit visuals?
[17:07] <Laney> andyrock: !!!
[17:08] <Laney> I have https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1595698 and was blaming it on gtk 320
[17:40] <Trevinho> hikiko: I think it's quite implicit by other cheks, isn't it=
[17:40] <Trevinho> ?
[21:51] <qengho> ayan: hihi