[05:16] <hikiko__> hello
[06:09] <didrocks> good morning
[06:10] <hikiko> good morning didrocks
[06:11] <didrocks> hey hikiko!
[06:53] <seb128> good morning desktopers
[07:00] <didrocks> re seb128
[07:00] <seb128> re didrocks
[07:08] <larsu> good morning!
[07:08] <seb128> hey larsu, wie gehts?
[07:09] <larsu> seb128: great thanks! Just making some tea which smells good :) How are you?
[07:10] <seb128> larsu, I'm good thanks! played tennis yesterday ;-)
[07:10] <didrocks> hey larsu!
[07:10] <larsu> seb128: ah right how was that? Do you have a new club in the hague?
[07:10] <didrocks> larsu: I have a bad news, so I hope you feel well :)
[07:11] <larsu> didrocks: morning. I simply won't listen
[07:11] <larsu> didrocks: :P
[07:11] <didrocks> heh ;)
[07:11] <didrocks> u-s-d isn't fixed for me
[07:11] <didrocks> like just do an install, 3rd screen -> u-s-d crash, controls jumping on the right
[07:11] <larsu> well this was a blind fix, the possibilty was there
[07:11] <didrocks> but I have a nice stacktrace for you!
[07:12] <didrocks> larsu: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1508327/comments/8
[07:12] <didrocks> larsu: should I keep the broken state?
[07:13] <larsu> didrocks: this is a different bt
[07:14] <didrocks> larsu: yep, maybe I had a different crash than seb128
[07:14] <larsu> indeed
[07:14] <larsu> let me finish making breakfast and I'll look into it
[07:14] <didrocks> thx
[07:14] <didrocks> keeping it that way for now
[07:14] <pitti> Good morning
[07:14] <didrocks> jibel: FYI (see bug report, still getting the crash here) ^
[07:14] <didrocks> hey pitti
[07:15] <seb128> hey pitti
[07:15] <pitti> salut mes amis français, comment allez-vous ?
[07:15] <pitti> hey larsu and hikiko, how are you?
[07:15] <didrocks> pitti: bien, j'ai le cou un peu bloqué, mais j'ai espoir que ça aime mieux dans la journée :) et toi ?
[07:15] <seb128> pitti, ça va bien ! et toi ?
[07:16] <seb128> pitti, j'ai joué au tennis hier (même s'il pleuvait un peu)
[07:16] <pitti> didrocks: uh, c'est de la nuit froide ? ou à cause du sport ?
[07:17] <larsu> didrocks: don't worry, I don't think there's much I can do to remote debug this (an you already gave the stacktrace)
[07:17] <didrocks> pitti: nuit froide, je pense
[07:17] <larsu> guten morgen pitti! Geht super danke, und dir?
[07:17] <didrocks> larsu: ok, I didn't connect any monitor or anything FWIW
[07:17] <didrocks> larsu: (looking at the stack…)
[07:17] <pitti> seb128: ah, très bien ! basketball aussi était grand hier, je devient lentement mieux :)
[07:17] <willcooke> morning all
[07:17] <willcooke> is it out yet.  hurr durr
[07:18] <pitti> larsu: prima
[07:18] <pitti> it's been a long time since I've slept until 9!
[07:18] <larsu> didrocks: yes, I understood you did the same as it says on the bug
[07:18] <seb128> hey willcooke
[07:18] <larsu> pitti: wow! What happened?
[07:18] <seb128> willcooke, not quite yet!
[07:19] <pitti> larsu: well, basketball until 22:30 (and I can't sleep right after that, still too pumped) and burning the midnight oil over bug 1504897
[07:20] <larsu> oh, "fun"
[07:20] <TheMuso> Hey folks.
[07:20] <larsu> hey TheMuso!
[07:20] <larsu> how are you?
[07:21] <TheMuso> larsu: Well thanks. Yourself?
[07:21] <didrocks> evening TheMuso
[07:21] <larsu> TheMuso: great! Finally feeling much better after having a bad cold for a long time
[07:21] <seb128> hey TheMuso
[07:21] <TheMuso> larsu: Great to hear, colds suck.
[07:22] <hikiko> hi pitti larsu didrocks seb128
[07:22] <hikiko> and willcooke
[07:22] <larsu> morning hikiko! How's life?
[07:22] <hikiko> good :)
[07:22] <hikiko> how are you?
[07:22] <larsu> I love how people say hi to willcooke even though he's not here yet
[07:22] <larsu> hikiko: great thanks :)
[07:22] <hikiko> lolol
[07:22] <seb128> larsu, he's there
[07:23] <seb128> he said hi at :17
[07:23] <larsu> damn! I cannot read
[07:23] <larsu> willcooke: belated good morning!
[07:23] <seb128> :-)
[07:23] <willcooke> o/
[07:23] <hikiko> and TheMuso ! hi TheMuso
[07:23] <desrt> good morning desktop
[07:23] <hikiko> hi desrt :)
[07:23] <pitti> hey desrt
[07:23] <TheMuso> Happy release day folks, EOD for me. I hope we have a name for X when I get online tomorrow. :)
[07:24] <willcooke> TheMuso, we have one now
[07:24] <larsu> morning desrt. How are you?
[07:24] <TheMuso> willcooke: We do Awesome.
[07:24] <hikiko> desrt, isn't it a bit early for you?!
[07:24] <desrt> a bit tired.  didn't sleep super-good.
[07:24] <willcooke> TheMuso, check Marks blog
[07:24] <desrt> hikiko: in germany for two weeks, remember? :)
[07:24] <TheMuso> willcooke: Right, I figured.
[07:24] <hikiko> :DD
[07:24] <TheMuso> Anyway, laters folks.
[07:25] <seb128> didrocks, I don't thet that new u-s-d segfault, going through install with decorations on the left
[07:25] <larsu> woah with pictures this time
[07:25] <seb128> hey desrt
[07:25] <didrocks> larsu: pictures were there already :p
[07:25] <desrt> hello pitti, seb128
[07:25] <hikiko> well, have fun
[07:25] <didrocks> seb128: you are more lucky than I am :)
[07:25] <seb128> didrocks, yeah, at least we fixed one issue
[07:25] <larsu> didrocks: not in the last couple
[07:25] <seb128> better than a non working fix
[07:25] <didrocks> yep ;)
[07:26] <didrocks> I still thinks that over the ~20 persons testing an iso, if one get a crash, we can't say "this will not happen in the general case", the % is high (or we would need more data)
[07:26] <larsu> ah, xenial makes *a lot* of sense
[07:26]  * larsu likes
[07:26] <seb128> "xenial xerus" it is then?
[07:26]  * seb128 dicts
[07:26] <pitti> seb128: oh, we have an animal now?
[07:27] <didrocks> pitti: yep, yesterday evening
[07:27] <pitti> and so we do! nice
[07:27] <larsu> pitti: and it is a squirrel!
[07:27] <willcooke> http://cache3.asset-cache.net/gc/508502145-cape-ground-squirrel-xerus-inauris-etosha-gettyimages.jpg?v=1&c=IWSAsset&k=2&d=7OxlzEN3xJ1c4%2Bb6chEutIwsFl8AhaEoPFhxnQIw%2BnOnmndsmWJfdO3w1Dytiern
[07:27] <pitti> I like that wily already knows the new name (distro-info, lintian, vim, etc.) -- it's been some time since we were able to do that
[07:27] <seb128> pitti, http://markshuttleworth.com/archives/1479
[07:27] <didrocks> willcooke: you should never work on marketing ;)
[07:28] <willcooke> \o/
[07:28] <larsu> ever.
[07:28] <willcooke> If you read the line in Mark's blog about "big....." I think that's where the joke came from
[07:28]  * pitti reads the LXD announcement and sighs a little; I wish lxc wouldn't have become so slow
[07:29] <didrocks> pitti: no server-less mode?
[07:29] <pitti> didrocks: how do you mean?
[07:31] <didrocks> pitti: you were complaining about no LXC standalone mode working without LXD now? (and thus the slowness due to extra communication roundtrip)
[07:31] <pitti> didrocks: no, that booting an lxc container takes quite long (about 10s, vs. some 400 ms in nspawn)
[07:32] <didrocks> seb128: I wonder if it's not opening unity-control-center which triggers the crash
[07:32] <didrocks> larsu: ^
[07:32] <didrocks> seb128: mind trying?
[07:32] <seb128> didrocks, "not opening"?
[07:33] <seb128> you mean?
[07:33] <seb128> oh, the other way around
[07:33] <seb128> open u-c-c?
[07:33] <didrocks> seb128: right ;) (the french "if not…") ;)
[07:33] <seb128> no issue
[07:33] <didrocks> "si c'est pas le fait de…"
[07:33]  * larsu still doesn't understand
[07:34] <didrocks> seb128: even after waiting a couple of seconds?
[07:34] <seb128> I did indicator-keyboard -> input settings and went back the main u-c-c grid
[07:34] <seb128> yeah
[07:34] <seb128> I just typed that on IRC
[07:34] <seb128> so it's like 30 secondes
[07:34] <seb128> installation done btw
[07:34] <didrocks> on ubiquity only mode?
[07:34] <seb128> I've the "do you want to reboot" dialog
[07:34] <seb128> yes
[07:34] <didrocks> ok, I was wondering, was matching quite well
[07:35] <didrocks> (like if some plugins were probing something…)
[07:35] <pitti> hmm, "xenial" isn't even on dict.leo.org :)
[07:35] <seb128> didrocks, http://people.canonical.com/~seb128/ubiquity.png
[07:36] <didrocks> seb128: my only difference is that I have the bluetooth indicator
[07:36] <larsu> pitti: dict.cc has a much better coverage (including xenial)
[07:36] <didrocks> but yeah, I did this though before install
[07:36]  * pitti chuckles about the "courage"
[07:36] <didrocks> I don't know how much that could change it… I would say not…
[07:38] <seb128> didrocks, seems like gsd_rr_screen_list_outputs() returns null for you
[07:39] <didrocks> yeah, the output being 0x0
[07:39] <didrocks> but that could be expected, no, as the int is 0 as well
[07:40] <seb128> well null[0] isn't going well
[07:41] <seb128> and would it mean you have 0 screen?
[07:41] <didrocks> seb128: hum, I'm maybe not in the same part of code than you are, I was in gpm-common.c:1726
[07:41] <didrocks> with external_monitor_is_connected
[07:41] <didrocks> (so external listing only?)
[07:41] <didrocks> in addition to primary monitor
[07:42] <seb128>         outputs = gsd_rr_screen_list_outputs (screen);
[07:42] <larsu> I wonder if ->outputs is NULL becasue of another dangling source
[07:43] <seb128> do we have the u-s-d log somewhere?
[07:43] <seb128> yeah, me too
[07:43] <seb128> wonder if it's similar to https://bugzilla.gnome.org/show_bug.cgi?id=740151
[07:43] <didrocks> seb128: no, I rebooted since, but I can reproduce in 10 minutes
[07:47] <seb128> I bet it's similar to ^, some GnomeRRConfigs object laying around
[07:47] <larsu> ya, tracking down what it might be just now
[07:48] <seb128> thanks
[07:50] <larsu> actually there *is* a case when this can be NULL
[07:50] <larsu> didrocks: anythin in the logs?
[07:51] <didrocks> larsu: as told, let me finish the current install… you told me that I could reboot :p
[07:51] <didrocks> and continue testing
[07:51] <didrocks> I'll reproduce then
[07:51] <didrocks> (btw, really can't get it in a live session…)
[07:53] <larsu> didrocks: indeed, my mistake :)
[08:01] <Trevinho> morning
[08:02] <didrocks> hey Trevinho
[08:02] <Trevinho> hey Didier
[08:03] <larsu> hi Trevinho
[08:03] <Trevinho> hi larsu
[08:04] <Laney> yo
[08:05] <larsu> yoyo
[08:07] <seb128> hey Trevinho
[08:08] <Trevinho> thanks for merge seb128
[08:08] <didrocks> larsu: seb128: do you know where the logs are stored in the ubiquity only session?
[08:08] <larsu> didrocks: can't reproduce in a vm. Want to try a patch?
[08:08] <didrocks> no .cache/upstart
[08:08] <Trevinho> oh, today netflix finally landed in Italy. /me back soon :P
[08:08] <seb128> didrocks, no, I looked for them yesterday and didn't find them :-/
[08:08] <seb128> didrocks, maybe in the journal?
[08:08] <larsu> Trevinho: famous last words :P
[08:08] <didrocks> seb128: let's see… I highly doubt
[08:09] <larsu> this is basically the same patch as last time :/
[08:09] <seb128> larsu, on another object?
[08:09] <didrocks> nope, just having segfault in libpower.so
[08:09] <didrocks> logged in the journal
[08:09] <larsu> seb128: yes
[08:09] <didrocks> larsu: let's give it a try I think :)
[08:10] <seb128> cyphermox, do you know where the output/log from e.g unity-settings-daemon are in installer mode?
[08:11] <larsu> didrocks: https://code.launchpad.net/~larsu/unity-settings-daemon/lp1508327-again
[08:11] <larsu> or prefer an MR?
[08:11] <didrocks> larsu: no, I will just build your branch
[08:13] <larsu> thanks. be back in 10
[08:19] <cyphermox> seb128: probably in /root?
[08:20] <willcooke> Laney, cheque ok?
[08:20] <didrocks> cyphermox: /root is empty
[08:21] <didrocks> (and I don't think that user-level daemons would be able to write in the root owned dir)
[08:27] <Laney> willcooke: old skool, I'll frame it
[08:27] <Laney> like a Knuth cheque
[08:27] <willcooke> :)
[08:28] <larsu> cheques still exist?
[08:28] <Laney> they tried to kill them a couple of years ago but backed down
[08:28] <Laney> so ya
[08:29]  * Laney only ever uses them to pay people that come around to do work on the house
[08:30]  * willcooke only ever uses them to pay for school photos
[08:32] <larsu> weird
[08:32] <Laney> flashbacks to a grim pot of combs and the dinner lady combing my hair
[08:32]  * Laney curls up under the desk
[08:32] <larsu> I think we have them as well still, but I have never given one and only once received (forget why)
[08:32] <Laney> sometimes people post them as presents too
[08:33] <willcooke> I would have thought that the advent of those credit card readers which plug in to your phone and/or things like Paypal would be preferable to dealing with a cheque
[08:33] <willcooke> but I guess some people still like the misery of going to the bank
[08:33] <willcooke> http://www.whizzy.org/2010/03/bye-bye-cheques/
[08:36] <hikiko> it seems that some people enjoy waiting at a queue
[08:36] <pitti> wow, cheques
[08:36] <pitti> I think I got one in my life, ever
[08:36] <pitti> my first bounty from no-name-yet.com in 2004 :)
[08:36] <larsu> awwwwwwww!
[08:36] <desrt> willcooke: think i can stop receiving a paystub in the mail in favour of a pdf any time soon? :)
[08:37] <pitti> I "liked" that for getting 200 EUR I had to pay some 10 EUR in fees, ridiculous
[08:37] <larsu> desrt: isn't this something to take up with the canadian canonical branch?
[08:37] <willcooke> desrt, :D  I know right!
[08:37] <desrt> larsu: i tried.  it's not possible.  except that it is possible.
[08:37] <larsu> makes sense
[08:37] <larsu> this is hr, after all
[08:37] <desrt> they sent me pdfs as a one-off when they were posting my paystubs to the wrong address for a few times and sent me some nice beautiful vector pdf equivalents
[08:37] <willcooke> When my pay slip doesn't arrive (about 1 time in 5) I email and ask for a PDF copy which they send over in seconds
[08:38] <desrt> but refused to make a routine of it
[08:38] <willcooke> same here
[08:38] <larsu> willcooke: just auto email them every month that it didn't arrive?
[08:38]  * Sweet5hark used traveller cheques on his first travel to the US, because he was a student and didnt had a credit card.
[08:38]  * desrt gets herself a "return to sender" stamp
[08:38] <Laney> s/that.*//
[08:38] <larsu> Sweet5hark: *wow*
[08:39] <Laney> oh I see what you mean :P
[08:39] <desrt> Sweet5hark: this sentence doesn't make sense in canada
[08:39] <desrt> banks here are falling all over themselves to give credit to _any_ perceived-to-be-untapped market
[08:39] <larsu> desrt: grammar or no traveller's cheques?
[08:39] <desrt> which means being a student = instant approval
[08:39] <larsu> ah.
[08:39] <desrt> being a recent immigrant = instant approval
[08:39] <larsu> foreign students as well?
[08:40] <Sweet5hark> which was weird because I used a traveller cheque to get cash. And even back then people in the US used cash a lot less than in europe.
[08:40] <desrt> being a recent immigrant student = i hope you wanted 4 cards because they'll just mail them to you
[08:40] <desrt> (this last part probably isn't true)
[08:41] <desrt> but ya... basically anyone who has a "valid reason" for not having a credit profile and seems like they might be on a path to becoming a constructive member of society == "here.  have credit.  please.  take it.  i want you to take the credit.  why won't you take the credit.  please take the credit.  thank you for taking the credit."
[08:41] <desrt> the trouble you have is if you somehow make it to 30 without building credit... then theyre ultra-suspicious
[08:42] <Sweet5hark> desrt: hrhr yeah. I wants there for studying though, but for vacation on a tourist visa.
[08:42] <desrt> Sweet5hark: ya.. just saying that this "student = no credit" equivalence only works in europe :)
[08:42] <larsu> so ... upgrade to x today?
[08:43] <Sweet5hark> desrt: ah! yeah
[08:43] <desrt> willcooke: nice post, but i still like cash :)
[08:43] <didrocks> nooooooooooooooooooooooooo ctrl+C in busybox :p
[08:44] <desrt> willcooke: unless we start giving square to the 5-year-old who runs the lemonade stand :)
[08:45] <larsu> desrt: not as out there as you think it is
[08:45] <desrt> larsu: i know...
[08:45] <desrt> when i was in cincinnati we went to this neighbourhood block party type thing and they had a beer tent which worked on a ticket system
[08:46] <desrt> i had like $2 on me, but managed to scrape together enough bits and pieces from the others to get me a ticket
[08:46] <desrt> but not before some randomer friend of the person selling tickets said "i can just run it through on my square and give you the cash"
[08:46] <desrt> and took it out and plugged it in, ready to go
[08:47] <Sweet5hark> the other cultural mismatch was: I carried my traveller cheques close to my body: In a money bag under my shirt. When I first needed some money, I walked into a bank in southern Arizona, still carrying a large hat and sunglasses as I wasnt used to the sun, and started fumbling for something under my jacket/shirt for some time in there ....
[08:47] <Sweet5hark> For some lucky reason, I wasnt shot though.
[08:47] <desrt> Sweet5hark: ah.  they assumed you were a local who wanted to show off your gun collection and share stories about your latest hunting wins!  nice!
[08:51] <desrt> Sweet5hark: reminds me of a friend who visited svalbard telling me that it's completely normal there to walk into a bank with a ski mask and shotgun out....
[08:51] <desrt> on account of the extreme cold and the freaking polar bears
[08:51] <seb128> Sweet5hark, so, it looks like the libreoffice .desktop actions sections have no translations ... is that a known issue?
[08:53] <Sweet5hark> seb128: yes
[08:53] <seb128> Sweet5hark, do you have a bug number? can you include that in your SRU from yesterday (which I didn't upload yet)
[08:55] <didrocks> larsu: I guess you fixed it \o/
[08:55] <didrocks> can't get it crash, how hard I tried
[08:57] <Sweet5hark> seb128: bug 1170035 -- would involve fixing one most horrible perl horror upstream :/
[08:57] <didrocks> larsu: mind MP it?
[08:58] <seb128> Sweet5hark, what do you mean "loaded"?
[08:59] <seb128> Sweet5hark, included in the .desktop?
[08:59] <larsu> didrocks: awesome! Man I love blind fixing stuff
[08:59] <larsu> didrocks: MR is coming up
[08:59]  * larsu needs to rebase
[08:59] <Sweet5hark> seb128: umm yeah, lemme change that (wasnt written by me)
[09:00] <seb128> Sweet5hark, can we have somebody to do it manually for release?
[09:01] <Sweet5hark> seb128: not sure if that will make it simpler -- first have to get those translations out of po files then. Let me have a look.
[09:03] <larsu> man, git bzr really doesn't make this simple
[09:06] <larsu> didrocks: https://code.launchpad.net/~larsu/unity-settings-daemon/lp1508327-again/+merge/275285
[09:07] <didrocks> larsu: approved, you are going through the train?
[09:08] <seb128> didrocks, larsu, please don't
[09:08] <didrocks> larsu: mind linking to the bug report?
[09:08] <didrocks> why?
[09:08] <seb128> because it's not going to be respinned
[09:08] <seb128> and I want to include a fix for the xsettings crash
[09:08] <seb128> so it can wait some hours
[09:08] <didrocks> well, I know our quality standard are lowers, I know…
[09:08] <didrocks> so yeah, ok, as you wish
[09:08] <didrocks> still worth linking to the bug report
[09:08] <seb128> well, it's not lower
[09:08] <larsu> just did
[09:08] <seb128> but they are clearly not respinning
[09:09] <seb128> so we can as well batch some more fixes
[09:09] <larsu> right
[09:09] <didrocks> well, you have your opinions, I have mine :)
[09:09] <seb128> on what?
[09:09] <didrocks> quality
[09:09] <seb128> the fact that they are not respinning?
[09:09] <seb128> well, feel free to get a landing ready and argue
[09:10] <seb128> but seeing -release I doubt they are wanting to respin
[09:10] <didrocks> well, seeing they said no yesterday for this one, yeah, I doubt they will
[09:10] <didrocks> still sad about it
[09:10] <seb128> yeah, me too
[09:10] <seb128> I think we are on the same side
[09:10] <seb128> I've been fixed e.u.c and bugs full time for like 3 weeks now
[09:11] <seb128> fixing*
[09:11] <seb128> but yeah, we still lack polish and have some issues in the release :-/
[09:11] <didrocks> yep :/
[09:11] <seb128> let's try to do better for the LTS
[09:11] <Laney> testing ISOs earlier on is a good lesson to learn I think
[09:11] <Laney> and this can be release noted
[09:12] <didrocks> I really fear the "it only happens to one person": look at the tracker, 4 people for the desktop image, I guess there is more not reporting, but I think most of them try on virtualbox, so same config…
[09:12] <didrocks> anyway, I've made my points, but agreed with Laney, sad that I didn't spot that one on beta
[09:13] <didrocks> (did only use my netbook at that time)
[09:14] <seb128> we should have done a round of iso testing in London
[09:14] <didrocks> yeah, didn't think about it
[09:14] <seb128> it was even on the blueprint list of items
[09:14] <seb128> oh, well, next time!
[09:14] <didrocks> but I wouldn't have that extra hw
[09:14] <didrocks> having some more avoid this "let's test in virtualbox" which isn't really adding more values once someone has done it
[09:14] <seb128> yeah, but the segfault was happening in a virtualbox
[09:14] <didrocks> your one, right?
[09:15] <seb128> at least the one from yesterday on my machine
[09:15] <didrocks> not the other one
[09:15] <didrocks> yep
[09:15] <seb128> well, those are race so maybe the one from today would have happened to somebody
[09:21] <didrocks> going for a run before it starts raining, bbl!
[09:21] <seb128> didrocks, enjoy!
[09:21] <didrocks> thx
[09:22] <larsu> Trevinho: know anything about unity-panel-service not respecting font size anymore?
[09:22]  * larsu has tiny clock now
[09:23] <larsu> works in the menus
[09:24] <Trevinho> larsu: unity-panel-service? You say it works in the menus, right?
[09:24] <larsu> yes
[09:24] <larsu> just the panel itself
[09:25] <larsu> icons seem normal as wel
[09:25] <larsu> *well
[09:25] <Trevinho> mh, so that's unity, not ups
[09:25] <Trevinho> Mh, we just use the default gtk font I think
[09:25] <Trevinho> yes, theming it of course
[09:26] <larsu> Trevinho: does it change size for you when you set it in tweak tool?
[09:26] <Trevinho> it does
[09:27] <seb128> larsu, wfm, when I change org.gnome.desktop.interface font-name the panel adapt as well
[09:27] <larsu> ok what am I doing wrong? Are you both up to date?
[09:27] <larsu> this just happened after an update + reboot for me
[09:27] <seb128> did you disable some u-s-d plugin yesterday when testing that segfault?
[09:28] <seb128> that's how I got bitten by the touchpad this morning :p
[09:28] <Trevinho> we monitor gtk-settings for that
[09:28] <larsu> Trevinho: which gets it's settings from xsettings plugin
[09:28] <larsu> *its
[09:28] <seb128> larsu, gsettings get org.gnome.settings-daemon.plugins.xrandr active
[09:28] <seb128> ?
[09:29] <Trevinho> xrandr?
[09:29] <seb128> ups
[09:29] <seb128> xsettings
[09:29] <larsu> xsettings plugin is active, yes
[09:29] <seb128> :-/
[09:29] <seb128> does it work in a guest session?
[09:29] <larsu> all other apps change
[09:29] <larsu> let me check
[09:30] <Trevinho> larsu: also only the indicators don't? WHat about tooltips or other elements? (dash is different)
[09:30] <larsu> seb128: good call it does :/
[09:30] <larsu> Trevinho: yes
[09:30] <Trevinho> ok... so /me out of the battle :)
[09:31] <Trevinho> mh, well,  not really... If only indicators don't
[09:31] <larsu> so strange!
[09:32] <Trevinho> larsu: what about decorations?
[09:32] <Trevinho> or LIMs?
[09:32] <larsu> works
[09:33] <Trevinho> mh, samecodepath...
[09:33] <larsu> so yeah, logging out helped
[09:33] <larsu> but wtf
[09:34] <Trevinho> maybe a race on reading the setting or what?
[09:34] <larsu> thanks
[09:34] <larsu> Trevinho: I guess
[09:34] <Trevinho> larsu: what was the thing? Now we have to connect to gsettings signals AFTER reading the value?
[09:35] <Laney> they reverted that
[09:35] <Trevinho> ah, in any case we were doing that
[09:35] <larsu> Trevinho: change it, there's a race there
[09:36] <Trevinho> larsu: I mean I think we were doing it properly... What's the way? Reading before or after?
[09:36] <Trevinho> ah, actually that's gtksettings, so... it's not our job
[09:36] <Trevinho> we don't read the font from gsettings directly
[09:40] <larsu> Trevinho: the correct way is to connect first, then read a value
[09:40] <Trevinho> ook
[09:40] <larsu> with desrt's patch, you have to do both in that order to get change notifications
[09:40] <larsu> but it's been reverted apparently (it did cause many problems)
[09:41] <larsu> well, much work really, the problems were there before
[09:41] <Laney> oh I should SRU that nautilus fix
[09:43] <Trevinho> mh, ok so... I think we were doing this mostly right.... Actually there's one place where it's wrong. BUT it doesn't affect indicators (only decorations when setting to use the system font for them)
[09:58] <seb128> Laney, \o/
[09:58] <Laney> not that we know it fixes it :P
[10:06] <seb128> Laney, :-P
[10:07] <Laney> is there a trusty branch?
[10:07] <Laney> ubuntu9.9?
[10:08] <seb128> no trusty vcs afaik
[10:08] <Laney> maaaany srus
[10:09] <seb128> indeed
[10:09] <seb128> nautilus likes to segfault
[10:09] <Laney> laney@nightingale> quilt applied | wc -l                                                                                                   ~/dev/canonical/packaging/desktop/nautilus/nautilus-3.10.1
[10:09] <Laney> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[10:09] <Laney> 48
[10:09] <seb128> lol
[10:09] <seb128> well, a good stack of those are git backports
[10:09] <Laney> yep
[10:10] <Laney> would be cool if there could be an arrangement where distros maintain old releases upstream
[10:10] <Laney> like we and whoever else ships 3.10 could backport stuff and do releases
[10:10] <Laney> sort of what they do with the kernel
[10:11] <seb128> there is
[10:11] <seb128> I think they usually they than people are welcome to do that if they have interested in a serie
[10:11] <seb128> it's just that nobody stepped up to do it
[10:11] <Laney> oh really
[10:13] <seb128> Laney, e.g https://bugzilla.gnome.org/show_bug.cgi?id=755889#c3
[10:14] <willcooke> seb128, Laney - Are you guys happy (enough) that we don't have any blockers at this point?  We have a few 0day SRUs though, right?
[10:15] <seb128> willcooke, +1
[10:15] <Laney> yeah
[10:16] <willcooke> jibel, ^^
[10:16] <willcooke> thanks
[10:16] <jibel> Great! and thanks for your help with testing
[10:16] <seb128> larsu, didrocks, https://code.launchpad.net/~seb128/unity-settings-daemon/xsettings-unload-segfault/+merge/275295 ... another of those (the xsettings segfaulting usd on unload)
[10:18] <seb128> jibel, yw, thanks as well ;-)
[10:21] <larsu> seb128: how do these creep up *now*
[10:22] <seb128> larsu, they don't, I just hit that one while trying to reproduce the one from yesterday, I guess most users don't unload plugins so they are not hit often
[10:22] <seb128> larsu, the one from yesterday was already there in vivid according to e.u.c, just not hit enough/reliably that we looked at before
[10:22] <larsu> seb128: ah ok. Anyway, thanks! Approved
[10:23] <seb128> larsu, thanks!
[10:26] <Laney> just_disconnect_all_the_bloody_signals(please)
[10:26] <larsu> ALL OF THEM
[10:28] <larsu> probably we should do a thorough review of all of this code
[10:29] <larsu> or - preferably - get rid of it
[10:29]  * larsu hates the concept of u-s-d
[10:37] <tseliot> Laney: hi, can you add LP: #1493888 to the release notes, please?
[10:38] <Trevinho> Laney: I've about 20 bugs I need to get targetted for trusty, can you handle them?
[10:38]  * Laney blinks
[10:38]  * Trevinho has not the power
[10:38] <Laney> tseliot: it's a wiki, probably best if you write the paragraph yourself if that's ok
[10:39] <Laney> Trevinho: get on the bug control team!
[10:39] <tseliot> Laney: sure, I can do that
[10:39] <Trevinho> Laney: I am, but I can't...
[10:39] <Laney> ?
[10:39] <Laney> show me an example?
[10:40] <Trevinho> https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1350821
[10:40] <Trevinho> Laney: i probably need to be on ubuntu drivers?
[10:41] <Laney> does it only let you nominate and not approve?
[10:41] <Trevinho> yes
[10:41] <Trevinho> Is nominating enough^?
[10:41] <Trevinho> For sru, I mean...
[10:41] <Laney> nein
[10:42] <Laney> ok, dump the list please
[10:42] <Trevinho> Laney: 1491913 1485073 1449654 1458950 1460626 1131385 1441626 1241972 913612 1366583 1446634 1045933 989588 1412937 1351591 1291950 1461618 1405349 1351591 1351591 1350821 1460626
[10:42] <Laney> ...
[10:42] <Trevinho> want links?
[10:43] <Laney> are they all unity?
[10:43] <Trevinho> most of them yes, one is indicator-session another ido
[10:44] <qengho> mornin'.
[10:44] <andyrock> good morning all
[10:45] <Laney> it's ok
[10:45] <willcooke> morning qengho andyrock
[10:57] <seb128> hey andyrock qengho
[10:57] <seb128> how are you today?
[10:57] <seb128> larsu, can I get another easy ack for https://code.launchpad.net/~seb128/unity-settings-daemon/gwarning_debug_leftover/+merge/275304 ?
[10:57] <seb128> then I can do a landing with those 3 changes
[10:58] <Laney> Trevinho: I think this is working
[10:59] <Laney> http://pastebin.ubuntu.com/12893348/
[11:00] <seb128> Laney, Trevinho, I think you don't really need to worry about that, the SRU team usually approve nominations when they review/approve uploads
[11:01] <Trevinho> seb128: ah, ok... This was my guess, but laney nain'ed ;)
[11:01] <Laney> oh well
[11:01] <seb128> didrocks, larsu, u-s-d with the segfault fix is building in silo 041, we should probably make the bug SRU compliant since it's likely to become a SRU
[11:01] <Laney> I always do the nominations
[11:01] <seb128> oh, k
[11:02] <Laney> don't know if that is required
[11:02] <Laney> but I still do
[11:02] <seb128> well I guess it's nicer
[11:04] <seb128> why is unity not picking up theme changes for the decorations? it's annoying, if you restart unity-settings-daemon you are stucked with ambiance style panel and decorations
[11:04] <Trevinho> how not?
[11:04] <Trevinho> seb128: it used to update them on the fly
[11:05] <seb128> never worked for me
[11:05] <seb128> use the light theme, restart u-s-d
[11:05] <Trevinho> seb128: never, either in say... trusty?
[11:05] <seb128> decorations go back to ambiance and never change back
[11:05] <seb128> well it was an issue for years
[11:06] <seb128> maybe you fixing it for trusty with the new unity decorations and that got buggy again next cycle
[11:06] <Trevinho> I think i never changed that code since then
[11:06] <seb128> does it work for you?
[11:07] <Trevinho> Oh..... right nope
[11:07] <seb128> see ;-)
[11:07] <Trevinho> I think it might have to do with the same issue...
[11:08] <Trevinho> But it DID work
[11:08] <seb128> those were good times :p
[11:08] <Trevinho> Damn, one more bug
[11:08] <Trevinho> :)
[11:08] <seb128> good that we have a whole cycle to fix issues and have a rocking LTS
[11:08] <Trevinho> seb128: your pleasure to open (and tag) it  😜
[11:09]  * Trevinho wants to break things before...
[11:11] <didrocks> seb128: great ;) yeah, I'll turn the bug out later today to be SRUable
[11:12] <Trevinho> seb128: howeverrrrrrrrrr.... That's still caused by soemthing like gsettings. In fact, running trunk unity in trusty still works
[11:12] <seb128> ah
[11:12] <seb128> maybe you connect in the wrong order
[11:12] <seb128> or something
[11:12] <seb128> Trevinho, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1508890
[11:13] <Trevinho> larsu: what we said for gsettings connecting order, is it valid also for gtksettings changes?
[11:35] <andyrock> Trevinho, larsu even chaning the order the problem is still there
[11:35] <andyrock> basically we don't get the signal any more
[11:35] <andyrock> wondering if after restarting u-d-s the gtksettings is no longer valid
[11:36] <andyrock> seb128 ^^^
[11:47] <larsu> gtksettings is different from gsettings
[11:47] <larsu> normal signals there, the connection order doesn't matter
[11:49] <larsu> andyrock: ^
[11:50] <andyrock> ok but after restarting u-d-s we don't get the signals any more
[11:50] <larsu> weird
[11:50] <larsu> hm this works for me
[11:51] <andyrock> I'm trying to debug it
[12:02]  * desrt gets extremely upset with apt-cacher-ng
[12:03] <desrt> change the location of the cache dir in the config file?  no problem.  it will use the new location
[12:03] <desrt> but it will also throw random state files in the hardcoded-default location
[12:03] <desrt> and if it no longer exists (because you move it) then it will silently fail to start
[12:03]  * desrt twitches, searches debian bug tracker
[12:04] <larsu> desrt: what are you using this for?
[12:04] <desrt> https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1279021
[12:04] <desrt> head -> desk
[12:05] <larsu> only 1.5 years :P
[12:05] <desrt> turns out in addition to the CacheDir: line in acng.conf there is also a CacheDir: line in zz_debconf.conf which overrides the earlier value
[12:06] <desrt> this is beyond stupidity....
[12:08] <desrt> # To override this values permanently, put the assignments into a file
[12:08] <desrt> # like /etc/apt-cacher-ng/zzz_override.conf .
[12:08] <desrt> lol.  of course.
[12:13] <desrt> so in an attempt to unscrew everything i decided to purge and reinstall the package.  big mistake, that
[12:13] <desrt> because the config is so fried at this point, it won't start
[12:13] <desrt> which means the postinst can't finish
[12:13] <desrt> which, hilariously, means i can't dpkg-reconfigure it to fix it
[12:13]  * desrt twitches some more
[12:16] <desrt> postinst must die.
[12:20] <desrt> cool.  problem was that the uninstall didn't remove the log directory, but did remove the user account.  reinstall recreated the user account and it got a new uid and the postinst didn't change the permission of the already-existing log directory, resulting in a fail to start
[12:21]  * desrt twitches
[13:10] <happyaron> ok I lost harddisk on canonistack...
[13:16] <larsu> physically? :P
[13:17] <Laney> They're throwing it aroudn the IS area now
[13:17] <Laney> and laughing about how it has all of happyaron's stuff on it
[13:17] <larsu> muhahha
[13:17] <willcooke> :)
[13:18] <happyaron> well well, I have backups
[13:19] <Laney> hope you tested restoring them
[13:19] <happyaron> yep
[13:19] <happyaron> I lost my VM for several times already
[13:20] <happyaron> actually I made it sort of an Active-Active cluster...
[14:08] <xnox> Laney: so pinentry-gnome3 only works with gnupg2, and not with gnupg1. Our default is still gnupg1, as a bunch of things did not yet transition to use gnupg2.
[14:08] <xnox> Laney: hence I had to manually update-alternatives into gtk2 pinentry =( to use with my gpg card
[14:25] <seb128> andyrock, Trevinho, I'm adding bug #1501289 to the rls list, it's not an important issue but it's a bug and is spamming logs
[14:26] <Trevinho> Mh, ok... I've been loking at that, but I didn't find where
[14:28] <seb128> :-(
[14:28] <seb128> well, it's not important, it's not user visible
[14:28] <seb128> I've just been chasing log warnings
[14:28] <Trevinho> seb128: ah, also... I think that for bug reports via apport it would be nice to get the com.canonical.Unity settings and the upstart log, how is this doable?
[14:28] <seb128> would be nice to have clean logs for the lts ;-)
[14:29] <seb128> Trevinho, it's easy, open a bug and I can have a look
[14:29] <Trevinho> seb128: the thing is that that issue might be in any of other the indicators... not in ups
[14:29] <seb128> paying a bit back for all the bug pings
[14:29] <Trevinho> seb128: on unity?
[14:29] <seb128> yes
[14:29] <Laney> xnox: I've never deliberately used gpg2 and I've been using pinentry-gnome3 all cycle
[14:30] <seb128> Trevinho, well, the bt has on_entry_removed (object=0x9eb4198 [IndicatorAppmenu]
[14:30] <Laney> That said, didn't you want to work on this migration anyway?
[14:30] <andyrock> seb128: yup
[14:30] <seb128> Trevinho, doesn't it suggest it's an indicator-appmenu issue?
[14:30] <xnox> Laney: yes. but i also care about wily being usable.
[14:30] <andyrock> I was working on it
[14:30] <Laney> It clearly is usable
[14:30] <Trevinho> seb128: mh, let me see
[14:31] <xnox> Laney: then i wonder what's wrong with my smartcard then =)
[14:31] <seb128> Trevinho, andyrock seems to be on it
[14:31] <seb128> xnox, smartcard not working != not usable
[14:31] <Laney> I don't have a smartcard I'm afraid
[14:31] <xnox> Laney: is there a non-smartcard way to trigger gpg1 to ask for a pinentry, perphaps to rule it out?
[14:31] <seb128> it's a bug, but it doesn't mean the component is not usable for everyone
[14:31] <Laney> make a new key?
[14:31] <xnox> seb128: sure.
[14:31] <Laney> we definitely would have heard if this was broken for everyone universally
[14:31] <Laney> also would have noticed ourselves
[14:33] <xnox> then i claim my machine is borked. okay, will troubleshoot futher. generating gpg1 key with gnome3 pinentry results in gpg/ask thing aborting and thus
[14:33] <xnox> gpg: cancelled by user
[14:33] <xnox> You don't want a passphrase - this is probably a *bad* idea!
[14:33] <xnox> sigh
[14:33] <Laney> anyone weird in your gpg config?
[14:36] <xnox> oh, let me use a brand new account / fresh gnupg home, et.al.
[14:38] <Trevinho> seb128: bug sent to you (assigned)
[14:38] <Trevinho> seb128: maybe there's even something more, but it can't be too much :)
[14:39] <xnox> Laney: works fine in a guest user account, so it's me again. And since it's not universal, i couldn't care less figuring it out.
[14:39] <xnox> looks like wily is perfect, after all =)
[14:40] <Laney> xnox: with the smart card?
[14:40] <Laney> there could be a fuck up there
[14:40] <Laney> I kind of want to get one anyway
[14:40] <Laney> can they handle 4K yet?
[14:44] <Trevinho> ah seb got you idle thing
[14:44] <Trevinho> err, source... (was an idle)
[14:45] <xnox> Laney: works in new account with gnome3 pinentry, with a smartcard, with both gpg1 & gpg2
[14:45] <Laney> bah
[14:46] <xnox> Laney: i have yubikey neo -> it has 2k openpgp card for signing, encryption, authentication (ssh), a separate ECC applet (which should be usable with gpg/ssh, but haven't tried that yet), and it's an U2F key, and it has big (unlimited?!) storage for other OTP tokens, and of cource normal yubikey OTP.
[14:46] <xnox> Laney: so e.g. i tap the yubikey on an NFC enabled phone to generate OTP codes, with no OTP material stored on the phone.
[14:47] <xnox> there is a desktop (qt) app to generate otp codes whilst on the desktop as well.
[14:47] <xnox> should get the ECC thing going though.
[14:48] <xnox> Laney: how is unity8 on the desktop comming along? does it play nice with unity7?
[14:48] <seb128> Trevinho, thanks
[14:48]  * xnox ponders to try it, as all my laptops are touch screen enabled....
[14:49] <Laney> xnox: should be a new session but I can't say I've tried it much
[14:50] <Laney> talk to bregma :P
[14:52] <bregma> xnox, if you just install unity8-desktop-session-mir it works OK, if you use the Ubuntu Personal image that was around for a while, well, don't do that
[14:52] <xnox> bregma: i'm giggling out loud. Ok. =)
[15:05] <Trevinho> seb128: as for the multi-arch support in unity (libunitycore), can you handle that?
[15:05] <seb128> Trevinho, can do yes
[15:05] <Trevinho> thanks
[15:05] <seb128> unsure that's needed though
[15:05] <seb128> yw
[15:06] <Trevinho> I don't think, but since it was listed...
[15:06] <seb128> yeah, I replied on the list saying that it doesn't make much sense for things which are not used for compiling other things
[15:06] <seb128> like having crosscompiling working is good
[15:07] <didrocks> I don't think it's needed
[15:07] <seb128> but some of those are not used
[15:07] <Trevinho> we don't want to be the bad guys... We're Mediterranean, but not bad :D
[15:07] <didrocks> as long as there is no other consumer
[15:07] <seb128> lol
[15:07] <seb128> didrocks, +1
[15:07] <didrocks> and I don't think unity8 is using it
[15:07] <seb128> you would wontfix?
[15:07] <didrocks> and unity-2d is… an empty sad package :p
[15:07] <Trevinho> we don't want to be the bad guys... We're Mediterranean, but not bad :D
[15:07] <seb128> or keep as a wishlist
[15:07] <didrocks> seb128: I would wontfix it
[15:07] <didrocks> with the rationale "no consumer"
[15:08] <Trevinho> we don't want to be the bad guys...
[15:08] <didrocks> Trevinho: it's not about the bad guys, it's about being the *smart* guys :)
[15:10] <seb128> technically we might accept a patch that does that one day in case the lib get other users
[15:10] <seb128> so wishlist ignored for now seems ok
[15:11] <didrocks> yeah, wishlist is ok
[15:11] <didrocks> or "opinion"…
[15:11]  * didrocks runs
[15:11] <Trevinho> Yeah, go for that
[15:11] <Trevinho> My connection got some problems...
[15:12] <Trevinho> slooowwwwwwww
[15:13] <Trevinho> didrocks: yeah, indeed... It was just, you know, not to be the only in list who doesn't do they duties
[15:13] <Laney> https://lists.ubuntu.com/mailman/listinfo/xenial-changes
[15:13] <Laney> gogogogo
[15:13] <Trevinho> their*
[15:13] <seb128> simple git question
[15:13] <Laney> doesn't exist
[15:13] <seb128> I did checkout some remote git, commited 2 revisions, want to push the first one
[15:14] <seb128> do I checkout ^ then push?
[15:16] <pitti> TBH, I never dared to do that
[15:17] <xnox> seb128: git push origin HEAD^:new-name
[15:17] <pitti> I format-patch the top one, git reset --hard HEAD^, git push, git am it bck
[15:17] <pitti> back
[15:17] <didrocks> waow pitti doing it the manual way :)
[15:17] <seb128> xnox, what is ":new-name"?
[15:17] <Laney> test with --dry-run first
[15:17] <xnox> pitti: that is so strange way to do it.... you can just push any commit-id to any location.
[15:17] <didrocks> seb128: remote branch name
[15:17] <pitti> well, checkout just changes the HEAD pointer, I'm not sure that actually influences git push
[15:18] <xnox> seb128: new-name is the branch name, on the other side you want to push to.
[15:18] <didrocks> (trunk or master)
[15:18] <seb128> didrocks, in french? ;-)
[15:18] <Laney> like HEAD^:master
[15:18] <xnox> HEAD^ -> is one commit back from where you are now (HEAD)
[15:18] <seb128> right
[15:18] <pitti> xnox: for the two times I needed it so far it was good enough :)
[15:18] <seb128> can't I just checkout HEAD^ and push with argument?
[15:18] <xnox> and instead of origin you can do things like "lp:...." without actually adding any remotes.
[15:18] <seb128> without
[15:19] <Laney> just test it with --dry-run first
[15:19] <xnox> seb128: well, if you checkout HEAD^, you become "detached" thus not associated to any local branch name, and hence remote branch name cannot be guessed either.
[15:19] <Laney> git push --dry-run origin HEAD^:master
[15:20] <seb128> giving no argument seems to work
[15:20] <seb128> To ssh://git.gnome.org/git/gnome-settings-daemon
[15:20] <seb128>    07c756c..a21ad97  master -> master
[15:20] <pitti> git is easy -- heads, branches, indexes, repositories, origins, detached states, what could possibly be unclear :)
[15:20] <seb128> yeah, indeed
[15:20] <seb128> origin HEAD^:master
[15:20] <xnox> seb128: giving no arguments, would have pushed all commits, rather than just one...
[15:20] <seb128> trivial, I just understand none of the 3 arguments :p
[15:20] <seb128> false, I understand HEAD^
[15:21] <Laney> push the HEAD^ commit to the master branch on origin
[15:21] <pitti> seb128: origin is the shorthand name for the remote repo you are pushing to
[15:21] <pitti> by convention the one you check it out from
[15:21] <Laney> git remote show origin
[15:21] <didrocks> Laney: I doubt what you are telling is helping seb128 if he doesn't have the notion of remotes :)
[15:21] <seb128> Laney, putting the words in another order doesn't make me understand them more, sorry :-/
[15:21] <xnox> seb128: cat .git/config -> should make things more clear as to what "origin" is.
[15:21] <seb128> Laney, I don't understand "origin"
[15:21] <seb128> nor "master"
[15:21] <pitti> seb128: i. e. "git clone <some url>" -> "some url" is the origin
[15:22] <pitti> seb128: and if you "git push origin", you are pushing to <some url> again
[15:22] <seb128> ssh://git.gnome.org/git/gnome-settings-daemon
[15:22] <seb128> then
[15:22] <seb128> k
[15:22] <xnox> seb128: in bzr, you have essentially repository per branch. hence the two are the same. have you ever used shared repositories in bzr?
[15:22] <seb128> xnox, no
[15:22] <pitti> seb128: right, it's really just an alias name for ssh://git...
[15:22] <seb128> and "masters" is the name of the branch?
[15:22] <pitti> seb128: yes
[15:22] <Laney> it's like sometimes I push to :parent in bzr
[15:22] <seb128> can't it default to the one I'm using?
[15:23] <pitti> seb128: right; bzr's :parent is roughly like "origin" in git
[15:23] <Laney> bet it can
[15:23] <xnox> seb128: right, in bzr one can do $ bzr init-repo and then that folder will contain all commit data, and all subfolders/branches under it will have pretty small .bzr folds with just state/info per branch. This way one can have many branches, without duplicating gigs of history.
[15:24] <xnox> seb128: in git, a repository store just the history, and it has a textfile / (files and folder) to store "branches" which are essentially "branchanme -> full commit id" hashmap.
[15:24] <Laney> like "git config push.default current" or something
[15:24] <xnox> seb128: in bzr, all pushes/pulls are essentially 1-to-1 mapping. One branch here, one branch there, and thus that's all there is need to be.
[15:25] <seb128> Laney, that should be default ;-)
[15:25] <xnox> seb128: in git, each repository by default has multiple branches. And so does a local one. Hence $ git push needs to know target location of .git folder (e.g. origin), but also what to push from local repo and where to in the remote repo.
[15:25] <Laney> not sure what the default is
[15:25]  * Laney is paranoid enough to always give the parameters
[15:26] <xnox> seb128: the new mega default is "match current local, and push same name remote, if exists" but that's very recent.
[15:26] <xnox> seb128: in practice one says what to push (local branch name):(remote branch name) (usually the same, but don't have to be) which is called "refspec"
[15:27] <Laney> HAHA
[15:27] <Laney> this is getting too deep
[15:27] <Laney> you need to let git sink in very very slowly
[15:28] <pitti> took me about 2 years to not screw up (most of the time) any more :)
[15:28] <Laney> I once ran git push --mirror
[15:28] <Laney> that was a fuck up
[15:28] <Laney> had an upstream and debian remote in the same checkout
[15:30] <seb128> Laney, I did some tutorial after the team sprint we had before summer and I was ok with the concept
[15:30] <seb128> but didn't use it much since
[15:30] <Laney> nod
[15:30] <Laney> just got to use it some
[15:30] <seb128> and all that is so not natural that I forgot most
[15:31] <Laney> you have yet to find the goodies
[15:31] <seb128> I'm still amazed that's was won mindshares
[15:31] <Laney> like git pull --rebase
[15:31] <Laney> very annoyed bzr doesn't have this now
[15:31] <pitti> "git rebase -i" and "git bisect run" are the two things which really make up for all this pain
[15:31] <seb128> I guess if you do dev it's useful
[15:31] <seb128> if you send a 3 lines patch or do packaging it's not
[15:31] <pitti> yeah, for upstream dev it's great
[15:31] <pitti> even for complex packaging like systemd
[15:32] <pitti> for simple projects or simple packaging it's overkill
[15:33] <Laney> also for simple stuff you don't need to use advanced features
[15:34] <seb128> $ git branch gnome-3-16
[15:34] <seb128> $ git statusSur la branche master
[15:34]  * seb128 scratches head
[15:34] <Laney> you probably wanted checkout
[15:35] <seb128> or did I want to checkout?
[15:35] <Laney> now you get to figure out how to delete a branch :)
[15:35] <seb128> grrr
[15:35] <seb128> did I create a branch now?
[15:35] <seb128> :(((
[15:35] <seb128> rm -r
[15:35] <seb128> git clone
[15:35] <seb128> there we go
[15:35] <Laney> NO
[15:35] <Laney> LEARN!
[15:35] <seb128> been there
[15:35] <seb128> I don't feel safe
[15:35] <pitti> right
[15:35] <seb128> I'm sure I'm going to screw things
[15:35] <pitti> better start from scratch if you're unsure
[15:35] <pitti> I screwed up so many times in the beginning it was safer to do something like "git diff > /tmp/p", re-checkout, and start over
[15:36] <Laney> that was a trivial problem to fix
[15:36] <pitti> yes, it was (git branch -D gnome-3-16)
[15:36] <seb128> why is git status not telling me I created branches?
[15:36] <Laney> you could have learned how to delete a branch
[15:36] <seb128> how do I know what I messed up if status doesn't tell me?
[15:36] <pitti> but for remotes which don't allow push --force, it's a real nuisance if you screw up
[15:37] <seb128> so if I checkout gnome-3-18
[15:37] <seb128> cherry pick
[15:38] <seb128> then I need to push origin gnome-3-18?
[15:38] <pitti> there's some magic with "--track" which does that by default
[15:39] <pitti> but better ask someone who's more familiar with that
[15:39] <pitti> normaly, "git push" should already push it to the same remote barnch
[15:39] <pitti> if not, it should tell "please run git bla bla track blabla"
[15:39] <pitti> then do that, and git push should DTRT
[15:40] <seb128> $ git push --dry-run
[15:40] <seb128> To ssh://git.gnome.org/git/gnome-settings-daemon
[15:40] <seb128>    753c48a..8419dac  gnome-3-18 -> gnome-3-18
[15:40] <seb128> seems so
[15:40] <seb128> let's see :p
[15:40] <didrocks> yep
[15:40] <pitti> ok, so it's already configured to track the remote branch
[15:40] <didrocks> pitti: you have name-by-name matching (and remote transport)
[15:43] <seb128> seems to have worked
[15:43] <seb128> didrocks, pitti, Laney, xnox, thanks
[15:43] <seb128> I did end up doing branch -D gnome-3-16 at the end
[15:44] <seb128> hope I didn't screw anything
[15:44] <seb128> https://git.gnome.org/browse/gnome-settings-daemon/log/?h=gnome-3-16 looks fine
[15:44] <Laney> https://git.gnome.org/browse/gnome-settings-daemon/commit/?h=gnome-3-16&id=e9c249bb4fb99766e0d1e4d087ca39a33922a4bc
[15:44] <Laney> \o/
[15:45] <Laney> *** the world ends ***
[15:50] <seb128> lol
[15:50] <seb128> Laney, I'm sure you get used to git, still feels like an aweful tool to use :-/
[15:51] <seb128> it's a bit annoying that it's what most project ask contributors to work on, way to raise the entry barrier
[15:51] <seb128> but oh well, that's a lost battle so no point arguing over this one
[15:51] <seb128> maybe it 15 years or so there is a next wave of inovation and we get a decent tool out of it ;-)
[15:52] <mdeslaur> seb128: you just need to read the manpages carefully: http://git-man-page-generator.lokaltog.net/
[15:52] <seb128> lol
[15:53] <seb128> the fun part is that it throws random uncomprehensible manpages to me and I've no clue if those are made up of random things and making no sense or actual git commands ;-)
[15:54] <seb128> "git-call-pathcall the unstaged paths to any reset objects"
[15:54] <seb128> if you say so :p
[16:02]  * pitti waves good night
[16:04] <seb128> pitti, night!
[16:04] <seb128> pitti, happy wily celebration ;-)
[16:08] <willcooke> cheers pitti
[16:41]  * didrocks goes off, see you guys on Monday!
[16:46] <Trevinho> Leaving too
[16:46] <seb128> Trevinho, have fun!
[17:09] <willcooke> g'night all
[17:35] <andyrock> g'night all!
[18:51] <BigWhale> So, are there any issues with restoring windows after screen unlock in 15.10? My windows are restored and resized somewhat randomly between desktops and physical screens and I think it has to do something with my new 4K display.
[19:03] <BigWhale> Apparently, this bug is bugging me: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295267 :)
[19:23] <sarnold> BigWhale: wild-ass guessing here, do the monitors come up in a different order in xrandr output before vs after sleep?
[19:24] <sarnold> BigWhale: maybe make a habit of ollecting xrandr output before leaving and after returning to look for patterns
[19:27] <BigWhale> sarnold, I've tried leaving them to go to sleep and then waking up the computer, but it seems that I need more time.
[19:27] <BigWhale> Setting the sleep timeout to one minute wasn't enough.
[19:28] <BigWhale> sarnold, but you might be onto something, yeah.
[19:44] <BigWhale> hm, xrandr output doesn't change even when screens are turned of and then back on and off and on... Windows are still displaced.