[04:36] <pitti> Good morning
[05:39] <RAOF> Hey pitti!@
[05:39] <pitti> hey RAOF, how are you?
[05:40] <RAOF> Pretty good, yourself.
[05:41] <RAOF> ?
[05:45] <pitti> RAOF: very well, thanks! looking forward to a long weekend (national holiday tomorrow, took off Friday)
[05:45] <RAOF> Aww, yeah!
[05:53] <RAOF> Hm.
[05:53] <RAOF> When are we going to get that Qt patch that makes it not crash when you plug a monitor in? :)
[06:29] <ricotz> Sweet5hark1, seb128, hi, jfyi, there is no sign of libreoffice 4.4.3 in vivid
[06:46] <seb128> ricotz, ? https://launchpad.net/ubuntu/vivid/+queue?queue_state=1&queue_text=libreoffice seems fine to me
[06:51] <ricotz> seb128, ah, didn't expect it to be still in the queue, sorry
[06:56] <larsu> mitya57: I don't care if you guys rebuild with every release. It seems wrong to me :)
[06:56] <larsu> mitya57: but Mirv opened a bug about it...
[06:56] <larsu> good morning!
[06:57] <mitya57> larsu, Actually we had a long discussion with lisandro and svuorela yesterday, and it looks like it *is* possible to fix our script. Someone just needs to write a regex for it :)
[06:58] <larsu> mitya57: cool. Err....... have fun?!
[06:58] <larsu> :P
[06:59] <mitya57> Will try to do it in the evening :)
[07:20]  * willcooke yawns
[07:20] <willcooke> morning
[07:20] <RAOF> Oh, yeah.
[07:20] <RAOF> Overnight for you :P
[07:21] <willcooke> :D
[07:21] <willcooke> late finish and early start today
[07:21] <willcooke> yay
[07:22] <RAOF> Winner!
[07:23] <seb128> hey willcooke robru
[07:23] <seb128> ups
[07:23] <seb128> hey willcooke RAOF
[07:24] <willcooke> hey seb128
[07:24] <willcooke> RAOF, do you use a standing desk?
[07:24] <RAOF> willcooke: I do, yes.
[07:24] <willcooke> RAOF, like all the time, even for writing code?  Are you happy with how you get on with it?  (I assume yes, otherwise why would you)
[07:25] <RAOF> Yes, except when I wander around with my laptop.
[07:25] <willcooke> I'm toying with the idea of having a standing area so I don;t just sit on my arse all day everyday
[07:28] <RAOF> It's particularly useful when you do your back, as I did on the weekend :(
[07:28] <willcooke> heh
[07:29] <larsu> willcooke: do it!
[07:30]  * larsu is standing right now
[07:30] <RAOF> But it's pretty easy, as my #warthogs pic should demonstrate :)
[07:31] <RAOF> I actually dislike the sitting down at sprints; after not too long you can go the whole day standing without really noticing it.
[07:44] <willcooke> I might give it a go for a few days and see what happens, but I need a proper height desk first
[07:45] <RAOF> One can easily be jerry-rigged by means of stacking.
[07:45] <willcooke> heh, I'll unpack the book shelf
[07:52] <mitya57> larsu, Mirv: so far all my attempts to write a regex that will take (a) namespaces and (b) virtual methods into account have failed
[07:58] <larsu> ah, the joys of c++
[07:58] <larsu> sorry :/
[08:05] <Laney> ahoy
[08:06] <larsu> morning Laney!
[08:06] <Laney> hey larsu
[08:07] <Laney> what's up homie
[08:07] <seb128> hey Laney didrocks
[08:07] <seb128> u.k wakes up :-)
[08:07] <Laney> team uk
[08:10] <Laney> hmm, seems I broke something, desktop-next didn't try to build
[08:12] <Mirv> mitya57: larsu: from my point of view it's ok to recompile gsettings-qt with it's Qt release. as a general trend, the private headers users just should go only downwards so I filed bugs against packages that seemed like they wouldn't really require them
[08:12] <seb128> Laney, why did you tweak?
[08:13] <Laney> some config changes were missed
[08:13] <Mirv> mitya57: larsu: gsettings-qt sees so little changes that it's not practical problem for Qt preparation, unlike with other packages (if I'm testing, every time a package needing a rebuild is changed, I need to rebuild again and the preparation PPA might be broken for a while)
[08:13] <larsu> Mirv: personally I think it's ridiculous that we need to recompile when it's only using public API and ABI
[08:14] <larsu> Mirv: no matter how little work it is
[08:14] <mitya57> Actually I am right now trying to rewrite the script using c++filt
[08:14] <mitya57> Let's see if I succeed :)
[08:14] <Mirv> larsu: sure, but there's a limit how much effort should be made to the symbol parsing. mitya57 seems having fun with the challenge though :)
[08:15] <mitya57> :-)
[08:15] <larsu> mitya57: how do you generate the symbols? nm(1) can demangle as well
[08:15] <larsu> ha, as long as it's fun I'm all for it!
[08:15] <mitya57> The symbols are generated by dpkg-gensymbols
[08:16] <larsu> ah, that uses c++filt as well
[08:31] <seb128> hum
[08:31] <tjaalton> no robert_ancell?
[08:31] <seb128> is anybody else having issues with gnome-keyring ssh/gpg in wily?
[08:32] <seb128> tjaalton, no, it's after his work hours
[08:32] <tjaalton> ok
[08:32] <tjaalton> xmir bomb.. :)
[08:32] <seb128> why did you need him?
[08:32] <tjaalton> gues it's not going upstream
[08:32] <tjaalton> +s
[08:32] <seb128> is there an issue with his upload?
[08:33] <tjaalton> no, it's fine
[08:33] <tjaalton> just need to import it to git, and there was some -xmir cruft left behind
[08:34] <seb128> k
[08:35] <RAOF> tjaalton: Oh, congratulations on being tagged with primary X maintainership :)
[08:35] <seb128> $ initctl -v start gnome-keyring-ssh
[08:35] <seb128> gnome-keyring-ssh stop/waiting
[08:35] <seb128> hummm
[08:36] <seb128> xsession-init stop/waiting
[08:36] <seb128> I guess that's the issue
[08:36] <tjaalton> RAOF: gee, thx.. ;)
[08:37] <willcooke> tjaalton, we are *extremely* grateful for you help and work on X.org
[08:37] <willcooke> thank you!
[08:37] <tjaalton> willcooke: well I haven't done anything yet
[08:38] <tjaalton> too busy with skylake in the kernel land
[08:38] <seb128> Laney, is xsession-init "started" for you?
[08:38] <mitya57> larsu, Looks like using c++filt will make the script *much* slower (Because we can't just fix all files with a single sed call, but we need to iterate over lines manually)
[08:38] <willcooke> tjaalton, we're still happy that you are able to help with it though :)
[08:38] <tjaalton> but after holidays and before FF there should be a refresh of the usual bits
[08:39] <willcooke> thanks
[08:39] <mitya57> (Rewriting the script in some real programming language may be an option, but I don't want to do that now :))
[08:40] <Laney> seb128: no, the script should just exec and finish, no?
[08:40] <seb128> Laney, k, just trying to figure out why gnome-keyring/-ssh is not active for me
[08:40] <seb128> it started earlier this week I think
[08:42] <larsu> seb128: doesn't start for me either
[08:44] <seb128> Laney, is it working for you?
[08:44] <Laney> stop/waiting
[08:44] <Laney> I can't confirm if it worked before though
[08:44] <larsu> mitya57: c++filt can filter a whole file from stdin, no?
[08:44] <Laney> it's the same on a vivid iso
[08:45] <seb128> Laney, k, well before something were asking for my ssh credential in a nice UI and storing them :p
[08:45] <seb128> that stopped happening for me in wily
[08:46] <Laney> does "start gnome-keyring-ssh" start it?
[08:47] <mitya57> larsu, It can, but I want to check output of c++filt on each line and then write the *original* (mangled) line back, appending an " 1" if needed
[08:47] <seb128> $ start gnome-keyring-ssh
[08:47] <seb128> gnome-keyring-ssh stop/waiting
[08:47] <seb128> no
[08:47] <seb128> not in ps list
[08:48] <larsu> mitya57: oh... what does the 1 mean?
[08:48] <seb128> tjaalton, oh, a robert_ancell, grab him!
[08:48] <seb128> robert_ancell, hey
[08:49] <robert_ancell> seb128, oh shit. I left xchat open :)
[08:49] <larsu> robert_ancell: hi! Good evening :)
[08:49] <seb128> lol
[08:49] <tjaalton> robert_ancell: heh, just pulled xserver -0u4 diff to git
[08:50] <robert_ancell> tjaalton, oh good. I thought it was something more serious :)
[08:50] <tjaalton> robert_ancell: well, I was wondering if there are plans to try get it upstream?
[08:50] <robert_ancell> tjaalton, where is the git branch?
[08:50] <tjaalton> pkg-xorg on git.debian.org
[08:50] <robert_ancell> tjaalton, for both Debian and Ubuntu?
[08:50] <tjaalton> but could also migrate it to lp at some point
[08:51] <tjaalton> yes
[08:51] <robert_ancell> tjaalton, yes, I'm working on it. I've cleaned the patches up a bit. The main bit I'm working on is how to make the DRI2 code shared.
[08:51] <tjaalton> ok cool
[08:51] <robert_ancell> I had a good idea at EOD which I think can now make it wokr
[09:14] <Laney> ok think I fixed the config
[09:17] <seb128> Laney, the iso builder one?
[09:18] <Laney> ya
[09:19] <Laney> there's a file that maps from cdimage outputs to launchpad builds
[09:19] <Laney> I messed up the fields in it
[09:21] <Laney> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-desktop-next all building
[09:21] <Laney> (all doomed to fail, of course)
[09:22]  * Laney hopes people aren't too irritated by the email spam
[09:22] <Laney> every failed test generates an email to the subscribers
[09:23] <seb128> Laney, where is that map file and why is it needed? just curious and can be handy one day, who knows ;-)
[09:24] <Laney> it's on a branch on nusakan (the cdimage build server)
[09:24] <seb128> k
[09:24] <seb128> I'm not enough into that world to understand what's going on I think :-/
[09:24] <seb128> thanks for fixing it though!
[09:25] <Laney> I was getting output like this: http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-desktop-next/wily/daily-preinstalled-20150603.1.log
[09:25] <Laney> those are names of the old style cdimage buildds
[09:25] <Laney> dedicated machines just for image builds
[09:25] <Laney> which indicated that it wasn't trying to use LP to build them
[09:26] <seb128> I see
[09:26] <Laney> some reading of code later and I found that config file which indeed was missing entries for desktop-next
[09:26] <Laney> code -> lp:ubuntu-cdimage
[09:26] <seb128> http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/revision/1520
[09:26] <seb128> I see :-)
[09:27] <Laney> a similar private one
[09:27] <Laney> that one was also borked
[09:27] <seb128> k
[09:27] <Laney> I think we could get rid of the -system-image bit for desktop-next btw
[09:27] <seb128> Laney, do you know if we have recommends enabled on that iso/where to check?
[09:28] <Laney> I think they have it for core because there was already something called ubuntu-core before
[09:28] <Laney> but for us there is only one desktop-next
[09:28] <seb128> oh? how?
[09:28] <Laney> livecd-rootfs -> delete all of the SUBPROJECT stuff for desktop-next
[09:28] <seb128> ah, I see what you mean
[09:29] <seb128> I though you were speaking about the " system-image-snappy-common : Conflicts: system-image-common but 3.0-0ubuntu2 is to be installed" issue
[09:29] <Laney> nop
[09:29] <seb128> do you know for the recommends?
[09:30] <Laney> yep
[09:30] <Laney> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.wily/view/head:/touch
[09:31] <Laney>  * Feature: no-follow-recommends
[09:31] <Laney> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.wily/view/head:/desktop
[09:31] <Laney> doesn't have it
[09:31] <Laney> (but touch-core does)
[09:31] <seb128> we inherit from core so have those disabled?
[09:32] <Laney> I think it means that the packages in core shouldn't have their recommends but the ones in desktop will
[09:32] <Laney> however there's also some config in livecd-rootfs to disable it which we have for touch but do not have for desktop-next
[09:32] <Laney> so I'm not actually sure
[09:33] <seb128> k
[09:33] <seb128> so need to lower that to a suggests I gues
[09:33] <seb128> s
[09:33] <Laney> the seeds are used to generate the Task: fields in the archive
[09:33] <Laney> so maybe the feature: only has an effect there
[09:38] <Laney> suggests> yeah I think so
[09:38] <seb128> Laney, thanks
[09:38] <Laney> if it's a recommends in 'desktop' it will get followed by germinate and then passed directly to apt-get
[09:38] <Laney> if in touch-core then recommends will be ok
[09:38] <Laney> (didn't check)
[09:39] <seb128> it's in desktop
[09:39] <seb128> ubuntu-system-settings
[09:39] <Laney> k
[10:28] <darkxst> Laney when are you planning on uploading gtk 3.16? how soon?
[10:28] <Laney> 10 minutes?
[10:28] <Laney> :)
[10:31] <larsu> \o/
[10:31] <darkxst> ok, but can you block it in proposed until we can get the gnome-shell and friends uploaded?
[10:31] <darkxst> or just breaks gnome-shell < 3.16
[10:32] <Laney> how long are you going to be?
[10:33] <darkxst> I can probably get mutter and gnome-shell done this evening
[10:33] <Laney> ok, will add a breaks
[10:34] <Laney> just for you
[10:34] <Laney> ♥
[10:39] <Laney> can't find the box that contains my flat pedals
[10:39] <Laney> seems to have gone missing in the house move
[10:39]  * Laney grr
[10:46] <darkxst> Laney, thanks, hopefully it doesnt go much deeper, I know gnome-session needs updatings, but that should mainly affect gdm I think
[12:02]  * Laney makes larsu happy
[12:02] <seb128> oh?
[12:02] <larsu> oh!
[12:02] <larsu> gtk?
[12:02] <Laney> almost
[12:03] <Laney> check your lp emails
[12:03] <larsu> already approving
[12:03] <larsu> well, reading, really
[12:04]  * larsu dances while reading
[12:05] <seb128> lol
[12:05] <seb128> be ready to get more work :-)
[12:05] <seb128> I should update to that version and start listing the issues I see :p
[12:06]  * larsu unsubscribes from bugs
[12:07] <seb128> roh
[12:07]  * seb128 goes for IRC nagging instead
[12:10] <larsu> hehe
[12:15] <larsu> Laney: the block starting at line 1021 in the diff should stay, no?
[12:15] <larsu> Laney: IGNORE ME
[12:15] <Laney> lemme ... ok!
[12:15] <larsu> reindent moved the block down
[12:15] <Laney> it's possible I made a mistake
[12:15] <Laney> when deleting lots of things like that it's easy to accidentally kill the wrong thing
[12:16] <larsu> ya
[12:16] <Laney> especially when some are ifndef and some are ifdef
[12:17] <larsu> Laney: did you autoindent or something? I wonder if the indent style was inconsistent before or your editor messed it up
[12:19] <Laney> it's possible,
[12:20] <Laney> I probably reindented using "=" when deleting blocks
[12:20] <Laney> might have forgotten to set stuff
[12:20] <larsu> Laney: cino=(0,{s,>2s,e-s,^-1s,n-s,t0
[12:21] <larsu> braces are in the wrong column
[12:21] <larsu> and that messes up the (otherwise awesome) diff in that one place
[12:21] <Laney> whatever does that mean
[12:21] <larsu> gnu style please
[12:21] <larsu> is what that means in vi-speak
[12:21] <Laney> is cino some vim thing?
[12:22] <Laney> I don't know about it
[12:22] <larsu> cinoptions
[12:22] <larsu> indentation options for c
[12:22] <larsu> it's ... complicated
[12:23] <larsu> Laney: I can reindent and send you a branch
[12:23] <Laney> might be easier
[12:27] <larsu> hm, some of that was wrong indentation in the first place
[12:29] <Laney> lunch, will look when I'm back
[12:42] <darkxst> Laney, I've merged mutter and gnome-shell (should be ready to upload), will require gsettings-desktop-schemas update first though
[12:45] <darkxst> Laney, I wont have time to look at that tonight, maybe Noskcaj can in the morning if you don't get to it first
[13:43] <Laney> darkxst: ok, I probably can do if it's simple
[14:21] <seb128> Laney, larsu, can you look at https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1448969/comments/18 ?
[14:22] <Laney> I got an email about it
[14:25] <Laney> they mostly don't have very much information
[14:25] <Laney> and then there are things like https://jenkins.qa.ubuntu.com/job/trusty-adt-update-manager/lastBuild/ARCH=amd64,label=adt/console
[14:36] <larsu> weird stuff :/
[14:36] <larsu> that upload wasn't very intrusive, was it?
[14:39] <Laney> we aren't starting from a clean baseline
[14:39] <Laney> nor is the infrastructure particularly reliable
[14:39] <Laney> soooooooooo it's likely to be false positives
[14:40]  * larsu nods
[16:43] <seb128> Laney, larsu, soooo
[16:44] <seb128> I upgraded to new gtk&co from the ppa ww
[16:44] <seb128> where are my scrollbars?!
[16:57] <mitya57> larsu: (sorry, was away) every symbols file has something like this in the header
[16:57] <mitya57> libQt5Concurrent.so.5 libqt5concurrent5 #MINVER#
[16:57] <mitya57> | libqt5concurrent5 #MINVER#, qtbase-abi-5-4-1
[16:57] <mitya57> the "1" means that dpkg should look at the line #1 and add a dependency not only on library package, but also on abi package
[16:59] <mitya57> larsu: By the way you can override the generated shlibs:Depends in your rules file, just after a dh_shlibdeps call
[17:00] <mitya57> And it looks like nobody wants to make the script slower (and more hackish), so it's unlikely that we'll be able to change the behavior
[17:38] <willcooke> g'night
[18:10] <andyrock> seb128: ping
[18:11] <seb128> hey andyrock
[18:12] <andyrock> seb128: hey do you happen to know who takes care of killing all applications on shutdown/logout?
[18:12] <andyrock> upstart/systemd or gnome-session?
[18:12] <desrt> andyrock: there are two mechanisms
[18:12] <desrt> most things in the session are connected either to x11 or dbus
[18:12] <desrt> so when the session bus or x server goes away they will die
[18:12] <desrt> but for lack of those, nothing explicitly goes around killing stuff
[18:12] <desrt> this is how screen sessions can stay alive, for example
[18:13] <andyrock> desrt: i'm looking for a way to make sure unity is the last thing to be killed
[18:13] <desrt> systemd causes some problems here because it _does_ kill stuff, according to cgroup membership... so using screen with systemd can be problematic
[18:13] <andyrock> at least before all the normal windows
[18:14] <desrt> andyrock: that's not really possible unless you start surfing the _NET_WM_PID properties on windows
[18:14] <desrt> various SM protocols do attempt to solve this, but of course that is opt-in
[18:15] <andyrock> the problem is that unity lockscreen allows to shutdown the pc
[18:15] <desrt> interesting.  that's another story.
[18:15] <desrt> on shutdown everything really does get signal 15 (then 9)
[18:15] <andyrock> and during shutdown+lockscreen would be nice that the lockscreen would be the last thing to go away
[18:15] <desrt> and that is upstart/systemd
[18:16] <desrt> i think upstart had a mechanism to prevent processes from getting the axe during that process
[18:16] <desrt> not sure about systemd
[18:17] <andyrock> axe?
[18:17] <desrt> getting the axe = being killed, i mean
[18:31] <andyrock> https://www.irccloud.com/pastebin/r5OMPlcD/
[18:31] <andyrock> desrt: ^^^
[18:31] <andyrock> looks like is just random