[04:07] <Mirv_> morning
[04:09] <mlankhorst> morning!
[05:30] <pitti> Good morning
[05:31] <desrt> pitti: thanks for reminding me that it's past my bed time
[05:31] <desrt> good night!
[05:31] <pitti> heh
[05:31] <pitti> desrt: sleep well!
[06:59] <jibel> good morning
[06:59] <didrocks> salut jibel, bon week-end?
[07:00] <jibel> salut didrocks! très bon w.e. et toi ?
[07:01] <didrocks> jibel: pareil! plutôt resté à l'intérieur à cause de la pluie, juste marché 12 kms :/ mais bon… Aujourd'hui grand soleil (le seul jour jusqu'à lundi prochain apparemment)
[07:09] <Mirv> we had some summer cottage preparation work, healthy outside exercise
[07:10] <didrocks> Mirv: oh nice, lucky you! I wish summer will finally starts here for more than a day :)
[07:10] <didrocks> or at least, spring!
[07:35] <Sweetshark> Goood Moin!
[07:36] <didrocks> oh, it's a Sweetshark :)
[07:37]  * Sweetshark feels much cooler now, having collected the business card of a member of parlament on the weekend ...
[07:37] <Sweetshark> Achievement Unlocked
[07:38] <didrocks> :)
[07:42] <Sweetshark> seb128: Please tell me I dont have to do this, and that it perfectly fine to upload a still somewhat shaky LibreOffice-4.1.0~beta1 to saucy: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1182170/comments/7
[07:42] <ubot2> Ubuntu bug 1182170 in libreoffice (Ubuntu) "libreoffice FTBFS in saucy" [High,In progress]
[07:42] <Sweetshark> :/
[07:55] <didrocks> tjaalton: mlankhorst: jibel seems to have issues with the nvidia module not loading on saucy, is that known?
[08:01] <mlankhorst> log?
[08:01] <mlankhorst> and nvidia kernel module, or xorg driver module
[08:16] <seb128> hey desktopers, happy monday
[08:16] <didrocks> salut seb128, joyeux lundi! :)
[08:16] <mlankhorst> bonjour
[08:16] <seb128> didrocks, lut, à toi aussi ;-)
[08:16] <seb128> mlankhorst, hey
[08:42] <jibel> didrocks, mlankhorst bug 1184536 with nvidia compiz starts but not unity
[08:42] <ubot2> Launchpad bug 1184536 in unity (Ubuntu) "Unity failed to load with nvidia-current" [Undecided,New] https://launchpad.net/bugs/1184536
[08:44] <didrocks> yeah, so all those Xlib:  extension "GLX" missing on display ":0".
[08:44] <didrocks> this is understing, any idea mlankhorst?
[08:45] <mlankhorst> looks like libGL.so is wrong
[08:45] <mlankhorst> you're probably using mesa libgl against nvidia somehow
[08:48] <mlankhorst> hm weirder, still
[08:52] <didrocks> mlankhorst: any way, we can provide more info?
[08:53] <mlankhorst> tseliot might know more, what does glxinfo say?
[08:53] <didrocks> jibel: ^
[08:53]  * tseliot looking
[08:54] <mlankhorst> it really looks like a wrongly installed nvidia driver to me, though
[08:54] <didrocks> Mirv: we should have done Qt today, with this issue on jenkins :p
[08:54] <jibel> mlankhorst, tseliot output of glxinfo attached to the report
[08:55] <mlankhorst> now that's weird
[08:55] <mlankhorst> and if you start compiz in the same way?
[08:56] <tseliot> jibel: also what's the output of this command? update-alternatives --display x86_64-linux-gnu_gl_conf
[08:57] <tseliot> err... direct rendering: Yes server glx vendor string: NVIDIA Corporation
[08:57] <mlankhorst> tseliot: yeah I have no idea what's going on there
[08:59] <tseliot> mlankhorst: doesn't glxinfo call glXQueryExtension?
[09:01] <mlankhorst> it should
[09:01] <mlankhorst> I have no idea how the errors from the gnome-session can be from the same configuration..
[09:01] <jibel> tseliot, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1184536/+attachment/3687714/+files/update-alternatives.log
[09:01] <ubot2> Ubuntu bug 1184536 in unity (Ubuntu) "Unity failed to load with nvidia-current" [Undecided,New]
[09:02] <tseliot> jibel: yes, it looks fine, as the rest. I don't think it depends on the nvidia package
[09:02] <mlankhorst> jibel: just to be sure, starting unity manually fails too?
[09:05] <jibel> mlankhorst, it fails too
[09:05] <mlankhorst> ldd /usr/lib/compiz/libunityshell.so |grep GL ?
[09:07] <jibel> mlankhorst, http://paste.ubuntu.com/5706210/
[09:08] <mlankhorst> looks sane enough
[09:08] <mlankhorst> i have no idea in what funny way you messed up your system :/
[09:09] <jibel> mlankhorst, I don't know either, I'm just running a standard saucy and apt-get install nvidia-current :)
[09:10] <tseliot> jibel: was it a clean installation of Saucy?
[09:10] <jibel> tseliot, upgraded from raring but nothing fancy
[09:11] <tseliot> hmm...
[09:13] <tseliot> jibel: one last thing: what's the output of ps aux | grep X
[09:13] <jibel> tseliot, http://paste.ubuntu.com/5706215/
[09:15] <tseliot> jibel: it is weird. Can you reproduce it across reboots?
[09:16] <tseliot> jibel: also, what's the output of "dkms status"
[09:17] <jibel> tseliot, I did not count how many reboots since this morning, and it fails reliably :) output of dkms http://paste.ubuntu.com/5706223/
[09:18] <tseliot> jibel: and what happens if you uninstall nvidia? Does compiz work properly?
[09:19] <Mirv> didrocks: yes, although there is always enough Qt stuff for me to do :)
[09:20] <tseliot> mlankhorst: I'm wondering if something changed in Xlib and maybe compiz needs to be rebuilt against it
[09:20] <Mirv> it's good that saucy Qt is about set up now, for anything that builds against it
[09:20] <didrocks> Mirv: ok, keep me posted if you need to upgrade anything to saucy, let's use that downtime in a profitable way :)
[09:20] <Mirv> didrocks: I will, currently looking at some precise/quantal Qt updates
[09:20] <mlankhorst> tseliot: I have no idea, sounds weird if that was the case
[09:20] <tseliot> very
[09:24] <tseliot> jibel: and another thing you can check is if running a guest session works
[09:27] <mitya57> Sweetshark: when you asked your question seb128 was not here yet, please ask it again
[09:27]  * mitya57 wants fixed libreoffice because it currently blocks poppler transition
[09:34] <jibel> tseliot, ah, a guest session works fine
[09:35] <tseliot> jibel: so I guess something wrong must have happened to your compiz settings. Something like this should help: dconf reset -f /org/compiz/
[09:35] <tseliot> jibel: log in with your username this time
[09:39] <seb128> mitya57, xnox was working on making libreoffice build on saucy's toolchain
[09:40] <mitya57> seb128: did you read Sweetshark's last comments on bug 1182170?
[09:40] <ubot2> Launchpad bug 1182170 in libreoffice (Ubuntu) "libreoffice FTBFS in saucy" [High,In progress] https://launchpad.net/bugs/1182170
[09:40] <seb128> mitya57, no, I didn't even know about that bug
[09:41] <mitya57> actually the question was: <Sweetshark> seb128: Please tell me I dont have to do this, and that it perfectly fine to upload a still somewhat shaky LibreOffice-4.1.0~beta1 to saucy: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1182170/comments/7
[09:41] <ubot2> Ubuntu bug 1182170 in libreoffice (Ubuntu) "libreoffice FTBFS in saucy" [High,In progress]
[09:42] <seb128> mitya57, well, it seems like Sweetshark is on it
[09:43] <jibel> tseliot, a reset fixed it, http://paste.ubuntu.com/5706270/ this is the diff of the dconf settings before and after the reset if it helps
[09:43] <jibel> didrocks, ^
[09:43] <mitya57> yes, but either he should upload 4.1 beta or we won't see the fix any time soon :)
[09:44] <tseliot> I'm no expert in compiz settings, hopefully Didier will shed light on it
[09:45] <jibel> tseliot, thanks for your help
[09:45] <tseliot> jibel: np
[09:48] <didrocks> jibel: weird, that you have ccp, I'll try to reproduce the upgrade
[09:48] <didrocks> seems some plugins didn't stick from the upgrade
[09:49] <didrocks> (some missing plugins, the most noticeable being the opengl one)
[10:00] <Sweetshark> 09:42 < Sweetshark> seb128: Please tell me I dont have to do this, and that it perfectly fine to upload a still somewhat shaky LibreOffice-4.1.0~beta1 to saucy:  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1182170/comments/7
[10:00] <ubot2> Ubuntu bug 1182170 in libreoffice (Ubuntu) "libreoffice FTBFS in saucy" [High,In progress]
[10:00] <Sweetshark> :/
[10:00] <seb128> Sweetshark, your call ... define "shaky libreoffice"?
[10:01] <seb128> Sweetshark, but uploading 4.1.0 beta1 wfm
[10:03] <Sweetshark> seb128: well, as a beta it hasnt seen too much testing (Its only 4 days old and has so far only seen testing by those who are nuts enough to try daily builds of libreoffice ;) )
[10:08] <seb128> Sweetshark, are libreoffice betas usually stable enough to get work done? or do they segfault every 5 minutes when you are trying to edit documents?
[10:10] <Sweetshark> seb128: I wouldnt exclude the possibility of the second, at least for beta1. beta2 is usually better.
[10:10] <seb128> Sweetshark, seems like it would be better to keep beta1 in a ppa then?
[10:11] <Sweetshark> seb128: So, no, I dont really feel comfortable dumping beta1 on the archive right now. I just dont like to bisect 10000 commits :/.
[10:11] <seb128> Sweetshark, what are you looking for in those 10000 commits? a fix for the failing test?
[10:11] <mlankhorst> Sweetshark: only 14 iterations!
[10:11] <seb128> Sweetshark, how long does a build take on your box? you said it's 16 build at max
[10:12] <seb128> seems like you just need to let your box work for a day for that?
[10:12] <Sweetshark> seb128: Yep, any first 4.1/saucy upload should spend some time in a PPA. After all, our build also might be somewhat different from the upstream one (e.g. trouble introduced by our gcc/boost/whatever ...)
[10:14] <Sweetshark> seb128: the builds arent what is annoying -- 4.0 doesnt build unpatched against our saucy gcc/boost, so I have to patch/backport the build fixes on each step ....
[10:15] <seb128> oh, "fun"
[10:15] <seb128> Sweetshark, what is failing, a test? can't you just disable that test until we get 4.1 beta 2 ?
[10:17] <Sweetshark> seb128: yep, that would work.
[10:17] <seb128> Sweetshark, then what about doing that?
[10:18] <Sweetshark> seb128: In seems like the lazy thing to do, but really is probably the right thing to do indeed.
[10:19]  * Sweetshark checks how far beta2 is off.
[10:19] <seb128> Sweetshark, well, "lazy" ... there are only so many hours in a day, that issue doesn't seem worth spending days on
[10:20] <Sweetshark> beta2 is June, 3rd-9th. Seems reasonable to go directly for that.
[10:21] <Sweetshark> seb128: Have I told you recently that I love you? ;)
[10:21] <seb128> haha
[10:42] <pitti> nous aimons tous seb128 !
[10:42]  * seb128 hugs pitti
[10:43]  * pitti te donne une accolade en retour
[10:43] <pitti> seb128: ça va ?
[10:44] <seb128> pitti, oui, ça va bien, il fait beau aujourd'hui !
[10:44] <seb128> et toi ?
[10:44] <pitti> je me sense comme hiver à nouveau
[10:44] <pitti> beacoup de pluie tout le week-end
[10:45] <pitti> et 6 °C
[10:45] <seb128> :-(
[10:45] <seb128> ici il a fait beau samedi
[10:45] <seb128> 15°C et du soleil
[10:45] <pitti> je le veux aussi !
[12:35] <jbicha> seb128: vala-0.20 will be default for saucy right?
[12:35] <seb128> jbicha, not decided, 0.18 is still default for the moment, why?
[12:35] <seb128> we need to test build the unity lenses with 0.20 and check they are still working before looking at changing
[12:36] <jbicha> I was just curious since Debian dropped 0.18 and .20 is default there
[12:37] <seb128> ok, I see no reason to not change if everything is working fine
[12:37] <seb128> we just need to test rebuild what is on the CD
[12:39] <jbicha> by the way it looks like gnome-shell 3.6 doesn't really work with gtk 3.8
[12:39] <seb128> hum, nobody tested that during all the time we were preparing gtk 3.8? what is the issue?
[12:41] <jbicha> darkxst said "it's getting stuck trying to read the mouse pointer position"
[12:41] <jbicha> clicks aren't working and it very quickly gets too bogged down to do anything
[12:42] <seb128> what is needed to update gnome-shell to 3.8?
[12:43] <jbicha> gnome-desktop3 which didn't look like too bad of a transition except that g-s-d will need some work
[12:43] <jbicha> https://git.gnome.org/browse/gnome-settings-daemon/log/?qt=grep&q=gnome-desktop
[12:43] <seb128> no g-s-d/g-c-c
[12:43] <seb128> e.g for input methods
[12:44] <jbicha> right, I meant backporting several commits (so that g-s-d can rebuild) and checking to make sure things still work
[12:45] <jbicha> we'll also need gsettings-desktop-schemas but we reverted the 2 commits that drop schemas we're still using
[15:24] <pitti> seb128: do we already have some plan to update to g-s-d 3.8?}
[15:24] <pitti> seb128: 3.6's power plugin doesn't work all that well with current logind (bug 1180513)
[15:24] <ubot2> Launchpad bug 1180513 in gnome-settings-daemon (Ubuntu) "lid close actions are ignored laptop always suspends" [Medium,Triaged] https://launchpad.net/bugs/1180513
[15:24] <pitti> I can backport the necessary changes, but want to avoid effort if we are going to update to 3.8 anyway
[15:52] <seb128> pitti, g-s-d/g-c-c are a bit tricky due to input methods/ibus and fallback mode drop in 3.8
[15:53] <seb128> pitti, we will eventually do it, but focus is on the phone and I'm not sure how much time we can spend sorting out g-s-d/g-c-c updates this cycle
[15:58] <pitti> seb128: ack, thanks
[16:22] <jbicha> software-center is pretty fragile here, by just clicking around I can get it to crash and it takes X down with it
[16:32] <desrt> jbicha: sounds like X is fragile, rather
[16:32] <seb128> jbicha, xorg going down is an xorg issue, you should report a bug with your Xorg.log
[16:33] <ogra_> just use Mir :P
[16:33] <desrt> ;)
[16:34]  * didrocks waves good evening
[16:34] <desrt> didrocks: ciao!
[16:34] <didrocks> desrt: see you tomorrow!