[04:50] hello [04:50] what is this crazy talk about 3.9.4 out already? [04:59] also, looks like 3.10 is slated for a late sept release. I wonder if that'll end up in 13.10 by default? [10:51] ricotz, hi [10:53] darkxst, hi [10:54] I was thinking to start upload some 3.9 bits to the ppa, what do you think? [10:54] darkxst, sounds fine [10:55] while there is finally a cogl release, it would be nice to transition to it immediately then [10:55] and enable the full wayland support with it [10:56] yeh that would be good [10:56] https://launchpad.net/~ricotz/+archive/unstable/+packages [10:56] dont install those packages like that ;) [10:56] there is a breaks missing which would prevent that [10:56] ok [10:57] ricotz, you added xwayland manually? [10:58] considering it hasnt been merged yet afaik? [10:58] yes [10:58] this is more for testing, the xorg-edgers package includes it too [10:58] there are still the ddx side patches needed [10:59] ok cool, too bad I am stuck on the binary blob here [10:59] yeah, intel is kind of the best to test it [10:59] could never get my second monitor to work on nouvaeu [10:59] my laptop has intel, buts its not really my dev playground. kind of needs to be stable ;) [11:01] darkxst, that is fine [11:01] maybe wayland works in vmware though? [11:02] hello everybody! I have a great problem with my vuze on ubuntu 13.04 : the window is not responding before I get the gnome 3.8 it was working perfectly, I am on vuze 5.0 is someone know what to do ? [11:02] darkxst, i guess it should [11:03] Rand_, you might be better trying a more generic channel such as #ubuntu for that. Vuze is not part of gnome [11:04] ricotz, I will try when I get a chance. [11:05] I do remember seeing mentions of wayland support in the changelogs along the way though [11:05] darkxst, it was quite in flux, but with the abi/api promise of wayland 1.1.91 it should calm down [11:05] only gtk builds the wayland backend [11:05] 3.9.8 require wayland 1.1.90 [11:06] to prepare the full support for mutter the support in cogl and clutter needs to be enabled too [11:06] I pretty sure I don't have any Qt apps (excluding ubuntu apps) [11:07] we have pretty much free reign on that this cycle though? assuming its actually ready [11:08] Jono has some idea of a Mir backend for gnome-shell, lol ;) [11:08] no idea where that will come from ! [11:09] huh? [11:09] i *really* doubt that [11:09] ricotz, yes me too [11:09] the needed changes for mutter are quite something [11:09] and no mir for gnome-shell, without support for mutter/cogl/clutter [11:10] and gtk, of course [11:10] yeh I know, its super complicated with just X and wayland [11:10] no way upstream will take a 3rd complication [11:10] absolutely [11:11] I think jono is just dreaming.... [11:11] because there is no way canonical would do it. and its well beyond us [11:13] let see what the future brings for mir [11:13] i hope fedora will pick up testing GNOME/wayland soon [11:14] or even debian [11:15] fedora should! its always broken anyways ;) [11:15] jfyi https://lists.launchpad.net/elementary-dev-community/msg02491.html [11:16] ricotz, that sounds almost exactly the same as the conversation I had with jono [11:17] darkxst, probably ;) [11:19] apparently there is some delusional idea that upstream might consider ubuntu flavours as different distros [11:20] darkxst, i hope they do in regards helping with wayland problems ;) [11:21] well ironically, they may well if all the flavours switch to wayland [11:21] is there an eta when mir lands in saucy? [11:21] (the package itself) [11:22] not entirely sure [11:22] currently its just Xmir [11:22] all input etc is still through X [11:22] yeah, i know [11:23] so really just a system compositor for rendering [11:23] i am just curious about the init changes when this happens [11:23] lightdm lauches u-s-c [11:24] you mean session-compositor? [11:24] yeh [11:24] they call it unity-system-compositor of course! [11:24] ok [11:24] so there shouldnt be any init changes provided you are using gdm or other dm [11:25] right [11:25] you can force fallback by patching a conf file [11:26] and I think there is also a lock file that is created after things fails, so lightdm doesnt bother trying again in case your system doesnt happen to work [11:32] anyway at the end of the day wayland is the future for gnome [11:33] and I am pretty sure we did bulk of work on landing the gnome 3.8 stack [11:34] yet they won't provide any help for example making gdm work under Xmir [12:26] ricotz, can you upload gtk 3.9.4? I will start uploading other packages then, when I get back from my adventures tomorrw [12:27] darkxst, you mean 3.9.8? [12:27] yeh that too [12:28] I have been running on jhbuild so far this cycle [12:28] it will break the unity menu stuff while there is no port of that patch [12:30] if i get to it everything will go into gnome3-staging/saucy first [12:30] ok sounds good [12:31] I mean it would be better we don;t break unity, but the people using staging probably don't care [12:34] darkxst, lars wasnt declined to work on porting the patch though if it is needed [12:41] ricotz, ok, that is good I guess [12:41] assuming wasnt == hasnt [13:49] hello friend [13:49] s === roasted_ is now known as roasted [14:42] darkxst: [17:28] darkxst: === roasted_ is now known as roasted [19:32] darkxst: I've been waiting here for a long time :( [19:32] darkxst: looks like you are not here [20:07] amjjawad: he has to sleep some time ;) === epzil0n is now known as Guest93057 [20:07] jbicha: thanks :) [20:07] I will catch up with him later then. He did not tell me what time he be online [23:58] darkxst: hibernate on lid close bug 1194328 [23:58] bug 1194328 in gnome-settings-daemon (Ubuntu) "Ubuntu 13.10 Close LID actions Ignored" [Undecided,Confirmed] https://launchpad.net/bugs/1194328 [23:59] (I don't use that feature but if you wanted somewhere to track that...)