[05:12] <larsu> bonjour!
[05:45] <pitti> bonjour larsu!
[05:45] <larsu> hi pitti! Wie gehts?
[05:53] <pitti> larsu: ganz gut, danke! Erkaeltung auf dem Rueckzug :) und dir?
[06:15] <didrocks> good morning
[06:20] <pitti> bonjour didrocks
[06:22] <didrocks> hey pitti, how are you?
[06:27] <pitti> didrocks: much better, thanks! how about yourself?
[06:33] <didrocks> pitti: did a long run yesterday evening (20kms in total). Exhausted and didn't really felt well in the end
[06:33] <didrocks> but much better today :)
[06:33] <pitti> didrocks: woow!
[06:33] <pitti> didrocks: so your knees really seem back in top shape, good to hear!
[06:34] <didrocks> pitti: yeah, well… they mandate stretching and I can feel them a little bit, but overall they are good :)
[07:02] <seb128> good morning desktopers
[07:05] <didrocks> re seb128
[07:42] <larsu> pitti: oh, gute Besserung! Jetzt nach dem Frühstück gehts mir auch gut :)
[07:55] <willcooke> o/
[07:55] <didrocks> morning willcooke
[07:56] <larsu> hi willcooke
[08:05] <Laney> hey hey
[08:06] <seb128> hey willcooke Laney
[08:06] <seb128> how is u.k today?
[08:06] <willcooke> Sunny!
[08:06] <didrocks> morning Laney
[08:06] <didrocks> willcooke: photo or it didn't happen!
[08:06] <willcooke> ha!
[08:06] <larsu> hi Laney!
[08:06] <seb128> he's clearly trolling
[08:06] <willcooke> My lies have been unveiled
[08:06] <seb128> but it's not friday yet!
[08:06] <didrocks> ahah
[08:07] <didrocks> seb128: not friday?
[08:07] <didrocks> WAT?
[08:07] <didrocks> :)
[08:07] <seb128> :-)
[08:07] <willcooke> Proof:  http://tinyurl.com/qfxua94
[08:07] <didrocks> tssssss
[08:07] <didrocks> well done
[08:08] <willcooke> oh, btw seb128 - once you get the Snappy image started TheMuso has offered to help.
[08:08] <seb128> oh, nice
[08:09] <willcooke> We had a chat last week, but we're not 100% sure what he can do, but he's keen to get involved
[08:09] <willcooke> so we'll work it out as we go
[08:09] <seb128> k
[08:21] <pitti> hmm, any news wrt. fixing shotwell? this has sat in -proposed for quite a while and holds up the libgphoto transition
[08:21] <pitti> it also has a block-proposed tag
[08:22] <pitti> perhaps we could remove it from -proposed for the time being, and reupload a fixed version once the issues with the window border got fixed?
[08:23] <Laney> just saw Robert's reply
[08:23] <Laney> does that mean he's not working on fixing it?
[08:24] <seb128> Laney, pitti, didn't he upload a fix yesterday?
[08:25] <pitti> seb128: ah, then not for the test
[08:25] <Laney> I didn't notice the version, just that the test still doesn't pass
[08:25] <seb128> what test?
[08:25] <seb128> no, I don't think he's aware there is a test issue
[08:25] <pitti> http://d-jenkins.ubuntu-ci:8080/job/wily-adt-shotwell/28/ARCH=amd64,label=adt/console
[08:25] <seb128> he uploaded a fix for the decoration
[08:26] <pitti> he should have gotten a CI notification
[08:26] <pitti> autopilot.exceptions.StateNotFoundError: Object not found with name 'GtkToolButton' and properties {'label': 'Import _All'}.
[08:26] <seb128> right
[08:26] <pitti> I suppose the new upstream version changed the layout or button naming or something similar
[08:26] <seb128> but jenkins often sends noise
[08:26] <seb128> so knowing robert I wouldn't be surprised if he just assumed that was noise
[08:27] <seb128> I can have a look if you want
[08:27] <pitti> that would be great; unless it's a complete rearrangement of the UI, I suppose updating the button label already ought to suffice
[08:27] <seb128> k, let me look
[08:28] <pitti> merci !
[08:28] <pitti> good to know that the header bar issue is fixed now (the block-proposed bug)
[08:32] <pitti> seb128: btw, run it against wily, not wily-proposed; it could be that the wily-proposed libgphoto2 also breaks the test (the umockdev record might need updating), that's something I can do
[08:32] <pitti> but it started failing with the old libgphoto (the button name issue)
[08:32] <seb128> pitti, ok
[08:44] <larsu> Laney: my terminal profiles stopped working again :(
[08:45] <larsu> do you know anything about that?
[08:45] <Laney> no
[08:45] <Laney> what command?
[08:45] <larsu> gnome-terminal --app-id de.uebernic.terminals.irssi --profile=Irssi
[08:45] <larsu> in a .desktop file
[08:45] <Laney> OH
[08:45] <larsu> but unity doesn't recognize it as a separate app
[08:46] <Laney> it still launches?
[08:46] <larsu> yes, launches correctly
[08:46] <Laney> I think I broke the app-id thing
[08:46] <Laney> I thought that it didn't work
[08:46] <larsu> but the terminal launcher item is highlighted
[08:46] <larsu> you did
[08:46] <larsu> _GTK_APPLICATION_ID(UTF8_STRING) = "org.gnome.Terminal"
[08:46] <Laney> so I was like fuck this shit it doesn't work why even have this
[08:46] <Laney> and deleted some code
[08:47] <Laney> :)
[08:47] <larsu> ...
[08:47] <larsu> we have this for nice people like didrocks (and me)
[08:47] <didrocks> larsu: "very" nice
[08:47] <didrocks> please
[08:47] <Laney> if you put --disable-factory in there does it work?
[08:47] <larsu> didrocks: sorry. exceptionally nice
[08:47] <didrocks> :)
[08:48] <Laney> I think I have to make --app-id do the custom terminal server thing too
[08:48] <larsu> Laney: ya. It even sets the correct app-id in that case
[08:48] <Laney> indeed
[08:48] <larsu> where did you make that change? In the wrapper?
[08:48] <Laney> yes
[08:49] <larsu> can you pretty please revert it?
[08:49] <Laney> I forgot the case where people have their own .service files
[08:49] <Laney> no
[08:49] <Laney> I'll fix it but it won't be a revert
[08:49] <larsu> right, fine by me :)
[08:49] <larsu> need help?
[08:49] <Laney> nope
[08:49] <larsu> thanks!
[08:50] <Laney> argh
[08:50] <Laney> vim-youcompleteme has somehow broken
[08:51] <Laney> 9999 errors when doing almost anything
[08:52]  * Laney installs it via the archive instead, works again
[08:52] <larsu> what's that?
[08:52] <Laney> omnicomplete thing
[08:52] <larsu> ah
[08:52] <Laney> https://github.com/Valloric/YouCompleteMe/blob/master/README.md
[08:54] <larsu> seems much more elaborate thatn the built-in completion
[08:54] <Laney> ya it's nice
[08:54] <Laney> I didn't set up the clang stuff yet
[08:54] <Laney> but the non smart completion is already pretty ok
[09:04] <Laney> larsu: can you share a g-t .service file?
[09:05] <darkxst> Laney, hey, what about gnome-system-monitor you were talking about last night?
[09:07] <Laney> hi darkxst
[09:07] <Laney> you got a review on your no headerbar patch
[09:08] <larsu> Laney: sure http://paste.ubuntu.com/11387868/
[09:09] <Laney> ta
[09:09] <Laney> I hope dbus is watching this directory and I don't have to restart or anything
[09:09] <darkxst> Laney, I though that was already upstream? certainly did not get an email of review though
[09:10] <darkxst> Laney, not going looking though, having a break atm
[09:10] <Laney> nm, I will fix it, simple enough
[09:15] <darkxst> Laney, I'm just a little overloaded with everything atm, legal battles, working almost for slave labour and trying to finish my thesis, might not be around much this cycle
[09:18] <Laney> darkxst: OK, no worries, take care of your stuff
[09:19] <Laney> We will go 3.16 with most things, hopefully Noskcaj or someone can do shell & friends
[09:19]  * Laney donates to the darkxst defense fund
[09:21] <Laney> larsu: try lp:~ubuntu-desktop/gnome-terminal/ubuntu please?
[09:21] <darkxst> Laney, that should be offense fund, $700AUD per/hour ;( just to fight my ex for what I deserved
[09:22] <darkxst> its not like I am in trouble with the law, lol
[09:22] <Laney> oh right!
[09:26] <larsu> Laney: getting a debsign error
[09:26] <larsu> usually that's a warning and it build the package anyway
[09:27] <Laney> pass -us -uc
[09:28] <larsu> I guess with a -- when using bzr bd?
[09:28] <Laney> I always forget if you need that or not :(
[09:28] <larsu> I did and it worked, thanks
[09:28] <Laney> I have DEBUILD_DPKG_BUILDPACKAGE_OPTS="-us -uc" in ~/.devscripts
[09:29] <larsu> I had this at some point... not sure what happened
[09:30] <didrocks> yeah you need -- as you pass parameters to dpkg-buildpackage
[09:30] <larsu> Laney: anyway, package works like a charm. Thanks for the quick fix!
[09:31] <larsu> didrocks: it's a bit weird, because usually "--" means "the rest of the args are file names"
[09:31] <didrocks> larsu: hum, not for quite some commands, it's more "pass those parameters to anything we spawn" when you use a wrapper
[09:32] <darkxst> larsu, no usualy "--" mean the rest of the args are passed through to the underlying process
[09:32] <Laney> git-buildpackage doesn't need it
[09:32] <Laney> so I get confused
[09:35] <larsu> apparently it means verious things then :)
[09:35] <Laney> also I'm getting extreme packet loss to and on this VPS
[09:35] <darkxst> git-buildpackage namespaced their own commands, so they don't need it
[09:35] <Laney> 56 packets transmitted, 5 received, 91% packet loss, time 55281ms
[09:35] <didrocks> Laney: but 91% of them were bad, it's some kind of jungle life, only the strongest resists :)
[09:35]  * Laney moves to the hood
[09:35] <darkxst> larsu, never heard your arguments about filenames before
[09:35] <darkxst> but generally the stuff after "--" gets passed straight through the wrapper script to the actual process
[09:40] <larsu> darkxst: git works that way, as do most gnu utilities
[09:40] <larsu> `rm -- -f` removes a file named -f
[09:40] <Laney> larsu: thanks for testing, will upload this fix along with gnome-terminal 3.16 probably
[09:40] <larsu> thanks
[09:40] <Laney> should be this week
[09:40]  * Laney checks if it requires *cough*
[09:40] <larsu> works for me - I'll just continue using this package until then
[09:40] <Laney> 3.10 \/ o \/
[09:40] <darkxst> larsu, I suspect in that case rm get passed those arguments directly, the only thing you win is not having to quote the -
[09:41] <larsu> darkxst: this is not a feature of the shell. rm needs to pass the single -- itself. It simply doesn't interpret anything following the -- as an argument anymore
[09:41] <larsu> but yeah, you don't gain much
[09:42] <Laney> oh I lost my connection to $other_irc_network
[09:42]  * Laney plays the "find the window irssi is outputting status messages to" game
[09:42] <larsu> Laney: 1?
[09:42] <Laney> I don't have a status window
[09:43] <Laney> it's window 50 this time!
[09:43] <larsu> oh can you close that?
[09:43]  * larsu always leaves it open at 1
[09:43] <Laney> I probably did this 10 years ago
[09:43] <Laney> but yes, somehow
[09:43] <larsu> haha
[09:43] <Laney> Authentication failure
[09:43] <Laney> great
[09:44] <darkxst> larsu I did not say that was a feature of the shell
[09:45] <larsu> darkxst: it sounded like it when you said "rm gets passed those arguments"
[09:45] <larsu> Laney: new pw?
[09:47] <darkxst> larsu it gets a string deprive of shekl globbing and what not
[09:47] <darkxst> shell
[09:48] <larsu> right, but -- is not part of that
[09:48] <darkxst> the majority of wrapper scripts then pass the straight though
[09:49] <darkxst> but really I don't care to argue on this, I supposed to be taking a break
[09:49] <Laney> ffs
[09:59] <larsu> Laney: do you see overshoots? I only get undershoots...
[09:59] <larsu> (which are the ones that signify more content)
[10:00] <Laney> I don't think they have a default style, or at least a noticable one
[10:00] <larsu> in Adwaita, I mean
[10:00] <larsu> ah! You only get them when using a touchpad
[10:00] <larsu> neat :)
[10:01] <Laney> I see it when using the mouse wheel
[10:01] <larsu> I don't see it when using trackpoint+middle button
[10:01] <Laney> but not page up or the arrows
[10:01] <larsu> anyhow, almost done with that
[10:01] <Laney> I can make it quite big using the touchpad though
[10:01] <Laney> which looks neat
[10:01] <larsu> also, link colors
[10:01] <Laney> nice
[10:02] <Laney> theme fixes \m/
[10:02] <larsu> if you want to review
[10:02] <Laney> I do
[10:02] <Laney> do you have a link to the yelp bug too?
[10:03] <larsu> yep https://bugzilla.gnome.org/show_bug.cgi?id=749947
[10:03] <ubot5> Gnome bug 749947 in General "Background uses "active" color from the theme" [Normal,New]
[10:03] <Laney> merci!
[10:19] <larsu> Laney: orange or grey overshoot?
[10:19] <larsu> I think I'm leaning towards grey
[10:19] <larsu> orange is a bit too much
[10:19] <Laney> don't know ...
[10:21] <larsu> turns out you're not a designer either?!
[10:21] <Laney> maybe there's a grey-ish orange
[10:21] <seb128> what is that overshoot you are talking about?
[10:21] <Laney> new gtk feature
[10:21] <Laney> tells you if you scroll too far
[10:21] <larsu> like on androind
[10:22] <Laney> http://www.colourlovers.com/color/C5793B/Grayish_orange
[10:22]  * larsu goes to meet dholbach for lunch. see you in a bit!
[10:22] <Laney> is it weird to use a new kind of orange?
[10:22] <Laney> oh ok, have fun!
[10:22] <larsu> Laney: I'd like to not introduce new colors if possible
[10:23] <Laney> ok let's get a designer to decide
[10:23] <seb128> larsu, say hello to Daniel and have fun:
[10:23] <seb128> !
=== sabdfl_ is now known as sabdfl
=== tsdgeos_ is now known as tsdgeos
=== strycore_ is now known as strycore
=== alan_g is now known as alan_g|lunch
[12:16] <larsu> Laney: decided on a slightly darker @bg_color for now (same as separators and grid lines)
[12:16] <larsu> and got rid of the complications from Adwaita
[12:17] <larsu> they have two gradients, which I copied at first
[12:17] <larsu> but I think I like this subtler one more
[12:20] <larsu> desrt: morning. Didn't you say that gnome-terminal-the-launcher should block until the tab/window that was opened finished?
[12:20] <larsu> because it doesn't do that currently
[12:21] <desrt> it should, indeed
[12:21] <larsu> okay. I'll have a look why it doesn't
[12:22] <desrt> huh.  you're right.
[12:22] <larsu> I wonder if any application should behave that way?
[12:22] <larsu> or should the launcher simply activate?
[12:22] <desrt> gedit should....
[12:22] <desrt> on account of 'EDITOR=gedit git commit'
[12:22] <larsu> right, but ... devhelp? epiphany?
[12:22] <larsu> I'm not so sure...
[12:22] <desrt> those ones, no
[12:22] <desrt> definitely not, in fact
[12:23] <larsu> ugh
[12:23] <larsu> now it
[12:23] <desrt> gedit and gnome-terminal are 'special'
[12:23] <larsu> now it's inconsistent
[12:23] <desrt> editors have an implicit relationship with things that have executed them
[12:23] <desrt> particularly in context of $EDITOR
[12:23] <desrt> 'normal apps' don't have this relationship
[12:24] <larsu> terminals do as well?
[12:24] <desrt> gnome-terminal is special because, well, it seems to want to emulate xterm insofar as is possible
[12:24] <desrt> i actually don't care about that case as much, but i thought that chpe did
[12:25] <larsu> apparently not
[12:25] <larsu> smoser does, though
[12:25] <desrt> so smoser can fix it? :)
[12:27] <larsu> well, I wonder what's the right behaviour now..
[12:28] <desrt> i'd argue that the current behaviour is the right behaviour
[12:28] <desrt> APIs and all that jazz
[12:28] <larsu> apparently it changed
[12:28] <desrt> my argument about gedit, for example, is based entirely on the (loose) API expected of $EDITORs
[12:28] <larsu> and man, you know the hoops we're jumping through (well, Laney is) to keep cmd line api
[12:28] <desrt> so now you have the issue of deciding if compatibility with the last 6 months is more important than compatibility with the 5 years before it
[12:29] <desrt> we had this problem in glib once, by accident
[12:29] <desrt> wasn't pretty
[12:29] <desrt> accidentally changed the ABI of GStaticMutex on ARM and didn't notice it for a year
[12:29] <desrt> so it was like "well... we could put it back, but then we'd break everything that was compiled in the last year...."
[12:30] <desrt> and it was just at a time that ARM was exploding in popularity
[12:30] <desrt> we chose to stick with the new incompatible choice... in your case maybe the old incompatible choice makes sense
[12:32] <larsu> not sure
[12:34] <larsu> according to him, this changed in 12.04 with the switch to the client/server model
[12:35] <larsu> so, quite a while
[12:40] <larsu> desrt: apparently there's a "new client": https://bugzilla.gnome.org/show_bug.cgi?id=745282
[12:40] <ubot5> Gnome bug 745282 in general "Add --wait option to wait for terminal to close" [Enhancement,New]
[12:40] <larsu> where they have a --wait for this purpose
=== alan_g|lunch is now known as alan_g
=== mzanetti is now known as mzanetti|otp
=== mzanetti|otp is now known as mzanetti
=== lifeless_ is now known as lifeless
=== rickspencer3_ is now known as rickspencer3
[16:27] <attente> hi, how do you propose changes to the ubuntu mainline kernel?
[16:29] <didrocks> attente: I guess just go to #ubuntu-kernel for this and ask apw
[16:30] <attente> didrocks: thanks
[16:30] <didrocks> yw
=== alan_g is now known as alan_g|EOD
[17:14] <Laney> climbing time
[17:14] <Laney> laters!
[17:27]  * willcooke -> EOD
[20:01] <Noskcaj> Is anyone planning to do the webkit2gtk transition/MIR? I'm pretty sure it would mean ubuntu seeding geoclue-2.0 though
[20:02] <Laney> Noskcaj: I don't think anyone is really expecting to spend time on that this cycle
[20:02] <Laney> what requires it?
[20:03] <Noskcaj> devhelp and anjuta both just changed to it in debian and are stuck in proposed as a result. I was just wondering what the plans for it are
[20:04] <Laney> I'd be up for the transition but don't know if I have space to work on geoclue-2.0
[20:05] <Laney> Maybe we could turn that off?
[20:11] <sarnold> Noskcaj: and note that security team loooooves blink and is unlikely to accept a second webkit thingy into main.
[20:13] <Laney> We'd be wantin to move to wbekit2gtk
[20:13] <Laney> hey, my touch typing is worse than I thought
[20:15] <Noskcaj> Ok. Would it be worth merging devhelp with it using webkitgtk so we can get 3.16?
[20:15] <Laney> sure
[20:18] <mdeslaur> we could also perhaps drop devhelp to universe
[20:19] <pmcgowan> bregma, fwiw I am losing my indicator panel a lot suddenly today on vivid desktop
[20:20] <bregma> pmcgowan, we haven't released any changes into vivid, but losing your Panel usually means unity-panel-service or compiz is crashing
[20:20] <pmcgowan> bregma, panel-service
[20:20] <Noskcaj> mdeslaur, A few things in main have a recommends on it, but that might be the easier way
[20:21] <bregma> u-p-s usually crashes because of an indicator plugin
[20:21] <pmcgowan> not sure why but lost it 3 times in a couple hours
[20:21] <pmcgowan> might be xchat notices
[20:21] <jdstrand> Noskcaj, Laney:I'll just also put it out there that the purpose of oxide is to allow the chromium content api to get regular updates while the api to apps doesn't change. someone working on gtk[23] for oxide (we currently have qt5) would likely help everyone in the long run
[20:21] <pmcgowan> but nothing changed Id thin
[20:21] <pmcgowan> k
[20:22] <jdstrand> s/gtk\[23\] for oxide/gtk[23] bindings for oxide/
[20:23] <jdstrand> obviously that isn't a short term thing, but it can neatly solve the maintenance problem for consumers of a web engine
[20:24] <jdstrand> if people are interested in that, I suggest joining oxide@lists.launchpad.net
[21:06] <Noskcaj> bug 1459434 has the patch
[21:06] <ubot5> bug 1459434 in devhelp (Ubuntu) "devhelp now requires webkit2gtk, which is not in main" [Undecided,New] https://launchpad.net/bugs/1459434
=== _thumper_ is now known as thumper
[22:06] <Noskcaj> Laney, Can you please take a look at merging tracker some time soon? It's the only package that needs to depend on the new libmediaart that isn't on the sponsors queue
[22:32] <Laney> Noskcaj: I'm doing all my merges, it'll get done
[22:33] <Laney> feel free if you want it done faster
[22:33] <Laney> I'm patch piloting tomorrow so ... ;)