[06:40] <darkxst> ricotz, hey, any ideas on this? https://launchpad.net/ubuntu/+source/gnome-control-center/1:3.16.3-0ubuntu2/+build/8215567/+files/buildlog_ubuntu-xenial-amd64.gnome-control-center_1%3A3.16.3-0ubuntu2_BUILDING.txt.gz
[06:40] <darkxst> I can't reproduce locally, with xenial-proposed sbuild ;(
[06:43] <ricotz> darkxst, vala needs to be MIRed -- https://launchpad.net/ubuntu/+source/vala/0.30.0-2
[06:47] <darkxst> ricotz, i see, didnt occur to me the sync would end up in universe, doh
[06:48] <ricotz> darkxst, but I guess it should fail more gracefully and saying so
[06:48] <ricotz> it got syned, but vala is a new source package again
[06:49] <darkxst> ricotz, yeh I realised that straight away once you mentioned it
[06:49] <ricotz> but afaics the component mismatch is the problem here
[06:50] <darkxst> ricotz, think can actually get g-c-c demoted to universe this cycle
[06:50] <darkxst> and just have the shared-data binary in main
[06:51] <ricotz> yeah, I thought it would be in universe already ;) which would have made my assumption wrong ;)
[06:52] <ricotz> oh, how I missed those 300mb daily package-updates :\
[06:52] <darkxst> there were a few users of the keybindings stuff from the -dev package, but I cleaned those up last cycle
[07:39] <ricotz> darkxst, hmm, gjs :\
[07:47] <ricotz> gjs contains API breaks and should have a package-name change
[08:45] <darkxst> ricotz, was there a new gjs release?
[08:46] <ricotz> http://metadata.ftp-master.debian.org/changelogs//main/g/gjs/gjs_1.44.0-1_changelog
[08:57] <darkxst> ricotz, yes, didnt realise upstream had done a new release
[08:58] <ricotz> https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1511253
[08:59] <ricotz> seems I ignored gjs for some time, I actually doubt that 1.40.0 is ABI-compatible with 1.43.3
[09:03] <darkxst> ricotz, that callargs stuff was, but there is something else in that LP diff
[09:05] <ricotz> the API change of gjs_define_interface_class is the most obvious one
[09:05] <ricotz> of course you can argue that maybe nothing is actually using it ;)
[09:10] <darkxst> indeed most projects don't hook that deep into gjs code
[09:12] <darkxst> I'd say probably bump the lib, but I don't have time to really look more tonight
[09:46] <j4s0nmchr1st0s> #qemu
[10:17] <darkxst> j4s0nmchr1st0s, you called me a clown, now your posting random hash tags, want a goodbye from this channel?
[10:18] <darkxst> I can make that happen ;)
[10:20] <darkxst> or better just play nice, calling the head of ubuntu-gnome a clown is just dumb!
[10:22] <j4s0nmchr1st0s> it is not so bad is it?
[10:22] <darkxst> j4s0nmchr1st0s, you dont speak english?
[10:22] <ricotz> darkxst, since you are still here ;), are there reports about gdm "hanging" after entering login?
[10:22] <darkxst> its pretty really bad
[10:23] <darkxst> ricotz, not heard of any
[10:23] <darkxst> odd report of hung spinner and then asks again for password
[10:23] <ricotz> darkxst, pressing ESC seems to resolve it and the login continues
[10:24] <darkxst> ricotz, no
[10:24] <darkxst> (not heard reports of that)
[10:24] <ricotz> the screen is completely empty e.g. nothing visible although there is still some interaction possible with panel and textbox
[10:25] <ricotz> empty = just the background
[10:25]  * ricotz is seeing this only on one machine
[10:26] <darkxst> maybe hardware specific? I have xenial, plus the ppas
[10:26] <darkxst> and nvidia blobs, login is fine here
[10:26] <ricotz> hmm, happens here on the nvidia-blob one
[10:27] <ricotz> 355.11
[10:27] <ricotz> seems not related to the kernel, happens with 4.2 stock and 4.3rc7
[10:27] <ricotz> bbl
[10:28] <darkxst> apparently I am still on 352.41
[10:28] <darkxst> ricotz, I will be gone for sure later
[10:29] <darkxst> have to pack for the weekend
[10:29] <darkxst> random climbing trip
[10:59] <ricotz> darkxst, have fun!
[14:21] <LinDol> ohoh
[14:21] <LinDol> i am making USB installing media > _<
[14:22] <LinDol> I am expecting to install Ubuntu GNOME 15.10 :)