[02:40] <duflu_> Does anyone know how errors.ubuntu.com works? It seems to only match stack traces to depth 4. Is that correct?
[06:35] <pitti> Good morning
[06:35] <pitti> duflu: should be the topmost 5, if it's using the same algorithm as apport
[06:36] <duflu> pitti: OK, hmm...
[06:36] <duflu> I wonder if that's enough
[07:04] <didrocks> morning
[07:17] <pitti> bonjour didrocks, ça va ?
[07:17] <didrocks> pitti: ça va bien, c'est vendredi ! et toi ? :)
[07:17] <pitti> didrocks: je suis d'accord, merci; j'ai dormi très bien
[07:59] <seb128> good morning desktopers!
[08:35] <willcooke> g'morn
[08:37] <didrocks> hey willcooke
[08:39] <seb128> hey willcooke
[08:39] <seb128> how are you?
[08:40] <willcooke> What is the point of Reddit?
[08:40] <willcooke> it just seems to be a forum for people to make things up and pass it off as fact.
[08:40] <seb128> sink your productivity on the internet? ;-)
[08:40] <willcooke> the Ubuntu things are 99% BS
[08:40] <willcooke> I want to reply but... no actually, I don't
[08:49] <willcooke> https://bugs.launchpad.net/mir/+bug/1324101
[08:49] <willcooke> \o/
[08:49] <willcooke> larsu, relevant to your interests I expect ^^
[08:51] <larsu> indeed :)
[08:51] <larsu> morning willcooke!
[09:04] <Laney> ahoy
[09:05] <didrocks> hey Laney!
[09:05] <larsu> happy Friday Laney!
[09:05] <Laney> happy friday!
[09:08] <seb128> hey Laney, wie gehts?
[09:15] <Laney> hey seb128
[09:15] <Laney> feeling good!
[09:15] <Laney> quality climbing session last night
[09:15] <seb128> great!
[09:15] <Laney> what about you?
[09:15] <seb128> doing good
[09:15] <seb128> it's friday!
[09:32] <seb128> that is a weird bug
[09:32] <seb128> that happens sometime, not sure what to blame, video driver, xorg, toolkits, ...
[09:32] <seb128> http://people.canonical.com/~seb128/bug.png
[09:33] <seb128> letters get missing in text, happens in most apps and is random, sometime on refresh they show and then hide again
[09:55] <willcooke> seb128, ?!?!?!?!?
[09:55] <seb128> willcooke, exactly...
[09:55] <willcooke> seb128, are you reading the matrix?
[09:55] <seb128> lol
[09:56]  * didrocks lost his ^
[09:56] <didrocks> they are going to an unfocussed window!
[09:56] <didrocks> a gnome-terminal one
[09:56] <willcooke> I'd think it was a tk issue, I think if it was a video driver thing it would be more broken
[09:57] <didrocks> I wonder if this isn't a gnome-terminal issue
[09:57] <didrocks> Laney: ^
[09:57] <didrocks> between 2 g-t
[09:58] <Laney> lost his what?
[09:58] <Laney> sorry I don't understand what you are saying
[10:00] <seb128> Laney, I guess he means the "^" key?
[10:00]  * seb128 is unsure as well
[10:01] <didrocks> Laney: so, all keys were going to the current gnome-terminal
[10:01] <didrocks> as you can expect
[10:01] <didrocks> but ^ keystrokes were sent to another gnome-terminal window
[10:01] <didrocks> happened twice since this morning
[10:03] <Laney> not heard of that
[10:03] <Laney> how can I make it happen?
[10:03] <didrocks> yeah, that's the part I'm unsure
[10:03] <didrocks> if I change the focused windows, then, it resets
[10:12] <Laney> try using shell for a bit or something to rule in/out the WM
[10:13] <didrocks> Laney: nice idea, will do that
[10:14] <didrocks> (not now, getting rules to get Touch booting on systemd)
[10:17] <darkxst> didrocks, Laney, I've heard of wierd focus issues but it involves non-standard settings
[10:18] <didrocks> it's still weird it's only one key though
[10:18] <didrocks> not the others
[10:18] <darkxst> didrocks, only one key gets sent to the wrong window?
[10:19] <darkxst> that is incredibly strange
[10:20] <didrocks> right
[10:20] <didrocks> it was the same twice
[10:20] <didrocks> all the other ones worked
[10:25] <darkxst> didrocks,  no idea then
[10:27] <darkxst> the reports I have heard all keyboard input goes to the wrong windo, but on;y when diabling window modifier key binding (i thing)
[10:35] <didrocks> I didn't disable it here, so not that one :/
[10:56] <darkxst> didrocks, my best guess is the unity key grabber, is messing up somewhere
[10:57] <didrocks> can be
[10:57] <didrocks> will see first if I can reproduce it more than twice
[11:31] <willcooke> desrt, http://www.bbc.co.uk/news/science-environment-30784886
[16:27] <Chipaca> what can make 'quilt push -a' work, but bzr-buildpackage fail complaining about fuzz and reversed patches?
[16:27] <didrocks> Chipaca: bzr bd is more restrictive than quilt pushing
[16:28] <didrocks> Chipaca: so in that can, quilt push <the patch that has fuzz>
[16:28] <didrocks> quilt refresh
[16:28] <didrocks> bzr commit, blablabla
[16:28] <Chipaca> quilt refresh says no changes
[16:28] <didrocks> the amount of fuzz it accepts it stricter
[16:28] <didrocks> is*
[16:28] <didrocks> bzr diff?
[16:28] <Chipaca> there is no fuzz, no diff, no status
[16:28] <didrocks> hum, that's weird, do you have the branch?
[16:29] <Chipaca> i'll pastebin the session because i wouldn't believe it myself
[16:29] <Chipaca> ah, sure, let me push it
[16:29] <didrocks> let me see if I reproduce first :)
[16:29] <didrocks> I remember having spent quite some time due to that
[16:29] <Laney> if you forget to edit with 'quilt edit' or similar
[16:29] <didrocks> but generally, it was just because of what I explained above
[16:29] <Chipaca> didrocks: lp:~chipaca/ubuntu-push/fix-1376282-for-rtm
[16:30] <Chipaca> Laney: this is a cherry pick, onto a project that didn't have patches before
[16:30] <Chipaca> it's the first distro-patch
[16:31] <Chipaca> Laney: so i did 'quilt import' to the patch
[16:31] <Chipaca> i have no idea if any of that is relevant to the problem :)
[16:31] <Laney> or if a file is directly edited before you then use quilt on it
[16:32] <Laney> so quilt and dpkg-source get different ideas about the before state
[16:32] <Laney> you can probably not use quilt for this branch though and just cherry-pick directly - I think that's usualy for rtm branches
[16:33] <Laney> s/usualy/usual/
[16:33] <Laney> kenvandine: confirm/deny ?
[16:33]  * kenvandine reads
[16:34] <kenvandine> i'd say just cherry pick for rtm branches
[16:34] <kenvandine> instead of quilt
[16:35] <Chipaca> Laney: kenvandine: my perhaps misguided idea was that i could use quilt to make keeping the base tree in sync easier
[16:35] <Chipaca> ie the tree without the patches is exactly a given revno of upstream
[16:35] <kenvandine> i think quilt is going to just make it harder
[16:36] <didrocks> yeah, the workflow with package branch is to be able to bzr merge from upstream
[16:36] <didrocks> that avoid those quilt issues
[16:36] <kenvandine> imo quilt makes most things harder :)
[16:36] <Chipaca> well, it has, but at least now i feel less bad about it :D
[16:40]  * Chipaca throws away quilt and does what he knows
[16:40] <didrocks> Chipaca: yeah, I'm getting failures with LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B .pc/info-loglevel.diff/ --reject-file=- < debian/patches/info-loglevel.diff
[16:41] <didrocks> Chipaca: really, the whole "release from branch" is about bzr merge upstream to your branch
[16:41] <didrocks> Chipaca: so I would really go with this :)
[16:41] <Chipaca> didrocks: I don't know what “the whole "release from branch"” even *is*, but i know bzr and am not afraid to use it
[16:42] <didrocks> Chipaca: if your branch has been properly bootstraped, just bzr merge :)
[16:42] <didrocks> if not, complain to #ubuntu-ci-eng ;)
[16:43] <Chipaca> also, also, schroot on shm + my little python .deb cache on shm [16:43] <didrocks> nice!
[16:49] <willcooke> unlol:  https://github.com/ValveSoftware/steam-for-linux/issues/3671
[16:50] <seb128> that's a fail indeed
[16:52] <didrocks>  rm -rf "$STEAMROOT/"*
[16:52] <didrocks> oh come on!
[16:52] <didrocks> I thought that would only happen at "professionals", I have names! :p
[16:52] <andyrock> seb128, do you know who should I ping on #gtk+ to get some info about GtkIconTheme
[16:52] <andyrock> ?
[16:53] <didrocks> willcooke: where it happened, it was on the company vcs-like (all very centralize) machines :p
[16:54] <willcooke> :/
[16:55] <seb128> andyrock, no, but maybe larsu or desrt can help you
[16:56] <andyrock> larsu, desrt http://paste.ubuntu.com/9762431/
[16:56] <seb128> larsu, thanks
[16:56] <seb128> andyrock, he replied on gtk
[16:56] <larsu> andyrock: you're not very patient ;)
[16:56] <andyrock> :D
[16:57] <andyrock> seb128, larsu that's what is causing the '?' icon bug in vivid
[16:58] <seb128> k
[16:59] <seb128> why are icons queried differently on first start and later?
[17:01] <andyrock> seb128, not sure
[17:01] <andyrock> seb128, Trevinho should know more
[17:06] <andyrock> larsu, thanks using lookup_icon should work just fine in bamf
[17:06] <larsu> andyrock: ya. Seems to me that has_icon() is pointless anyway
[17:06] <larsu> especially for bamf's use-case
[17:12] <xnox> pitti: i look how upstart handles -1 from fork() call -
[17:12] <xnox>         /* Goodbye, cruel world. */
[17:12] <xnox>         exit (signum);
[17:13] <pitti> xnox: heh
[17:13] <pitti> xnox: well, at that poitn pretty much everything is lost, I figure :)
[17:15] <xnox> pitti: well documentation is EAGAIN, spawning jobs it does loop until fork >= 0
[17:15]  * xnox needs lunch
[17:15] <didrocks> xnox: EAGAIN had_lunch >=0 :p
[17:16] <didrocks> xnox: sounds weird to not fail in that case though and looping retrying forking
[17:18] <pitti> xnox: well, when it happens in a generator, I think it's safe to abort -- if you can't fork during boot, you are busted anyway
[17:36] <didrocks> EOW! have a nice week-end guys :)
[17:49] <willcooke> EOW - party hearty
[17:49] <willcooke> toodles
[18:03]  * Laney relocates downstairs to finish watching The Tunnel :O