[06:02] <hikiko> hi
[06:38] <didrocks> good morning
[06:55] <pitti> Good morning
[06:55] <didrocks> bonjour pitti !
[06:55] <didrocks> ton cours hier était bien ?
[06:56] <seb128> good morning desktopers
[06:56] <seb128> salut pitti
[06:56] <pitti> bonjour ! oui, on a parlé beaucoup :)
[06:56] <pitti> salut seb128
[06:57]  * pitti bataille les nuages à nouveau -- mon sport de matin
[06:57] <didrocks> pitti: souffle un bon coup !
[06:58] <didrocks> les nuages partiront :)
[06:58] <pitti> didrocks: non, non ! ils cassent tous le temps, je les veux marcher ! :-)
[06:59] <didrocks> pitti: pourtant, c'est la bonne saison pour les nuages !
[06:59] <pitti> ("I want them to work" -- est-ce que c'était compréhensible ?)
[07:00] <pitti> didrocks: en effet :)
[07:00] <didrocks> pitti: oui oui, je dirais juste "je veux qu'ils marchent"
[07:01] <pitti> http://autopkgtest.ubuntu.com/running.shtml -- 430 tests on the wall, 430 tests; ressussitate one cloud again, 429 tests on the wall
[07:01] <pitti> didrocks: ah, merci
[07:02] <pitti> au moins les autres deux marchent -- nous avons eu ~ 1.100 tests hier
[07:07] <didrocks> tout de même… :)
[07:27] <larsu> good morning!
[07:27] <didrocks> hey larsu!
[07:27] <larsu> bonjour didrocks!
[07:28] <seb128> hey larsu! wie gehts?
[07:30] <larsu> seb128: guten morgen! Gut danke! Und dir?
[07:31] <seb128> auch gut, danke!
[07:33] <seb128> pitti, does "test in progress" actual means test is active or does it mean "in the queue"?
[07:33] <seb128> on update_excuses I mean
[07:33] <pitti> seb128: either; see http://autopkgtest.ubuntu.com/running.shtml for details
[07:33] <larsu> guten morgen pitti :)
[07:33] <pitti> hey larsu, wie gehts?
[07:33] <larsu> gut gut, danke! Und dir>
[07:33] <larsu> ?
[07:33] <pitti> seb128: unlike the last big KDE/Qt landing, people can now actually look at the damn thing :)
[07:33] <pitti> larsu: auch gut, danke!
[07:33] <seb128> pitti, k, that's explained why those tests are "in progress" since yesterday 16h
[07:34] <pitti> seb128: yeah, Qt landing + lcy01 being down :(
[07:34] <pitti> seb128: I've spent an hour with IS again, it's back with some capacity, but it'll still take some time to catch up
[07:34] <seb128> it's over me why they can't provide a stable infra :-/
[07:36] <pitti> If you look at running.html right now: the backlog is gone, I flushed the queues as I'm rolling out a new britney; that will re-request the missing ones
[07:36] <pitti> meh @ http://autopkgtest.ubuntu.com/running.shtml#pkg-appstream -- doesn't look that stable yet :?
[07:41] <pitti> seb128: btw, it's on my list to make the excuses.html links more useful; pass/regression should directly link to the corresponding log, and "in progress" will link to running.shtml; clicking on teh arch will show the results list as it does now
[07:41] <pitti> I did the ground work for this yesterday, now it's just a matter of wiring this up in html
[08:03] <seb128> pitti, great
[08:29] <darkxst> hey pitti, seb128 larsu
[08:29] <darkxst> ,didrocks
[08:30] <didrocks> evening darkxst
[08:30] <larsu> good evening darkxst
[08:30]  * darkxst wonders why my gdm -> gdm3 work fine when dist-upgrading, but not always when doing a release update
[08:31] <darkxst> ^debconf scripts
[08:31] <seb128> hey darkxst
[08:31] <darkxst> is there some difference in the ordering of the way maintscripts/configs run?
[08:32] <didrocks> $ diff -Nrup ubuntu/plymouth-0.9.0/debian/ plymouth-0.9.2/debian/ | lsdiff | wc -l
[08:32] <didrocks> 105
[08:32] <didrocks> fun fun fun !
[08:34] <darkxst> i.e xenial gdm -> xenial gdm3 works
[08:34] <darkxst> wily gdm -> xenial gdm3 not so much
[08:35] <Trevinho> Morning
[08:35] <seb128> Trevinho, hey!
[08:36] <didrocks> hey Trevinho
[08:36] <didrocks> darkxst: you have more packages in one case, so the config (package configuration order) might change
[08:36] <seb128> darkxst, ordering is not fixed and depends of the upgrade set, so things might be in different order between packages
[08:39] <darkxst> can the old gdm.config run in that case?
[08:42] <darkxst> I suppose debconf caches that possibly?
[08:47] <darkxst> my gdm3.config forces the gdm -> gdm3 change without a question
[08:47] <darkxst> and I purge the old gdm debconf profile, in gdm.postinst, but that didnt even seem to run either
[09:02] <Laney> yo
[09:02] <seb128> hey Laney
[09:02] <darkxst> hey Laney
[09:02] <seb128> Laney, how are you?
[09:03] <pitti> hey Laney, good morning
[09:03] <seb128> Laney, are you working on another room recently? I'm curious what change that you say hey one or two minutes earlier now ;-)
[09:03] <Laney> HAHA
[09:03] <seb128> :-p
[09:03] <larsu> morning Laney!
[09:04] <Laney> no change that I know of
[09:04] <Laney> maybe my laptop got faster to resume
[09:04] <Laney> !
[09:04] <seb128> hehe
[09:04] <Laney> and hi darkxst larsu and pitti
[09:04] <Laney> what a great group of people
[09:04] <larsu> seb128 is very observant ....
[09:04] <seb128> or maybe the clock you use to know when it's work time is slightly shifted?!
[09:04] <didrocks> good morning Laney!
[09:04] <Laney> it's the BBC pips
[09:04] <Laney> hey didrocks!!!!
[09:05] <larsu> THE BBC IS NEVER WRONG ABOUT ITS PIPS
[09:05] <Laney> https://www.youtube.com/watch?v=wQi58lKrRuU
[09:05] <hikiko> oh :) hi Laney seb128 larsu darkxst didrocks pitti willcooke :)
[09:05] <Laney> I hear that and I'm like oh shit got to get to seb128
[09:05] <larsu> the queen personally pushes the button for the pips
[09:05] <hikiko> and Trevinho :)
[09:05] <didrocks> hey hikiko!
[09:05] <larsu> are you aying the queen is wrong?
[09:05] <larsu> are you?
[09:05] <larsu> morning hikiko :)
[09:06] <willcooke> morning all
[09:06] <Laney> aaaactually
[09:06] <larsu> hi willcooke
[09:06] <Laney> if I listen online they will lag behind reality
[09:06] <Laney> maybe THAT explains it
[09:06] <larsu> Laney: you can turn in your British citizenship at the door
[09:06] <Laney> hello hikiko and willcooke
[09:07] <Laney> I bet even DAB lags too
[09:07] <willcooke> the lag on dab is very annoying
[09:07] <didrocks> hey willcooke
[09:07] <Laney> haha
[09:07] <Laney> never measured it
[09:07] <willcooke> because all the decoding and error correction is done on the radio, it means that even two radios in the same room have lag
[09:07] <Laney> what is it?
[09:07] <Laney> if I put my two DAB radios on then they sound synchronised
[09:08] <Laney> so it's <30ms
[09:08] <Laney> between the two anyway
[09:08] <willcooke> so when you have the radio on in the kitchen and another in, say, the lounge, and you can hear both.... arrrgh
[09:08] <larsu> same model?
[09:08] <willcooke> *dont have the same lag
[09:08] <seb128> hey hikiko willcooke
[09:08] <Laney> no
[09:08] <Laney> well the other one could be a rebadged Pure one I guess
[09:10] <Laney> pitti: do you know about these "Unable to find a source package" failures?
[09:10] <didrocks> waow, plymouth ubuntu and debian initramf integration is completely different
[09:10] <didrocks> even more lesigh :p
[09:10]  * darkxst don't have to worry about lag in DAB, don't get it here!
[09:10] <pitti> Laney: not yet, but I suspect the last cloud-init SRU on precise; I guess it doesn't have precise-updates/restricted apt sources any more
[09:10] <pitti> Laney: it's on my list
[09:11] <pitti> Laney: btw, I pushed and rolled out the new britney this morning; the code should now be a lot less convoluted and easier to understand
[09:11] <Laney> nice
[09:11] <pitti> I did some more cleanup last night
[09:11] <Laney> are there any functional changes?
[09:11] <pitti> Laney: not that much, just that it now doesn't forget about some architectures some times (i. e. bug fixes)
[09:12] <pitti> Laney: and the results.cache data format changed
[09:12] <pitti> Laney: we now have the run IDs of the individual tests there, so we can expose them in excuses.html to directly point to the log
[09:12] <Laney> cool!
[09:12] <pitti> Laney: and for the running ones I plan to point to /running.shtml instead
[09:13] <Laney> ah, http://autopkgtest.ubuntu.com/packages/u/unity-scope-click/xenial/armhf/
[09:13] <pitti> Laney: so I thought "armhf: pass" -> the "armhf" points to teh autopkgtest per-page results page as it does not, and the "Pass" directly to the log
[09:13] <pitti> Laney: oh nice, you added the bluez workaround?
[09:13] <Laney> yeah
[09:13] <pitti> ln -s /dev/null /etc/systemd/system/bluetooth.service
[09:13] <pitti> yay
[09:13] <Laney> I just cowboyed it to worker.conf on the cyclops-*
[09:14] <Laney> couldn't find if that came from anywhere else
[09:14] <pitti> Laney: it's not; I keep the master copy on my laptop and just parallel-scp it
[09:15] <Laney> hehe
[09:15] <pitti> Laney: if we keep this much longer, I should probably add it to git and do some credentials templating like on the cloud stuff
[09:15] <pitti> but I'm currently wrestling with lxd (and firewall/proxy again), so that at some point we can cloudify this
[09:15] <darkxst> seb128, didrocks, pitti, Laney, so back to previous question, is it possible for the the old gdm.config to get run when doing a release upgrade before the gdm3.config runs?
[09:15] <Laney> I didn't read your discussion
[09:15] <pitti> news to me too
[09:15] <Laney> what's a gdm.config?
[09:15] <pitti> but no, I don't think you can enforce it
[09:15] <darkxst> the debconf stuff
[09:15] <pitti> the maintscript
[09:16] <darkxst> we renamed source gdm -> gdm3
[09:16] <pitti> but why would you need to run debconf for the old packae? it's going to be removed anyway?
[09:16] <pitti> you can do upgrade stuff in gdm3.preinst
[09:16] <darkxst> gdm binary is now a transitional package
[09:17] <darkxst> pitti, and it does not have .config, but still getting the question on release upgrades
[09:20] <darkxst> even when gdm3 config script forces the settings, without a question
[09:24] <pitti> darkxst: ah, so gdm's postrm calls debconf again?
[09:24] <pitti> (which would make sense in general for a DM)
[09:25] <seb128> ok good desktop people, be happy new nautilus is coming your way ;-)
[09:28] <darkxst> pitti, well not explicitly so far as I can see, but something fishy like that is going on here,
[09:30] <darkxst> and it does seem feasible that a postrm would trigger debconf, but then its gdm real binary to gdm transitional binary, I wouldnt have expected that to trigger postrm even
[09:30] <pitti> if gdm3 replaces gdm, then gdm.postrm will run, as it gets removed
[09:30] <pitti> and then gdm3.postinst
[09:30] <pitti> and the preinst/prerm in between of course
[09:31] <darkxst> pitti, I did it as a transitional package, so gdm depend on gdm3
[09:35] <seb128> larsu, I would like to get geonames in Ubuntu, do you want to roll a 0.1 tarball or something we can package? or make it land through CI train (unsure if that works with git projects yet)? or...?
[09:36] <Laney> is anything ported to use it yet?
[09:37] <seb128> larsu had some work in progress for unity-control-center iirc
[09:37] <seb128> why?
[09:38] <seb128> there is also a test demo program in the source
[09:38] <Laney> just wondering if you wanting to upload it is motivated by something else wanting to use it
[09:39] <seb128> we said we would switch u-c-c and ubiquity to it this cycle
[09:39] <seb128> so trying to get things going
[09:39] <seb128> it's on my todo of things to land and I would like to empty the new packages/default changes part before holidays
[09:40] <seb128> also I tried gnome-logs again today
[09:42] <seb128> I can't really say why but it doesn't feel nice to use to me
[09:43] <seb128> I think it's a combinaison of the window being small by default, the UI elements bigs and only displaying the titles and not the full log
[09:43] <seb128> it feels like I don't have a good view of the log content
[09:43] <seb128> did other try it? how do they feel about it?
[09:46] <Laney> I didn't try it, sorry
[09:47] <Laney> did just try thunderbird calendar though
[09:47] <seb128> http://people.canonical.com/~seb128/oldlog.png
[09:47] <seb128> vs
[09:47] <seb128> http://people.canonical.com/~seb128/newlog.png
[09:47] <Laney> the EDS extension makes it fail to start :)
[09:47] <seb128> urg
[09:47] <seb128> that's also on my list of things to try/look at ;-)à
[09:48] <Laney> cannot register existing type 'ESource'
[09:48] <Laney> ...
[09:48] <Laney> gnome-calendar ftw
[09:48] <seb128> yeah, that's my feeling as well
[09:48] <Laney> I actually used it a few times in reality
[09:48] <Laney> which is probably a good sign
[09:48] <seb128> I'm unsure how well maintained it is
[09:48] <Laney> no need to start evo to do calendar stuff
[09:48] <seb128> but it's mostly working
[09:49] <Laney> or go to the website
[09:49] <seb128> I opened an upstream bug a week ago about dropping the OnlyShowIn=GNOME but no reply yet :-/
[09:49] <seb128> it's currently not listed in unity which is a bit of a fail
[09:49] <seb128> easy to fix though ;-)
[09:51] <Laney> that is weird
[09:51] <Laney> I wonder why they did that
[09:53] <seb128> yeah, not sure, they probably consider it a GNOME desktop component
[09:54] <Trevinho> I've sent a mail to pkg-config maintainer... Let's see what's the output
[09:54] <seb128> Trevinho, thanks
[09:54] <seb128> you might want to open a bug report as well?
[09:54] <Trevinho> seb128: I was considering that as well,  I wanted to see if I can get an informal reply before...
[09:55] <Trevinho> but I could
[09:58] <seb128> Trevinho, that wouldn't hurt I guess
[09:58] <seb128> but you can as well wait a few days to see if you get a reply
[09:59] <willcooke> Trevinho, seb128 - running a couple of mins late - internet problems
[09:59] <Trevinho> willcooke: ok
[10:00] <seb128> k
[10:07] <willcooke> Trevinho, seb128 - omw
[10:08] <willcooke> seb128, hikiko andyrock - https://plus.google.com/hangouts/_/canonical.com/place-holder?authuser=0
[10:08] <willcooke> sorry for the delay guys
[10:08] <hikiko> sure willcooke sec
[10:25] <hikiko> willcooke, https://bugs.launchpad.net/unity/+bug/1521947
[10:26] <ubot5`> Ubuntu bug 1521947 in Unity "Shaped and multi-rectangular windows don't have shadows" [High,New]
[10:37] <andyrock> willcooke: sorry i tought it was one hour later :O
[10:37] <willcooke> andyrock, no worries, we know that you;re still working on it
[10:47] <didrocks> Trevinho: andyrock: so, now that I updated to xenial, my weechat window is matched to byobu
[10:47] <didrocks> anything to help debugging this?
[10:48] <didrocks> actually, any terminal is matching byobu, not just my IRC one
[10:48] <Trevinho> didrocks: it's byobu issue
[10:48] <didrocks> do you have a bug reference for this?
[10:48] <didrocks> (and understood what changed there?)
[10:50] <didrocks> is it its StartupWMClass=gnome-terminal-server?
[10:51] <Trevinho> didrocks: yes, sorry otp
[10:52] <didrocks> (I guess bug #1503418)
[10:52] <ubot5`> bug 1503418 in bamf (Ubuntu) "[SRU] [REGRESSION] launching byobu from unity uses the terminal icon rather than the application icon" [Medium,Triaged] https://launchpad.net/bugs/1503418
[10:52] <didrocks> let me revert this change anyway for now
[10:54] <Trevinho> didrocks: yes, that's the bug
[10:54] <didrocks> Trevinho: let me revert the change, add rationale and give the example we have with weechat
[10:54] <didrocks> thanks to Laney's excellent compatibility wrapper
[10:54] <Trevinho> didrocks: the problem is that it's harder now to match gtk apps by class
[10:54] <didrocks> Trevinho: yeah, I guess using the same strategy than the one we discussed in Brussels is fine for now, and he can ships this terminal file
[10:57]  * didrocks gives it a try
[10:58] <didrocks> ah, better :)
[10:59] <larsu> seb128: (sorry was at the gym) what's better for you? I think I'd prefer anything that doesn't involve uploading tarballs ;)
[12:37] <seb128> larsu, do you intend for those to be used out of Ubuntu?
[12:38] <larsu> seb128: probably not for now
[12:39] <seb128> k, let's land through CI than
[12:39] <seb128> we can always change to roll tarballs later if we want
[12:39]  * larsu nods
[12:39] <seb128> larsu, is the current git something good for upload? or did you want to do changes before that?
[12:39] <larsu> it's good
[12:40] <larsu> only missing the locale part
[12:49]  * larsu is out for lunch
[12:50] <seb128> larsu, enjoy!
[12:51] <didrocks> enjoy larsu :)
[12:52] <Mirv> Qt 5.5.1 now dropped the use of GStreamer 0.10 in xenial(-proposed). it seems there are still ~10 other users though.
[12:54] <seb128> not on the iso at least
[12:54] <Mirv> not on the iso but archive in general
[12:54] <Mirv> gcompris has GStreamer 1.0 port done in Debian
[12:54] <seb128> right, well it's not worth spending efforts on that
[12:55] <seb128> it's not like you are ever going to clean the archive from old cruft ;-)
[12:55] <seb128> demoting to universe (if it's not the case yet) could be nice though
[12:55] <Mirv> maybe some low hanging fruits though
[12:56] <seb128> there are always low hanging fruits
[12:56] <seb128> I would rather spending efforts getting gconf out of the iso
[12:57] <ricotz> or this https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1521989
[12:57] <ubot5`> Ubuntu bug 1521989 in libzeitgeist (Ubuntu) "Please remove libzeitgeist from the archive" [Undecided,New]
[12:57] <ricotz> hey desktopers
[12:57] <seb128> hey ricotz
[12:57] <seb128> I've little interest in removing things from the archive
[12:57] <seb128> as said it's not like the archive/debian didn't have ton of things that are old and buggy and unmaintained
[12:57] <seb128> it's not a few more or less that's going to make a difference
[12:58] <ricotz> seb128, did you read the bug?
[12:58] <seb128> no
[12:58] <seb128> just the title
[12:58] <ricotz> please do then
[12:58] <seb128> it's a duplicate
[12:59] <seb128> bug #1197569
[12:59] <ubot5`> bug 1197569 in Unity Videos Lens "Move from zeitgeist-1.0 to zeitgeist-2.0" [Medium,In progress] https://launchpad.net/bugs/1197569
[12:59] <seb128> and patches are welcome
[12:59] <seb128> but yeah, switching to the new one would be nice
[12:59] <ricotz> ah, I see
[13:07] <ricotz> seb128, looking at nautilus
[13:13] <xnox> seb128, any reason why we are using old mono, and didn't like move to 4.2.1?
[13:15] <Laney> ask directhex
[13:22] <seb128> xnox, no idea, what Laney said
[13:28] <ricotz> seb128, https://paste.debian.net/plain/340591
[13:29] <seb128> ricotz, thanks, can you add it to the bug, I'm going to commit it in a bit
[13:29] <ricotz> seb128, ah, wait
[13:30] <ricotz> it crashed while testing
[13:33] <ricotz> (make check isn't running on package-build)
[13:33] <seb128> k
[14:46] <ricotz> seb128, next try ;) https://paste.debian.net/plain/340611/
[14:53] <seb128> ricotz, was the previous code leaking? I see you added unref calls in that one?
[14:57] <seb128> larsu, did you see my comments about gnome-logs this morning?
[14:58] <larsu> no?!
[14:58] <willcooke> Trevinho, any reason we can't disable the upstream bug tracker on Unity right now and make sure new bugs are only opened against unity (Ubuntu)?
[14:58] <larsu> seb128: did you ping me?
[14:59]  * larsu scrolls back
[14:59] <ricotz> seb128, forget about some api changes, and yeah, it was likely leaking before
[15:00] <seb128> willcooke, I don't think you can disable the tracker unless the open bugs list is empty
[15:00] <willcooke> oh, didrocks ^ >?
[15:01] <didrocks> seb128: you can disable it, it will just mask them (but you can still get the other tasks)
[15:01] <didrocks> I'm unsure how the launchpad API is working though, we can give it a try
[15:01] <didrocks> it's just a masking anyway, if you reenable, you see them again
[15:01] <seb128> larsu, no, I probably didn't directly ping you, I raised as a topic on the channel and I though you were around
[15:02] <seb128> didrocks, ok, I saw it forced you to empty the list first
[15:02] <seb128> saw->though
[15:02] <didrocks> seb128: not last time I tried (I guess 3 months ago?)
[15:02] <seb128> because that's what people usually do
[15:02] <seb128> but I guess it's to not loose bugs rather then
[15:03] <didrocks> yeah, but you won't anyway
[15:03] <didrocks> you reenable it, and surprise, they are back!
[15:03] <didrocks> (I guess only auto-expiring isn't enabled)
[15:03] <larsu> seb128: indeed, logs uses the standard text size and log viewer a smaller one
[15:03] <didrocks> I'm just unsure how the API is working, if lp.projects["unity"] will list them
[15:04] <larsu> seb128: but it's the same content, no?
[15:04] <larsu> seb128: just a bit smaller on screen
[15:04] <seb128> larsu, I don't know, I've the feeling I've no useful content on http://people.canonical.com/~seb128/newlog.png
[15:04] <larsu> seb128: yeah looking at it and trying to find the differences
[15:04] <seb128> it feels overloaded
[15:05] <larsu> I agree it doesn't look at nice
[15:05] <seb128> I can't really point out why though
[15:05] <larsu> it's the white background!!!1!
[15:05]  * larsu can fix that :P
[15:10] <didrocks> seb128: it's not hidden from the API side FYI
[15:11] <seb128> larsu, is it?
[15:11] <seb128> larsu, a bit smaller text or bigger window wouldn't hurt probably
[15:11]  * larsu was joking
[15:12] <seb128> lol
[15:12] <seb128> sorry, mind busy on other things, I didn't catch that :p
[15:12] <didrocks> seb128: even better, if you know the bug number, you can directly type the url :p
[15:13] <larsu> seb128: no worries ;)
[15:13] <seb128> didrocks, let me open all the bugs in firefox so  the awesome bar remembers!
[15:13] <didrocks> seb128: oh YEAH! :)
[15:13] <didrocks> let me try the new bug url
[15:15] <didrocks> seb128: no, they protected the url
[15:15] <didrocks> seb128: but I'm sure you can opens some through the API :p
[15:17]  * Laney meows
[15:17] <seb128> hey Laney, wie gehts?
[15:19] <Laney> hi, felt quiet today so wanted to make some noise
[15:22] <seb128> :-)
[15:22] <seb128> what are you working on?
[15:22] <seb128> still appstream things?
[15:25] <larsu> desrt: why do you export the internal GSimpleActionGroup of a GtkApplicationWindow instead of the window itself?
[15:25] <Laney> seb128: yeah, following some checklist to get it deployed
[15:25] <Laney> should be able to file that RT today
[15:26] <Laney> also librsvg update
[15:26] <seb128> cool
[15:26] <seb128> Debian also got a new dbus ;-)
[15:26] <seb128> (hint hint)
[15:26] <larsu> desrt: https://git.gnome.org/browse/gtk+/tree/gtk/gtkapplication-dbus.c#n274
[15:26]  * seb128 should stop looking at red lines on version
[15:26] <larsu> desrt: mind if I change that? My whole nautilus hack doesn't work because of this
[15:26] <Laney> yes I know
[15:26]  * larsu should file a bug
[15:31]  * Laney unlearns "+gp and learns "+p instead
[15:34]  * didrocks tries a new command
[15:34] <didrocks> Laney merge plymouth
[15:34] <Laney> permission denied
[15:34] <seb128> didrocks, try with sudo just in case
[15:34] <didrocks> sudo !!
[15:34] <Laney> SHIT
[15:34] <Laney> FINE
[15:34] <didrocks> \o/
[15:34] <Laney> $ grab-merge plymouth
[16:00] <seb128> Laney, larsu, just for info I opened https://bugs.launchpad.net/ubuntu/+source/gnome-logs/+bug/1522078
[16:00] <ubot5`> Ubuntu bug 1522078 in gnome-logs (Ubuntu) "[MIR] gnome-logs" [Wishlist,New]
[16:03] <Laney> thx
[16:03] <Laney> I will do one for the calendar soon
[16:05] <larsu> thanks!
[16:07] <seb128> Laney, oh, great, I had that on my list ... dropping it then ;-) do you plan to reply on the mailing list about your testing as well?
[16:07] <seb128> I'm going to back up your gnome-calendar +1
[16:07] <Laney> yeah but maybe tomorrow
[16:08] <Laney> online-accounts :/
[16:08] <Laney> we might need to see about stealing mardy for a bit to work on that if possible
[16:08] <Laney> I tried to add my google account on my xps to get calendars and it didn't really work very smooth
[16:17] <seb128> Laney, what issues did you get?
[16:18] <seb128> I don't think those bits changed in the recents cycle and were never pointed out as an issue
[16:18] <seb128> or did you hit bugs?
[16:19] <seb128> iirc you get an embedded webview asking for your login/passwd?
[16:19] <Laney> well I expect my calendars to magically appear in the indicator and gnome-calendar
[16:19] <Laney> but they aren't there
[16:20] <Laney> I think it's broken with 2fa accounts maybe?
[16:20] <seb128> did you restart the evolution-calendar-factory?
[16:20] <seb128> or whatever that process is called?
[16:20] <Laney> no why would I do that :P
[16:20] <seb128> just to see if it's it not picking updates
[16:20] <seb128> to determine what component has an issue
[16:20] <seb128> trying to pin down what is buggy
[16:21] <seb128> if it works after a restart it means it doesn't refresh
[16:21] <Laney> ok did now, not there
[16:22] <seb128> :-(
[16:22] <seb128> is gnome-calendar listing the calendar?
[16:22] <Laney> no
[16:22] <seb128> :-(((
[16:22] <Laney> I think on my desktop I added the ics files directly in evolution a while ago
[16:22] <Laney> so eds has them and it works
[16:23] <seb128> on my machine I added the account in u-c-c and it works
[16:23] <Laney> got 2fa?
[16:23] <Laney> try with @canonical.com
[16:26] <didrocks> ok, just added my @gmail.com (which is 2fa), didn't restart anything (g-c or e-c-f) -> nothing appears
[16:27] <Laney> are you in a position to restart your session? :P
[16:27] <didrocks> (btw, typing "calendar" in the dash doesn't find the .desktop)
[16:27] <didrocks> Laney: not that much, I'm tempted :)
[16:28] <didrocks> let me try to first close g-c and restart
[16:28] <didrocks> and then kill e-c-f
[16:28] <Laney> desktop issue is known, it has OnlyShowIn
[16:28] <didrocks> roh, nice
[16:28] <didrocks> ok, restarting g-c -> nothing
[16:29] <seb128> didrocks, OnlyShowIn is what I wrote this morning
[16:29] <seb128> Laney, yes, it's the canonical 2fa account
[16:29] <didrocks> seb128: sorry, missed that line probably
[16:29] <seb128> it was buggy on wily and started working with 3.18 again in xenial
[16:29] <seb128> automagically on login after the next login
[16:30]  * didrocks waits on e-c-f which restarted if anything will sync…
[16:30] <Laney> hoping didrocks can confirm that...
[16:30] <seb128> Laney, didrocks, is calendar component activated in the google account in settings?
[16:30] <Laney> yep
[16:30] <Laney> toggled it even
[16:30] <didrocks> seb128: yep
[16:30] <seb128> can you start the e-d-s services by hand and see the output?
[16:30] <didrocks> Laney: nothing until now appearing here as well
[16:30] <didrocks> only e-c-f, right?
[16:31] <Laney> will let didier do this, seems we are in the same state
[16:31] <Laney> adding the ics url in gnome-calendar makes it go into eds properly though
[16:31] <Laney> which is quite nice
[16:31] <Laney> no need to use evolution for this any more
[16:31] <seb128> good
[16:32] <seb128> but adding the google account should be enough to get the calendar filed
[16:32] <Laney> it should, that's why I am complaining
[16:33] <didrocks> seb128: hum, no output, but I see the subprocesses being created when launching gnome-calendar though
[16:33] <Laney> now I'm getting notification for every desktop weekly meeting ever
[16:33] <Laney> AWESOME!
[16:34] <willcooke> hah!
[16:34] <didrocks> Laney: see you in 10 days!
[16:34] <didrocks> hum, and no --verbose
[16:34] <Laney> G_MESSAGES_DEBUG=all ?
[16:35] <didrocks> Laney: already tried, nothing
[16:35] <didrocks> only have some debug message when it's autoclosing
[16:35] <didrocks> on client disconnect
[16:36] <didrocks> (the weird part is that it's the registering)
[16:36] <didrocks> so I wonder if the subprocess output are not redirected
[16:36] <didrocks> and so, it's only when they close that their stdout/stderr are flushed by the main process
[16:39] <seb128> didrocks, Laney, if you start evolution does it list the calendar?
[16:40] <didrocks> I would have to install evolution first :p
[16:40] <Laney> no
[16:40] <didrocks> Laney: do you have it handy?
[16:40] <Laney> no calendar or gmail account
[16:51] <seb128> Laney, didrocks, can you check your .cache/upstart/dbus.log ?
[16:52] <seb128> do you have (evolution-source-registry:15044): module-ubuntu-online-accounts-WARNING **: ubuntu_online_accounts_got_userinfo_cb: Failed to create ESource collection for AgAccount
[16:52] <seb128> ?
[16:52] <seb128> I've that in a guest session
[16:52] <Laney> no, just a load of activations
[16:52] <didrocks> no
[16:52] <Laney> for eds stuff
[16:52] <didrocks> same than Laney
[16:52] <didrocks> Activating service name='org.gnome.evolution.dataserver.Calendar7'
[16:52] <didrocks> Successfully activated service 'org.gnome.evolution.dataserver.Calendar7'
[16:52] <didrocks> for instance
[16:53] <seb128> :-(
[16:53] <didrocks> blackbox, I tried to get more logs, couldn't :/
[16:56] <seb128> yeah, I tried to look at bugzilla/grep source, not a lot of useful info
[16:56] <seb128> there is https://wiki.gnome.org/Apps/Evolution/Debugging#Calendar_Backends but that's lying
[16:56] <seb128> GOOGLE_BACKEND_DEBUG=1 doesn't exist in the source
[16:59]  * Laney knows nothing about the o-a stack really
[17:00] <Trevinho> willcooke: about your question before; I don't know about disabling that bug-tracker... Mh, Actually in some way I wouldn't do that, as we used that for targetting bugs, but... As you prefer
[17:02] <willcooke> Trevinho, what's the impact of targeting the bugs? The triaging we did was done on the ubuntu packages right?  So those are targeted correctly
[17:02] <Trevinho> seb128: you said you were working on removing the gconf backend, right?
[17:03] <seb128> Trevinho, no, but I guess I can have a look if you want, I've no idea about compiz though
[17:03] <seb128> I hope it's as trivial as dropping an optionnal build flag :p
[17:03] <Laney> you packager
[17:04] <seb128> Laney, didrocks, any signond error in syslog?
[17:05] <didrocks> seb128: nope, I looked at that first :/
[17:06] <seb128> didrocks, what if you
[17:06] <seb128> $ account-console list
[17:06] <seb128> $ account-console show <google id>
[17:07] <seb128> well, I'm unsure that's useful
[17:07] <seb128> would need mardy but he might off for today already
[17:07] <didrocks> seb128: installing -tools
[17:08] <didrocks> seb128: I have all secrets and such listed for the calendar google cred
[17:09] <didrocks> I guess at that point, let's see with mardy tomorrow?
[17:10] <seb128>      export CALDAV_DEBUG=all
[17:10] <seb128>  /usr/lib/evolution/evolution-calendar-factory
[17:10] <seb128> just try that
[17:10] <seb128> and then yes, otherwise need help from others
[17:11] <didrocks> seb128: same, no log :/
[17:11] <seb128> k, dunno then
[17:11] <seb128> wfm
[17:11] <seb128> you didn't have the account created before either?
[17:11] <seb128> I wonder if that's a bug in the account creation in xenial
[17:11] <seb128> I bet on new glib :p
[17:12] <didrocks> seb128: no, I had some that I removed a while ago
[17:12] <didrocks> but yeah, can be a bug in account creation
[17:13] <Laney> haha nice try
[17:13] <Laney> I would not have had to add my canonical calendars by URL if it worked in previous releases
[17:15] <Laney> I remember trying with one time passwords and stuff before
[17:17] <seb128> always worked for me
[17:17] <seb128> next time open a bug please
[17:17] <seb128> but let's debug this one
[17:17] <seb128> I wonder if evo changed
[17:17] <seb128> evolution let you add online calendar and seems to pick configured google account
[17:17] <seb128> I wonder if they force you to go through that rather than auto add all calendars linked to the account now
[17:19] <Laney> I did open a bug thanks
[17:19] <Laney> can't find it though :(
[17:22] <seb128> there was one but I though it was closed/marked as fixed
[17:22] <seb128> thanks for reopening
[17:22] <seb128> on that note, sport time, bbl
[17:27] <Laney> dude
[17:27] <Laney> don't act like that please
[17:39] <Trevinho> seb128: yeah, it should be easy...
[17:39] <Trevinho> (the gconf stuff)
[17:39] <Trevinho> if you prefer or have troubles let me know, that I can look at it
[17:40] <Trevinho> willcooke: yeah, but we always had different revisions upstream than in distro, so keeping the bugs there is like a list of "things hopefully to fix somewhen"...
[17:42] <willcooke> Trevinho, I see.  I think though, that's not manageable but just us few guys now..  Like, we should be more ruthless with bug triage.  If we think it's worth working on one day, it goes in the backlog (or gets targeted to a release) if not, WONT FIX
[17:42] <Trevinho> ok. It's just that we can't nominate bugs by default, so having targets is harder
[17:43] <Trevinho> I should probably get into the proper lp group
[17:43] <Trevinho> infinity: can I get access to ~ubuntu-release-nominators ?
[17:46] <willcooke> didrocks, Trevinho - let's pick this up tomorrow then.  Thanks guys
[17:46] <didrocks> yeah, let's see tomorrow, have a good evening guys!
[17:46] <willcooke> cheers didrocks
[17:47] <Trevinho> enjoy!
[17:47] <didrocks> see you willcooke!
[18:02] <Laney> bye
[18:03] <willcooke> night Laney
[18:45] <willcooke> g'night al;l