[05:41] <hikiko> Good morning :-)
[05:45] <pitti> Good morning
[05:51] <RAOF> Good morning!
[05:51] <pitti> hey RAOF, how are you?
[05:52] <RAOF> Butting my head against one of the two hard problems of computer science :)
[05:52] <RAOF> Other than that, pretty good. How about yourself? :)
[06:02] <hikiko> Hi pitti RAOF !
[06:02] <RAOF> Hey hikiko!
[06:02] <didrocks> good morning hikiko, RAOF
[06:02] <hikiko> Haha and didrocks!
[06:39] <pitti> hey hikiko, how are you?
[06:39] <pitti> ça va didrocks, as-tu eu un bon week-end?
[06:39] <pitti> RAOF: hah -- is one of them "create a project name"? :-)
[06:39] <RAOF> pitti: That is a special case of one of them, yes ;)
[06:40] <RAOF> (The two hard problems of computer science are naming, cache invalidation, and off-by-one errors)
[06:40] <didrocks> bonjour pitti ! Bon week-end, oui, joué à des jeux de société, et toi ?
[06:41] <didrocks> RAOF: :p
[06:42] <pitti> didrocks: un week-end calm aussi; on faisait la dernière jardinage, et on a joué au badminton à nouveau
[06:42] <pitti> didrocks: nous avons la première neige !
[06:43] <didrocks> pitti: oh waow, pas encore ici :)
[06:43] <didrocks> mais mes parents, si
[06:43] <pitti> ponctuel pour l'ouverture de marché de Noël
[06:45] <didrocks> cool :)
[07:18] <darkxst> hey didrocks pitti
[07:19] <didrocks> evening darkxst
[07:22] <darkxst> anyone able to sponsor bug 1518478 to unbreak Ubuntu GNOME images?
[07:23] <didrocks> darkxst: having a look, will probably patch pilot today/tomorrow anyway
[07:24] <darkxst> didrocks, thanks, its just trivial fallout from gdm3 rename, and some cleanups
[07:24] <didrocks> darkxst: yeah, no more 16gdmnopasswd?
[07:24] <didrocks> how is it configured for the live session then? (just curious)
[07:24] <darkxst> didrocks, that script has not done anything for ~2 cycles
[07:24] <darkxst> didrocks, autologin in intially
[07:25] <darkxst> if you logout, then you get the password prompt re-logging back in
[07:25] <didrocks> darkxst: how does gdm3 then knows it should do an autologin?
[07:26] <darkxst> didrocks, autologin is in 15autologin
[07:26] <didrocks> ah ok ;)
[07:26] <didrocks> yeah, this was just for relogin
[07:26] <didrocks> got it
[07:27] <didrocks> sounds safe and can't impact the rest, sponsoring then
[07:27] <darkxst> its hard to fix the logout from a non-persistent live session now, not worthwhile
[07:27] <darkxst> didrocks, thanks
[07:27] <didrocks> darkxst: I think we still ask for the password for lightdm in that case
[07:27] <flocculant> morning desktoppy peoples - the update to Gtk Version: 3.18.5 has made things go pop over the weekend :) bug 1518661 for example
[07:33] <seb128> good morning desktopers
[07:33] <pitti> hey darkxst, how are you?
[07:33] <darkxst> didrocks, yeh and probably not many bother to log out anyway
[07:33] <pitti> bonjour seb128, comment vas-tu ?
[07:34] <darkxst> pitti, good, my leg has mostly recovered, and been good weather, though that won't last!
[07:34] <didrocks> darkxst: I guess they just reboot if they feel themeselves stuck"
[07:36] <pitti> darkxst: "good" means "< 35 degrees"? :)
[07:36] <darkxst> pitti, < 30 for me! tomorrow is going to be 30 and storms, that is bad!
[07:44] <darkxst> seb128, bug 1518813
[07:45] <darkxst> seb128, that is going to cause the reverse problem when gnome-user-share/vino get updated
[07:46] <seb128> hey pitti didrocks darkxst
[07:46] <didrocks> re seb128
[07:47] <darkxst> hey seb128
[07:47] <seb128> darkxst, yeah, but g-u-s and vino are not being updated :p
[07:47] <seb128> I looked at updating vino on friday
[07:47] <seb128> but basically the new version is mostly things dropped we would have to revert + translations updates
[07:47] <darkxst> seb128, our sharing panel is completely broken atm
[07:48] <seb128> why?
[07:48] <seb128> vino didn't change much
[07:48] <seb128> they just dropped the standalone UI
[07:48] <seb128> and changed the autostart
[07:48] <darkxst> seb128, because g-c-c/g-s-d don't use the gsettings keys for autostart
[07:48] <seb128> is that part the issue?
[07:48] <darkxst> instead g-s-d manages the services
[07:48] <seb128> that seems like easy enough to patch
[07:49] <darkxst> seb128, I am also concerned about having to bluetooth obex proxy's running
[07:49] <darkxst> one in the old gnome-user-share and one in g-c-c
[07:50] <darkxst> if we hit a bug in that situation is going to incredibly hard to work out what is causing it
[07:50] <seb128> can't you just drop GNOME from those autostart .desktop?
[07:50] <seb128> to not have g-u-s starting under g-s
[07:51] <darkxst> seb128, we need g-u-s running for the webdav stuff
[07:51] <seb128> so patch the g-c-c one out?
[07:51] <darkxst> seb128, no its not equivalent, it has per network sharing options
[07:52] <darkxst> later g-u-s did split binaries before dumping obex though
[07:52] <darkxst> maybe can use that
[07:52] <seb128> we could probably patch g-u-s to have the code in a if(XDG_CURRENT_DESKTOP=...
[07:52] <seb128> or that
[07:53] <darkxst> then there is still the autostartcondition, I can override the setting, but if anyone ever opens up the old UI and disables it, it will be broken forever
[07:56] <seb128> unsure to understand the autostart thing
[07:56] <andyrock> morning all
[07:56] <seb128> if they use an UI to disable something they can use it to enable it back no?
[07:56] <seb128> hey andyrock
[08:01] <darkxst> more like if they use some obscure UI to disable something, will they remember how to enable it back!
[08:01] <darkxst> toggling the settings in g-c-c, which is the obvious place, doesnt touch the autostart key
[08:03] <darkxst> but toggling the setting in g-u-s or vino will change that key
[08:10] <larsu> good morning all! Happy Monday
[08:11] <didrocks> Happy Monday larsu!
[08:12] <larsu> hi didrocks! how are you?
[08:12] <larsu> had a good weekend?
[08:12] <didrocks> larsu: good, thanks! rainy week-end, but went to play board games and painting walls to my aunt's :)
[08:12] <didrocks> and you?
[08:13] <larsu> good as well thanks - quiet and relaxing
[08:14] <pitti> hey larsu
[08:14] <larsu> morgen pitti! wie gehts?
[08:14] <pitti> larsu: super, danke! Badminton, Sauna, und erster Schnee, prima Wochenende :)
[08:15] <larsu> :)
[08:15] <seb128> hey larsu! how are you?
[08:15] <seb128> pitti, oh, it has been snowing?
[08:16] <larsu> morning seb128!
[08:16] <larsu> indeed it has
[08:16] <pitti> seb128: oui, hier il y avait la première neige
[08:16]  * larsu sees some snow out the window
[08:16] <seb128> nice
[08:16] <pitti> seb128: ponctuel pour l'ouverture de marché de Noël :)
[08:17] <seb128> hehe
[08:17] <seb128> j'aime cette période de l'année ;-)
[08:18] <pitti> il fait trop froid maintenant; je prefère les saisons chaudes :)
[09:00] <Trevinho> Ciao!
[09:00] <pitti> hey Trevinho!
[09:00] <Trevinho> pitti: hi
[09:01] <didrocks> hey Trevinho
[09:02] <seb128> hey Trevinho Laney willcooke
[09:02] <Laney> morning
[09:03] <pitti> hey Laney, how are you? nice long weekend?
[09:03] <willcooke> morning
[09:03] <willcooke> hey seb128
[09:03] <pitti> hey willcooke
[09:04] <didrocks> morning willcooke
[09:04] <didrocks> and wb Laney!
[09:05] <Laney> hey pitti
[09:05] <Laney> got a cold :-(
[09:05] <pitti> urgh
[09:07] <Laney> bleh, irssi is misbehaving
[09:07] <Laney> ah!
[09:07] <Laney> pitti: before this arrived, the weekend was nice though ;-) cocktails, climbing & family visiting
[09:07] <Laney> how are you?
[09:07] <Laney> and you seb128!
[09:07] <Laney> and didrocks!
[09:08] <Laney> 156 "Ubuntu" emails
[09:08] <Laney> these days they are usually from autopkgtest workers ;-)
[09:09] <seb128> Laney, doing good! went to see simply red on saturday, had lunch with friends yesterday and watched some tennis during the (rainy) w.e
[09:10] <seb128> today is sunny which is good because I've tennis practice tonight ;-)
[09:10] <Laney> c-c-c-c-cold today
[09:10] <seb128> Laney, hope you get over the cold!
[09:15] <pitti> Laney: I dealt with them, kill them all
[09:16] <didrocks> Laney: btw, did you get any stacktrace when running in virtual? The generator is supposed to work
[09:16] <pitti> Laney: partly the usual cloud noise, partly my fault while playing with the workers
[09:16] <Laney> didrocks: I didn't try yet, there was that paths problem
[09:16] <didrocks> Laney: (I still think there is something that can be improved, but that shouldn't prevent you for running)
[09:16] <didrocks> Laney: really? sys.prefix should return the virtualenv ones
[09:17] <didrocks> (on the line you showed me)
[09:17] <Laney> well you never came back to me to say it wasn't a problem
[09:17] <Laney> so I didn't know that
[09:17] <didrocks> Laney: that's why I'm coming back to you now, to tell it's not a problem :)
[09:18] <Laney> ok then
[09:18] <didrocks> (still, there is one function where upstream use first system, then trunk, and another one where they are using trunk, then system, I'll fix it)
[09:18] <didrocks> I thought you pointed it to me because you found there is an issue
[09:21] <Laney> when trying to run it before I did
[09:21] <Laney> but never got far enough on the virtualenv due to the previous problem
[09:21] <didrocks> ok
[09:25] <didrocks> Laney: generator.py will have an issue though, upstream forgot "default" (for templating, but that's an issue with globally installed version as well)
[09:33] <Laney> oh yeah
[09:39] <didrocks> Laney: waiting for upstream to appear online, but that should be cleaner: https://github.com/ximion/appstream-dep11/pull/2
[09:41] <larsu> morning Laney! sorry about the cold :(
[09:42]  * larsu hands Laney some virtual ginger tea with lemon
[09:44] <Laney> thanks larsu! I feel better already
[09:44] <Laney> how's it going?
[09:46] <larsu> Laney: good thanks! Already went to the gym this morning and had a delicious breakfast
[09:46] <larsu> how was your weekend? I hope not determined by the cold?
[09:47] <Laney> larsu: it only arrived about 6pm yesterday, so no
[09:47] <Laney> I hope I didn't pass it to Henry though :(
[09:47] <larsu> poor henry!
[09:49] <larsu> all the best to both of you
[09:50] <Laney> :)
[09:50] <seb128> larsu, how was your w.e?
[09:50] <Laney> did you have a good weekend?
[09:50] <Laney> snap
[09:50] <seb128> seems like your week start was good :-)
[09:50] <seb128> hehe
[09:51] <larsu> yes!
[09:52] <larsu> weekend was good as well: went to a peruvian restaurant and had really good pisco sour, walked through some parks, listened to a choir, went to the movies, and slept a lot :)
[09:52] <larsu> oh and went to play table tennis :)
[09:53] <Laney> \o/
[10:07] <seb128> sounds like a good w.e indeed ;-)
[10:10] <willcooke> ?! robert_ancell
[10:10] <robert_ancell> willcooke, hi
[10:10] <willcooke> robert_ancell, working late! :)
[10:11] <robert_ancell> willcooke, yeah, thought I'd catch some UK people while they are awake
[10:11] <willcooke> wow, nice, thanks!
[10:12] <willcooke> That reminds me, I need to chase mvo  and cjwatson about the GS mini-sprint
[10:12] <seb128> hey robert_ancell
[10:12] <seb128> robert_ancell, saw my email about poppler?
[10:13] <robert_ancell> seb128, nope
[10:13] <Laney> "oh would you look at the time /quit"
[10:13]  * larsu looks at the time and quits
[10:13] <willcooke> :D
[10:13] <robert_ancell> seb128, I have them queued up and was just waiting to get it out of NEW
[10:14] <robert_ancell> seb128, I'm never sure if you have to wait or you can upload them directlly...
[10:14] <Laney> rebuilds?
[10:14] <robert_ancell> Either way, since the change is quite small it shouldn't cause any issues
[10:14] <robert_ancell> Laney, yeah, if I upload inkscape for example, does it build against the popple in the NEW queue or the old one?
[10:15] <seb128> robert_ancell, right, it just means rebuilding rdepends, including things like libreoffice, and sometime some of those get caught in another transition
[10:15] <pitti> robert_ancell: only against release+updates+proposed, not the NEW queue
[10:15] <seb128> robert_ancell, you need to wait for them to be out of queue
[10:15] <Laney> definitely not the queue
[10:15] <willcooke> seb128, robert_ancell - just sent you and email since you're both around
[10:15] <robert_ancell> I thought so
[10:15] <seb128> willcooke, saw that
[10:15] <pitti> not only need to wait for out of the queue", but "published into archive.u.c."
[10:15] <Laney> ftpmaster.internal ;-)
[10:15] <Laney> rmadison is good enough™
[10:15] <robert_ancell> racy!
[10:16] <robert_ancell> OK, I'll upload them tomorrow.
[10:16] <seb128> robert_ancell, we just had some quite hairy transitions, like the start of cycle uploades made gnome-desktop/libgtop/poppler/ffmpeg/other things all need to go together, because sometime you have a package that use libraries involved in different transitions
[10:16] <seb128> robert_ancell, I'm still going to look at the current ongoing tansitions before accepting those binaries
[10:17] <Laney> someone else might accept it
[10:17] <Laney> that happened before
[10:18] <seb128> I can reject it now
[10:18] <seb128> and move it to accepted later
[10:18] <seb128> to avoid that :p
[10:19] <seb128> (poppler upstream are really annoying btw, there are 5 commits between 0.37 and 0.38 and they still find the way to bump the soname)
[10:19] <robert_ancell> yeah, they love to make new sonames
[10:19] <robert_ancell> They also didn't remove any symbols
[10:20] <robert_ancell> Actually, we don't track symbols on the main lib - was there a reason for that?
[10:20] <seb128> not that I know
[10:20] <seb128> is the soname change justified?
[10:21] <robert_ancell> I was going to add that.
[10:21] <robert_ancell> Probably not
[10:21] <seb128> maybe we should just revert that
[10:21] <robert_ancell> We should not modify upstream sonames...
[10:21] <seb128> I'm tired of those transitions costing us days or work
[10:21] <seb128> so maybe we should just skip that update
[10:21] <seb128> I don't see anything worth the work
[10:21] <robert_ancell> We could patch all the changes into our current version. I'd just bring it in, surely everything will get rebuilt by the end of the cycle anyway.
[10:23] <robert_ancell> mvo, do you know why reviews.ubuntu.com provides both a ratings average and a histogram? The average can always be derived from the histogram right?
[10:25] <mvo> robert_ancell: look at the code in software center, its not using an average but instead something more elaborate, let me find the relevant lines
[10:26] <robert_ancell> mvo, yeah, I'm just wondering why the server provides redundant fields - is that because the histogram was added later or is it for simple clients that just want an average without doing the calculation themself?
[10:26] <mvo> robert_ancell: http://bazaar.launchpad.net/~ubuntuone-control-tower/software-center/trunk/view/head:/softwarecenter/utils.py#L681 the wilson_score stuff - aha, I think the wilson score was added later
[10:27] <mvo> robert_ancell: or maybe the web part was using the average instead
[10:27] <mvo> robert_ancell: calac_dr() is what you want
[10:27] <robert_ancell> mvo, yeah, so I can just ignore the average field, store the histogram and calculate the score myself.
[10:31] <mvo> robert_ancell: yeah, I think thats the way to go. actually I wonder why the servier is not just doing that instead
[10:31] <robert_ancell> mvo, probably backwards compatibility
[10:31] <robert_ancell> it is json after all
[12:12] <dholbach> hiya
[12:12] <dholbach> can somebody take a look at https://code.launchpad.net/~fourdollars/unity-settings-daemon/fix-lowest-brightness/+merge/278108 maybe?
[12:41] <tkamppeter> Any font exper/maintainer around? Please have a look at this: https://bugzilla.redhat.com/show_bug.cgi?id=1284215 We should check whether Ubuntu is also affected.
[12:52] <willcooke> andyrock, is this related to your other "mem. leak" issue?  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/987060
[12:52] <andyrock> yup
[12:52] <andyrock> that was the bug
[12:52] <willcooke> ahh
[12:52] <willcooke> I'll assign it to you then :)
[12:53] <willcooke> tkamppeter, can you ping sladen - he might know
[12:53] <andyrock> but seems like it's not a leak
[12:53] <willcooke> seb128, can you have a look at dholbach message up there ^^ seems like an important fix
[12:53] <willcooke> andyrock, yeah I remember now.  Just doing some triage of the X list so I will tidy that one up by assigning to you :)
[12:57] <seb128> willcooke, I can but I think pitti and Laney reviewed/acked the xenial version so maybe it's easier if they review the SRU as well?
[12:57] <willcooke> oh, cool, thanks seb128
[12:57] <seb128> np
[12:58] <Laney> not me
[12:58] <Laney> blerhghgGHGHGHGH
[12:58]  * Laney goes for some honey and lemon
[13:00]  * didrocks hugs Laney (with care)
[13:00] <willcooke> burn your clothes didrocks
[13:01]  * didrocks puts everything in the incinerator
[13:06] <Laney> :)
[13:12] <tkamppeter> willcooke, thanks.
[13:12] <tkamppeter> willcooke, have you seen my mail concerning the libopenjpeg MIR?
[13:13] <willcooke> tkamppeter, seen but not read yet
[13:13] <willcooke> one sec...
[13:13] <willcooke> tkamppeter, ack - will chase.
[13:14] <tkamppeter> willcooke, thanks.
[13:15] <seb128> willcooke, tkamppeter, what about openjpeg?
[13:15] <willcooke> seb128, https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061
[13:15] <willcooke> just reading the comments now...
[13:18] <seb128> tkamppeter, willcooke, I don't think poppler has an embedded version of openjpeg
[13:18] <seb128> we just have our poppler without support for that format
[13:18] <tkamppeter> seb128, and that makes it really important that openjpeg makes it into main.
[13:19] <seb128> tkamppeter,  is that format that important?
[13:19] <tkamppeter> seb128, it seems that Poppler hat something else embedded formerly but they dropped it.
[13:19] <seb128> we don't get too many complain about it missing
[13:20] <seb128> and if the security team states there are issues with the library...
[13:20] <tkamppeter> seb128, PDFs can have images embedded using this format. Images which are files on their own, like photos from cameras are never JPEG2000, but in case of cameras usually JPEG.
[13:20] <Laney> the comment robert_ancell made says that there was some internal decoder
[13:20] <Laney> so I doubt it was an actual copy of this lib
[13:21] <Laney> was/is -> deprecated
[13:22] <seb128> tkamppeter, right, I'm just saying that that format is not the most commonly used, would still be good to support but if the only libraries to enable it are poor maintained and have security issues we might be better off not having the support than exposing users to security issues
[13:25] <tkamppeter> seb128, it seems that maintenance of openjpeg has improved and now it has to be investigated whether it got acceptable.
[13:26] <seb128> tkamppeter, right, let's see then
[13:27] <willcooke> tkamppeter, I think you need state that openjpeg maint. has improved in the comments on that bug
[13:27] <seb128> if that's true
[13:28] <seb128> you might want fact to backup that statement
[13:28] <seb128> because from reading the comment it seems it is maintained but not very actively and that is true for a while
[13:29] <tkamppeter> willcooke, this was already stated in the comments.
[13:31] <seb128> Laney, larsu, https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1518661 seems created by the bg-color change
[13:31] <tkamppeter> Debian seems to have accepted it as their Ghostscript uses the external libopenjpeg and not the embedded "secured by Artifex" version.
[13:31] <seb128> tkamppeter, Debian doesn't have the MIR concept
[13:31] <seb128> they support all their packages the same
[13:39] <pitti> or more precisely, their "main" is our "main+universe"
[13:39] <larsu> seb128: is this only on compiz?
[13:48] <seb128> larsu, no, cf upstream bug
[13:49] <larsu> seb128: how can this come from our patch then?
[13:50] <seb128> larsu, I don't understand
[13:50] <larsu> ah, it is our patch
[13:50] <larsu> so not an upstream issue at all
[13:50] <seb128> right
[13:50] <seb128> I just say to look at the bugzilla comments for details
[13:50] <seb128> not that it was an upstream issue
[13:50] <larsu> right, got it now :)
[13:51] <seb128> larsu, btw no need to context change too much, if you are still on the nautilus menu maybe get that done first and then look at gtk
[13:53] <larsu> seb128: ok
[13:53] <larsu> (was distracted by that weird font bug anyway)
[14:12] <desrt> hello co-workers
[14:12] <larsu> morning desrt
[14:12] <larsu> what's up?
[14:12] <desrt> sitting on the couch drinking coffee
[14:12] <larsu> sounds good
[14:13]  * larsu sits in a chair and drinks coffee
[14:13] <desrt> watching xclaesse work on one of my projects
[14:13] <desrt> it's a good morning :)
[14:13] <larsu> :)
[14:13] <desrt> played _so much_ ingress this weekend.  i'm pretty far ahead of schedule on my levelling plan
[14:14] <desrt> got a week pass for the TTC.  been visiting all kinds of cool places that i've never been before because of the high portal density
[14:14] <didrocks> good morning desrt
[14:14] <desrt> (and high portal density tends to correspond to interesting places in general, so win)
[14:14] <willcooke> nice!
[14:14] <desrt> it's getting cold and windy, but i got some nice touch gloves :)
[14:15] <larsu> desrt: appservice, eh? Is that the confinement thing?
[14:16] <seb128> hey desrt
[14:17] <desrt> yup
[14:18] <desrt> turns out collabora also wants to confine dconf :)
[14:18] <desrt> ...and using apparmor, no less
[14:18] <larsu> whoo
[14:18] <seb128> nice!
[14:19] <desrt> too bad they don't know any kernel hackers who could help :p
[14:21] <desrt> seb128, larsu, willcooke: good morning, btw :)
[14:21] <larsu> morning
[14:23]  * didrocks feels left alone :p
[14:23] <desrt> eep!
[14:23] <desrt> good morning didrocks.  sorry :)
[14:23]  * didrocks feels better now! :)
[14:23] <desrt> didrocks: i forgot you existed after you stopped fighting for our team!
[14:24] <desrt> ;)
[14:25] <didrocks> rohhhhhhhhh
[14:25] <didrocks> I was protecting you even before you knew that was a thing!
[14:25]  * didrocks removes is cape
[14:25] <desrt> lol
[14:26] <larsu> hehe
[14:26] <desrt> making sure i lived in a nice clean sea of blue, free from encroachment of any slime
[14:26] <didrocks> :)
[14:29]  * desrt plays another new alternate reality game with a cool-sounding name
[14:30] <desrt> maybe you heard of it.  it's a real mind-bender
[14:30] <desrt> it's called....
[14:30] <desrt> " inotify "
[14:30] <larsu> i, notify
[14:30] <desrt> there's these things littered around the filesystem called inodes
[14:31] <desrt> and 'events' are entering our world, through these "inodes"
[14:31] <desrt> and you have to capture them
[14:31] <desrt> but it's almost impossible to capture all of the events that you want without also getting a lot of useless ones
[14:31] <desrt> very fun game!
[14:32] <larsu> desrt: I thought you had it all figured out
[14:33] <desrt> i do
[14:33] <desrt> but it's pretty wildly complicated :)
[14:33] <larsu> ya... no shit
[14:33] <desrt> it involves quite a few abstractions
[14:33]  * larsu still thinks this isn't a problem worth solving
[14:34] <desrt> i do.  the state of things before was very bad
[14:34] <desrt> the state of things now is still quite bad
[14:34] <desrt> and it's starting to look more and more like we will never have anything better from the kernel
[14:34] <desrt> which is sort of what we were waiting for
[14:34] <desrt> so we may as well stop using stop-gaps
[14:35] <larsu> what could the kernel do better without growing all this complex logic itself?
[14:35] <larsu> watching abitrary paths is close to impossible
[14:36] <desrt> basically, fanotify without the stupid restrictions
[14:36] <desrt> reporting to a userspace daemon
[14:36] <desrt> based on that we could build something very close to what macos has
[14:37] <larsu> what does that do differently from inotify?
[14:37] <larsu> sounds the same from a quick look
[14:38] <larsu> minus a lot of event tupes
[14:38] <larsu> *types
[14:38] <desrt> it means that user processes don't have to go through the insane hassle of spidering the filesystem adding watches to all of the paths
[14:38] <desrt> anyway... i don't expect that this will happen any time soon
[14:38] <desrt> so i'm going to stop dreaming about it and go back to dealing with what we have today
[14:51] <willcooke> seb128, Trevinho (anyone who cares) - I've finished my triage of our rls-x-incoming bugs.  Things which I think should certainly be worked on I have targeted and removed the tag.  Everything else in that list (for us) is either a) I don't care b) I don't know.  Can you guys and anyone else parse that list and then we can have a quick joint session to deal with the remaining ones?
[14:51] <willcooke> link:  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-x-incoming-bug-tasks.html
[14:51] <seb128> willcooke, sure, just set up something on the calendar?
[14:52] <Trevinho> yeah, fine
[14:52] <willcooke> seb128, Trevinho - let me know when you're done and I'll set something up.  It's taken me a week longer than I thought it would - so I don't want to tie you to an unreasonable date
[14:53] <Trevinho> Mh, ok...
[14:53] <Trevinho> andyrock: too ^
[14:54] <lifeless> desrt: all hai 'solutions'
[15:08] <qengho> Good morning.
[15:09] <willcooke> hey qengho
[15:09] <qengho> seb128: I have a proposal for merged xdg-utils from Debian. https://launchpad.net/~cmiller/+archive/ubuntu/proposed/+packages
[15:10] <qengho> willcooke: 'sup.
[15:10] <larsu> morning qu
[15:10] <larsu> *qengho ;)
[15:13] <seb128> qengho, hey, great, maybe attach the debdiff to one of the bugs it fixes and subscribe ubuntu-sponsors?
[15:13] <seb128> qengho, I'm going to try a look later if nobody else picks it up before
[15:14] <seb128> hey qengho btw :-)
[15:37] <qengho> seb128: merci.
[16:28] <pitti> seb128: oh, j'ai perdu à te dire: xenial a des nouveaux paquets de langue depuis ce matin
[16:29] <seb128> pitti, j'ai vu, merci ;-)
[16:29] <seb128> pitti, et "perdu" -> "oublié"
[16:29] <seb128> perdu = lost
[16:30] <pitti> seb128: ah, merci
[16:30] <seb128> de rien !
[17:03]  * didrocks waves good evening and good night
[17:04] <seb128> didrocks, night!
[17:04] <didrocks> enjoy your tennis seb128 :)
[17:04] <seb128> brb session restart
[17:10] <larsu> desrt: ugh! https://git.gnome.org/browse/glib/tree/gio/gapplication.c#n1204
[17:11] <desrt> what?
[17:11] <larsu> I had to dig into glib source to find out why this is crashing
[17:11] <desrt> i don't think this was ever allowed
[17:12] <larsu> where does it say it isn't? People do this all the time
[17:12] <desrt> i wrote a blog post about it once :)
[17:12] <larsu> right.....
[17:13] <desrt> but basically, it can be logically determined to be problematic if you think about it
[17:13] <larsu> I know this
[17:13] <larsu> but don't always think about it (like just now)
[17:13] <larsu> and there's no way to figure this out but read the source
[17:13] <larsu> and by the way, this code doesn't assert on any other properties
[17:13] <desrt> ya
[17:14] <larsu> nor does any constructed anywhere else
[17:14] <desrt> i'm trying to remember if there was a specific reason that this property was problematic
[17:14] <desrt> probably because of the way its default value is picked
[17:14] <desrt> i guess we could tweak that
[17:14] <desrt> i mean, in fact, this assert is there to prevent a leak
[17:15] <desrt> if you just removed this assert and did nothing else, your code would not behave how you expected and also, it would leak
[17:15] <desrt> so simply removing the assert is out of the question
[17:16] <desrt> we may do something more intelligent, however
[17:16] <desrt> 1) we could turn the assert into a free.  this is an awful choice.
[17:16] <desrt> 2) we could turn the assert into a g_error() with an explanation
[17:16] <desrt> 3) we could turn the assert into an if statement preventing the calculation of the resource path if a non-NULL one was already specified
[17:16] <desrt> i guess you probably want 3?
[17:18] <larsu> dunno
[17:18] <larsu> I don't care really
[17:18] <larsu> 2 would be fine as well
[17:18] <desrt> are you making an app with dynamic app id?
[17:18] <larsu> no, patching nautilus
[17:19] <larsu> could do it "right", but master is already doing that and I want a minimally invasive patch
[17:19] <larsu> because we don't use master
[17:19] <larsu> and I don't want to rename all the resources
[17:19] <desrt> isn't the base resource path specified with a single switch to the resource compiler?
[17:20] <desrt> or are you concerned about the other locations that use the resources?
[17:20] <larsu> ya
[17:20] <desrt> fair enough
[17:20] <desrt> fwiw, in this case, i think we could do 3
[17:20] <larsu> it's just a matter of /org/gnome/nautilus vs /org/gnome/Nautilus
[17:20] <desrt> lol
[17:20] <larsu> ya, srsly
[17:20] <larsu> welcome to my life
[17:20] <desrt> send in a patch for g_str_casehash and g_str_caseequal
[17:20] <larsu> haha no
[17:20] <larsu> that's be so wrong
[17:20] <desrt> and modify gresource
[17:21] <larsu> meh
[17:23] <Trevinho> 'night...
[17:23] <desrt> "You can disable automatic resource loading functionality by setting the path to NULL."
[17:23] <desrt> this is why
[17:23] <desrt> NULL doesn't mean "to be decided in the future".  it means "nothing, please"
[17:23] <larsu> indeed
[17:23] <desrt> so if we permit setting this value before construction then we get ourselves into the trouble of having to ignore NULL
[17:24] <desrt> ie: best to always force the user to call g_application_set_resource_base_path() after new() and before run()
[17:24] <larsu> I put it into the g_object_new() call now
[17:24] <desrt> so ya... i guess the best patch is one changing the assert to a g_error() pointing the user at g_application_set_resource_base_path()
[17:24] <larsu> this is what I used...
[17:24] <larsu> in init()
[17:25] <desrt> ya.  you're not allowed to do that :)
[17:25] <larsu> I think the right patch is to deprcate init() :P
[17:25] <desrt> ya... no kidding
[17:25] <desrt> gotta love our 8-pass construction system
[17:26] <larsu> sigh
[17:26] <desrt> "let's make a type system that inits everything but is completely oblivious to properties... we'll add a separate layer later that deals with the properties after the fact.... what could go wrong?"
[18:01] <Laney> darkxst: reckon you could merge g-o-a?
[18:02] <Laney> now gvfs requires the new one ;-)
[18:02] <Laney> maybe can revert back to webkit1?
[18:02] <Laney> or webkit2 2.4
[19:40] <willcooke> g'night all
[19:44] <Laney> darkxst: ok, I monkeyed up a revert, check out ppa:ubuntu-desktop/ppa
[19:46] <Laney> (assuming mixed linkage isn't going to be a problem, hope not)
[21:13] <darkxst> Laney, I suppose that might work
[23:33] <xnox> Laney, are you going to merge virt manager?