[06:58] <didrocks> good morning
[07:00] <darkxst> hey didrocks
[07:00] <didrocks> hey darkxst
[07:01] <darkxst> didrocks, curious what happens to all our MIR's now?
[07:03] <didrocks> darkxst: don't have time to look retrospectively to old ones, I would say, we need the discussion that started on grilo to end up with strong resolutions first, and then, if someone has time, they can go back in time
[07:04] <darkxst> didrocks, was talking more future, than resprospectively
[07:05] <didrocks> darkxst: you need to find some team at canonical wanted to support the source I guess
[07:05] <didrocks> darkxst: if you are concerned by this, I would say raise it to the technical board
[07:07] <darkxst> didrocks, its a little concerning, some of it is due to -desktop team still holding randsom over g-s-d/g-c-c, but the rest comes from the large overlap with Ubuntu
[07:08] <darkxst> and many times in the overlap case, Canonical don't want the new features that pull in the new deps, or they want to wait etc
[07:08] <darkxst> (Canonical teams)
[07:08] <didrocks> darkxst: yeah, nothing I can really do here, so when you get the issue and you are stuck, feel free to raise it there I guess
[07:11] <darkxst> didrocks, I wasnt expecting you to fix it, but sooner or later it will have to come that that (TB)
[07:22] <seb128> good morning desktopers
[07:22] <didrocks> hey seb128
[07:22] <seb128> TB ... not sure what they can do there?
[07:22] <seb128> they can't decide that packages should be supported even if there is nobody to support those
[07:27] <mlankhorst> morning
[07:28] <didrocks> morning mlankhorst
[07:36] <seb128> hey mlankhorst
[07:36] <larsu> good morning
[08:24] <darkxst> seb128, except there are teams to support them, just not Canonical teams, so either thats a technical issue that the archive structure is insufficient, or its a political issue
[08:25] <darkxst> unless support is meant to mean some bespoke custom development on demand type things
[08:28] <seb128> darkxst, the issue is also to know that if there is a security problem in one of those packages in 3 years there is somebody to deal with it
[08:29] <seb128> darkxst, or there is no garanty that volunteers are still going to be around or wanting to resolve the issues in 3 years
[08:30] <seb128> so I don't think it's a Canonical or not, just need to have a solid reference which can be trusted
[08:33] <seb128> sorry, user switching screwed my session :-/
[08:34] <darkxst> and what make a solid reference?
[08:35] <seb128> dunno, if you were in charge, what would make you trust somebody to still be around in 3 years?
[08:35] <seb128> I guess it mostly mean having a commercial backing behind
[08:36] <seb128> or a group solid enough that you trust them to not vanish easily
[08:36] <seb128> like Debian
[08:36] <seb128> well, those are in nowhere official statements
[08:36] <seb128> just my view on the issue
[08:37] <darkxst> seb128, IT companys come and go like the wind
[08:37] <seb128> not all
[08:37] <seb128> I'm ready to bet my money that microsoft, apple and google are still there in 3 years
[08:37] <darkxst> and all of the packages we have MIR'd are well maintained in Debian
[08:38] <seb128> well, maybe that has to be enough
[08:38] <seb128> as said I'm just doing loud thinking there, those are not official statement
[08:39] <seb128> the current archive layout is suboptimal
[08:39] <seb128> shame that the archive re-org was never fully done
[08:39] <darkxst> seb128, sure the big boys will be around, will canonical be?
[08:39] <seb128> the idea was to be able to tag packages as supported without having to rely on the main/universe split
[08:39] <seb128> darkxst, not sure, but that's not really revelant to the discussion
[08:40] <seb128> we are talking about how Canonical hold to its engagement to maintain those packages and deal with security issues&co
[08:40] <darkxst> seb128, just saying IMO commercial backing doesnt provide a huge guarantee in itself
[08:40] <seb128> if Canonical is not sure anymore the question of how they provide their support vanishes iwth it
[08:41] <seb128> not sure->not there
[08:41] <seb128> right
[08:41] <seb128> so you argue that support should be provided only for things Canonical is ready to support itself
[08:41] <seb128> and not trust anyone else, including other IT companies
[08:41] <seb128> which is a fair position
[08:42] <darkxst> seb128, no I argue, there needs to be a way for this to work, for the community flavours
[08:42] <seb128> "this" being?
[08:43] <seb128> you can't force Canonical to provide free support for things you need but Canonical has no direct interest in
[08:44] <darkxst> we don't even want to do that, but the archive structure seems to dictate it
[08:45] <seb128> well, there are solutions
[08:45] <seb128> including finishing the archive reorg
[08:45] <seb128> or moving sources to universe
[08:46] <seb128> we could also duplicate sources if really needed
[08:46] <seb128> like have a nautilus in main and nautilus-tracker in universe
[08:46] <seb128> in practice there is no real problem so far though
[08:47] <seb128> Canonical teams have been happily taking over some extra packages in those cases to try to accomodate for others
[08:47] <seb128> like desktop team subscribed to tracker and grilo
[08:47] <willcooke> morning desktoppers
[08:47] <seb128> hey willcooke, how is grey London today?
[08:49] <darkxst> seb128, yes for the couple of cases that were bought up
[08:49] <didrocks> morning willcooke
[08:49] <seb128> darkxst, so in practice there is no real issue?
[08:50] <darkxst> seb128, if desktop team, takes all our MIR requests then no
[08:51] <darkxst> you probably want gom anyway eventually (that will be next up I think)
[08:52] <darkxst> next MIR
[08:54] <seb128> what is gom doing?
[08:54] <seb128> "GObject Data Mapper"
[08:54] <seb128> k
[08:55] <didrocks> seb128: it's like the django model, you write classes and it's translated into sql queries
[08:56] <didrocks> seeing the number of bugs/issues that I heard about it, not sure it suits main though
[08:58] <darkxst> didrocks, its quite new still
[08:59] <didrocks> yeah, that's the reason why it's maybe too new to be in main
[09:00]  * willcooke curses the wifi
[09:01] <darkxst> didrocks, I agree its not ready, but it will need to be at some point
[09:02] <didrocks> yeah, just don't feed the MIR before it is :)
[09:02] <didrocks> file*
[09:06] <darkxst> didrocks, have I ever filed any unreasonable MIR's? I don't think so
[09:06] <didrocks> darkxst: no, but when you were telling "gom will be next up", I started to be afraid that you were referring for something like "soon"
[09:09] <Laney> grr
[09:09] <darkxst> didrocks, I did not say soon
[09:09] <Laney> no network on resume, as usual
[09:09] <Laney> restart network manager, system hangs
[09:09] <Laney> #fail
[09:10] <didrocks> Laney: did you try with upstart?
[09:10] <didrocks> at least, to get systemd out of the loop
[09:10] <Laney> that was upsstart
[09:11] <didrocks> ah
[09:11] <didrocks> so, on both? seems networkish managerish or rfkillish/hardwarish
[09:12] <darkxst> didrocks, atleast for now, we have got though the backlog of MIR's for 3.12/14
[09:12] <darkxst> grilo/plugins is planning on using gom, not sure they have switched yet though
[09:13] <darkxst> (on a hard-dep basis)
[09:13] <didrocks> doesn't seem yet from git master
[09:16] <Laney> it will do, which will be an improvement imho
[09:16] <Laney> some of the current direct interaction with sqlite is a bit shonky
[09:18] <darkxst> Laney, then again some of sparql also plays up with sqlite at times
[09:19] <darkxst> but it should be much easier for a higher level framework to write valid SQL you would think
[09:38]  * Laney looks at didrocks 
[09:40] <Laney> seems to me as if you are in https://launchpad.net/~ubuntu-test-case-dev ... want to review that machine-id test fix? :)
[09:42] <didrocks> Laney: pfff, I'm in as a *side effect* ;)
[09:43] <didrocks> joke apart, I think the QA team should review the tests (even if this seems to be trivial), I'm happy to do it as a fallback if no-one is available though
[09:43] <Laney> tried pinging this cihelp thing, no reply yet
[09:43] <darkxst> Laney, I messed your comment of the gnome-contacts FFe, but guess its needs a UIFe no also
[09:43] <Laney> ya
[09:43] <Laney> is it worth it now?
[09:44] <darkxst> the UI is largely unchanged on Unity (except the proper menu bar I added) and the change to add account dialog
[09:45] <didrocks> Laney: keep me posted
[09:45] <Laney> I'll just ask plars or someone
[09:46] <darkxst> Laney, guess its ok to land first thing in W though
[09:46] <Laney> no promoted desktop iso since march 6th sucks
[09:47] <Laney> darkxst: If you want to ask for the UIFe then go for it
[09:47] <Laney> if you think the benefits are worth it
[09:49] <darkxst> Benefits for us, not for you guys, though larsu thinks both existing and new UI's are bad
[09:50] <seb128> Laney, what's the issue with the iso?
[09:50] <Laney> smoke tests are failing
[09:56] <seb128> what tests/on what error?
[09:57] <Laney> https://jenkins.qa.ubuntu.com/view/vivid/view/Smoke%20Testing/ -> https://jenkins.qa.ubuntu.com/view/vivid/view/Smoke%20Testing/job/vivid-desktop-amd64-smoke-default/131/artifact/utah-35520-vivid-amd64_default.run_2015-03-18_08-03-10.yaml
[10:02] <seb128> oh, it's the machine-id thing you were discussing which is the issue
[10:05] <Laney> ye
[10:05] <Laney> not sure why there's a test for this implementation detail
[11:12] <seb128> larsu, Laney, can one of you maybe review https://code.launchpad.net/~seb128/unity-settings-daemon/non-unity-sessions-need-scaling/+merge/250153 for me? it's sitting there for a while and I think it's correct/should land for vivid since it fixes oem issues
[11:15] <seb128> brb session restart
[11:20] <larsu> seb128: approved. Thanks. Going to lunch now :)
[11:20] <seb128> larsu, thanks!
[11:20] <larsu> :)
[11:22]  * Laney wonders how to get email about these MPs
[11:22] <seb128> larsu, the 16/9 value thing is just copy from GNOME code, but agreed on fixing it at the right place, if possible
[11:22] <seb128> but seems it's the hardware sending buggy values
[11:22] <seb128> so unsure we can compute valid ones
[11:36] <seb128> larsu, Laney, review on https://code.launchpad.net/~seb128/unity-settings-daemon/battery-info-key/+merge/253336 appreciated as well
[11:40] <Laney> seb128: don't want to take that upstream commit to make the notification work?
[11:45] <seb128> Laney, no
[11:46] <seb128> Laney, I tried to use a notification, it looks weird with notify osd
[11:46] <seb128> well, first the function use doesn't work under notify-osd so you still don't get a notification
[11:46] <seb128> I did a custom one like we do for others but it looks weird
[11:46] <seb128> like having a battery icon and 100% as text
[11:47] <seb128> we could draw a progressbar like for volume
[11:47] <seb128> but I'm unsure it's a good UI
[11:47] <seb128> that would need proper design
[11:47] <seb128> if somebody is interested to work on that feel free
[11:47] <Laney> yeah it seems like a weird action
[11:47] <Laney> i wonder why they want that
[12:23] <larsu> seb128: too late :)
[14:46] <seb128> Trevinho, attente_, hey, when you added the keygraber to compiz to handle GNOME keybindings, did you look at providing the timestamp as well?
[14:46] <Trevinho> seb128: mh, attente did the internals... But I think he did
[14:46]  * Trevinho checks
[14:47] <seb128> no, it's an uu
[14:47] <Trevinho> seb128: no, in fact...
[14:47] <seb128> I'm asking because we would need to avoid focus issues
[14:47] <seb128> https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=487a936e61766f0306772c1269e2ff437fc53a46
[14:47] <Trevinho> seb128: so... where's the new API?
[14:47] <seb128> Trevinho, new API?
[14:48] <Trevinho> you're faster than my fingers :P
[14:48] <Trevinho> seb128: that's the new api I guess... we cpouldn't use uuu before
[14:48] <attente_> seb128: i don't think so
[14:48] <seb128> attente_, Trevinho, is that something you could easily change?
[14:49] <seb128> not sure if unity has the timestamp value handy at this point of the code
[14:49] <Trevinho> seb128: is that already in vivid (the {u,g}-s-d part)?
[14:49] <seb128> Trevinho, no, signatures need to match
[14:49] <Trevinho> seb128: yes, compiz gives us
[14:49] <seb128> so we can't land only one side
[14:49] <Trevinho> seb128: I know... so we should update them all together
[14:49] <seb128> I was looking at backporting that commit
[14:49] <seb128> but then it complains about the mismatching signature
[14:49] <seb128> so I'm asking if somebody could do the unity side
[14:49] <Trevinho> seb128: we can sync with that
[14:49] <Trevinho> I can prepare a branch in seconds
[14:50] <seb128> Trevinho, please do
[14:50] <Trevinho> seb128: sure
[14:50] <seb128> :-)
[14:50] <seb128> thanks
[14:52] <Trevinho> seb128: ouch I hope I've not been too positive, as we've the timestamp on options, let me check further
[14:52] <seb128> Trevinho, k
[14:52] <Trevinho> seb128: ah, no sorry... we've it
[14:52] <Trevinho> no worries
[14:52] <seb128> great :-)
[14:56] <Trevinho> seb128: do you have a bug for it?
[14:56] <seb128> Trevinho, no, but I can open one if you want, I was just checking if I find one
[14:56] <Trevinho> seb128: ok, I leave that to you with great pleasure :)
[14:57]  * Trevinho really can't understand why they didn't do this from the very beginning... timestamp MUST BE THEREEEEEE (or crazyness happens)!
[15:02] <Trevinho> seb128: lp# ready? :)
[15:03] <seb128> Trevinho, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1433648
[15:03] <Trevinho> cool
[15:06] <Trevinho> seb128: here it is https://code.launchpad.net/~3v1n0/unity/gnome-keys-timestamp-api/+merge/253380
[15:07] <seb128> Trevinho, thanks!
[15:09] <seb128> Trevinho, I'm testing the combined changes, give it a bit to build and I can confirm if it works
[15:10] <Trevinho> seb128: cool, ChrisTownsend will check the unity code meanwhile
[15:10] <seb128> Trevinho, great, thanks
[15:30] <tejota> How could I setup an web accessible Ubuntu desktop (VDI/DaaS sort of thing, I guees) on a VPS (say, with Digitalocean)?
[15:49] <Laney> http://cdimage.ubuntu.com/daily-live/current/
[15:49] <Laney> a new current image is born
[15:57] <didrocks> Laney: I hope it does boot under upstart :p (see #ubuntu-release ;))
[15:57] <Laney> ha
[16:12] <happyaron> Laney: just come up with a patch for language-selector's pkg_depends, how can I test whether it work in installation?
[16:12] <Laney> install it in a live session and try installing
[16:12] <happyaron> OK
[16:12] <Laney> didn't somebody else come up with a patch already?
[16:12] <happyaron> nope, :)
[16:12] <Laney> bug #1431337
[16:13] <Laney> ffs
[16:13] <Laney> https://launchpadlibrarian.net/200029284/fcitx-support.debdiff
[16:14] <happyaron> ic, the way of modifying it is correct, but it's not pulling in the correct packages
[16:14] <happyaron> didn't notice the patch though, quickly merged after it's reported
[16:15] <Laney> probably give this guy credit
[16:15] <happyaron> that's not a problem
[16:15] <happyaron> will
[16:15] <happyaron> will write him in changelog
[16:18] <happyaron> 9.48MB/s getting daily-live, yay
[16:23] <seb128> Trevinho, the changes work great, thanks ;-)
[16:25] <seb128> bregma, hey, do you plan an unity landing in vivid soon? I would like to see https://bugs.launchpad.net/unity/+bug/1433648 fixed but it needs to coordinate u-s-d and unity landings
[16:26] <bregma> seb128, soon, just focused on a Unity 14.04 SRU at the moment, the MP for that bug is in the review queue right now
[16:26]  * bregma is keeping away from ci-train after breaking it the last time
[16:26] <seb128> bregma, k, how do you want to handle the sync? do you plan to include u-s-d in the next unity silo?
[16:27] <bregma> we could do it that way
[16:27] <bregma> what's the u-s-d MP?
[16:27] <seb128> not up yet
[16:27] <seb128> I'm wondering if I should use a versionned Breaks
[16:28] <seb128> and on what unity version then
[16:28] <seb128> to ensure they get updated together
[16:28] <bregma> hamm, we could do an upstream Unity release to keep it simple
[16:29] <seb128> did you plan to bump the version for the next vivid landing?
[16:30] <bregma> I can, if we release 7.3.2 upstream
[16:30] <seb128> well, should I use that in my u-s-d mp then?
[16:30] <bregma> yes, let's do that
[16:32] <seb128> bregma, https://code.launchpad.net/~seb128/unity-settings-daemon/timestamp-for-commands/+merge/253394
[16:33] <seb128> bregma, please include in your next unity update silo then ;-)
[16:33] <bregma> will do
[16:34] <seb128> bregma, thanks
[16:34] <seb128> larsu, your gnome-desktop current patch seems to work fine, is it still creating issues with nautilus?
[16:34] <seb128> or should I upload?
[16:35] <seb128> I test my testcase with scale 1 and 2 and nautilus with scale 1 and 2, things look fine
[16:35] <seb128> though nautilus with scale 2 has the image not properly scaled it seems but that was already the case
[17:03] <larsu> seb128: works for me, but please test it again to make sure
[17:06] <larsu> seb128: it propery scales it now with the new version of my patch. not for you?
[17:06] <seb128> larsu, well, I built a package and test both testcase and nautilus
[17:06] <seb128> larsu, is GDK_SCALE=2 nautilus supposed to render the full bg image?
[17:06] <seb128> or is with scaling 2 the image supposed to go over the screen?
[17:08] <larsu> no, it shouldn't go over the screen
[17:11] <seb128> larsu, sorry, tried again and took screenshot, I probably got confused by the big icons
[17:11] <seb128> exactly the same
[17:11]  * seb128 validates larsu's fix and upload
[17:11] <larsu> \o/
[17:12] <seb128> larsu, thanks again for working on that!
[17:12] <seb128> larsu, I commented on the upstream bug saying that the fix works for me
[17:12] <larsu> seb128: just saw, thanks
[17:13] <seb128> yw!
[17:13] <larsu> seb128: it's not exactly the same. Should be better (try with an image where you can see the pixels)
[17:13]  * larsu had a blck/white 1x1 checker pattern to test
[17:23] <Laney> JohnLea_: willcooke: hi, do you plan to address #21 / #22 from https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1429011 ?
[17:24] <willcooke> Laney, nope, but JohnLea_ might ^^^^
[17:24] <Sweet5hark> larsu: you Berlin guys certainly have too much VC flying around: http://www.deutsche-startups.de/startups-jobs/stellenangebote/tester-qualitaetsmanager-bordelle-mw/
[17:26] <larsu> Sweet5hark: lol!
[17:26] <willcooke> Laney, JohnLea_ - I will email Alex as well
[17:27] <Laney> willcooke: ok, if you could give a size budget of 4M that would be helpful too. ;)
[17:27] <willcooke> Laney, sure
[17:29] <Laney> thanks
[17:31]  * Laney looks out for xnox's OCD
[17:32] <willcooke> :D
[17:32] <xnox> Laney: is there a new wallpaper, or are you gonna kill me with off-set one?!
[17:32] <willcooke> xnox, were you more concerned about the horizontal alignment, or both horizontal and vertical?
[17:33] <willcooke> or was it the dots?
[17:33] <xnox> willcooke: the horizon height is imho critical.
[17:33] <seb128> Laney, larsu, any news of the theme/csd decoration look changes?
[17:33] <xnox> willcooke: the rest are minor, knit pickings.
[17:33] <xnox> willcooke: the "center horizontal fold"
[17:33] <willcooke> ack
[17:33] <larsu> seb128: not yet :(
[17:33] <willcooke> so it needs to be, well, in the middle
[17:33] <willcooke> ?
[17:33] <xnox> willcooke: john lea is not the one who has assets or drew this.
[17:34] <xnox> willcooke: previously i would just wonder around blue fin, until i find the right person to nudge things in photoshop and email them to me.
[17:34] <willcooke> no but he's the Design person in the channel
[17:34] <xnox> LOL
[17:34] <willcooke> xnox, if you're in the office, then I expect Alex is as well, he's the guy who drew them
[17:34] <xnox> willcooke: honestly, just find the person who drew it direct.
[17:34] <seb128> Laney, larsu, I don't think we need to ask for permissions, we just need to drop them a fyi and upload
[17:34] <Laney> yes we do
[17:35] <xnox> willcooke: i quit canonical last year, fyi ;-)
[17:35] <Laney> it didn't show up on the list though
[17:35] <seb128> Laney, we do what?
[17:35] <willcooke> oh! yeah!
[17:35] <willcooke> xnox, yeah, I've email him
[17:35] <seb128> fyi or ask for permission?
[17:35] <Laney> need the fyi at least
[17:35] <Laney> but it's not even on there yet
[17:35] <seb128> right
[17:35] <Laney> I asked pmatu something to moderate the list but it's still not there
[17:35] <larsu> Laney: awaiting approval... if this is the process, it isn't good
[17:36] <Laney> yeah no shit
[17:36] <seb128> on what list is it moderation? documentation?
[17:36] <Laney> ubuntu-doc
[17:37] <seb128> k
[17:37] <seb128> asking on #ubuntu-devel in case
[17:37] <seb128> larsu, who would be the right person to review/ack https://code.launchpad.net/~larsu/ido/prelight-and-focus-scale/+merge/252293 ? charles ?
[17:37] <larsu> Laney: are you on that list? Can you please just send an email from your account?
[17:37] <larsu> that would at least get *this* thing moving
[17:37] <Laney> don't know
[17:38] <Laney> I think not
[17:38] <seb128> larsu, can you fwd me the email you sent?
[17:38] <larsu> seb128: yes, and the original reporter of the bug (ochosi)
[17:39] <seb128> ochosi, can you test/review ^ ?
[17:39] <larsu> Laney: why not?
[17:39] <larsu> seb128: sure
[17:39] <Laney> why not what?
[17:39] <ochosi> hey guys
[17:39] <ochosi> i'm using that same code in a panel plugin for xfce, that's how i noticed the bug :)
[17:40] <ochosi> so yeah, that fix works for me there, but i can try to test it with ido too
[17:40] <larsu> Laney: I asked if you can send an email and your next message was "don't know. I think not." I guess that was unrelated?
[17:40] <Laney> first you asked if I was on the list. :P
[17:40] <seb128> ochosi, thanks
[17:40] <ochosi> anything special i need to know for testing/building that lib?
[17:40] <seb128> charles, can you review https://code.launchpad.net/~larsu/ido/prelight-and-focus-scale/+merge/252293 ? should be an easy one
[17:40] <larsu> ochosi: wait... if my fix to ido works for you, you must be using ido, no?
[17:41] <ochosi> larsu: nope, we borrowed the scalemenuitem code for an xfce plugin
[17:41] <larsu> ochosi: how else would you be affected
[17:41] <larsu> ochosi: so you copied the fix?
[17:41] <seb128> code copy
[17:41] <larsu> well then…
[17:41] <seb128> larsu, should I see any difference under unity
[17:41] <seb128> or a "look the same" is good?
[17:42] <ochosi> larsu: yes, this is where we use it: http://imgur.com/TXhMUsA
[17:42] <larsu> seb128: it's there, but very subtle
[17:42] <larsu> seb128: switch to adwaita and you'll see it
[17:42] <seb128> larsu, k
[17:44] <seb128> larsu, switched to adwaita, windows decoration from your branch look weird, the min/max buttons and title are white on light grey
[17:45] <seb128> larsu, http://people.canonical.com/~seb128/ucc.png
[17:46] <seb128> not well vertically centered as well
[17:46] <seb128> but I guess in practice people don't use adwaita on unity
[17:50] <larsu> seb128: woah, I thought you were still talking about the scalemenuitem branch
[17:50] <larsu> seb128: how can changes to ubuntu-themes affect adwaita?
[17:51] <seb128> larsu, oh sorry, not I mean the ubuntu-themes decoration changes
[17:51] <seb128> oh, maybe it was there before
[17:51] <seb128> I don't try adwaita often
[17:51] <seb128> I've your branch applied though
[17:51] <seb128> ignore that
[17:51] <larsu> seb128: probably. Don't switch to adwaita to test those changes. They're for ubuntu-themes
[17:51] <seb128> it doesn't seem a real world usecase
[17:51] <seb128> larsu, I was switching to test ido
[17:51] <seb128> but ja
[17:52] <seb128> larsu, can you resend your ffe email? the moderator said he doesn't see it in the queue...
[17:52] <seb128> well, not to me but to the list
[17:52]  * didrocks waves good evening
[17:52] <seb128> didrocks, night
[17:52] <larsu> seb128: ok
[17:52] <seb128> larsu, danke
[17:52]  * larsu would have thought email works reliably these days
[17:52] <seb128> you did get an email saying it's waiting for moderation?
[17:52] <larsu> yes
[17:53] <Laney> suspicious
[17:53] <seb128> larsu, in fact the moderation says it probably got disgarded, sorry about that
[17:53] <seb128> just resend
[17:53] <Laney> haha
[17:53] <seb128> the guy is around and can approve it
[17:53] <larsu> done
[17:53] <Laney> see, email is reliable
[17:53] <Laney> it's those pesky humans
[17:53] <larsu> pesky
[17:53] <Laney> good word
[17:53] <larsu> indeed
[17:54] <larsu> Your message to ubuntu-doc awaits moderator approval
[17:54] <larsu> Your message to ubuntu-doc awaits moderator approval
[17:54] <larsu> let's see…
[17:54] <ochosi> ok done
[17:56] <seb128> ochosi, thanks
[17:56] <seb128> larsu, Laney, https://code.launchpad.net/~3v1n0/unity/gnome-keys-timestamp-api/+merge/253380 if you want another easy review ;-)
[17:56] <ochosi> seb128: np, thanks to larsu for coming up with the fix :)
[17:56] <seb128> hum, I don't have rights to approve https://code.launchpad.net/~larsu/overlay-scrollbar/blacklist-gnome-boxes/+merge/251566
[17:57] <seb128> can somebody do that for me?
[17:57]  * larsu feels out of place to do so
[17:57] <Laney> hahaha
[17:57]  * Laney loves the blacklist bonanza
[17:57] <Laney> no rights either
[17:58] <Laney> seb128: did you mean to link the usd branch instead?
[17:58] <Laney> the bug's a bit light on details
[18:00] <seb128> Laney, yes, sorry
[18:01] <seb128> Laney, added a testcase to the bug, but it's basically "use keybinding to open an app (calc, web, email) and it goes to background"
[18:01] <seb128> I noticed when testing my fix for the battery info key
[18:01] <Laney> cheers
[18:02]  * Laney remapped the keys to do volume actions instead, lemme change
[18:02] <seb128> Laney, I mapped ctrl-alt-c to calculator to try
[18:03] <seb128> larsu, please send email again, you were in autodiscard for some reason, he fixed it for good this time
[18:03] <Laney> it seemed to try and put them in empty space
[18:03] <Laney> stupid algorithm
[18:04] <larsu> seb128: should I write a script that sends it every 10 mins?
[18:04] <Laney> https://imgur.com/HIe0Mq4
[18:04] <Laney> :D
[18:06] <larsu> Laney: I've never understood why gnome-calculator is not a single-instance application
[18:06] <larsu> *single-window, sorry
[18:06] <larsu> bbiab
[18:07] <Laney> I can imagine wanting to do a few different calculations at once
[18:07] <Laney> maybe...
[18:07] <Laney> got to go, ttyl!
[18:12] <seb128> larsu, lol, sorry :(
[18:30]  * willcooke -> EOD.  tata