[05:36] <larsu> bonjour!
[05:47] <pitti> Bonjour tout le monde !
[05:50] <larsu> hola pitti!
[06:02] <didrocks> good morning
[06:06] <larsu> hi didrocks!
[06:08] <didrocks> hey larsu!
[06:10] <pitti> bonjour didrocks!
[06:12] <didrocks> salut pitti !
[06:30] <pitti> didrocks: oh, display-managers test manages to shut down eth0 (I see a DHCPRELEASE in journal until ssh stops working)
[06:32]  * pitti files bug 1449380
[06:32] <didrocks> pitti: hum, can be "systemctl default"
[06:32] <pitti> yeah, I need to look at that more closely
[06:33] <didrocks> I didn't call isolate on purpose for this
[06:33] <didrocks> daemon-reload should be harmless
[06:39] <seb128> good morning desktopers, didrocks, pitti
[06:39] <pitti> bonjour seb128 !
[06:39] <didrocks> hey seb128!
[06:39] <seb128> wie gehts?
[06:42] <pitti> super, danke!
[06:42] <pitti> und Dir?
[06:51] <seb128> great, thanks ;-)
[07:20] <willcooke> *yawn*
[07:20] <willcooke> morning
[07:25] <didrocks> morning willcooke
[07:25] <willcooke> hey didrocks
[07:26] <seb128> hello willcooke
[07:26] <willcooke> morning seb128
[07:30] <willcooke> Hrm, looks like my issues with Chromium aren't isolated
[07:30] <willcooke> errors.u.c makes it clear :(
[07:32] <larsu> morning willcooke!
[07:38] <willcooke> hey larsu
[07:49] <willcooke> What do you think about having a weekly meeting this week?
[07:50] <willcooke> I mean, mostly it'll be "went to a spint"
[07:50] <larsu> what a coincidence. I went to a sprint, too!
[07:51] <willcooke> :D
[07:53] <seb128> willcooke, we would use it to summarize week/blueprints&co
[07:53] <seb128> but we can also skip if you prefer
[08:01] <willcooke> oh, so actually looks like I have a UOS meeting at 1630
[08:01] <willcooke> let me see what I can move
[08:02] <Laney> hello!
[08:03] <didrocks> morning Laney
[08:04] <willcooke> yo
[08:16] <larsu> Laney: morning! What exactly did you want me to test from your ppa? Did you disable o-s for gtk2?
[08:18] <Laney> no
[08:18] <Laney> not on purpose anyway
[08:18] <larsu> ah, sounded like it
[08:18] <Laney> go into gedit
[08:18] <Laney> and make it scroll
[08:19] <Laney> I get some weird grey area
[08:19] <larsu> the overshoot thing?
[08:20] <Laney> could be
[08:20] <larsu> hm I'm not seeing it in ambiance
[08:21] <Laney> in Adwaita I get a dashed line there
[08:21] <Laney> so it's probably saying that there is more content up here
[08:22] <larsu> right
[08:22] <larsu> is this with gtk 3.16?
[08:22] <Laney> ya, from the ppa
[08:22] <seb128> hey Laney, wie gehts?
[08:22] <Laney> hey seb128
[08:22] <Laney> doing good thanks!
[08:23] <Laney> we started to organise a protest ride last night ;-)
[08:23] <Laney> how are you? good rest of w.e.?
[08:23] <Laney> (we are bikeshedding the name of the ride atm)
[08:23] <pitti> hey Laney!
[08:24] <seb128> Laney, I'm good thanks, yeah, we had a good w.e in London, and it didn't rain after all :-)
[08:24] <Laney> \o/
[08:26] <Laney> hiya pitti
[08:28] <pitti> seb128: how did you like the Phantom?
[08:29] <pitti> err -- comment vous avez aimé l'opéra ? :-)
[08:29] <seb128> pitti, it was very nice, the scenery was excellent
[08:29] <pitti> "avez-vous", argh
[08:29] <seb128> :-)
[08:29] <seb128> c'était très bien !
[08:30]  * pitti aime la musique
[09:17] <pitti> didrocks: systemctl default is the same as systemctl isolate default.target, no? at least that seems to shut down everything which isn't in graphical.target, like apparently the ifup@s; I'll have a closer look at it, don't worry (just keeping you posted)
[09:18] <didrocks> pitti: yeah, it's a shortcut to systemctl <something> default.target. Can be isolate…
[09:18] <didrocks> and so, this would make sense
[09:34] <Laney> larsu: do you remember the bug # for inverted horizontal scrolling?
[09:34] <Laney> the lp on
[09:34] <Laney> e
[09:35] <Laney> oh, i found it, the power of asking someone else
[09:35] <larsu> :)
[09:35] <pitti> didrocks: ah, interesting; setting IgnoreOnIsolate=yes for ifup@.service works; I wonder if that's actually desirable (not shutting down interfaces on isolate), or whether we should just do this for these tests
[09:36] <pitti> it might break "isolate rescue.target" or whatever
[09:37] <didrocks> pitti: how would it break it? do you expect the ifup@.service being able to do some loop-hell and then, blocking our rescue?
[09:37] <didrocks> pitti: or we might only set that during autopkgtests…
[09:37] <pitti> didrocks: I mean, don't we want it to actually stop on isolating rescue or some other early/late/minimal target?
[09:39] <didrocks> pitti: can we add conflicts="generic@.service"? I don't know if that works
[09:39] <pitti> didrocks: add where? what's "generic"?
[09:40] <didrocks> like in rescue.target Conflicts=ifup@.service
[09:40] <didrocks> and that would conflict to all ifup instances
[09:40] <didrocks> (I'm unsure this is supported)
[09:42] <pitti> didrocks: maybe rather PartOf=network.target, and whenever that shuts down, ifup@ also shuts down?
[09:42] <pitti> ah, due to our dbus shutdown hack, isolating rescue doesn't work anyway ATM
[09:45] <didrocks> urgh
[09:47] <pitti> didrocks: so, PartOf=networking.target and IgnoreOnIsolate=yes actually behave quite well
[09:50] <didrocks> yeah, sounds logical, it will still be activated in rescue though
[09:50] <didrocks> or we should conflicts
[09:51] <pitti> didrocks: rescue is fine
[09:52] <pitti> didrocks: I guess I meant emergency.target, or whichever target does *not* want (or shuts down) network-online.target and similar
[13:14] <pitti> Laney: any luck with sbuild and the PPA?
[13:50] <Laney> pitti: oh yes, let's try
[13:51] <seb128> does anyone has a nautilus 3.16 version to test something?
[13:56] <pitti> seb128: I can build it from the upstream tarball, if that helps:
[13:56] <pitti> ?
[13:56] <seb128> pitti, I can do that too, but I guess it needs a new GTK, etc
[13:56] <pitti> ah, right
[13:56] <seb128> don't bother, it's not important, it was to confirm if https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448474 is still an issue
[13:57] <pitti> certainly an issue in vivid, but only in Ctrl+1 (list mode)
[13:57] <pitti> in grid mode the names are just wrapped
[13:58] <ricotz> seb128, hi, this is still an issue
[13:59] <seb128> ricotz, hey, thanks
[13:59] <seb128> pitti, right, I'm on vivid, I confirmed it's an issue there, and I confirmed it's not in nautilus 3.10 (I had debs unpacked to test), just wanted confirmation of current upstream before sending to b.g.o
[13:59] <seb128> thanks
[14:02] <Laney> pitti: still a bug - let me try to make a cloud instance which gets it
[14:04] <seb128> Laney, larsu, what do you think about bug #1448969? (basically suggesting to backport https://git.gnome.org/browse/gtk+/commit/?id=83e104b093f49ea452c25c370ce85cd247be4614 to trusty)
[14:05] <larsu> seb128: I already looked into it but haven't confirmed the fix yet (will do in a bit)
[14:06] <seb128> larsu, k, thanks
[14:06] <larsu> seb128: it's fixed as of 3.14, but broken on the lts
[14:06] <seb128> right
[14:06] <seb128> larsu, also bug #1448407 ... could you have a look? unsure if that's a theme issue
[14:07] <seb128> larsu, basically if you dnd to a folder with a > 100% zoom level, the destination folder icon switch to an unzoomed one
[14:07] <larsu> interesting
[14:07] <larsu> I'll have a look
[14:08] <seb128> thanks
[14:11] <pitti> Laney: meh, would have been too easy :)
[14:18] <qengho> willcooke: when you get the watchdog timeout crash, does chromium, or anything else, appear to be hung or unresponsive? I am starting to think the hung predicate is wrong altogether.
[14:19] <willcooke> qengho, hiya
[14:20] <willcooke> qengho, I'm not 100% certain, I can reboot and see what happens - but not quite yet - I'll give it a go later
[14:42] <ochosi> larsu: hey! since 15.10 is opening up, wanna do something wrt indicators and symbolic icons?
[14:44] <seb128> Sweet5hark, hey, did you see https://errors.ubuntu.com/problem/8311cfa576acddfbbb5f1e7a01d4055d6b0e123a ?
[14:45] <Sweet5hark> seb128: yes, saw it, havent digged too deep into it, there is no good reproduction descriptions yet, it seems ...
[14:46] <seb128> Sweet5hark, k, can you triage the bug? it's number 10 on the daily e.u.c report for vivid
[14:50] <Sweet5hark> seb128: the only one there says "crashed on closing the document" and the stack trace suggests this being about StarBasic macros in a document -- so might be somewhat tricky. That said: it is a regression vs. 4.3 (which should help somewhat), but without a reproduction document, its still fly by instrument flight (aka guesswork unless I manage to reproduce myself).
[14:51] <larsu> ochosi: I'll try to get to it, but it's not highest priority
[14:52] <seb128> Sweet5hark, right
[14:52] <ochosi> larsu: sure, i was also wondering whether you wanted/needed help with that, since we discussed it during 15.04 at some point. i guess a list of indicators that would need patches would also be helpful
[14:53] <larsu> ochosi: right. there's also an open question about whether we should merge icon themes at some point. everything's all over the place now
[14:54] <ochosi> i understand, actually moving to symbolic icons would enable that process
[14:54] <ochosi> or at least make it easier
[14:54] <ochosi> but yeah, all in all the two things could be done independently
[14:55] <ochosi> with the icon theme, i guess moving to the icons from mobile would be the ideal way to go
[14:55] <qengho> Since I didn't come to the sprint, my progress report isn't "went to a sprint".
[14:55] <qengho> * DONE: Cr 42.0.2311.90 is tested, and almost ready.
[14:55] <qengho> * IN-PROGRESS: It's delayed a few days because I'm adding some start-up tests and recommendations to update the Flash player packages. Doing that right is hard. Almost happy with it.
[14:55] <qengho> * IN-PROGRESS: Mir support again.
[14:55] <qengho> * TO-DO: GPU watchdog hangs. Extended timeout didn't help much last time.
[14:55] <qengho> So, there you go. Meeting of one.
[14:59] <larsu> ochosi: it's not clear yet if we want to move to the mobile icons
[14:59] <ochosi> k
[14:59] <larsu> I think I'll wait for that decision before starting to work on it
[15:02] <seb128> qengho, thanks for the update :-)
[15:05] <willcooke> thx qengho
[15:07] <Laney> pitti: okay, I got into a similar but not identical state on this vm
[15:07] <Laney> here it rips the mount out before sbuild can even get going
[15:08] <Laney> should be the same bug
[15:09] <Laney> ssh ubuntu@10.55.32.96 & poke around with the 'vivid' container which has a 'vivid' schroot inside
[15:12] <pitti> Laney: cheers!
[15:12]  * qengho boggles at https://bugs.launchpad.net/bugs/1449607
[15:12] <qengho> "acceleration"
[15:29]  * desrt can feel it
[15:29] <desrt> t -30
[15:29] <desrt> 20
[15:29] <seb128> desrt, °C?
[15:29] <seb128> winter is back?
[15:29] <desrt> 10
[15:29] <willcooke> desrt, check your email :)
[15:29] <desrt> oh
[15:29] <desrt> :(
[15:30] <willcooke> It seems to have been sent twice as well
[15:30] <willcooke> so, I don't know, sucks to be you
[15:30] <desrt> got it :)
[15:30] <Laney> maybe he'll do another fake meeting
[15:30] <willcooke> rather, sucks to be your mail client because you dont love it
[15:30] <desrt> sure glad i didn't get to 0
[15:30] <willcooke> lolz
[15:30] <desrt> that would have looked ridiculous!
[15:30] <willcooke> :D
[15:30] <seb128> :-)
[17:40] <seb128> Laney, larsu, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448388 is by design right?
[18:35] <larsu> seb128: because header bars I guess?!
[19:07] <willcooke> g'night all