[05:24] <hikiko> hi
[05:50] <seb128> good morning desktopers
[05:52] <hikiko> hi seb128
[05:52] <seb128> hey hikiko, how are you?
[05:53] <hikiko> fine, you?
[05:53] <TheMuso> Hey seb128, you're up early. :)
[05:53] <seb128> hey TheMuso
[05:53] <TheMuso> Hey hikiko.
[05:53] <seb128> looks like it
[05:53] <seb128> not pitti early though!
[05:54] <sarnold> pitti early is way too early
[05:55] <hikiko> hi TheMuso
[06:04] <larsu> good morning everyone!
[06:05]  * larsu is traveling to one of yours today
[06:11] <seb128> hey larsu!
[06:11] <seb128> how are you?
[06:11] <seb128> safe travel!
[06:12] <larsu> I'm great thanks! I hope Toronto has as much sun as Berlin :)
[06:12] <larsu> how are you?
[06:23] <seb128> I'm good thanks, though a bit tired
[06:23] <seb128> working on it through coffee though ;-)
[06:23] <seb128> do you have any specific goal for the hackfest?
[06:28] <larsu> seb128: not yet, no. I plan to be around and see what other people are working on
[06:28] <larsu> and maybe help out a bit ;)
[06:36]  * TheMuso -> EOD, later folks.
[06:44] <didrocks> hey larsu, seb128
[06:44] <didrocks> larsu: you won't be in Berling next week I guess then?
[06:45] <larsu> morning didrocks! how are you?
[06:45] <didrocks> larsu: I'm :) and you?
[06:45] <larsu> I'll be back end of next week. are you coming?
[06:45] <didrocks> Sunday to Wednesday
[06:45] <larsu> nooooooo
[06:45] <didrocks> so I guess it's a miss
[06:45] <didrocks> :(
[06:46] <didrocks> Julie was coming as well
[06:46] <larsu> :'-(
[06:46] <larsu> holiday?
[06:46] <didrocks> no, work
[06:46] <didrocks> but holidays for her, yeah :)
[06:47] <larsu> well enjoy anyway. and come back soon!
[06:47] <seb128> lut didrocks
[06:47] <didrocks> larsu: hope to see you there soon :)
[06:47] <larsu> such bad timing
[06:47] <didrocks> and safe travel meanwhile
[06:47] <didrocks> yeah… :(
[06:47] <larsu> thanks! :)
[07:33] <pitti> Good morning
[07:33] <pitti> seb128, sarnold_: I slept until 9, but that did me and my cold rather well :)
[07:34] <seb128> hey pitti!
[07:34] <seb128> seems like we reversed roles today
[07:34] <seb128> glad to hear than your cold is getting better!
[07:34] <seb128> oh, and good morning pitti ;-)
[07:36] <didrocks> hey pitti
[07:36] <pitti> bonjour didrocks !
[08:03] <willcooke> o/
[08:04] <Laney> ahoy!
[08:05] <willcooke> morning Laney
[08:05] <seb128> good morning u.k!
[08:05] <seb128> how is the island today?
[08:05] <willcooke> urgh, all the bitey insects were out last night
[08:05] <Laney> sssssssunny
[08:06] <Laney> just been planting some flowers
[08:07] <Laney> seb128: why so early? ;-)
[08:07] <Laney> .nl time
[08:07] <Laney> it's in a different timezone to .fr right
[08:07] <Sweet5hark> moin
[08:07] <seb128> Laney, indeed!
[08:07] <seb128> though a bit earlier than usual
[08:08] <seb128> I was just awake and felt like I wouldn't manage to get back to sleep in the half an hour before the alarm clock
[08:08] <seb128> hey Sweet5hark!
[08:09]  * Sweet5hark had an "interesting eventing" yesterday. A tornado has hit my hometown. It missed my parents house by just some 300 meters ...
[08:09] <willcooke> woah
[08:09] <seb128> urg
[08:09] <willcooke> everyone ok?
[08:09] <seb128> tornados in Germany? wth
[08:09] <pitti> weather has been crazy lately indeed :/ lots of floods in the south too
[08:12] <Sweet5hark> I drove to their house to check (they are on vacation). And every road I wanted to take there was closed by the police and fireworkers -- that wasnt reassuring at all. When I finally found a way to sneak in the whole street was full of fireworkers sawing down trees and clearing damage ...
[08:13] <seb128> did you manage to get to the house at the end?
[08:14] <seb128> was it still standing?
[08:15] <Sweet5hark> The house seems fine though. As said: A few hundred meters further, there was quite a bit of distruction. 1000 fireworkers had been in action. Here is how it looked for someone inside the storm: https://www.youtube.com/watch?time_continue=9&v=68_o_B0C4pI
[08:16] <Sweet5hark> seb128: There wasnt any visible damage at all to the house. But the video above was filmed just maybe 500m from were the house is.
[08:17] <pitti> ouch
[08:20] <willcooke> happyaron, how did you get on with the nm stuff today?
[08:20] <happyaron> willcooke: will send an email to seb for n-m/1.2.2 very quickly, and later today for the nm-applet
[08:21] <happyaron> replying to oem chih's email atm
[08:21] <willcooke> thx happyaron
[08:21] <Sweet5hark> Tornado are apparently _very_ local phenomena. I was 5km from there in my flat, and while I heard thunder and saw the clouds in the north, there was not a single drop of rain -- it was even sunny. I can easily believe how people are careless when a tornado hit -- one is just to amazed at how fast it is happening.
[08:33] <seb128> happyaron, hey, I got your mail, thanks, going to look into it in a bit
[08:33] <happyaron> ty
[09:59] <andyrock> morning all
[10:18] <willcooke> hey andyrock
[11:41] <seb128> back
[11:41] <seb128> waouh, that was an epic fail
[11:41] <Laney> uh oh
[11:41] <seb128> I disabled glx in xorg.conf to try to reproduce a cogl segfault
[11:42] <seb128> of course compiz didn't like that
[11:42] <seb128> which is fine, I tried under wmaker
[11:42] <seb128> well, first compiz didn't like it at the point that the session was sending me back to lightdm
[11:42] <seb128> then I removed the config
[11:42] <seb128> of course compiz screwed its config from the failed login
[11:42] <seb128> no opengl plugin
[11:43] <seb128> tried to dconf reset -f /org/compiz/ without luck
[11:43] <seb128> with all that 15 minutes before I had to go for lunch
[11:44] <seb128> long story short, some rm and ccsm and gsettings/dconf calls later I'm back from lunch with a working session
[11:44] <seb128> did I miss anything? ;-)
[11:47] <seb128> tjaalton, wasn't libinput possible to sync? I had a look and it seemed we only had one patch which was upstream now?
[11:51] <tjaalton> seb128: no, we have two patches of our own
[11:51] <tjaalton> which are not upstream yet
[11:51] <seb128> tjaalton, k, I guess I got confused by your changelog entry since you don't summarize the remaining changes in the merge entry
[11:52] <tjaalton> usually don't
[11:52] <tjaalton> it's in git
[11:52] <tjaalton> "refresh patches, drop .."
[11:52] <tjaalton> would imply there still are patches :)
[11:53] <seb128> yeah, good that I didn't do the sync, I was about to some days ago ;-)
[11:53] <seb128> closing bug #1537793 though!
[11:53] <seb128> shrug
[11:53] <seb128> https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1587396
[11:53] <seb128> copy fail
[11:54] <tjaalton> that was in the changelog
[11:54] <tjaalton> maybe it's stuck in proposed still?
[11:54] <seb128> yeah
[11:54] <seb128> set it to fix commited :p
[11:54] <seb128> tjaalton, sorry for the noise, and thanks for updating it!
[11:55] <seb128> btw I saw on #debian-gnome that Debian reverted to not use libinput by default yet
[11:55] <seb128> well that was some days ago
[11:55] <seb128> does that stand?
[11:58] <tjaalton> no, x-x-input-all still depends on libinput, but the config snippet order got changed
[11:58] <seb128> the result is the same no?
[11:58] <tjaalton> for now
[11:59] <seb128> what was the motivation to switch?
[11:59] <tjaalton> to libinput by default?
[12:00] <seb128> I guess I didn't understand what they were saying
[12:00] <seb128> I was under the impression that they changed the config back to not use libinput for touchpad by default in the session
[12:01] <tjaalton> they had issues because there was a packaging bug in libinput (it didn't install the udev quirks)
[12:02] <seb128> k, so that was just a bug and they went back on that change?
[12:02] <tjaalton> but then upstream decided it makes sense to flip the config order because soon the default is to have only libinput installed (not yet in debian) and then if you really want to use synaptics/evdev you can
[12:02] <tjaalton> and wacom to
[12:02] <tjaalton> too
[12:03] <tjaalton> just that x-x-i-all hasn't been modified to not install the other drivers yet
[12:03] <tjaalton> from what I can tell
[12:03] <seb128> I see
[12:04] <seb128> thanks
[12:04] <seb128> I'm still trying to get an opinion about which one we should prefer
[12:04] <seb128> the Debian discussion suggested that they still somewhat considered libinput to not be mature/tested enough
[12:05] <tjaalton> well we still don't have a way to configure it..
[12:06] <tjaalton> and since that's not coming in 16.10 then our x-x-i-all will at least recommend the other drivers too
[12:07] <seb128> k
[12:07] <seb128> well the way to config coming or not is part of the reason why I try to determine if we need libinput or can safefly wait
[12:08] <seb128> if there were strong reasons we should switch that would give some more priority to the u-c-c work
[12:56] <desrt> In today's chapter of the story, Allison finds herself taking a short time-out in the middle of the day, to travel to the airport.  There, she will meet an old friend.
[12:56] <desrt> good morning, all :)
[13:01] <pitti> hey Allison!
[13:01] <pitti> desrt: btw, I'd really think it's easier to just push a tag to https://github.com/desrt/systemd-shim/ and get a release tarball this way, unless you object (I can do that myself)
[13:01] <desrt> ya.  please do.
[13:02] <desrt> i've really really stopped caring :)
[13:02] <pitti> ack
[13:02] <pitti> desrt: I mostly did too, but for the courtesy of Debian
[13:07] <pitti> desrt: ack, https://github.com/desrt/systemd-shim/releases → pretty convenient thingy
[13:10] <pitti> gosh, I forgot how to import a new upstream version into bzr-buildpackage
[13:11] <pitti> oh, got it
[13:31] <attente> seb128: hey, sorry about this. i don't really have a lot of confidence in the rebase, so i just uploaded to the ppa the delta with just the fixes
[13:31] <seb128> attente, hey, nothing to be sorry about!
[13:31] <seb128> did you get specific negative feedback on the rebase?
[13:31] <seb128> or did you notice regressions?
[13:31] <seb128> or it's just complex/quite some changes so you are unsure about it?
[13:32] <willcooke> seb128, attente - does that make this moot:  https://plus.google.com/+WillCooke/posts/719SEcKwCvC
[13:33] <attente> seb128: the complexity. i found that sometimes it can't detect whether a snap was already installed properly, but i think it's a snapd problem
[13:36] <attente> willcooke: call for testing should still be useful, but yeah, the changes are small enough that i'm less afraid of a regressino
[13:37] <willcooke> attente, but it's not the 3.20.2 rebase now right? Just the other fixes?
[13:38] <attente> willcooke: correct. still on 3.20.1
[13:38] <willcooke> oki, I will update the post accordingly, thx
[13:39] <willcooke> attente, and thanks for making the call :)
[13:39] <attente> sorry about that
[13:39] <willcooke> attente, aint no thing
[13:44] <willcooke> attente, you still want to do the call for testing or can we just go to proposed?
[13:45] <attente> think we can just go to proposed. it still has to wait a week there, right?
[13:45] <willcooke> attente, actually - another plan - could we keep the rebase PPA for testing and create another one just for the fixes which we can sru now?  i.e. straight in to propsed?
[13:45] <willcooke> seb128,  ^
[13:45] <attente> yeah, we could do that
[13:48] <seb128> willcooke, attente, having the rebase in the ppa makes sense, unsure if we need another ppa/space for the SRU, we could do debdiff on a bug or email for sponsoring
[13:49] <Laney> there's already a bzr branch for it
[13:50] <seb128> attente, you just won a volunteer sponsors who seems to know where things are ;-)
[13:50] <Laney> it's a normal branch
[13:50] <seb128> I'm sure it is
[13:51] <attente> but the changes are all on the git.gnome.org branch
[13:51] <seb128> I'm a bit confused on how all that work
[13:52] <seb128> the vcs is outdated compared to the archive
[13:52] <seb128> which I guess is because robert doesn't know about/use the bzr branch
[13:52] <Laney> Vcs-Bzr has it
[13:53] <seb128> read what I wrote
[13:53] <seb128> https://launchpad.net/ubuntu/+source/gnome-software/3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu2
[13:53] <seb128> is missing
[13:53] <seb128> at least
[13:53] <seb128> didn't check more
[13:53] <attente> i'm uncertain how the debdiff is supposed to work either. don't we need to upload a orig.tar.xz?
[13:53] <Laney> don't be rude
[13:53] <Laney> It's out of date, but not because it's confusing
[13:54] <Laney> in that respect the package is standard
[13:54] <Laney> from attente's side it's a make distcheck of the branch to upload then merge this tarball into bzr and push that somewhere to be reviewed
[13:55] <seb128> sorry, didn't meant to be rude
[13:56] <Laney> np!
[13:57] <seb128> your comment seemed a bit orthogonal to what I was saying though
[13:57] <seb128> we might want a ppa to test that SRU or not still
[13:57] <seb128> probably not I would said if it's a safe one
[13:57] <seb128> also I can't be bothered to create a sru branch
[13:57] <seb128> I tend to do SRUs by diff+dput
[13:58] <seb128> but if somebody wants to do that I'm not going to say anything against it
[13:58] <Laney> you were talking about how to get the package to upload it
[13:58] <seb128> oh, also I was not joking about the fact that I would appreciate if you could help attente/sponsor it for him
[13:58] <Laney> it's already in bzr so using that seems to make sense
[13:59] <Laney> ok
[13:59] <seb128> thanks
[13:59] <seb128> yeah, I though the vcs had moved on for yakkety
[13:59] <seb128> but apparently nto
[13:59] <seb128> we should probably fix that though
[14:00]  * Laney just did GET https://launchpadlibrarian.net/263245608/gnome-software_3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1_3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu2.diff.gz | zcat | patch -p1; debcommit -r; bzr push :parent
[14:01] <seb128> hacker skillz :-)
[14:01] <seb128> thanks
[14:02] <seb128> attente, btw what was that scheme handler issue mentioned during the meeting?
[14:02] <jbicha> Laney: bzr add
[14:02] <Laney> aaaaaaaah you got me
[14:03] <Laney> jbicha is the new work police I see
[14:03] <Laney> I push --overwrited it
[14:03] <seb128> lol
[14:04] <seb128> I clearly didn't pay enough attention :p
[14:04] <seb128> jbicha, hey, and thanks for catching that one ;-)
[14:06] <seb128> cyphermox, hey, thanks for the nm-applet 3g icon fix ... do you plan to commit that upstream as well, or is ubuntu specific? (it seems you commited the first version to git but not the updated one)
[14:07] <jbicha> attente: how difficult would it be to get bug 1590115 in for this sru?
[14:08] <attente> jbicha: i didn't realize there were two commits to cherry-pick there
[14:08] <attente> it looks ok though
[14:09] <jbicha> yeah I thought there was only one at first but it needs both to fully work
[14:20] <Trevinho> pitti: hey, do you happen to know who sets the ID_INPUT* env in input devices nowadays?
[14:21] <Trevinho> pitti: as I'm running an lxc where these envs aren't set, while they are in the host...
[14:21] <pitti> Trevinho: it's an udev builtin
[14:21] <Trevinho> pitti: mh, so... mh, no way to get these inside the lxc (where I guess udev doesn't run)...
[14:21] <pitti> Trevinho: remember, no udev in LXC containers
[14:21] <pitti> but I thought that /dev gets bind-mounted from the host, doesn't it?
[14:21] <Trevinho> pitti: eh, that's the thing :)
[14:22] <Trevinho> pitti: it does, but still
[14:22] <Trevinho> pitti: see what i get http://pastebin.ubuntu.com/17117221/
[14:22] <Trevinho> same if I query /dev/input/mouse*
[14:23] <pitti> Trevinho: ah, no /run/udev/data bind mount in the container, I figure
[14:23] <pitti> doing that might do the trick
[14:23] <Trevinho> pitti: I tried, but I think it didn't work
[14:23] <Trevinho> let me check again
[14:23] <pitti> but yeah, don't try to do hardware in containers
[14:23] <Trevinho> thanks
[14:23] <pitti> unless that's just for convenient local testing, then this might work
[14:24] <Trevinho> pitti: well, I don't do harwdare, but in unity8 and (X I believe) these IDs are used to check the kind of the device
[14:24] <pitti> right
[14:25] <pitti> Trevinho: I just thought unity8 wasn't a thing that anyone would try and run in a standard container
[14:25] <pitti> Trevinho: for those I think it's easier to enable udev in the container
[14:25] <pitti> it's running in lxd containers already
[14:25] <pitti> and for lxc, you need to make /sys read-write
[14:29] <willcooke> attente, seb128 - sorry, was in a meeting and didnt follow the discussion about g-s.  So we're going to upload the new version without the rebase as an SRU now?
[14:30] <seb128> yes
[14:30] <willcooke> thanks seb128
[14:30] <seb128> yw!
[14:30] <Trevinho> pitti: well, I'm able to properly run it from the container... It's just that unity8 checks wheter there are touch or pointer devices. And depending on that it shows or hides the cursors, or adapts the interface... So it's just doing some parsing, not much more
[14:31] <pitti> Trevinho: this is "classic" LXC, not LXD?
[14:31] <Trevinho> pitti: it seems I can't mout the /run/udev though... For some unknow reason. maybe becaus it's not filled
[14:32] <Trevinho> pitti: yeah... I probably should have done an lxd then?
[14:32] <pitti> Trevinho: you need to do that from the config file, you can't do this from inside the container
[14:32] <Trevinho> As I was just used to the classic container, so I didn't change my workflow
[14:32] <pitti> you need to bind-mount the host's dir
[14:32] <Trevinho> pitti: yeah, sure... but when doing it lxc doens't start
[14:32] <Trevinho> maybe because /run is something filled later?
[14:32] <pitti> hm, perhaps (I've never tried this)
[14:33] <Trevinho> lxc.hook.mount might help
[14:34] <Trevinho> or.. .lxc.hook.pre-mount ?
[14:37] <willcooke> seb128, attente  - updated the G+ post
[14:37] <seb128> willcooke, thanks
[14:45] <Trevinho> pitti: so... the thing is that /run is mounted as tmpfs on /run... Then I should mount this after it has been created, and it doesn't seem trivial
[14:45] <Trevinho> I see if I can get some info from Stephane
[14:46] <pitti> Trevinho: indeed; simpler to figure out how to mount /sys read-write so that udev starts, or use lxd
[14:46] <Trevinho> pitti: I see thanks
[14:54] <Trevinho> pitti: I managed to do it in two steps, and it works... Thanks a lot
[16:25] <attente> seb128: what should the sru bug be about?
[16:25] <seb128> attente, which one?
[16:25] <seb128> similar to the previous SRU
[16:26] <seb128> one line by changeset with a bug reference
[16:26] <seb128> and each corresponding bug having the standard SRU info
[16:26] <seb128> impact/test case/regression potential
[16:27] <attente> seb128: do you think it matters much that the diff is still rather large? it's almost 3000 lines...
[16:27] <seb128> oh, that SRU!
[16:27] <seb128> for that one get a bug "update to 3.20.3 stable version"
[16:27] <attente> yeah ;)
[16:27] <attente> oh. no. not doing that...
[16:27] <seb128> in addition of selected/specific fixes you want to mention
[16:28] <attente> ok. i'll just do one for the specific fixes. i'm not sure why the debdiff is so large actually...
[16:28] <attente> like there's a giant aclocal diff
[16:28] <seb128> that's fine
[16:29] <seb128> just look at the code changes
[16:29] <seb128> but either the changes are covered by the different issues you list
[16:29] <seb128> or you have a "<something that justify random changes>"
[16:29] <seb128> like rebase on current stable
[16:29] <seb128> or whatever you did
[16:29] <seb128> with a specific bug for that part of the changes
[16:30]  * seb128 goes for some exercice, be back in an hour or so
[17:57] <attente> seb128: hey, can you take a look at this to make sure it's ok? https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1590508
[18:44] <tafb2>  can anyone help me install ddrescue-gui on ubuntu 16.04? I'm having real troubles :(
[18:45] <seb128> attente, ideally you would use specific bugs for the issues which have ones, like the rating
[18:46] <seb128> bug #1581938
[18:47] <seb128> attente, but yeah, looks good otherwise
[18:48] <attente> ah, ok
[18:48] <attente> thanks seb128
[18:50] <seb128> yw