[06:36] <pitti> Bonjour tout le monde !
[06:41] <didrocks> hey pitti!
[06:41] <didrocks> how are you ?
[06:41] <pitti> didrocks: bonjour !
[06:42] <pitti> didrocks: quite tired TBH, it was a long night :)
[06:42] <pitti> so many heart attacks
[06:42] <larsu> hi didrocks and pitti!
[06:42] <pitti> larsu: Alter!
[06:42] <didrocks> hey larsu :)
[06:42] <didrocks> pitti: who won at the end ?
[06:42] <didrocks> will we meet you guys ?
[06:42] <pitti> I got up at an outright "normal" time at 8:30 :)
[06:42] <darkxst> hey pitti , didrocks larsu
[06:43] <pitti> didrocks: yes, we will; we won 2:1, but don't ask how :)
[06:43] <larsu> hi darkxst!
[06:43] <didrocks> morning darkxst
[06:43] <pitti> didrocks: so, the big showdown on Friday
[06:43] <didrocks> pitti: ahah, ok, I won't, I'll just say "nice" :)
[06:43] <pitti> didrocks: FRA : GER Friday 18:00 I mean
[06:43] <didrocks> yeah ;)
[06:43] <didrocks> I'm still sure I won't watch it TBH :p
[06:43] <pitti> not that France's game against Nigeria was that much more convincing, so let's see
[06:43] <larsu> pitti: by putting the ball into the goal of the enemy, twice?
[06:44] <didrocks> already had to suffer 10 minutes of to Nigeria-France to order some beers at the bar with seb128
[06:44] <pitti> larsu: you didn't watch it, did you?
[06:44] <didrocks> (it was of course a really packed)
[06:44] <larsu> pitti: lol. no.
[06:44] <pitti> didrocks: poor you
[06:44] <larsu> I donated blood, took a walk, and went to bed fairly early last night
[06:44] <didrocks> pitti: first world issue! :)
[06:44] <pitti> didrocks: I'm really glad that I can at least still be friends with *you* after Friday night!
[06:44]  * didrocks envies you guys being able to donate blood in the evening
[06:45] <didrocks> pitti: ahah, yeah :)
[06:45] <larsu> didrocks: it was more like 5pm (they were available in the school in my street from 4 to 7)
[06:45] <larsu> going too late is bad though, because too many people will be there coming from work
[06:47] <didrocks> larsu: here, there are 2 buildings, both are closing at 3:30pm
[06:47] <didrocks> and they are at 4kms from home
[06:47] <didrocks> so quite hard to leave during the day
[06:48] <didrocks> pitti: you're still up before seb128 if that can reconfort you :)
[06:49] <larsu> didrocks: oh? They don't come around the neighborhoods?
[06:49] <didrocks> larsu: not where I leave, they are doing that close to the business area, but I'm quite far from it
[06:50] <didrocks> going*
[06:50] <larsu> understood
[06:53] <didrocks> ahah, a new IT shop from a brand is opening, and they display that: https://plus.google.com/photos/+ldlc/albums/6030735454222755633/6030735454625964194?pid=6030735454625964194&oid=104301983842916548085
[06:54] <larsu> lol :)
[07:37] <jibel> mvo, can you join #ubuntu-release?
[07:37] <seb128> good morning desktopers!
[07:37] <seb128> hey didrocks pitti mvo jibel
[07:37] <didrocks> hey jibel, seb128!
[07:37] <pitti> bonjour seb128, ça va ! Recontrer à vendredi !
[07:37] <jibel> Good morning seb128 didrocks
[07:37] <seb128> pitti, mvo, larsu, well done, nice game yesterday ;-)
[07:38] <pitti> seb128: well, FSVO "nice" -- the first 30 mins gave all of us a heart attack!
[07:38]  * larsu is unsure what he did…
[07:38] <pitti> (well, and the other 90 mins as well really, but in a slightly better way)
[07:39] <larsu> I'm not sure, but I think pitti knows of a "slightly better way" to have a heart attack
[07:39] <seb128> pitti, yeah, it was nice to watch if you like suspens ;-)
[07:39] <pitti> seb128: c'était une nuit très longue, je suis fatigué
[07:40] <seb128> pitti, tu t'es levé tôt ?
[07:40] <pitti> seb128: non, j'ai me levé à 8h30
[07:40] <pitti> seb128: but of course I woke up with my wife at 5, and didn't really sleep tight after that any more
[07:41] <pitti> seb128: oh, "je suis me levé", not "j'ai me levé" ?
[07:42] <pitti> seb128: I suppose I should learn some French swearing by Friday
[07:43] <seb128> pitti, "je me suis levé" ;-)
[07:43] <seb128> lol
[07:44] <pitti> seb128: what does "never ever was this a foul, you idiot!" mean in French? :-)
[07:44] <mvo> hey seb128
[07:44] <seb128> lol
[07:45] <jibel> mvo, your upload of update-notifier has been rejected, there is no version in the dependency on update-manager. You can talk to RAOF for details.
[07:45] <mvo> jibel: sure, joining now
[07:45] <mvo> jibel: ok, I will do a re-upload right away, but iirc there is no need for a dependency as the code with use os.path.exists() to figure out if it needs it or not
[07:46] <larsu> hm, appearance page in unity-control-center crashes :(
[07:46] <seb128> larsu, bt? missing schemas and gsettings aborts?
[07:47] <larsu> seb128: some assertions about radio button groups not found. I'll have a look later, aftre I finally finish tab theming
[07:47] <larsu> this has been on my todo _forever_
[07:47] <seb128> k
[07:48] <larsu> seb128: speaking of which, do we have a screenshot on how it's supposed to look?
[07:49]  * larsu asks google
[07:49] <seb128> I don't think so
[07:49] <seb128> why? want to change things there?
[07:50] <larsu> no, I want to restore how it's supposed to look and don't have a trusty handy
[07:50] <larsu> I've found a screenshot though
[07:51] <larsu> turns out, theming notebooks is rather messy
[07:51] <larsu> who'd have thought...
[07:51] <seb128> why is it looking different? gtk?
[07:51] <seb128> oh
[07:51] <larsu> yes, after the update. For example, there's a too thick border below tabs
[07:51] <larsu> and frames around the tab header
[08:00] <lool> do you folks get a crash when opening the appearance control panel?
[08:02] <seb128> see what larsu was just saying
[08:03] <seb128> so seems "yes"
[08:03]  * seb128 is on trusty so can't test right now
[08:04] <Laney> hey hey
[08:04] <seb128> Laney, hey, how are you?
[08:05] <Laney> yeah, doing good!
[08:06] <Laney> none of this futbol business to worry about here :-)
[08:06] <Laney> you?
[08:06] <didrocks> morning Laney!
[08:09] <ochosi> hey seb128, may i quickly bug you about https://code.launchpad.net/~ochosi/xdg-utils/support_xfce/+merge/224076 again?
[08:10] <Laney> hey hey didrocks
[08:11] <larsu> hi Laney
[08:13] <darkxst> hey Laney
[08:13] <Noskcaj> ochosi, I notice that the upstream and branch patches are different
[08:14] <ochosi> Noskcaj: well, ubuntu carries a (useless) patch, so ofc they're different
[08:14] <Noskcaj> ok
[08:14] <ochosi> i proposed to drop the patch in ubuntu as well
[08:15] <ochosi> but what i'm primarily interested in (now) and with this MR is an SRU for trusty
[08:15] <ochosi> cause it kinda sucks that the screensaver always kicks in, even if mediaplayers want to inhibit
[08:15] <ochosi> so i kept it minimal
[08:15] <Noskcaj> ok. I've had the same issue
[08:15] <ochosi> yeah, everyone does ;)
[08:16] <seb128> Laney, doing good, thanks ;-)
[08:16] <seb128> ochosi, yeah, no reply from upstream then, I'm just going to upload your change
[08:21] <ochosi> seb128: thanks, i'm willing to work on a different solution with upstream as well, we can always get that into utopic then. but i'd be happy if we can sru this change to trusty and for 14.04.1
[08:21] <seb128> right
[08:26] <didrocks> mvo: pitti: hey, stupid question, but imagine that one function I called GLib.idle_add() on raises an exception, I'm unsure why my try: exception around mainloop.run() doesn't seem to catch it (like a KeyboardInterrupt event), any idea? seems quite common though…
[08:29] <didrocks> I'm trying Ctrl+C in a while True loop and it doesn't seem even to raise the Interrupt
[08:29] <darkxst> didrocks, idle_add probably doesnt run in the main thread?
[08:30] <didrocks> darkxst: it does, let me pastebin a simple example
[08:30] <didrocks> http://paste.ubuntu.com/7730311/
[08:31] <didrocks> when I hit Ctrl + C in the foo function, this should raise an exception…
[08:31] <pitti> didrocks: that's known
[08:31] <pitti> didrocks: pygi can't "tunnel" exceptions through the C layer of callbacks
[08:32] <didrocks> pitti: ok, I'm not that crazy then ;). Any best practice/workaround then?
[08:32] <pitti> didrocks: so your callbacks themselves have to intercept the exceptions and handle them, or pass them to the main thread via global variables, signals, messages, etc.
[08:33] <didrocks> pitti: ok, that makes sense. Thanks Martin! :)
[08:33] <pitti> didrocks: it's not technically multithreading, but behaviourally it's "kind of"
[08:33] <pitti> didrocks: but the main reason is that it's really difficult to propagate exceptions through arbitrary C functions
[08:34] <didrocks> yeah, I guess the conversion isn't really easy, I was just puzzled that even a trivial example wasn't working and was first blaming the input() method or my nested calls :)
[08:34] <didrocks> thanks pitti, will do as you suggest
[08:39] <darkxst> yes pitti's answer is much better than my "guess" at why that would never work!
[08:40] <pitti> well, for synchronous callbacks it could technically work (with lots of effort)
[08:40] <pitti> but with async callbacks, idle handlers etc. the concept itself also makes no sense as they are "kind of" in a separate thread
[08:50] <didrocks> pitti: hum, I propably didn't get exactly what you told then. I tried to have the exception handled in my callback itself, but it didn't work. I reproduced it in that trivial example: http://paste.ubuntu.com/7730381/
[08:51] <pitti> didrocks: I'm not sure about the semantics of KeyboardInterrupt (in fact, first time I hear about it)
[08:51]  * didrocks tries an except without anything then
[08:51] <pitti> didrocks: but python-gi installs its own SIGINT handler
[08:52] <pitti> didrocks: which is mostly due to being backwards compatible how pygobject used to behave
[08:52] <pitti> didrocks: i. e. SIGINT quits the main loop, but doesn't raise an exception
[08:52] <didrocks> pitti: yeah, it's sucked in from what I see
[08:52] <didrocks> hum
[08:52] <didrocks> it doesn't quits the main loop in that example
[08:53] <darkxst> pitti, that was my guess, i.e. separate thread
[08:55] <pitti> interesting; that sounds like a regression then
[08:55] <didrocks> pitti: so, my first example should quit when I hit Ctrl + C, right? http://paste.ubuntu.com/7730311/
[08:56] <pitti> didrocks: no, you'll never get KeyboardInterrupt with pygobject
[08:56] <pitti> didrocks: well, it should quit because pygobject stops the mainloop
[08:56] <didrocks> pitti: but SIGINT should be trapped by the python-gi handler?
[08:57] <didrocks> yeah
[08:57] <pitti> but not through the exception handler
[08:57] <didrocks> it's not the case
[08:57] <didrocks> right right
[08:57] <didrocks> sorry, should have removed the handler
[08:57] <didrocks> pitti: just to be clear, that should quit: http://paste.ubuntu.com/7730404/
[08:57] <pitti> didrocks: correct
[08:57] <didrocks> it doesn't on trusty at least :/
[08:59] <pitti> yeah, that's what I meant with "regression"
[08:59] <pitti> there's a test case in pygobject for SIGINT, but apparently it behaves differently
[08:59]  * pitti bbiab
[08:59] <didrocks> pitti: I wonder if it's not https://bugzilla.gnome.org/show_bug.cgi?id=622084
[09:03] <pitti> didrocks: yeah, there are probably several bugs for that, we already had some a few years ago when I was looking into that
[09:03] <didrocks> pitti: ok, FYI, I used the workaround from the bug description: signal.signal(signal.SIGINT, signal.SIG_DFL)
[09:04] <didrocks> and it works for an INT
[09:04] <didrocks> at least, I would know as well the other cases for the exceptions raised in the callback and adapt my code to it
[09:04] <didrocks> I'm sure it's a declaration of war for Friday!
[09:04]  * didrocks hugs pitti :)
[09:04] <pitti> didrocks: yeah, that'll restore Python's normal SIGINT behaviour with KeyboardInterrupt
[09:38] <seb128> Dir
[09:38] <seb128> ups
[09:39] <seb128> Laney, why did you remove the QDir include in the click changes?
[09:40] <Laney> it's moved to the header
[09:41] <Laney> are you looking at doing a landing soon?
[09:41] <seb128> yes, today or tomorrow
[09:41] <seb128> Saviq has one lined up first to switch to the suru icon theme
[09:41] <seb128> he aims at landing that today
[09:41] <Laney> okay, I think I can fix the rest of the icons based on my earlier investigation
[09:42] <Laney> stupid spec violators
[09:42] <seb128> do you want to do that on the same merge request?
[09:43] <seb128> it might be good to add some comments in there, I'm re-reading the code you "refactored", it seems suboptimal that we need to play with paths and parsing that way, feels like click could be better a providing the info we need
[09:43] <seb128> having the rational of why we need to do that "manual work" could be useful
[09:43] <Laney> k
[09:44] <seb128> thanks
[09:45] <seb128> "Overwrite the icon with the .desktop file's one if we have it. This one is more reliable."
[09:46] <seb128> what's the point of having an icon info if it's not reliable...
[09:48] <Laney> I think the desktop file one is used by the app scope
[09:48] <Laney> so maybe this one can bitrot or something
[09:49] <Laney> although to be fair ...
[09:49]  * Laney notices something
[10:48] <papars> Hi. Can somebody help me? My problem is described here: http://askubuntu.com/questions/490292/dell-fans-not-working
[11:55] <bregma> lool, if you're still having trouble with large text on HiDPI screens, check the Universal Access 'Large Text' setting in the control center -- see bug #1332947
[11:58] <lool> bregma: at the moment the settings panel crashes for me
[11:59] <lool> bregma: but thanks, I've sub-ed there
[11:59] <lool> bregma: and indeed, large text is turned on
[12:20] <Laney> seb128: I pushed a version that finds ALL the icons on my device
[13:32] <sil2100> didrocks: as mentioned, I would like to fetch from launchpad API the list of all bugs with a certain tag
[13:33] <didrocks> sil2100: yeah, I'm afraid you need a bug_target for that, let me reread the doc quickly
[13:33] <sil2100> didrocks: I already asked on #launchpad, but no one knows it seems
[13:33] <sil2100> didrocks: yeah... couldn't find anything, and ubuntu?ws.op=searchTasks only returns ubuntu targetted ones
[13:34] <didrocks> sil2100: you can on project, distro, series, milestones for sure
[13:34] <didrocks> (so not only ubuntu)
[13:34] <didrocks> let me continue to check for available targets
[13:34] <didrocks> I'm sure there is person
[13:34] <didrocks> yeah, person…
[13:34] <sil2100> hmmm...
[13:35] <didrocks> sil2100: project_group is maybe what you want? (but we don't really use project_group in LP, apart from the indicators)
[13:35] <sil2100> Damn, I would have to 'tag' those specific bugs with a certain dummy project then
[13:35] <sil2100> project_group? I wonder what those can be
[13:35]  * sil2100 looks
[13:36] <didrocks> sil2100: yeah, the dummy project is what I did for the unity time
[13:36] <didrocks> you can as well have a team that is subscribed to the bugs
[13:36] <didrocks> and filter on them
[13:36] <didrocks> or ensure they have an ubuntu task
[13:36] <didrocks> and filter on that
[13:37] <sil2100> didrocks: thanks! I'll try to work-around it in that way then ;)
[13:37] <didrocks> that's the 3 easiest options I confirm that is possible (after reareading the doc)
[13:37] <didrocks> yw sil2100 :)
[13:37] <Laney> I think that it's probably deliberate
[13:37] <Laney> to not let people search across the collection of all bugs
[13:37] <didrocks> Laney: well, you can do that for all ubuntu bugs
[13:37] <didrocks> whatever series and so on
[13:37] <sil2100> Yeah, but you can still do that in LP manually, and not sure if people use the API so much
[13:38] <didrocks> which is I guess even bigger that all projects unioned
[13:38] <didrocks> sil2100: there are a lot of people using the API, and if you use a bot, you get kind emails regularly with bots owners :p
[14:12] <seb128> Laney, how did you workaround your issues then print calls were not showing up on stdout from qml?
[14:13] <Laney> use warnings :(
[14:13] <seb128> :/
[14:13] <Laney> I asked in app-devel but nobody replied
[14:27] <Laney> seb128: which bug are you looking at?
[14:28] <seb128> Laney, I just wanted to put a debug print in the click sorting selector, it seems to always be set on "name" even if the gsettings key is false
[14:29] <seb128> did you try to debug that yet?
[14:29] <Laney> no, was going to though
[14:29] <Laney> well, I did some weeks ago
[14:29] <Laney> before I found out about using warnings
[14:46] <seb128> Laney, do you remember what is supposed to set the sort role on start?
[14:46] <seb128> is that the gsettings key being read and a sortRole being written then?
[14:47] <Laney> lemme look
[14:48] <Laney> erm
[14:48] <Laney> when did qtcreator get a windows style file chooser?
[14:48] <seb128> do you have that upstart fix to set the session-id variable?
[14:48] <larsu> Laney: I've noticed the same in qmlscene
[14:48] <larsu> might have happened with the qt 5.3 update?!
[14:49] <Laney> seems likely
[14:49] <Laney> it used GtkFileChooser before
[14:49] <Laney> I have that variable yes
[14:51] <seb128> :-/
[14:55] <larsu> what does qt usually look at to find out which platform it's on? XDG_CURRENT_DESKTOP?
[14:56] <seb128> larsu, GNOME_DESKTOP_SESSION_ID
[14:56] <seb128> oh, sorry, that was qt4
[14:57] <seb128> (https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1305294)
[15:10] <seb128> Laney, you are sure that ever worked since we use the backend rather than the js code we had?
[15:11] <Laney> seb128: I just found the fix
[15:11] <Laney> one liner!
[15:11] <seb128> Laney, great ;-)
[15:11] <Laney> looks like the gsettings isn't hooked up though
[15:11] <seb128> was it a missing init something?
[15:11] <Laney> you have to invalidate the model after re-sorting it
[15:12] <Laney> do you have the bug # handy?
[15:16] <seb128> Laney, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1320160
[15:16] <Laney> ty
[15:17] <Laney> lemme hook up the gsettings key
[15:30] <seb128> oh, it's meeting time!
[15:30] <didrocks> hey! :)
[15:32] <seb128> qengho, Laney, tkamppeter_, larsu, didrocks, hey, it's meeting time
[15:32] <seb128> short list today
[15:32] <qengho> Heya, folks!
[15:32] <brookswarner> morning guys
[15:32] <seb128> Bjoern is on vac, Canada is having a national holiday
[15:32] <qengho> Vacations?
[15:33] <seb128> qengho, hey
[15:33] <seb128> qengho, you can start I guess ;-)
[15:33] <qengho> Okay!
[15:33] <qengho> * Set up chromium-mir build tree. (Current status, upstream bug: linker failures with ozone enabled.)
[15:33] <qengho> * Worked with Legal to satisfy Ad*be that we know how to deliver Fl*sh plugin.
[15:33] <qengho> * Still testing chromium-browser 35.0.1916.153. I delayed to fix a Aura high-dpi geometry problem, but it's taking too long. Just releasing soon.
[15:33] <qengho> EOF
[15:34] <seb128> qengho, thanks
[15:34] <seb128> Laney, hey
[15:35] <Laney> • Continue to fix folks/zeitgeist fallout in Debian, upload new folks upstream.
[15:35] <Laney> • Investigate / cherry-pick fix for glib/gcc-4.9 test failure
[15:35] <Laney> • Fix ubuntu-sso-client adt failure
[15:35] <Laney> • Merges/syncs: vte3 gupnp glade
[15:35] <Laney> • Patch pilot
[15:35] <Laney> • Fix and fwd nautilus segfault upstream (applied, thanks mclasen)
[15:35] <Laney> • Discuss webkigtk/arm64 with Debian
[15:35] <Laney> • Test/discuss gnome-desktop 3.12, give feedback, need to test second round of fixes from Tim
[15:35] <Laney> • u-s-s: show all click icons, make click list sorting work, reviews
[15:35] <Laney> • Chat to fluendo about a segfault in their plugin, get it fixed, upload to Debian & sync
[15:35] <Laney> • Give desktop-next a little warning on its cdimage page directing to the wiki
[15:35] <Laney> • Fight with a flaky VPS
[15:35] <Laney> ☘
[15:36] <seb128> what was the fluendo segfault?
[15:36] <seb128> is that in that lib (don't remember the name) that didn't change for years?
[15:37] <Laney> I had an ancient mp3 that was a bit corrupted
[15:37] <Laney> and its parser didn't like that
[15:37] <Laney> got a mediascanner segfault on every startup because of this
[15:37] <seb128> oh, k
[15:37] <qengho> metadata encoding problem?
[15:38] <seb128> what's the status-quo on the gnome-desktop discussion?
[15:38]  * seb128 lost track
[15:38] <seb128> we are still trying the new service approach?
[15:38] <seb128> rather than robert_ancell code copy one?
[15:39] <Laney> https://core.fluendo.com/gstreamer/trac/changeset/2622/trunk/gst-fluendo-mp3/src/bitstream.c
[15:39] <Laney> yeah just trying darkxst's stuff for now
[15:39] <seb128> k
[15:39] <Laney> but he said he'd be fine doing the other approach if necessary
[15:39] <seb128> right
[15:39] <seb128> let's see how that goes
[15:39] <seb128> Laney, thanks
[15:39] <seb128> tkamppeter_, hey
[15:40] <seb128> no tkamppeter_?
[15:40] <seb128> larsu, hey
[15:41] <larsu> hi!
[15:41] <larsu> last week I did some gsettings-qt cleanup and bug fixing
[15:41] <larsu> added a simpler dbus api to indicator-messages for the push notification guys
[15:42] <larsu> (who I've talked to a lot because libmessaging-menu isn't awesome for their use case on the phone)
[15:42] <larsu> nobody's given me any feedback on that yet, though
[15:42] <larsu> I've also talked to Company and mclasen about the Adwaita -> gtk move and how it effects our theme
[15:43] <larsu> and tested it with master - seems to be fine so far
[15:43] <larsu> also, the dialog/csd patches landed after some cleanup
[15:43] <larsu> hm, I think that's about it ...
[15:43] <seb128> great for master and the csd patches ;-)
[15:44] <seb128> larsu, you got feedback on https://code.launchpad.net/~larsu/indicator-messages/add-simple-dbus-api/+merge/224622
[15:44] <Laney> did you ask push guys for review on the MP?
[15:44] <seb128> but not review feedback
[15:44] <larsu> ah, I've done further work on getting the theme ready for 3.12 (some notebook fixes and getting headerbars to work for us)
[15:44] <seb128> just "user" feedback
[15:44] <seb128> who should be reviewing that?
[15:44] <larsu> seb128: Chipaca is the push notification guy I talked to
[15:44] <seb128> charles?
[15:44] <Laney> fdo notifications sounds nice ;-)
[15:44] <Laney> could we actually have that?
[15:45] <seb128> Laney, don't get larsu started
[15:45] <larsu> seb128: I think ted wanted to do this
[15:45] <Laney> but I want to :(
[15:45] <larsu> Laney: yes, we could, but don't get me started.
[15:45] <seb128> we all would like that here
[15:45] <seb128> but other teams are not on the same line
[15:45] <larsu> ah, some code reviews and the usual bug discussion as well last week. I think that's it then
[15:46] <Laney> ho hum
[15:46] <larsu> seb128: right. There's also some problems with click packaging and org.freedesktop.Application
[15:46] <larsu> and XDG_DATA_DIRS
[15:46] <larsu> I hope those will get sorted sooner rather than later
[15:46] <seb128> right
[15:47] <seb128> let's not go into too much detailed discussion on those topic during the meeting, we could spend an hour on it
[15:47] <larsu> the API I proposed now doesn't have the org.freedesktop.Applicaiton part, otherwise it's very similar to the one GNOME is using now
[15:47] <larsu> so we could consolidate them if we decide that it's worth it
[15:47] <seb128> great
[15:47] <larsu> seb128: ya, sorry.
[15:47] <seb128> larsu, thanks
[15:47] <seb128> nothing to be sorry about ;-)
[15:47]  * seb128 gets confused by the order with the missing Canadians
[15:48] <seb128> I think it's didrocks' turn?
[15:48] <didrocks> yep!
[15:48] <seb128> ;-)
[15:48] <didrocks> * added more and more tests (150+ now) in the developer tools center
[15:48] <didrocks> * shell completion enablement of udtc
[15:48] <didrocks> * fighting/had fun to define a model where I can send arbitrary UI from framework. A lot of force and back and now, expanding it :)
[15:48] <didrocks> * finally, enabling the android studio setup, using that for the base of the future interactions with framework (and will probably refactor + add tests once the base will be done)
[15:48] <didrocks> * some MIRing (still tracker on the list)
[15:48] <didrocks> EOF
[15:48] <charles> seb128, IMO this would be better for ted or tvoss to review; this looks like it's a continuation of the discussion from Malta
[15:48] <seb128> charles, ok, thanks
[15:48] <charles> s/ted/tedg/
[15:49] <seb128> didrocks, you forgot the "fought with python-gi" ;-)
[15:49] <didrocks> I was trying to be politically correct in the notes :p
[15:49] <larsu> charles: I've pinged tedg a couple of times about it - is he on vacation?
[15:49] <Laney> oh cool we got new clutter in release after libinput
[15:49] <seb128> lol
[15:49] <Laney> thanks didrocks!
[15:49] <seb128> ok, let's not get you started about that then :p
[15:49] <didrocks> Laney: yw ;)
[15:49] <didrocks> seb128: yeah :)
[15:49] <seb128> didrocks, thanks
[15:49] <tkamppeter> Sorry, I missed it. Here is my stuff:
[15:49] <seb128> ok, my turn
[15:49] <seb128> ups
[15:49] <tkamppeter> - Got hint to new driver project for proprietary Brother laser printers, "brlaser": https://github.com/pdewacht/brlaser, added entries to OpenPrinting
[15:49] <tkamppeter> - cups-filters: Fixed bug in cups-filters, generating queues pointing to remote raw queues
[15:49] <tkamppeter> - ghostscript: SRU for a crash
[15:49] <tkamppeter> - Mentoring of GSoC students, midterm evaluations
[15:49] <tkamppeter> - Some organizational stuff for OpenPrinting Summit.
[15:49] <seb128> tkamppeter, sure, go ahead
[15:49] <tkamppeter> - Bugs.
[15:50] <seb128> tkamppeter, thanks
[15:50] <seb128> k, my turn this time ;-)
[15:51] <seb128> • debian merges (evince)
[15:51] <seb128> • SRUs (shotwell)
[15:51] <seb128> • sponsoring (synced cinnamon)
[15:51] <seb128> • fixed an issue with the shotwell/online accounts integration
[15:51] <seb128> • landings (overlay-scrollbars)
[15:51] <seb128> • discussed/reviewed the options for gnome-desktop updates/what to do with u-s-d/u-c-c
[15:51] <seb128> reviewed touch settings current designs, looked at some issues, filed some bugs, triaged bugslist
[15:51] <seb128> • bug fixes (shotwell)

[15:51] <Laney> über triaging
[15:52] <seb128> right, did quite some on u-s-s .... there is quite some work to do there :/
[15:52] <charles> larsu, ted is on vacation but I don't know for how many days, checking the calendar now
[15:52] <larsu> Laney: 100 points for proper use of umlauts
[15:53] <Laney> thänkß lärßü
[15:53] <charles> larsu, ah, he's in DC for Independence Day
[15:53] <seb128> ok
[15:53] <larsu> charles: is the the one supposed to work on that api?
[15:53] <seb128> is there any other topic we should discuss?
[15:53] <charles> that's right, we all chatted about that last week
[15:54] <larsu> charles: or can you/tvoss/thostr give input as well?
[15:54] <larsu> the situation is a bit defused now, but only because the push guys did more work than necessary :-/
[15:56] <seb128> seems like that's a wrap then
[15:56] <seb128> thanks everyone
[15:56] <didrocks> thanks!
[15:57] <seb128> Laney, "Some click packages ship spec-violating desktop files" ... shouldn't we fix that/have the click tool refuse to build a .click when the content is invalid?
[15:57] <seb128> "invalid"
[15:58] <Laney> I think it'll result in a spec fix
[15:58] <Laney> to allow relative paths
[15:59] <Laney> but I need to know how the ubuntu app launch stuff works really
[15:59] <Laney> I think it must add some stuff to PATH/XDG_*_DIRS each time