[01:50] <cyphermox> dupondje: hey
[03:51] <pitti> Good morning
[04:03] <duflu> pitty: afternoon :)
[04:03] <duflu> pitti: afternoon :)
[04:03] <duflu> Wow, dyslexia corrects my spelling
[04:03] <duflu> or not
[04:04] <duflu> too many ts
[04:05] <sarnold> it took me entirely too long to spot the difference :)
[04:16] <pitti> heh, it's a pitty, isn't it :)
[06:13] <didrocks> good morning
[06:18] <pitti> bonjour didrocks, ça va ?
[06:20] <didrocks> ça va pitti, et toi ?
[06:22] <pitti> didrocks: je vais bien, merci !
[06:26] <didrocks> hum, on the phone ML: "
[06:26] <didrocks> I've now opened up publication permissions to everybody … This means that if your silo does not touch any files under debian/, you can publish your own silos totally by yourself, no trainguards required."
[06:26] <didrocks> I wonder if the tech board/release team is aware about this
[06:27] <didrocks> it means that publications are not handled by people with upload rights anymore
[06:27] <didrocks> Laney: thought? did you know about it? ^
[06:27] <robru> didrocks: yes slangasek told me this was agreed with tech board.
[06:28] <didrocks> ah nice!
[06:28] <robru> the rule is as long as debian/ isn't touched
[06:28] <robru> and only for canonical-owned projects
[06:28] <didrocks> robru: do you have anything to guard when debian/ is touched, just for the curiousity?
[06:28] <didrocks> or it's just the existing warning?
[06:28] <thumper> o/
[06:28] <robru> didrocks: yes, the same "packaging diff" is in place, ACK requires proper checkUpload rights
[06:29]  * thumper is done for the day
[06:29] <thumper> I miss you folks
[06:29] <didrocks> robru: ok, as long as people are not too eager clicking checks, that's a nice one! :)
[06:29] <didrocks> hey thumper!
[06:29] <didrocks> thumper: have a nice evening, long time not seeing you!
[06:29] <thumper> yeah.. one day... one day we might have another all hands
[06:29] <didrocks> heh, yeah, one day ;)
[06:29] <thumper> it'd be epic
[06:30] <thumper> maybe when we actually make money
[06:30] <thumper> :)
[06:30] <didrocks> ;)
[06:30] <thumper> laters
[06:31] <pitti> didrocks, robru: err, I certainly didn't agree to this; you can break stuff with the upstream parts just as well as with the packaging bits; and the silo is not limited to touch-y packages, you can upload kernels or glibc or whatever to it
[06:31] <robru> pitti: uh, our boss told me to do this, sorry, wasn't my decision
[06:32] <pitti> well, "my boss told me" != "TB agrees" :)
[06:32] <robru> pitti: he told me it was agreed with the TB.
[06:33] <robru> pitti: I'll dig up the emails and forward them
[06:34] <pitti> hm, so we now have folks who never signed the CoC, never received any ubuntu dev training, ignore test results, and have unrestricted access to the ubuntu archive
[06:34] <didrocks> that's the difference with the daily release, indeed, when we had a filtering list (in addition to the bot which only uploaded some components) on components to autopublish
[06:35] <robru> pitti: didrocks: some discussion here: https://bugs.launchpad.net/cupstream2distro/+bug/1459186
[06:35] <pitti> didrocks: was that a public ML, or internal one? I. e. anything to refer to on the TB list?
[06:35] <robru> pitti: if there are train users you know of who didn't sign CoC please let me know and I'll hound them
[06:37] <didrocks> pitti: I was referring to the announcement on the phone ML
[06:37] <pitti> robru: hm, wasn't that bug just the opposite? restricting silo uploads (or at least publication) to people who can upload that package directly to ubuntu too?
[06:37] <didrocks> yeah
[06:37] <didrocks> I understand the bug the same
[06:37] <didrocks> especially with: "2) Signoff permissions should track the archive permissions for a package: respecting archive components (ubuntu-core-dev vs. motu) and per-package uploaders."
[06:37] <pitti> didrocks: I meant, was it the public phone ML?
[06:37] <robru> pitti: in the comments slangasek explains the exception for canonical-owned projects that have no debian/ changes
[06:38] <didrocks> pitti: yes "IMPORTANT ANNOUNCEMENT: CI Train changes"
[06:38] <didrocks> robru: yeah, but he seems to intend that "must enforce checkupload for merges with diffs, all manual sources, and NEW.
[06:38] <didrocks> "
[06:38] <didrocks> as you wrote
[06:38] <pitti> robru: right, but that certainly doesn't cover things like glibc, qt, systemd, gcc, etc.
[06:38] <didrocks> did you add those checks?
[06:39] <didrocks> (before opening publication for the other case to everyone)
[06:39] <robru> pitti: maybe it wasn't clear, not just anybody can upload anything. train is not allowing kernels or glibc published by anybody. only canonical-owned stuff.
[06:39] <pitti> robru: i. e. you can upload anything directly to the silo
[06:39] <robru> pitti: you can upload anything to the silo but the only time checkUpload is not enforced is if the package is owned by canonical and has no debian/ changes.
[06:39] <pitti> robru: ah, which creds do you need to upload directly to a silo?
[06:39] <didrocks> ah, so you only enable people to publish if there is no change in debian/, (and so, not a new packages) + only canonical project?
[06:40] <robru> pitti: also actually not just anybody can upload to the silos.
[06:40] <pitti> robru: ok, so for publishing the silo it checks the packages against a whitelist?
[06:40] <didrocks> ok, the announcement wasn't clear about it :)
[06:40] <robru> pitti: you need ~ci-train-ppa-service membership to upload sources to silos.
[06:41] <robru> pitti: there's no whitelist per se, currently the train assumes "MP = canonical owns this", which is reasonably true at this point as there are rather narrow packaging requirements that the train enforces that other random source packages don't have.
[06:41] <robru> pitti: eg if you were a bad actor and you tried to fake an MP to get around the check, your MP would necessarily have a ton of packaging changes that would trigger the check.
[06:42] <robru> or it wouldn't even build
[06:45] <pitti> robru: thanks for clarifying
[06:46] <robru> pitti: you're welcome! Feel free to raise this with slangasek when he's back next week, I'm happy to revisit this (actually I wasn't even involved in the original decision anyway)
[06:46] <pitti> robru: well, it sounds like it's certainly far from "if your silo does not touch any files under debian/, you can publish your own silos totally by yourself"
[06:47] <robru> pitti: right, it's for MPs only, i forgot to mention that.
[07:02] <Mirv> didrocks: the ACK:s are now not possible by anyone who does not have the actual upload rights to the particular package
[07:02] <Mirv> so, all main packages with debian/ changes always require a core-dev to run the publishing
[07:03] <Mirv> robru: pitti: manually uploaded packages can't be published regardless of which changes they had, the publisher needs to have MOTU or core-dev rights accordingly
[07:03] <Mirv> oh, as discussed
[07:04] <robru> heh, yeah
[07:04] <didrocks> ;)
[07:04] <didrocks> thanks for confirming, I guess he main misunderstanding is coming from the email (a little bit too vague)
[07:04] <Mirv> I just started from where I was higlighted with 'trainguards'
[07:04] <didrocks> :p
[07:05] <robru> I'll clarify the email
[07:05] <didrocks> thanks robru!
[07:05] <robru> didrocks: you're welcome
[07:16] <larsu> good morning!
[07:18] <seb128> good morning desktopers ;-)
[07:19]  * larsu gets some Schrippen
[07:20] <seb128> larsu, bread?
[07:21] <didrocks> good morning larsu, seb128!
[07:22] <seb128> lut didrocks
[07:22] <larsu> seb128: https://en.wikipedia.org/wiki/Bread_roll
[07:22] <larsu> it even contains that word :)
[07:22] <pitti> bonjour seb128 !
[07:22] <pitti> hey larsu, guten Appetit!
[07:22] <larsu> salut didrocks and pitti !
[07:22] <seb128> pitti, salut, ça va ?
[07:22] <larsu> danke :)
[07:22] <pitti> seb128: ça va bien, et toi ?
[07:27] <seb128> pitti, ça va bien aussi merci ;-)
[07:33] <larsu> pitti: Laney suggested last night that there might be some dh_ magic for my rules file to get language-specific things installed
[07:33] <larsu> or would I need to hack langpacks for that?
[07:34] <pitti> larsu: what are "things"?
[07:35] <pitti> larsu: pkgstriptranslations currently strips out GNOME help files
[07:35] <pitti> (both old and mallard)
[07:35] <larsu> pitti: translations of place names
[07:35] <larsu> for the list in system settings
[07:35] <larsu> (when autocompleting time zone)
[07:35] <pitti> larsu: are these po files?
[07:36] <pitti> I really suggest that this should use standard gettext with po/mo files, not some custom XML lists or what not
[07:36] <larsu> pitti: it would be more efficient if they weren't
[07:36] <larsu> I was kind of expecting this answer :)
[07:37] <pitti> larsu: so, we have a concept of "static" translations, like translated help files or screenshots; pkgbinarymangler can pick those up and put them into the _static.translations.tar.gz tarball
[07:37] <pitti> they will then end up in langpacks
[07:37] <pitti> but these are hard to translate obviously
[07:37] <pitti> so if you actually care for translations, do use gettext -- what makes this hard?
[07:37] <larsu> I don't
[07:37] <larsu> I already have the translations
[07:38] <larsu> they're part of geonames
[07:38] <larsu> pitti: how does this work exactly?
[07:39] <dupondje> nobody with wily that uses L2TP ? ;) might be cool if somebody could test https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/1487183 on wily.
[07:41] <pitti> larsu: so, if you e. g. have a file "geonames_de.xml", you can put that into the static tarball; and then langpack-o-matic needs a corresponding patch to recognize those, detect the locale from the path or file name, and put that into the corresponding langpack
[07:41] <pitti> but that's a really inflexible hack
[07:42] <pitti> larsu: again -- please do use gettext at runtime, static translations are hideously hard to translate, process, and update; we also don't support translating them on LP
[07:42] <pitti> larsu: if you need some fast typeahead search, build a list of all translated items (for your current locale) in memory
[07:42] <pitti> but I figure adding a dgettext() call to the iteration should be okay
[07:43] <pitti> dgettext is fast
[07:44] <seb128> dupondje, you might want to try on #ubuntu-devel unsure anyone on desktop use strongswan
[07:46] <larsu> pitti: if I use it at runtime I might as well use .po files. Not sure that we'll ever need translations on launchpad for this, but I guess you're right: let's go with the known workflow first and change it when if we notice problems
[07:46] <larsu> pitti: thanks!
[07:46] <pitti> larsu: asked the other way around, what makes calling dgettext at runtime harder than using some pre-translated separate files?
[07:48] <larsu> pitti: it's not harder, but doing a string lookup (with context, as there are different cities with the same name in different countries) might be less efficient
[07:48] <larsu> (not in speed, but memory)
[07:48] <larsu> but lets see how big this will get
[07:49] <pitti> larsu: you have the .mo files on the system anyway, no?
[07:49] <pitti> larsu: I can't see how loading a pre-translated set of names into memory would be much more efficient
[07:51] <larsu> pitti: hm, indeed. I got most of this from a short discussion with desrt yesterday. I'm not yet sure myself :)
[07:56] <Sweet5hark> moin
[07:58] <seb128> hey Sweet5hark
[07:59] <willcooke> goodly morlode
[08:02] <didrocks> hikiko: hey, when you get a chance, do you mind having a look at https://code.launchpad.net/~didrocks/unity/remove-unity2d/+merge/271916?
[08:02] <seb128> hey willcooke
[08:02] <seb128> is that command working for others?
[08:02] <seb128> $ /usr/share/software-center/piston_generic_helper.py --datadir /usr/share/software-center/ --needs-auth --no-relogin SoftwareCenterAgentAPI subscriptions_for_me
[08:03] <seb128> I've errors about it in my syslog
[08:03] <seb128> mvo_, dobey, ^ do you know about that?
[08:03] <seb128> "ERROR: can not obtain a oauth token"
[08:04] <didrocks> seb128: opening a window, want me to connect?
[08:04] <hikiko> hey didrocks
[08:04] <hikiko> sure
[08:04] <didrocks> thx :)
[08:04] <seb128> didrocks, if you can, just to see if it works
[08:04] <mvo_> seb128: same failure, without further looking at this I wonder if the sso api has changed maybe?
[08:04] <seb128> mvo_, yeah, unsure ... what would be the component to report that on?
[08:05] <mvo_> seb128: its part of software-center
[08:05] <Laney> hullo
[08:05] <didrocks> seb128: mvo_: interesting, wfm though (and I see my previous purchases)…
[08:05] <mvo_> seb128: or did you maybe revoke your token at some point?
[08:05] <didrocks> hey Laney
[08:05] <hikiko> didrocks, give me 10 minutes to get rid of my built unity and I ll compile it
[08:06] <seb128> mvo_, I didn't but maybe it had been revoked for some external factor, shouldn't it reprompt me then?
[08:06] <seb128> didrocks, thanks
[08:06] <mvo_> seb128: iirc it will ask via dbus for a token from the sso-client and then verify the client against the server. for me it seems to fail in this step, what backtrace do you get?
[08:06] <mvo_> seb128: and yes, it should re-prompt you, not sure why its not doing this
[08:06] <mvo_> seb128: aha, because of "--no-relogin"
[08:07] <seb128> File "/usr/lib/python2.7/dist-packages/piston_mini_client/__init__.py", line 491, in get
[08:07] <seb128> return self.request_url(url, method='GET', headers=headers)
[08:07] <seb128> File "/usr/lib/python2.7/dist-packages/piston_mini_client/__init__.py", line 435, in request_url
[08:07] <seb128> body = handler.handle(response, response_body)
[08:07] <seb128> File "/usr/lib/python2.7/dist-packages/piston_mini_client/failhandlers.py", line 116, in handle
[08:07] <seb128> data=self.data)
[08:08] <mvo_> seb128: is that the full bt? if not, could you pastebin the full one? no api error or something like this?
[08:10] <seb128> mvo_, http://paste.ubuntu.com/12519695/
[08:13] <mvo_> seb128: thanks, thats similar to what I see - looks like a genuine bug :/
[08:18] <seb128> mvo_, is that something dobey or nessite would know about if it's ubuntusso?
[08:18] <mvo_> seb128: so if you use seahores and delete the "Ubuntu one" token, I suspect it will ask you to relogin?
[08:18] <seb128> mvo_, I guess I could try but then I loose the way to reproduce and test a fix/get more info
[08:18] <mvo_> seb128: not sure if they will know, maybe re-prompt expired tokens never got implemented in s-c, I'm not sure
[08:18] <mvo_> seb128: ok, then keep it this way
[09:05] <Laney> https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-wallpapers/ubuntu/view/head:/warty-final-ubuntu.png
[09:06] <Laney> O_O
[09:06] <Trevinho> mhmh
[09:07] <willcooke> wat
[09:08] <Trevinho> I guess that nautilus desktop is smart enough to convert that log in some kind of art...
[09:08] <Laney> turns out that dbus logs translate exactly to the Ubuntu default wallpaper
[09:08] <Laney> WHO KNEW
[09:09] <Trevinho> Now that we know the trick, we can just do the new art design by ourselves at every release :)
[09:10] <seb128> lol
[09:13] <didrocks> seeing the number of "Laney" occurence in the calendar events, we don't know at all who committed that for sure :p
[09:13] <Laney> https://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-wallpapers/ubuntu/changes?filter_file_id=elephantskin.jpg-20070925092320-wp63xkqaf9y3tbmp-1
[09:13] <Laney> this probably gives it away too :P
[09:13] <didrocks> Laney: quick, whistle and walk away :p
[09:13] <Laney> willcooke: btw...
[09:14] <Laney> looking at this reminds me that we have an "official" greyscale too
[09:14] <Laney> do we get a new version of that?
[09:14] <willcooke> Laney, I'll speak to design now...
[09:14] <Laney> /usr/share/backgrounds/Suru_Wallpaper_Desktop_4096x2304_Gray.png
[09:15] <Laney> it's based on the colour one
[09:15] <didrocks> thanks for the merge Trevinho :)
[09:15] <Laney> so hopefully not much work
[09:16] <willcooke> yeah, should be easy
[09:16]  * didrocks was cleaning his desktop, hence the unity2d notice
[09:16] <Trevinho> seb128: can you ack me this https://code.launchpad.net/~3v1n0/libunity/launcher-use-class-settings/+merge/271847 ?
[09:16] <Trevinho> didrocks: np, I'll land that soon
[09:21] <Trevinho> seb128: for bug #1470097 is there a way to get those ddebs on a ppa instead of waiting the SRU thing?
[09:22] <seb128> Trevinho, you can do an upload to a ppa, citrain ones include ddebs I think
[09:22] <seb128> Trevinho, let me review the settings one
[09:23] <Trevinho> it shouldn't https://bugs.launchpad.net/ubuntu-lt/+bug/1420185
[09:23] <Trevinho> ah, last comment doesn't match the bug status, so maybe...
[09:27] <hikiko> didrocks, it looks good to me
[09:27] <hikiko> I can't see anything wrong
[09:27] <hikiko> I am going to approve it
[09:28] <didrocks> hikiko: great! I think that Trevinho approved it already though
[09:28] <hikiko> hahaha
[09:28] <hikiko> lol and I didn't look at the diff, I built it first...
[09:28] <hikiko> \m/
[09:28] <hikiko> then I noticed
[09:28] <hikiko> it's just text
[09:28] <hikiko> :p
[09:29] <hikiko> fail :p
[09:34] <seb128> Trevinho, libunity change  approved, thanks
[09:36] <Trevinho> seb128: thank you!
[09:37] <seb128> Trevinho, yw! thanks for the fix ;-)
[09:38] <Trevinho> seb128:  I was thanking you... Then you went out, so my tab autocompletion was actually about to mention s---abdfl
[09:38] <Trevinho> thank God i didn't press enter too quickly :D
[09:38] <seb128> lol
[09:38] <seb128> Trevinho, seems like xchat-gnome closed/segfaulted/something
[09:38] <Trevinho> seb128: I've this one for you too btw :) https://code.launchpad.net/~3v1n0/compiz/vivid-rebuild-ddebs/+merge/271930
[09:38] <seb128> I saw the notify-osd bubble but xchat was closed
[09:39] <seb128> Trevinho, there is a merge conflict there
[09:39] <Trevinho> ah, yeah I was wondering what happened... That's weird that it was a segfault though as we got the "Remote host closed the connection", and not ping timeout
[09:39] <Trevinho> seb128: sorry, I ddin't propose to vivid branch (lp-propose doesn't work that way -_-)
[09:40] <Trevinho> seb128: this should work https://code.launchpad.net/~3v1n0/compiz/vivid-rebuild-ddebs/+merge/271931
[09:42] <seb128> Trevinho, right, approved
[09:43] <Trevinho> seb128: thanks
[09:43] <seb128> yw!
[09:43] <Trevinho> ... and silo'ed
[13:30] <Trevinho> Europeans, do the agency replied promptly to you for tickets request? I got no answer yet (since yesterday)
[13:30] <pitti> Trevinho: Omnia? yes, they usually do within a few hours
[13:30] <Trevinho> pitti: yeah, generally so it happens, but not this time
[13:31] <larsu> Trevinho: they replied to my email from last night an hour ago
[13:31] <Trevinho> larsu: mh, ok... maybe I'm on the queue then
[13:31] <larsu> Trevinho: ya, probably they're just a bit busy right now
[13:37]  * larsu files dbus bug after not being able to hunt the problem down himself
[13:38] <Laney> iz dbug bug?
[13:38] <larsu> yes
[13:38] <larsu> https://bugs.freedesktop.org/show_bug.cgi?id=92074
[13:38] <seb128> Laney, btw, new glib stable is out, I guess it's on your list?
[13:38] <larsu> thankfully we have busctl monitor now, which works as expected because it doesn't yet use the new BecomeMonitor stuff
[13:38] <seb128> I'm asking because I'm chassing some of the warnings spam in logs and they turn off deprecation warnings
[13:39] <seb128> which I could use ;-)
[13:39] <didrocks> haha, they did as well, nice \o/
[13:39] <larsu> oh wow
[13:39] <Laney> yes thanks
[13:39] <larsu> I guess they didn't consult desrt?
[13:39] <seb128> https://git.gnome.org/browse/glib/commit/?id=3bd1618ea955f950f87bc4e452029c5f0cea35aa
[13:39] <seb128> unsure
[13:39] <seb128> no bug report mention
[13:40] <larsu> that commit message is gold
[13:40] <Laney> I think it's just the done thing now
[13:40] <larsu> (and spot on)
[13:40] <desrt> also only on the stable release, as we did before
[13:40] <seb128> I'm glad people agreed on that
[13:40] <larsu> desrt: you argued against doing that....
[13:40] <seb128> desrt, there was some pushback previous cycles to do it even in stable
[13:40] <desrt> larsu: and yet, did it :)
[13:41] <larsu> indeed
[13:41] <desrt> i don't like it, but i agree with the commit message
[13:41] <didrocks> seb128: +1+1+1 :)
[13:41] <seb128> didrocks, :-)
[13:41] <Laney> glad you are all so excited
[13:41]  * larsu learns about org.freedesktop.DBus.Debug.Stats
[13:41]  * desrt yawns
[13:41] <larsu> how is that not specified? This is awesome stuff
[13:41] <desrt> got an extra-large coffee today.
[13:42] <desrt> *bzz*
[13:51] <Laney> bzbzbz
[14:12] <chrisccoulson> ricotz, please let me know if you have any issues with the firefox-beta.* branches (I've not tried creating a Firefox 42 upload from it yet)
[14:35] <ricotz> chrisccoulson, I will notice soon then
[15:16] <qengho> chrisccoulson: Will you please give me a tutorial of your firefox workflow one day?
[15:26] <willcooke> it's coming
[15:30] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2015-09-22
[15:30] <meetingology> Meeting started Tue Sep 22 15:30:53 2015 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <didrocks> let's meet!
[15:31] <willcooke> Roll call: andyrock (out), attente, desrt,  dgadomski, didrocks, fjkong, happyaron (out), hikiko, laney, larsu, qengho, seb128, sweet5hark (probably out), themuso (out), tkamppeter, trevino, robert_ancell (out)
[15:31]  * Trevinho with "h" is here :)
[15:31] <Laney> revino
[15:31] <Laney> evino
[15:31] <FJKong> hi
[15:31] <Laney> vino
[15:31] <Laney> ino
[15:31] <Laney> no
[15:31] <Laney> o
[15:31] <seb128> hey
[15:31] <Laney>
[15:32] <dgadomski> hey
[15:32] <Trevinho> Vino... (means wine in Italian :p)
[15:32] <qengho> Three wines, plz
[15:32] <Trevinho> that's it :D
[15:32] <larsu> \o
[15:32]  * willcooke fixes his list
[15:33] <willcooke> and has one of the wines
[15:33] <Trevinho> :D
[15:33] <willcooke> Right then...
[15:33] <willcooke> #topic andyrock
[15:33] <willcooke> * Bug scrubing
[15:33] <willcooke> * Investigating on why the scopes on 15.04+ are not reliable
[15:33] <willcooke> * Code reviews
[15:33] <willcooke> * Helping understanding the cause of #1497002 Recent Wily i386 live
[15:33] <willcooke> DVDs load with no launcher, top bar, desktop icons, etc. There is a
[15:33] <willcooke> quick workaround
[15:33] <willcooke> * Updating some old branche
[15:33] <willcooke> #topic attente
[15:34] <attente> popup menu placement continued, in the process of porting over several gtk widgets to it
[15:34] <attente> spent a day up at xdc with desrt and robert_ancell
[15:34] <attente> (eof)
[15:34] <willcooke> thanks attente
[15:34] <willcooke> #topic desrt
[15:36] <willcooke> desrt we will come back to you
[15:37] <willcooke> #topic dgadomski
[15:37] <dgadomski> hey
[15:37] <dgadomski> only 1 thing in the desktop area this week: I've been looking into the reason for problems with installing PPA version of octave on trusty with HWE updates - bug #1424059. Looks like the cause was incorrect resolving of versioned dependencies with 'Provides:'. A workaround for now is to prepare a osmesa-less build of octave (agreed with the ppa maintainer and tested).
[15:37] <dgadomski> EOF
[15:37] <willcooke> thanks a lot dgadomski
[15:37] <willcooke> #topic didrocks
[15:37] <didrocks> o/
[15:38] <didrocks> !\ This reports include the last 2 weeks as was on a conference last week
[15:38] <didrocks> Ubuntu Make:
[15:38] <didrocks> - released 15.09.2 featuring Android SDK downlod only, exit code fixes (both of those, by external contributor)
[15:38] <didrocks> - added additional pep8 and tests fixes. Loving pep8 on trusty btw (no easy way to get something passing on trusty pep8 and wily pep8 in term of identation) :p
[15:38] <didrocks> - archived our daily jenkins test jobs to ensure we have an in-code backup
[15:38] <didrocks> - bugs management and PR reviews
[15:38] <didrocks> Developer experience:
[15:38] <didrocks> - experiment and play on our developer experience writing a Go service on snappy
[15:38] <didrocks> - write that experience on a (too long) documentation, one with and without snapcraft, on a VM and with a raspbery pi 2
[15:38] <didrocks> - draft what our next step for developer experience on snappy should be and separation of tools concerns
[15:38] <didrocks> - attended to various meetings on this
[15:38] <didrocks> Misc:
[15:38] <didrocks> - attended to Polymer first ever conference. Back with some plastic ideas on how our HTML5 developer story should be
[15:38] <didrocks> - talked with dbarth about an eventual prototyping around our HTML5 developer story & polymer would be
[15:38] <didrocks> - archive admin and patch piloting duties
[15:38] <didrocks> EOF
[15:38] <willcooke> thanks didrocks
[15:38] <willcooke> #topic FJKong
[15:39] <FJKong> pinyin search:
[15:39] <FJKong> improve speed of indexing file to db
[15:39] <FJKong> research on index every first Chinese Character
[15:39] <FJKong> switch to cmake
[15:39] <FJKong> sogou pinyin:
[15:39] <FJKong> test right clicking pop menu
[15:39] <FJKong> eof
[15:40] <willcooke> thanks FJKong
[15:40] <willcooke> FJKong, any visa issues or is that all good?
[15:41] <desrt> zomg.  sorry!
[15:41] <FJKong> no problem
[15:41] <willcooke> FJKong, great!
[15:41] <willcooke> #topic desrt
[15:41] <FJKong> I have VISA for 2 years for UK
[15:41] <willcooke> FJKong, excellent, that's worked out nicely then
[15:42] <willcooke> hey desrt
[15:42] <desrt> hey.  had a minisprint last week for a few days, also went to xdc for a day and worked on the usual inotify stuff during friday.  did some patch reviewing and stuff this morning.
[15:42] <Laney> doing better the Ai Weiwei
[15:42] <desrt> not much else to report
[15:42] <willcooke> thanks desrt
[15:43] <willcooke> #topic happyaron
[15:43] <willcooke> 1. fcitx package update (but not a complete fix, thanks Laney)
[15:43] <willcooke> 2. libxml2 NMU mess resolved for Debian
[15:43] <willcooke>     http://anonscm.debian.org/cgit/debian-xml-sgml/libxml2.git/diff/?h=debian/2.9.2%2bzdfsg1-4&id=76c19f4d5b3328c05649314336d27c1f44a49e96&id2=fccd80a7d35b9eefabcc384d5c9fe89d9545dd22
[15:43] <willcooke> 3. ubiquity slideshow update for Ubuntu Kylin
[15:43] <willcooke> 4. fcitx upstream bug triaging/analysis:
[15:43] <willcooke>     a) misconfiguration cases - a lot for those who turn off the
[15:43] <willcooke> installation of Recommends packages
[15:43] <willcooke>     b) fcitx ^w out-of-process UI has issues when the desktop runs
[15:43] <willcooke> with thin client configurations
[15:43] <willcooke> 5. pinyin search packaging: in progress
[15:43] <willcooke> #topic hikiko
[15:44] <hikiko> hi, : closed some bugs, fixed the cube and deformed cube caps images that appeared off-center, and I am going to investigate this shadow bug and  a few other issues that were revealed while I was trying to reproduce the problem and fix the cubeaddon eof
[15:44] <willcooke> thanks hikiko
[15:44] <willcooke> #topic Laney
[15:45] <Laney> • Normal release team stuff (FFes and so on)
[15:45] <Laney> • Test/sync glib
[15:45] <Laney> • Work on some s-l-o-w machines to address a gdk-pixbuf build failure - Company committed it upstream & I just uploaded to Debian, will sync if it works.
[15:45] <Laney> • gtk 3.16.7
[15:45] <Laney> • glib 2.45.8
[15:45] <Laney> ∘ smooth some test failures (upload/fwd a fix for tracker, some retries)
[15:45] <Laney> • Patch pilot, concentrated on http://reqorts.qa.ubuntu.com/reports/sponsoring/ubuntu-desktop.html - almost empty, help appreciated on the remainders.
[15:45] <Laney> • Notice Unity was deleting launcher icons when applications were upgraded, slight behaviour change in glib, fix that.
[15:45] <Laney> • Hopefully fix some trigger loops to avoid (dist-) upgrade failures
[15:45] <Laney> • Look at new default wallpaper, needs greyscale version
[15:45] <Laney> • Update gst-fluendo-mp3 in Debian to new release & drop 0.10 version
[15:45] <Laney> • Fix toolbar fullscreen hiding in eog, not uploaded since waiting for other fixes
[15:45] <Laney> ☠
[15:46] <larsu> Laney made the glib top contributors list this cycle
[15:46] <Laney> HAHA
[15:46] <Laney> I think the barrier was pretty low
[15:46] <willcooke> thanks Laney
[15:46] <willcooke> #topic larsu
[15:46] <Laney> thanks larsu ♥
[15:46] <seb128> Laney, we should have a look at updating the fluendo plugin in the partner archive
[15:46] <larsu> - investigate and fix unity crasher (bug #1495173)
[15:46] <larsu> - unsuccessfully hunt down dbus-monitor bug (file it instead)
[15:46] <larsu> - [in progress] geonames: package, review, think about how to efficiently incorporate translations
[15:46] <larsu> - [in progress] unity-control-center: draft branch that works with geonames
[15:46] <larsu> - [in progress] eog: fix fullscreen toolbar; add traditional menubar
[15:46] <larsu> - [in progress] investigate making all output go to the journal and use gnome-logs

[15:47] <larsu> s/>/u>/
[15:47] <willcooke> thanks larsu
[15:47] <larsu> sorry about all the in progress stuff
[15:47]  * larsu should wrap up
[15:47] <willcooke> seb128, larsu shall we talk fluendo now or at the end?
[15:47] <seb128> yes
[15:47] <willcooke> s/larsu/laney
[15:47] <seb128> larsu, good list of in progress ;-)
[15:48] <larsu> willcooke: you and didrocks....
[15:48] <seb128> larsu, btw I tried gnome-logs, it's nice but we loose e.g access to Xorg.0.log
[15:48] <seb128> so unsure if we should switch this cycle
[15:48] <seb128> or plan better for next cycle
[15:48] <larsu> yes, wait for next
[15:48] <larsu> it's too tight
[15:48] <seb128> k
[15:48] <larsu> also missing traditional menu and title bar
[15:48] <seb128> willcooke, sorry for interrupting ;-)
[15:48] <willcooke> nw
[15:48] <seb128> larsu, well, that's ok
[15:49] <seb128> more annoying at the windows corners
[15:49] <seb128> but that's not specific to gnome-logs
[15:49] <larsu> seb128: blame Trevinho...
[15:49] <seb128> yeah, we need to put that bug on the lts list
[15:49] <didrocks> +1
[15:49] <larsu> seb128: I'm all for doing the switch in gtk, but then we lose shadows
[15:49] <seb128> Trevinho, do you have a unity/compiz bug for that?
[15:50] <Trevinho> seb128: mh, I think i read something, let me check
[15:50] <seb128> Trevinho, thanks
[15:50] <seb128> willcooke, I think we can continue with the meeting ;-)
[15:50] <willcooke> :)
[15:50] <willcooke> #topic qengho
[15:50] <qengho> * fixed new armhf build problem with chromium-browser.
[15:50] <qengho> * l10n and Athlon SSE worries worked out, so giving to #security for release.
[15:50] <qengho> * learning how to work on firefox. Hopefully will prepare next release.
[15:50] <qengho> * looked for flights, but haven't picked one yet.
[15:50] <qengho> EOF
[15:51] <willcooke> thanks qengho
[15:51] <willcooke> #topic seb128
[15:51] <Laney> qengho: will it fix the autopkgtests?
[15:51] <seb128> • synced some bugfix updates from debian
[15:51] <seb128> • desktop updates (totem, webkitgtk, bluez)
[15:51] <seb128> • NEW reviews
[15:51] <seb128> • fixed u-c-c/bluez5 regression with ssp devices
[15:51] <seb128> • reviewed e.u.c top errors, reported some bugs on launchpad and upstream, pinged some people about some of the issues
[15:51] <seb128> • helped with the unity bugs triaging
[15:51] <seb128> • investigated software-center/unity integration issue
[15:51] <seb128> • looked at syslog warnings and reported some bugs with details about some of those
[15:51] <seb128> • reviewed packaging & tried new geonames library for larsu
[15:51] <seb128> • contributed to https://bugs.launchpad.net/ubuntu/+bugs?field.tag=rls-w-incoming ... if you have some free cycles please try to have a look and pick a few bugs
[15:52] <seb128> we have quite some annoying bugs on that list ^, would be nice to tackle some before wily if we can
[15:52] <qengho> Laney: No, it won't. That's some dependency of a dependency of a dependency problem that I haven't tracked down.
[15:52] <seb128> willcooke, I wonder if we need another list for wily, or maybe milestone as well
[15:52] <Laney> you're meant to triage from the incoming list
[15:52] <larsu> seb128: thanks for looking at those warnings!
[15:52] <seb128> we dumped "would be nice to fix for the lts" on rls-w-incoming
[15:52] <willcooke> seb128, well I was adding to that list because X-incoming doesn't (didnt) exist
[15:53] <seb128> Laney, yeah, but we didn't use it this way, we used it as a lts todolist...
[15:53] <didrocks> or use priority to order the list?
[15:53] <seb128> Laney, see ^
[15:53] <willcooke> so I think if we can do anything on that list now, great - but then we can do a proper review at the sprint at take across the ones we want
[15:53] <Laney> it can be both
[15:53] <seb128> didrocks, launchpad doesn't have priority, importance you mean?  but some "low" importance are easy to fix and should be done for wily imho
[15:53] <Laney> to target bugs, nominate and remove the tag
[15:53] <Laney> review the rest of them to move to rls-x-incoming
[15:54] <willcooke> seb128, oh - right, what you said.  Misread it.
[15:54] <didrocks> seb128: importance, yeah, sorry, I think we could focus on the critical/high one. Doesn't prevent anyone having some free time to pick an easy "low" one
[15:54] <seb128> right
[15:54] <seb128> we should probably make a rls-x-incoming and move things there
[15:54] <willcooke> +1
[15:54] <seb128> good
[15:54] <seb128> thanks
[15:54] <Laney> why?
[15:55] <Laney> or, why before this release?
[15:55] <seb128> Laney, to have a better view of what is for wily
[15:55] <seb128> and what is not
[15:55] <Laney> that view is supposed to be http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-w-tracking-bug-tasks.html
[15:55] <seb128> so we just need to accept nominations?
[15:56] <Laney> nominate and remove the tag
[15:56]  * Laney just checked that old email
[15:56] <seb128> k
[15:56] <seb128> wfm
[15:56] <seb128> going to do that
[15:56] <seb128> Laney, thanks ;-)
[15:56] <Laney> then we can see what's left after release to move over
[15:56] <Laney> ty
[15:56] <seb128> I didn't use that page for a while, I forgot how it was working
[15:56] <Laney> try with some test one at first maybe
[15:56] <Laney> to make sure it works
[15:56] <seb128> right
[15:57] <willcooke> ok, that sounds good
[15:57] <willcooke> so keep adding to rls-w-incoming for now then
[15:58] <seb128> :-)
[15:58]  * willcooke checks the sprint agenda
[15:59] <willcooke> added
[15:59] <willcooke> to the top
[15:59] <willcooke> #topic sweet5hark
[15:59] <willcooke> - LibreOffice conference
[15:59] <willcooke> #topic TheMuso
[16:00] <willcooke> * Finished  packaging up PulseAudio 6.99.2, which will become 7.0 shortly. It can be found in ppa:ubuntu-audio-dev/pulse-testing, amd64 and i386 only, armhf failed to build due to qemu related segfault.
[16:00] <willcooke> * Fleshed out a little more design for the accessibility profile blueprint, and finished drafting a blog post about it.
[16:00] <willcooke> * Started preparing at-spi and orca package updates to be put into the Ubuntu Accessibility dev PPA for general use. Updates will be provided from ppa:accessibility-dev/ppa for Orca, and the at-spi stack, for the LTS, vivid, and wily.
[16:00] <willcooke> #topic tkamppeter
[16:00] <tkamppeter> - hplip: Backported hpcups crash fix from upstream, use pkexec instead of gksu for hp-plugin-ubuntu
[16:00] <tkamppeter> - cups: USB-backend: Added new quirk rules for delayed closing of the backend for several older HP LaserJet printers
[16:00] <tkamppeter> - ippusbxd: Released 1.23 which logs all communication content as hex dump in debug mode and actually automatically terminates when the printer is disconnected or turned off.
[16:00] <tkamppeter> - Bugs.
[16:00] <willcooke> tjamls tkamppeter
[16:01] <willcooke> erm, thanks tkamppeter
[16:01] <willcooke> tkamppeter, did your parcel arrive yet?
[16:02] <willcooke> #topic Trevinho
[16:02] <Trevinho> · Debugging webkit-gtk to get proper OSB theming. Speaking with upstream.
[16:02] <Trevinho> · Fixed unit tests on nux, now they run at every build.
[16:02] <Trevinho> · Fixed nux events handling on mouse-release when a new view was getting the mouse input
[16:02] <Trevinho> · Some tweaking on bugs management scripts
[16:02] <Trevinho> · Show-menus-tuning unity branch
[16:02] <Trevinho> · New unity/nux landing
[16:02] <Trevinho> · Add selective grab to compiz and use it in move and resize plugins
[16:02] <Trevinho> · New fixes for gsettings in libunity
[16:02] <Trevinho> · Prepared no-change SRU for compiz in vivid to get dbgsym's
[16:02] <Trevinho> · Finished work on new dash OSB (after fighting with nux bugs and oddities), needs cleanup
[16:02] <Trevinho> · Got sprint flights
[16:02] <Trevinho> · Reviews
[16:02] <Trevinho> 
[16:03] <willcooke> :) thanks Trevinho
[16:03] <willcooke> #topic robert_ancell
[16:03] <willcooke> - Attended XDC 2015
[16:03] <willcooke> - Released simple-scan 3.18.0
[16:03] <willcooke> #topic any other business
[16:04] <willcooke> Please get your travel auth in if you haven't already
[16:04] <willcooke> Anyone else?
[16:04] <desrt> i'd like to share this:
[16:04] <desrt> http://www.animalstown.com/animals/animals-x.php
[16:04] <willcooke> :D
[16:05] <Laney> do I need to do auth to buy the train ticket myself?
[16:05] <willcooke> Laney, nah, just expense it
[16:05] <Laney> yessssssssssss
[16:05] <willcooke> well, that's what I'm doing
[16:06] <andyrock> do we need to ask for a pass card to enter in the office?
[16:06] <Laney> nah
[16:06] <andyrock> \o/
[16:06] <willcooke> andyrock, you'll get a visitors badge
[16:06]  * willcooke will make sure reception are expecting you
[16:06] <desrt> are we staying at citizenM?
[16:07] <willcooke> desrt, we are
[16:07]  * Trevinho has an office pass :P
[16:07] <desrt> awesome
[16:07] <willcooke> I find the place a bit oppressive tbh
[16:08] <desrt> it's modern and not too fancy
[16:08] <desrt> and the plumbing works properly
[16:08] <willcooke> hahaha
[16:08] <willcooke> and the windows don't rattle
[16:08] <willcooke> and there are less ghosts
[16:08] <desrt> they also have international power plugs in the room
[16:09] <desrt> because, ya, sometimes hotel guests come from other countries
[16:09] <Trevinho> for some reason nobody consider the Italian plug anyway (with ground in the middle)
[16:09] <willcooke> ???
[16:09] <Laney> they have a bed which you can sleep in any way round
[16:09] <Laney> and colouful showers
[16:09] <Laney> so it wins for me
[16:09]  * willcooke likes the breakfast
[16:09] <desrt> they also have a nice downstairs area
[16:09] <desrt> yes.  breakfast is very very good there.
[16:10] <desrt> the staff is also friendly and helpful
[16:10] <willcooke> I'm probably only going to stay over weds & thurs night and commute the rest of the time.  Because babies
[16:10] <willcooke> anyway - we can continue this after the meeting
[16:10] <willcooke> #endmeeting
[16:10] <meetingology> Meeting ended Tue Sep 22 16:10:42 2015 UTC.
[16:10] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2015/ubuntu-desktop.2015-09-22-15.30.moin.txt
[16:10] <willcooke> Thanks a lot everyone
[16:10] <desrt> their checkin system is awful, though
[16:10] <andyrock> sorry for being late
[16:10] <desrt> ditto
[16:11]  * desrt goes back into airplane mode again
[16:11]  * Laney likes being called LANE IAIN/MR
[16:11]  * desrt does not care for this
[16:12] <Trevinho> slash mister?
[16:12] <Laney> sometimes IAINMR indeed
[16:12] <didrocks> thanks
[16:12] <Laney> that form is usually on travel tickets
[16:12] <Laney> (amity travel are weird)
[16:13] <Trevinho> ah, sure... I'm MARCOMR...
[16:13] <Trevinho> or, according to my fiber provider Marco Partita Iva (= Marco VAT)
[16:13] <sethj> Can anyone else reproduce this? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1286910 I see andyrock marked it as confirmed, so I'm not sure if that means he reproduced it or if he was just fixing the status.
[16:14] <sethj> (I cannot FWIW)
[16:14] <andyrock> sethj: well i can
[16:15] <sethj> oh hi anyrock, I thought you were out for the day. What steps did you take to reproduce it?
[16:15] <seb128> unsure of the specifics
[16:15] <seb128> but changing the lock screen layout doesn't change the session one
[16:15] <seb128> so you change, unlock and need to change again
[16:15] <seb128> which is annoying
[16:15] <andyrock> nope i was just late for the meeting :D
[16:16] <andyrock> well i switch keyboard layout before locking the screen
[16:17] <andyrock> let's say from italian to english
[16:17] <andyrock> and in the lockscreen the language is set to english
[16:17] <andyrock> it should be italian
[16:18] <andyrock> maybe it is a slightly different bug
[16:18] <sethj> strange. For me, if I changed the layout to Spanish (LA) and then lock the screen the greeter changes to the default language (en-us)
[16:19] <andyrock> I'll take a look
[16:19] <sethj> I'll give it a shot again a little later.
[16:19] <andyrock> can be annoying
[16:19] <andyrock> if you don't notice that
[16:19] <andyrock> you are going to blame the lockscreen becuase it does not accept your password
[16:19] <andyrock> :D
[16:23] <andyrock> sethj: btw I can't reproduce it 100%
[16:23] <andyrock> but it happens
[16:25] <Trevinho> andyrock: but isn't that more related to the indicator to unity itself?
[16:25] <andyrock> Trevinho: yep
[16:28] <attente> seb128: there's this comment by ChrisTownsend: https://bugs.launchpad.net/unity/+bug/1324489/comments/1
[16:29] <attente> we did that by design and it would've made our lives easier to not implement the current behaviour at all
[16:30] <seb128> attente, ok, I can see why, that makes sense
[16:30] <seb128> I guess it's not really possible to carry for all usecases
[16:30] <seb128> though I would argue that people who want to have their word editor in english have the "by window layout tracking"
[16:30] <seb128> and don't change it for the session
[17:00] <seb128> hum
[17:01] <seb128> Trevinho, andyrock, hey, I just had issues today on my laptop and my test machine, going back from the greeter to my session made me enter my password twice (e.g the screenlock in the session didn't dismiss after entering the password on the unity-greeter), is that a known issue?
[17:01] <seb128> that's on wily
[17:01] <andyrock> seb128: nope first time I don't see this bug
[17:02] <andyrock> does it happen all the time?
[17:02] <seb128> yes
[17:02] <seb128> just tried
[17:02] <Laney> ttyl!
[17:03] <seb128> Laney, have a good evening!
[17:05] <Trevinho> seb128: it might happen in some cases, but it generally shouldnt... as we listen to a logind signal to unlock
[17:05] <seb128> Trevinho, in never happened before yesterday or today, I wonder if that's a regression
[17:08] <seb128> different topics but I've those warnings in my log
[17:09] <seb128> [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.6" (uid=0 pid=874 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.66" (uid=1000 pid=2111 comm="/usr/lib/i386-linux-gnu/indicator-messages/indicat")
[17:09] <seb128> jdstrand, tedg, ^ do you know if that's known (wily desktop)
[17:11] <jdstrand> I've not seen it. mdeslaur, have you? ^
[17:11] <seb128> jdstrand, you don't have any of those in your auth.log?
[17:11] <seb128> weird, I just booted my test laptop and it has the same
[17:11] <mdeslaur> I don't run wily, so hven't seen it yet
[17:11] <seb128> (well after using xchat-gnome and receiving a message)
[17:12] <jdstrand> seb128: ah, I am still on vivid. I thought you were wondering if I've seen bugs, etc
[17:13] <seb128> jdstrand, any info that would be useful in a bug report? against what should that be reported?
[17:15] <seb128> reported bug #1498591
[17:16] <jdstrand> seb128: fyi, this seems to be a policy kit issue/bus policy issue (ie, it isn't an apparmor issue-- the message would look different)
[17:16] <jdstrand> that is a wild guess
[17:16] <seb128> jdstrand, ok, I though it would be, but I was unsure if that was due to the dbus mediation
[17:17] <seb128> desrt, larsu, ^ do you know if those errors are more likely to be buggy client code? or a dbus issue?
[17:17] <seb128> jdstrand, thanks
[17:17] <jdstrand> yeah, none of those processes run under vonfinement
[17:17] <jdstrand> confinement
[17:26] <desrt> seb128: that looks really weird
[17:26] <desrt> i can't imagine this is buggy client code... looks rather like a broken security policy
[17:26] <seb128> https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1498594 seems a bit similar
[17:27] <desrt> seems very similar
[17:27] <desrt> both bluetooth and accountsservice are root
[17:27] <desrt> so they should be allowed to do anything as per dbus policy
[17:28] <desrt> read: likely apparmor fail
[17:28]  * jdstrand notes that there isn't apparmor policy for those processes
[17:29] <jdstrand> not to mention, the log message would look different
[17:29] <desrt> could it rather be something about the processes on the other end to whom accountsservice is trying to send the message?
[17:29] <desrt> the bluetooth one is different.  i make no statement about that.
[17:29] <jdstrand> apparmor would mediate that, but neither process should have a profile
[17:29] <desrt> but rejecting a method_return from a root-owned process?  how could that possibly be happening?
[17:30] <jdstrand> (and the message would look different)
[17:30] <tyhicks> possibly due to the bus policy
[17:30] <tyhicks> that is in /etc/dbus-1/system.conf
[17:31] <desrt>     <allow send_requested_reply="true" send_type="method_return"/>
[17:31] <desrt> for user *
[17:31] <tyhicks> but the logged message is not a requested_reply: requested_reply="0"
[17:32]  * jdstrand wonders if that is overriden in /etc/dbus-1/system.d/* somewhere
[17:32] <desrt> looking at this one: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1498591
[17:32] <desrt> this is the really interesting one
[17:32] <desrt> Rejected send message, 9 matched rules; type="method_return", sender=":1.6" (uid=0 pid=874 comm="/usr/lib/accountsservice/accounts-daemon ")
[17:32] <desrt>   destination=":1.66" (uid=1000 pid=2311 comm="/usr/lib/i386-linux-gnu/indicator-messages/indicat")"
[17:34] <desrt> one way or another, indicator-messages likely has a whacked apparmor or dbus policy
[17:34] <desrt> another one here: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/346513
[17:39] <jdstrand> $ sudo ps -axZ|grep indicator-m
[17:39] <jdstrand> unconfined                       1677 ?        Ssl    0:00 /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service
[17:39] <jdstrand> that VM is slightly out of date, but it is unconfined
[17:39] <jdstrand> I am updating the VM, but I can say for sure we didn't not confine it
[17:40] <jdstrand> (as in the security team)
[17:40] <tyhicks> jdstrand: and the accounts-daemon is also unconfined?
[17:41] <jdstrand> $ sudo ps -axZ|grep accounts-d
[17:41] <jdstrand> unconfined                        508 ?        Ssl    0:00 /usr/lib/accountsservice/accounts-daemon
[17:41] <desrt> where are the current set of profiles maintained?
[17:41] <desrt> just out of curiosity...
[17:41] <jdstrand> in the packages themselves
[17:41] <desrt> ah
[17:41] <jdstrand> for anything shipped by default that is
[17:42] <jdstrand> there are the apparmor-profiles* packages, but they are not installed by default and complain mode only
[17:42] <jdstrand> and are*
[17:47] <larsu> desrt: where are you seeing this line? The only policy file I ave for accountsservice is in /etc/dbus-1/system.d/
[17:47] <desrt> larsu: in the base policy in system.conf
[17:48] <larsu> desrt: isn't that overridden by a file in etc?
[17:48] <tyhicks> "Rejected send message" comes from a failed bus_client_policy_check_can_send() call, which is a access control check for the bus config and not the apparmor policy
[17:48] <desrt> larsu: ya.. /etc/dbus-1/system.conf...
[17:48] <larsu> desrt: that file is empty for me...
[17:48] <larsu> what system are you on?
[17:48] <desrt> debian.  assumed it was the same :)
[17:48] <larsu> hahahahaha
[17:48] <larsu> you're funny
[17:49] <desrt> thanks for your understanding :)
[17:50] <jdstrand> nothing changed after upgrading
[17:50] <larsu> desrt: https://paste.debian.net/?show=312912
[17:55] <larsu> desrt: and I don't have that line in /usr/share/dbus-1/system.conf either
[17:55] <larsu> I wonder when this switch happened
[17:57] <larsu> which package installs that file for you?
[18:05] <desrt> dbus
[18:06] <larsu> dbus ships a rule for accountsservice?
[18:06] <desrt> my accountsservice file is same as yours
[18:06] <larsu> or is that a general rule?
[18:07] <desrt> dbus ships system.conf
[18:07] <desrt> the accountsservice policy comes with accountsservice, of course
[18:07] <larsu> sure sure
[18:07] <larsu> I have this as well, but in /usr/share
[18:07] <desrt> where?
[18:07] <desrt> you're living in fancy future-world :)
[18:07] <larsu> ya
[18:08] <larsu> the one in /etc is still there, but it simply points to this one
[18:08] <larsu> now the question remains why this isn't applied :/
[18:25] <larsu> seb128: can you reprodcue this error message?
[18:25] <seb128> larsu, yes, you should also I guess, if you are on wily
[18:25] <seb128> it's in auth.log
[18:25] <larsu> I am, but I can't seem to
[18:25] <seb128> I've it on my test machine as well
[18:26] <larsu> hm ok I'll keep trying
[18:26] <seb128> I think it's "use xchat-gnome (or another app integrated to indicator-message) and receive a message"
[18:26] <larsu> just making sure :)
[18:26] <seb128> larsu, ping?
[18:27] <larsu> oh hehe
[18:27] <larsu> using dbus calls directly :)
[18:27] <seb128> lol
[18:27]  * larsu is in irssi but thanks
[18:27] <seb128> well, I wanted a pong with my name :p
[18:27] <larsu> wow indicator-messages is calling this method on the wrong interface
[18:28] <larsu> ugh nevermind
[18:29] <larsu> it creates a proxy for that interface but then calls g_dbus_connection_call() directly (with all of the proxy's information except for the inteerface)
[18:29] <larsu> *sigh(
[18:29] <seb128> larsu, confirmed, the warnings are displayed when I receive an irc msg
[18:34] <tyhicks> larsu: has indicator-messages been doing that for a couple releases now?
[18:34] <tyhicks> (ubuntu releases, that is)
[18:35] <larsu> tyhicks: it appears so - this code was first added in Sep 14
[18:35] <tyhicks> larsu: of last year?
[18:36] <larsu> tyhicks: sorry, yes, September 2014
[18:36]  * tyhicks nods
[18:36] <tyhicks> now that I think about it, I'm pretty sure those unrequested reply messages caused me a lot of headache while developing the apparmor mediation in dbus-daemon
[18:36] <larsu> calling the method on accountsservice manually doesn't trigger the warning for me
[18:37] <jjohansen> yeah those unrequested replies are evil
[18:44] <jdstrand> tyhicks: I was going to mention that, but didn't want to confuse the issue
[18:57]  * qengho afk.
[20:30] <chefpv> anyone home?


[00:14] <mup> PR snapd#2443 opened: removing circular dependency between snapstate and hookstate <Created by cyberb> <https://github.com/snapcore/snapd/pull/2443>
[05:03] <liuxg> has anyone successfully compiled the mosquitto sample in the snapcraft demos at https://github.com/snapcore/snapcraft/tree/master/demos/mosquitto? I get some errors like http://paste.ubuntu.com/23617381/
[06:49] <mup> PR snapd#2445 closed: cmd/snap,tests: alias support in snap run <Critical> <Created by pedronis> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2445>
[08:12] <dholbach> hey hey
[08:15] <didrocks> hey dholbach!
[08:17] <dholbach> salut didrocks
[08:22] <seb128> hey dholbach!
[08:22] <dholbach> salut seb128
[08:27] <simon_b> How can I set environment variables in a snap? I am trying to use gstreamer, but it can't find its plugins in there it seems.
[08:27] <simon_b> this is what I get from gstreamer: GStreamer-WARNING **: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though.
[08:27] <mup> PR snapd#2451 opened: tests: add check to ensure that we get the version number <Created by mvo5> <https://github.com/snapcore/snapd/pull/2451>
[08:30] <kalikiana_> simon_b: Are you using any of the desktop- parts mentioned here? https://wiki.ubuntu.com/snapcraft/parts
[08:30] <kalikiana_> Those would set the gstreamer path for you
[08:32] <simon_b> kalikiana_: I am actually using "desktop/gtk3"
[08:33] <simon_b> kalikiana_: I opened up the snap out of curiosity and took at look at desktop-launch
[08:33] <simon_b> kalikiana_: In there is a line "export GST_PLUGIN_SYSTEM_PATH=$SNAP/usr/lib/$ARCH/gstreamer-1.0"
[08:36] <simon_b> I don't understand what the issue is, the plugins are there in the snap but gstreamer can't locate them
[08:39] <didrocks> ogra_: so, I restarted my pi2, I don't have an i2c interface.
[08:39] <didrocks> ogra_: pi2                   16.04-0.17    29   canonical  -
[08:39] <didrocks> ogra_: and then, I can't upgrade it due to the network issue we discussed longely here and on the ML
[08:39] <didrocks> did you enable it in a later gadget snap?
[09:19] <mup> PR snapd#2447 closed: many: fixes cherry-picked for the 2.19.1 release <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/2447>
[09:45] <mup> PR snapd#2452 opened: Fix AppArmor rules <Created by bergotorino> <https://github.com/snapcore/snapd/pull/2452>
[10:15] <mup> PR snapd#2083 closed: cmd/snap: generate account-key revocation requests <Created by cjwatson> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/2083>
[10:21] <mup> PR snapd#2453 opened: store: retry user info request <Created by stolowski> <https://github.com/snapcore/snapd/pull/2453>
[10:22] <kalikiana_> Hmmm installing a devmode snap without --devmode seems to wrongly suggest it doesn't exist
[10:26] <mup> Bug #1649237 opened: snap install without devmode claims it doesn't exist <Snappy:New> <https://launchpad.net/bugs/1649237>
[10:50] <mup> PR snapd#2440 closed: release: 2.19 <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2440>
[10:58] <mup> PR snapd#2420 closed: overlord/snapstate: setup/remove aliases as we link/unlink snaps <Critical> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/2420>
[11:32] <mup> PR snapd#2454 opened: client: only allow Dangerous option in InstallPath <Created by chipaca> <https://github.com/snapcore/snapd/pull/2454>
[11:47] <om26er> Is there an "official" daily image of Ubuntu Core for kvm ?
[12:24] <ogra_> ogra@pi3:~$ grep i2c /boot/uboot/config.txt
[12:24] <ogra_> dtparam=i2c_arm=on
[12:24] <ogra_> dtparam=i2c_vc=on
[12:24] <ogra_> ogra@pi3:~$ ls /dev/i2c-*
[12:24] <ogra_> /dev/i2c-0  //dev/i2c-1
[12:24] <ogra_> ogra@pi3:~$
[12:24] <ogra_> didrocks, ^^^^
[12:25] <ogra_> (i'm on vacation btw)
[12:25] <ogra_> the pi2 should be identical
[12:27] <ogra_> didrocks, if the pi2 is different please note so in a bug and assign to me
[12:31] <ogra_> om26er, http://people.canonical.com/~ogra/snappy/all-snaps/daily/current/ is as official as it gets atm, if you wait for actual cdimage builds, foundations is supposed to set them up, ask infinity where that stands
[12:32] <om26er> ogra_: ok, good to know.
[12:35] <om26er> ogra_: can you tell who is the console-conf person of contact ?
[12:38] <renato__> mvo, jdstrand, could you approve ubuntu-docviewr-app ?
[12:39] <renato__> mvo, jdstrand, looks like something has landed in the store. Now the package is not rejected anymore but it still need manual approval
[12:41] <mup> PR snapd#2451 closed: cmd: fix mkversion.sh and add regression test <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/2451>
[12:49] <didrocks> ogra_: the parameters are there, but snap interfaces shows no i2c interface
[12:50] <didrocks> ogra_: so, it's between the gadget snap or snapd
[12:50] <didrocks> (crazy that nobody even try a snap interfaces to ensure things are working)
[12:50] <didrocks> on a bug report for this, I opened one a month ago and referenced it on the feedback email
[12:57] <mup> PR snapd#2455 opened: many: implement alias command <Created by pedronis> <https://github.com/snapcore/snapd/pull/2455>
[13:12] <mup> PR snapd#2456 opened: WIP: Implement 'shadow' interface for mounting snap folders <Created by kalikiana> <https://github.com/snapcore/snapd/pull/2456>
[13:30] <mup> PR snapd#2444 closed: debian: depend on snap-confine at least 2.19 <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2444>
[13:44] <mup> PR snapd#2457 opened: cmd/snap: reject "snap disconnect foo" <Created by zyga> <https://github.com/snapcore/snapd/pull/2457>
[13:47] <abeato> ogra_, ping
[14:05] <mup> PR snapd#2456 closed: WIP: Implement 'overmount' interface for mounting snap folders <Created by kalikiana> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/2456>
[14:09] <mup> PR snapd#2441 closed: debian: add split ubuntu-core-launcher and snap-confine packages <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2441>
[14:25] <mup> PR snapd#2458 opened: release: 2.19.1 <Created by mvo5> <https://github.com/snapcore/snapd/pull/2458>
[14:41] <mup> PR snapd#2459 opened: interfaces/builtin: add iio interface <Created by morphis> <https://github.com/snapcore/snapd/pull/2459>
[14:59] <mup> PR snapd#2457 closed: cmd/snap: reject "snap disconnect foo" <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/2457>
[15:03] <mup> PR snapcraft#954 opened: pluginhandler: convert to package <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/954>
[15:16] <jdstrand> renato__: you need a desktop file
[15:17] <jdstrand> renato__: it looks like revisions 2 and 3 have it. you just need to press the 'release' button
[15:17] <renato__> jdstrand, yes this is on the rev 2 e 3
[15:18] <renato__> jdstrand, thanks
[15:18] <renato__> jdstrand, I did not find a way to cancel the review
[15:18] <jdstrand> roadmr: hi! I asked a little while ago about a store pull for r809. it seems we are still at r798. is this still queued up?
[15:18] <roadmr> jdstrand: let me check
[15:19] <jdstrand> renato__: fyi, ubuntu-calculator approved
[15:19] <renato__> thnaks
[15:20] <roadmr> jdstrand: 809 should have been deployed last week; sorry, it was a bit hectic so I didn't tell you about it :(
[15:20] <jdstrand> hmm
[15:20] <jdstrand> ok
[15:20] <jdstrand> that calculator one was older
[15:21] <jdstrand> roadmr: thanks!
[15:23] <roadmr> \o/ :)
[15:27] <jdstrand> mvo: hi! fyi I took care of ubuntu-docviewr-app
[15:43] <mup> PR snapd#2460 opened: tests: remove snap-confine/ubuntu-core-launcher after the tests <Created by mvo5> <https://github.com/snapcore/snapd/pull/2460>
[15:44] <mup> PR snapd#2423 closed: overlord,overlord/snapstate: implement snapstate.Alias <Critical> <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/2423>
[15:49] <mup> PR snapd#2461 opened: tests: check if snap-confine --version is unknown <Created by zyga> <https://github.com/snapcore/snapd/pull/2461>
[15:51] <ondra> ogra_ hi
[16:02] <roadmr> jdstrand: hey a question about classic, if you have a sec to help us clarify
[16:08] <mvo> jdstrand: thanks a bunch
[16:15] <mup> PR snapd#2462 opened: cmd/snap-confine: allow content interface mounts <Created by zyga> <https://github.com/snapcore/snapd/pull/2462>
[16:30] <mup> PR snapd#2460 closed: tests: remove snap-confine/ubuntu-core-launcher after the tests <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2460>
[16:33] <mup> PR snapd#2463 opened: tests: remove ppa:snappy-dev/image again <Created by mvo5> <https://github.com/snapcore/snapd/pull/2463>
[16:40] <mup> Bug #1649331 opened: Disconnecting ubuntu-app-platform doesn't really work until a reboot <Snappy:New> <https://launchpad.net/bugs/1649331>
[17:09] <niemeyer> jdstrand: Hey, can you please have a second look on #2413 when you have a moment?
[17:10] <niemeyer> jdstrand: We discussed a few changes which are hopefully fine with you as well
[17:12] <jdstrand> niemeyer: yes, plan to do that in a few minutes. discussing the content sharing rw issue with zyga atm
[17:39] <mup> PR snapcraft#953 closed: sources: refactor base sources into new package <Created by kyrofa> <Closed by kyrofa> <https://github.com/snapcore/snapcraft/pull/953>
[17:48] <mup> PR snapcraft#955 opened: sources: convert to package <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/955>
[17:48] <mup> PR snapd#2464 opened: cmd/snap: mock terminal.ReadPassword instead of using /dev/ptmx <Created by pete-woods> <https://github.com/snapcore/snapd/pull/2464>
[18:21] <julio__> hi there, could anyone tell me what is the easiest way to execute a startup script in Ubuntu Core 16?
[18:25] <kyrofa> julio__, package what you want to run as a snap, and you can declare the script in question to be a service which snapd will run
[18:27] <julio__> huh, will I be able to set the system time using hwclock?
[18:28] <jdstrand> niemeyer, z: fyi, 2413 reviewed
[18:28] <jdstrand> tab-complate fail
[18:28] <jdstrand> complete*
[18:29] <kyrofa> julio__, I suspect you can as long as you utilize the time-control interface
[18:30] <julio__> kyrofa, thank you.
[18:33] <julio__> kyrofa, next question: how could I override the /etc/issue file since the system is readonly? I notice that some of the files in the /writable partition are copied over but what process determines which files get copied over?
[18:50] <jdstrand> niemeyer: hey, so on https://github.com/snapcore/snapd/pull/1613 I *think* you gave a +1 since you gave a LGTM earlier with some questions, which I answered, which you responded to today as ok/let's not block.
[18:50] <mup> PR snapd#1613: interfaces/builtin: add dbus interface (LP: #1590679) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/1613>
[18:50] <jdstrand> niemeyer: I'm going to merge from trunk and then resubmit and see how the tests do
[18:51] <jdstrand> niemeyer: is there anything more you need from this?
[18:51] <jdstrand> niemeyer: note that I'd like to answer sabdfl's question on the status of this in the most positive way possible since it has been dragging (for various understandable reasons)
[19:07] <jdstrand> niemeyer: also, there is an open question for you in https://github.com/snapcore/snapd/pull/2450
[19:07] <mup> PR snapd#2450: interfaces: add network-namespace-control (LP: #1624675) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/2450>
[19:09] <mup> PR snapd#2413 closed: interfaces/apparmor: allow access to core snap <Critical> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/2413>
[20:03] <hol> Hi guys, noob question here. I just installed the ubuntu core on my raspberry, no monitor, no keyboard available. Can I log on via ssh? what is the user/password?
[20:03] <niemeyer> jdstrand: Yeah, I'm hoping we can get this in tomorrow
[20:04] <niemeyer> jdstrand: No blockers from me.. invited pedronis for a quick look today
[20:04] <kgunn> yo, i've just installed an img for Rpi3, i have a keyboard and monitor...is it expected to see "a start job is running for Raise network interfaces (time/5min)
[20:06] <hol> well, it's running now for 1,5h and still: ssh<EMAIL_ADDRESS><EMAIL_ADDRESS>password: Permission denied, please try again.
[20:06] <hol> password: ubuntu
[20:06] <jdstrand> niemeyer: fantastic!
[20:07] <jdstrand> niemeyer: it be great to get the network-namespace-control one in too (already has a +1 from zyga). that one has the open question on if that should be its own interface or not
[20:08] <davmor2> hol: you login with the user key you set up in console-conf on first boot of the device not ubuntu
[20:09] <mup> PR snapcraft#956 opened: tests: idempotent store installs <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/956>
[20:15] <niemeyer> jdstrand: Sounds good, will try to have a look later today still
[20:16] <jdstrand> niemeyer: awesome. if it works better for you tomorrow morning, that's fine with me (I'm here all week)
[20:57] <mup> PR snapd#2463 closed: tests: remove ppa:snappy-dev/image again <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2463>
[20:57] <mup> Bug #1649399 opened: 'daemon: dbus' is incomplete <Snappy:New> <https://launchpad.net/bugs/1649399>
[21:35] <popey> how does one install core over ubuntu-core?
[21:35] <popey> http://paste.ubuntu.com/23620875/
[21:35] <kyrofa> popey, blow away snapd :P
[21:38] <popey> how?
[21:38] <popey> and is that serious, given the smiley?
[21:38] <kyrofa> popey, unfortunatey, yes, I'm serious
[21:39] <popey> wait, lose every snap I have installed?
[21:39] <popey> alan@gort:~$ snap list | wc -l
[21:39] <popey> 64
[21:39] <kyrofa> popey, that's the only way *I* know of anyway. You can wait for the snapd folks to respond though
[21:39] <popey> ok
[21:40] <popey> ( following your blog post and stuck at the "Also verify that you have the core snap installed, not ubuntu-core:" step
[21:40] <kyrofa> popey, indeed, I had to blow everything away to get core
[21:41] <kyrofa> niemeyer, is there any way around that?
[21:42] <kyrofa> Some nifty way to convince snapd to remove ubuntu-core and install core instead?
[21:44] <niemeyer> popey, kyrofa: Let's please not say that
[21:45] <niemeyer> kyrofa: Yes, there is.. we need to develop the migration between one and the other
[21:45] <mup> PR snapd#2462 closed: cmd/snap-confine: allow content interface mounts <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2462>
[21:45] <niemeyer> kyrofa: If you know somebody with knowledge of snapd internals that could be motivated enough to tackled that sooner rather than later, please let me know! ;-)
[21:47] <kyrofa> niemeyer, automatic is one thing. Is there no way to do it manually?
[21:48] <niemeyer> kyrofa: No.. we need to update ubuntu-core.. that's the proper way to do that sooner rather than later.. hopefully this week
[21:49] <kyrofa> Alrighty
[21:50] <mup> PR snapd#2458 closed: release: 2.19.1 <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/2458>
[21:50] <mup> PR snapd#2461 closed: tests: check if snap-confine --version is unknown <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2461>
[21:51] <niemeyer> kyrofa: The update is really not that hard.. the problem is everything else
[21:52] <kyrofa> Yeah if they were updated in tandem no one would even notice
[21:53] <niemeyer> kyrofa: That was the plan.. but reality loves surprises
[21:55] <popey> niemeyer: kyrofa so the short answer is "wait"?
[21:58] <kyrofa> popey, for switching from ubuntu-core to core, yeah sounds like it. Core is used on new installs though
[21:58] <popey> ok
[21:59] <jdstrand> fwiw, I installed core, then disabled ubuntu-core, then uninstalled ubuntu-core. however, I don't claim that will dtrt with already installed apps. I only had a couple installed so I uninstalled them and reinstalled
[22:00] <jdstrand> so, ymmv
[22:00] <kyrofa> jdstrand, did you have to disable ubuntu-core first?
[22:00] <kyrofa> jdstrand, popey's paste showed an error when initially installing core
[22:01] <jdstrand> "then disabled ubuntu-core"
[22:01] <jdstrand> yes
[22:02] <kyrofa> jdstrand, to clarify: you said you installed core, then disabled ubuntu-core. However, popey's paste indicated that installing core in the first place would fail
[22:02] <jdstrand> I was told that wasn't technically supposed to work, but at the time I did, it did
[22:02] <kyrofa> jdstrand, so did you actually need to do those steps the other way around?
[22:02] <kyrofa> Ah
[22:02] <jdstrand> snap install core ; snap disable ubuntu-core ; snap remove ubuntu-core
[22:02] <jdstrand> that is what I did ^
[22:02] <kyrofa> Indeed, that appears to no longer work
[22:03] <popey> okerror: cannot disable "ubuntu-core": snap "ubuntu-core" cannot be disabled
[22:03] <jdstrand> I make no claims that that will dtrt with your interface connections or policy. I suspect it will not
[22:03] <niemeyer> popey: Yes, let's please not recommend anything else.. it'll be unnecessary churn.. we'll fix this soon enough
[22:03] <popey> ok
[22:04] <jdstrand> well, there you go. wait :)
[22:14] <cholcombe> i'm getting permissions denied on my strict enforced snap with the [home] plug.  I'm telling it to access my home directory .config file and it's failing.  Are . files not allowed?
[22:16] <kyrofa> cholcombe, indeed, last I heard, dot files directly in $HOME weren't allowed (to prevent, say, SSH keys from being stolen), but dot files elsewhere are okay
[22:16] <cholcombe> kyrofa, Alright is there an interface that allows me to give it access to /etc say?
[22:17] <kyrofa> cholcombe, I don't believe so. Snaps are supposed to be self-contained. If they have configuration files, they're contained within it somewhere
[22:18] <cholcombe> that won't work.  the configuration files i need are generated at runtime by a charm that connects to other services
[22:19] <kyrofa> cholcombe, can you explain what you're trying to accomplish?
[22:19] <cholcombe> kyrofa, https://github.com/cholcombe973/preserve is the app i'm building.  It connects to several different backends, Ceph, Gluster, Amazon, etc.  It won't know that config information until the preserve charm makes a config file for it
[22:20] <kyrofa> cholcombe, do you have any control over where the charm places the config?
[22:20] <cholcombe> yup
[22:20] <cholcombe> total control
[22:21] <cholcombe> from what i've found i can't actually write into the snap
[22:21] <kyrofa> cholcombe, indeed, snaps are squashfs images (by definition read-only)
[22:21] <kyrofa> cholcombe, however, there are some well-defined places they can read/write
[22:21] <cholcombe> kyrofa, do tell :)
[22:21] <kyrofa> cholcombe, this might be faster: https://askubuntu.com/questions/762354/where-can-ubuntu-snaps-write-data
[22:22] <cholcombe> ah there we go.  /var/snap
[22:23] <kyrofa> cholcombe, note that /var/snap is the root for all snaps. You're looking for /var/snap/<snapname>/current, probably
[22:23] <cholcombe> kyrofa, yeah
[22:24] <kyrofa> cholcombe, soon you'll be able to just have the charm configure the snap directly (using `snap set key=value`)
[22:24] <kyrofa> Assuming that's something in which you're interested
[22:24] <cholcombe> kyrofa, that'll be sweet
[22:24] <cholcombe> so it'll just the config info from env data?
[22:25] <kyrofa> cholcombe, no, calling `snap set` would run a hook contained within your snap, which could then act upon those values
[22:25] <cholcombe> oh i see. yeah that might be fine also
[22:25] <kyrofa> cholcombe, like this: https://github.com/snapcore/snapd/wiki/hooks#configure
[22:25] <cholcombe> kyrofa, yeah i think that would be ok
[22:27] <kyrofa> cholcombe, anyway, hopefully you have a way forward?
[22:27] <cholcombe> kyrofa, yeah i think i can work it out from here.  thanks !
[22:27] <kyrofa> Excellent, any time :)
[22:30] <mup> PR snapcraft#955 closed: sources: convert to package <Created by kyrofa> <Merged by kyrofa> <https://github.com/snapcore/snapcraft/pull/955>
[22:36] <mup> PR snapcraft#957 opened: sources: refactor base sources into module <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/957>
[22:48] <cholcombe> kyrofa, crap i just realized something.  for this application to do backups it's going to need to be able to read the entire filesystem potentially.  It also needs write access to potentially anywhere so that it can do a backup restore
[22:49] <kyrofa> cholcombe, I'm not sure we have an interface that would cover such a use-case. jdstrand might know more
[22:49] <cholcombe> kyrofa, so i'll have to stick to dev mode for now then
[22:50] <kyrofa> cholcombe, indeed. Your snap is not the only one that needs such things-- shells, for example, are limited without that ability as well
[22:50] <cholcombe> yeah
[23:08] <jdstrand> cholcombe, kyrofa: there is no interface for that. that'll need to use either devmode or classic
[23:10] <cholcombe> jdstrand, ok i'll stick to devmode for awhile
[23:11] <jdstrand> niemeyer: fyi, https://github.com/snapcore/snapd/pull/1613 still has you requesting changes. I think that should be 'approved' now based on our earlier conversation. then just need pedronis
[23:11] <mup> PR snapd#1613: interfaces/builtin: add dbus interface (LP: #1590679) <Created by jdstrand> <https://github.com/snapcore/snapd/pull/1613>


[01:34] <pieq> duflu, hi! I'm reviewing the bugs I opened during 19.10 beta testing. Regarding this: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1736, do you know what's the GNOME process usually? Do they leave all the bugs unassigned until it's taken by someone?
[01:35]  * duflu looks
[01:35] <duflu> pieq, yes exactly as you said
[01:36] <pieq> duflu, ok, thanks!
[01:36] <duflu> It's not affecting enough people for a developer to want to own it yet I guess
[01:52] <pieq> duflu, yeah I can imagine.
[01:53] <duflu> Made harder by the fact your dev machine would need a touchscreen... I wonder can you trigger it without one?
[01:53] <pieq> duflu, even though, it's a bit ironic in a way. The "curtain" you have to lift to unlock your desktop in GNOME3 is here because of the touchscreen (cause using a mouse to lift it is really a pain)
[01:53] <pieq> so I assumed they would be more proactive regarding touchscreen issues... but well.
[01:54] <pieq> duflu, I don't know how the OSK is triggered. I know you cannot click on the keys with the mouse, so I don't think it could be used at all without a touch screen
[01:55] <duflu> Well, if I was writing it I would make sure it was debuggable with a mouse *shrug*
[02:01] <pieq> :)
[05:40] <duflu> Morning mvo. The PulseAudio people would like some feedback (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749)
[05:41] <mvo> duflu: aha, right. yes, will do. I provided most logs already but not a debug log yet
[05:41] <duflu> Thanks. I don't have working HDMI audio handy myself
[05:43] <duflu> Though my DisplayPorts offer the HDMI audio sink, they don't trigger the bug
[06:19] <didrocks> good morning
[06:52] <oSoMoN> good morning desktoppers
[06:56] <Wimpress> Morning o/
[07:06] <oSoMoN> morning Wimpress
[07:10] <duflu> Morning didrocks, oSoMoN and Wimpress
[07:12] <oSoMoN> hey duflu
[07:12] <oSoMoN> salut didrocks
[07:17] <didrocks> hey duflu, oSoMoN, Wimpress
[07:30] <Wimpress> didrocks jibel JIm Salter talks about Ubuntu 19.10 and ZFS on root in the Techsnap Podcast episode 414.
[07:30] <Wimpress> https://www.jupiterbroadcasting.com/136002/rooting-for-zfs-techsnap-414/
[07:30] <Wimpress> ZFS discussion starts at 21m 20s
[07:30] <didrocks> Wimpress: thanks! I'll listen to it during my daily exercise :)
[07:33] <ackk> hi, I installed 19.10 a couple of days ago, nightlight doesn't seem to work anymore. how can I debug the issue?
[07:36] <duflu> ackk, just subscribe to bug 1847551 :)
[07:38] <ackk> oh, I did search for night light, didn't find it
[07:38] <ackk> thanks
[07:40] <duflu> Yeah I usually think unresolved mutter bugs should have gnome-shell tasks so people can find them and save time/duplication
[07:41] <duflu> But since a fix already exists for mutter it might cause confusion if people think I'm suggesting fixing gnome-shell instead
[08:03] <Laney> hi!
[08:09] <oSoMoN> hi Laney
[08:12] <Laney> heeeeeeeeeeeeeeeeeeeeeeey oSoMoN
[08:13] <duflu> Hi Laney
[08:16] <Laney> YOOOOOOOOOOOOOOOOOOOOOOOO DUFLU
[08:17]  * duflu falls off chair
[08:17] <Laney> damn it, now I have to do that for everyone to be fair
[08:22] <Laney> https://launchpadlibrarian.net/447949360/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz
[08:22] <Laney> what
[08:23] <duflu> exit 1
[08:39] <marcustomlinson> morning desktoppers
[08:39] <duflu> Morning marcustomlinson
[08:39] <pieq> duflu, regarding LP #1847551, is there a fix planned to land soon in Ubuntu? I just noticed the exact same issue while testing Wayland on a device we have here
[08:40] <oSoMoN> good morning marcustomlinson
[08:41] <duflu> pieq, it looks like we're waiting on upstream to complete a mutter 3.34.2 release. Unless someone wants to package a fix quicker
[08:42] <pieq> duflu, got it
[08:42] <duflu> It looks relatively big already, so hopefully soon
[08:42] <duflu> Laney would know
[08:45] <Laney> https://wiki.gnome.org/ThreePointThirtyfive
[08:45] <Laney> Towards the end of November
[08:46] <Laney> HIIIIIIIIIIIIIIIII MARCUSTOMLINSON
[08:47] <Laney> oSoMoN: do you know if something changed in snapd to make https://launchpadlibrarian.net/447949360/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz happen?
[08:48] <duflu> pieq, Trevinho might want to do a sooner update of 3.34 since he's working on it upstream. Wait till he gets here
[08:48]  * Laney picked you as the most likely person to know in here atm
[08:49] <didrocks> (and not an innocent random victimà
[08:49] <didrocks> )*
[08:50] <oSoMoN> Laney, nope
[08:50] <Laney> :(
[08:50] <pieq> Laney, one month without night light, my eyes are gonna melt.
[08:50] <oSoMoN> Ken would know, I suppose
[08:50] <didrocks> pieq: easy, no screen at nights from now on! :)
[08:50] <duflu> I say ask Marco because generally by the time I prepare a single fix SRU he usually has a multi-fix SRU ready to replace it
[08:51] <pieq> didrocks, you're so healthy...
[08:52] <didrocks> it's rather: do what I say, not what I do :p
[08:55] <duflu> Yes it is the noisiest eoan regression I have seen
[08:55] <duflu> subjectively
[08:57] <Laney> We agreed it wasn't a rls bug for the team, but if someone wanted to propose an upload with the patch and see it through the process, it could still happen.
[08:57] <Laney> mooooooooiiiiinnnnnn didrocks btw
[08:57] <didrocks> heyyyyyyy Laney ;)
[08:58] <Laney> didrocks: did you see the canary image failures? seems the PPA needs a focal package published
[08:59] <didrocks> Laney: well, the image doesn't boot anyway, but let's open the focal archive in the PPA as it's easy enough
[08:59] <Laney> alternative is to drop it from cdimage
[09:00] <didrocks> Laney: we aren't sure yet what will happen, let's wait for the Vancouver's sprint output, until then, I'll just do a dummy small upload, thanks for the ping!
[09:00] <Laney> okey!
[09:14] <duflu> pieq, conclusion: No plan yet. So I might have a go at it before the end of the day
[09:14] <duflu> Which for us is soon
[09:18] <pieq> duflu, cool! Thanks :)
[09:38] <duflu> Oh. I didn't realise it was Wayland only. That would be why it's low priority
[09:39] <duflu> Still the noisiest regression though
[09:51] <seb128> goood morning desktopers (from London today!)
[09:51] <marcustomlinson> hey seb128
[09:51] <seb128> Laney, thx for relaying that canary image ping from yesterday evening to didrocks :)
[09:51] <seb128> hey marcustomlinson , how are you?
[09:51] <Trevinho> seb128: hi,
[09:51] <Laney> hi seb128
[09:51] <Laney> didn't see any ping
[09:51] <Laney> just failure emails
[09:51] <seb128> ah ok, infinit_y asked on the channel in the evening about it
[09:52] <duflu> Morning seb128 and Trevinho
[09:52] <marcustomlinson> seb128: tired :P I woke up at 5 this morning, drove 50miles to accept a delivery at my parents house, and 50 back in time for work
[09:52] <seb128> marcustomlinson, urg :(
[09:52] <seb128> hey duflu, bonjourno Trevinho
[09:52] <marcustomlinson> seb128: yourself? :)
[09:52] <Wimpress> seb128: o/
[09:53] <Wimpress> I'm sat at a hot desktop by the turing space :-)
[09:53] <seb128> Laney, the snap issue you pinged Olivier about, could it be because we didn't open the stable/ubuntu-20 track for them yet?
[09:55] <Trevinho> there are probably already few fixes that are sru material on shell / mutter, i will get few cherry picks ready (assuming .2 is not coming soon)
[09:56] <Laney> seb128: no, that fails in a much more obvious way
[09:58] <Laney> try like "snap download --channel=stable/ubuntu-20.04 gtk-common-themes" (it works)
[10:00] <seb128> we are looking at it with W_impress
[10:02] <seb128> Laney, do you know what command is returning the 'error: cannot validate seed:'?
[10:02] <seb128> is that the check you added not long ago?
[10:02] <Laney> snap debug validate-seed or something
[10:03] <ricotz> hey desktopers :)
[10:03] <ricotz> I am curious about https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk/commit/3a906fe2ce99ec58f4327c25635d42aa1a1700ad#note_630137
[10:03] <Laney> yeah, that's right
[10:04] <seb128> Laney, Martin thinks the 20.04 track is missing and that install just fallback silently, refresh gives you an error
[10:05] <seb128> when you try to refresh with the stable/ubuntu....
[10:06] <Laney> why did we get builds previously then? https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/ubuntu/
[10:08] <seb128> is the channel/track to use set somewhere and was just updated?
[10:08] <seb128> or maybe you are right and it's not the issue
[10:10] <Laney> it's computed by livecd-rootfs
[10:10] <Laney> local CHANNEL=${3:-"stable/ubuntu-$(release_ver)"}
[10:11] <Laney> and you can see it passed to snap-tool in the build log
[10:11] <Laney> https://paste.ubuntu.com/p/MtnTWyxKBH/
[10:11] <Laney> channel is there
[10:12] <seb128> Wimpress, ^
[10:15] <seb128> (we are also in a meeting so looking on the side)
[10:22] <Laney> Trevinho: just SRU a snapshot imho if you're looking at doing lots of picks
[10:29] <Laney> oho, jbicha just said same on #debian-gnome :>
[10:29] <jbicha> good morning
[10:30] <Laney> o/
[10:38] <Wimpress> seb128: https://github.com/intel/dptf
[10:40] <seb128> Wimpress, thx
[10:41] <Wimpress> dptfxtract is in the archive too.
[10:43] <ricotz> seb128, hi :)
[10:45] <ricotz> seb128, I am hoping you will have time for https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1803136
[10:48] <seb128> ricotz, hey, thx for the reminder, I will try to have a look today
[10:48] <clobrano> morning all 0/
[10:49] <clobrano> if any of you preferred the dark gnome shell, now it can be changed :)  https://github.com/ubuntu/yaru/pull/1578
[10:49] <ricotz> seb128, that would be great, thanks!
[10:51] <seb128> ricotz, k, just did it since it was easy enough :)
[10:52] <seb128> hey clobrano , how are you?
[10:52] <seb128> clobrano, nice one! :-)
[10:52] <clobrano> hey seb128, I'm fine, yourself?
[10:54] <seb128> I'm good, in London today and tomorrow for some meetings and next cycle desktop plans reviews
[11:06] <ricotz> seb128, oh, so you will upload it?
[11:07] <seb128> ricotz, it's uploaded now, needs SRU team review next
[11:07] <ricotz> great!
[11:30] <seb128> oSoMoN, I commented on bug #1849162 , one reason we didn't do it at the same is that we already have a calendar preinstalled (gnome-calendar)
[11:30] <seb128> we can have the discussion on how they would overlap, but we should talk about it before adding it imho
[11:37] <ricotz> seb128, sorry, could you point me to the uploaded package for me to follow? I would have expected it here https://launchpad.net/ubuntu/bionic/+queue?queue_state=1
[11:42] <seb128> ricotz, sorry, I signed up with my Debian key, reuploading
[11:42] <ricotz> ok
[11:49] <ricotz> \o/
[11:51] <Trevinho> Laney: yeah, well I would love to snapshot, if it wasn't that I hate to make them.... In the sense that making it + pristine tar and stuff is a waste of time, or am I doing it wrong?
[11:51] <Laney> ninja dist?
[11:52] <Trevinho> Laney: yeah, plus creating a fake tag, plus import, push three branches...
[11:53] <Trevinho> but ideally I had just few commits in mind, but let me see
[11:53] <Laney> what fake tag?
[11:53] <Laney> think you are exaggerating just a little bit
[12:00] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319
[12:00] <Wimpress> seb128: That is the bug I mentioned. Tagged as requested.
[12:05] <Trevinho> Laney: well we need a 3.34+git34568790 tag to make gbp happy to import it, no?
[12:05] <Trevinho> well, .1..
[12:06] <Trevinho> anyways, I think i've to follow that rood
[12:06] <Trevinho> road*
[12:15] <didrocks> Wimpress: quite impressed about the Techsnap review, indeed. Accurate and deep dive :)
[12:17] <seb128> Wimpress, thx
[12:27] <Laney> Trevinho: sorry was looking into some ppc64el weirdness
[12:27] <Trevinho> Laney: np
[12:27] <Laney> it's ninja dist; gbp import-orig --upstream-vcs-tag=<the commit you disted at>
[12:27] <Laney> https://salsa.debian.org/laney/mutter did it there for you
[12:28] <Laney> enjoy
[12:28] <seb128> Trevinho, I got that weird bug with the lockscreen being displayed over the session but not really
[12:29] <Trevinho> seb128: mh, still in your slow machine right?
[12:29] <seb128> same as the other day, screen autolocked on idle and and immediatly moved the mouse because I didn't want to have it locking
[12:29] <seb128> yes
[12:29] <seb128> looks like it's an issue when you try to prevent the locking by an action when it already kicked in
[12:30] <Trevinho> seb128: so like stopping the idle..
[12:30] <seb128> yeah
[12:30] <Trevinho> seb128: try playing with gsettings set org.gnome.desktop.session idle-delay 1
[12:30] <Trevinho> (i'm also doing it)
[12:40] <seb128> Trevinho, so yeah, trivial to trigger here
[12:40] <oSoMoN> seb128, re-lightning, that makes sense, I wasn't aware of the rationale
[12:41] <Trevinho> seb128: ouch, I can't instead... mhmh, indeed some racing issue, can you give me access there via tmate?
[12:41] <Trevinho> once in broken state
[12:41] <oSoMoN> that doesn't prevent me from bundling lightning into the main thunderbird package, but maybe not enabled by default? that would be a good first step in the right direction
[12:41] <Trevinho> well, just before either
[12:42] <seb128> Trevinho, I'm in between meeting in the office, I will probably do that once I'm back, no hurry
[12:42] <Trevinho> or if you don't want to install tmate in snap there's something similar... can't remember the name though
[12:42] <Trevinho> sure
[12:42] <seb128> oSoMoN, yeah, I think it's fine
[12:43] <Trevinho> willcooke: do you remember the name of that? ^
[12:43] <willcooke> reading
[12:44] <willcooke> what was that for?
[12:45] <willcooke> ohh
[12:45] <willcooke> erm
[12:45] <seb128> oSoMoN, adding it isn't going to add a new .desktop right? like looking in the overview for calendar would not list it?
[12:46] <willcooke> teleconsole
[12:46] <willcooke> Trevinho, seb128 ^
[12:46] <oSoMoN> seb128, nope
[12:47] <oSoMoN> lightning is a pure thunderbird extension, it's installed as a packed xpi file in /usr/lib/thunderbird-addons/extensions/, so no desktop files
[12:49] <seb128> k, good
[12:59] <ricotz> oSoMoN, hi, did you noticed localizations issues in thunderbird, exspecially names of default folders?
[13:00] <oSoMoN> ricotz, yeah, that's a known bug, let me look up the number
[13:00] <oSoMoN> bug #1847772
[13:00] <ricotz> oSoMoN, ah, good
[13:00] <ricotz> oSoMoN, any concerns about this WeTransfer add-on?
[13:01] <ricotz> personally I would not want to have it by default
[13:02] <oSoMoN> ricotz, it's on by default in the upstream builds, so it kinda makes sense
[13:02] <oSoMoN> but you have to explicitly opt-in to use it in the settings
[13:02] <oSoMoN> so I think it's a fine balance
[13:03] <ricotz> hmm, I tend to disable things which I don't use, but I see
[13:10] <Trevinho> willcooke: thanks
[13:27] <hellsworth> good morning desktopers!
[13:28] <marcustomlinson> hey hellsworth
[13:30] <kenvandine> Hello desktopers, meeting time!
[13:30] <kenvandine> #startmeeting Desktop Team Weekly Meeting - 2019-10-22
[13:30] <meetingology> Meeting started Tue Oct 22 13:30:23 2019 UTC.  The chair is kenvandine. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <kenvandine> Roll call:  didrocks, duflu (out), hellsworth, jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 (out) , tkamppeter, trevinho, robert_ancell (out)
[13:30] <marcustomlinson> o/
[13:30] <Trevinho> o/
[13:30] <oSoMoN> o/
[13:30] <hellsworth> \o
[13:32] <didrocks> o/
[13:32] <kenvandine> let's get started
[13:33] <kenvandine> we don't have rls-ff tracking reports yet, so we can skip those :)
[13:33] <kenvandine> #topic rls-ee-bugs
[13:33] <kenvandine> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:34] <kenvandine> anyone with opinions on bug 1845801
[13:36] <kenvandine> sounds like it causes pain, but probably a corner case
[13:37] <didrocks> I didn't have autologin issues when doing iso testing, I think Laney would know about the session handling maybe?
[13:37] <didrocks> I'm wondering about the "do-release-upgrade" was rocky
[13:37] <didrocks> so maybe a consequence?
[13:38] <didrocks> I think duflu started engaging with them and added to the list, maybe he should continue following up?
[13:38] <Laney> I can try it, I have an nvidia machine
[13:38] <kenvandine> Laney: great
[13:38] <Laney> it should be accepted if it's a real bug
[13:38] <Laney> if i can't make it happen, will need to hand it off though
[13:38] <didrocks> agreed
[13:40] <kenvandine> the other incoming bug has been reported upstream
[13:41] <kenvandine> duflu assigned it to himself
[13:41] <Laney> link it?
[13:41] <kenvandine> bug 1849135
[13:42] <kenvandine> sorry :)
[13:42] <Laney> thx
[13:42] <Laney> so one pixel doesn't work for clicking
[13:42] <Laney> -1 for tracking imho
[13:42] <kenvandine> agreed
[13:42] <didrocks> -1 as well
[13:42] <kenvandine> #topic rls-dd-bugs
[13:43] <seb128> (it's the one pixel you end up if you throw your mouse to the corner I think)
[13:43] <kenvandine> hey seb128!
[13:43] <seb128> hey
[13:44] <kenvandine> nothing for us in rls-dd-incoming
[13:44] <seb128> (anyway, -1 is probably fine, there has been only one report so far)
[13:44] <kenvandine> looks like duflu is looking into it anyways and he initially reported it upstream
[13:46] <kenvandine> everything under rls-dd-tracking looks fine.  All either assigned or fix committed
[13:46] <kenvandine> #topic rls-bb-bugs
[13:47] <kenvandine> nothing incoming for us
[13:48] <kenvandine> and everything tracking looks fine
[13:48] <kenvandine> #topic update_excuses_by_team.html#desktop-packages
[13:48] <Laney> not open yet
[13:48] <Laney> come back next week :>
[13:49] <kenvandine> :)
[13:49] <kenvandine> yay
[13:49] <kenvandine> #topic aob
[13:49] <kenvandine> One thing from me... Great release everyone!
[13:49] <kenvandine> lots of positive press, loving it
[13:49] <didrocks> yeah \o/
[13:50] <hellsworth> woo!
[13:50] <seb128> indeed, well done team, great release!
[13:50] <marcustomlinson> :)
[13:50] <kenvandine> and another note... sadly willcooke's last week
[13:51] <marcustomlinson> :,(
[13:51] <oSoMoN> you'll be missed willcooke
[13:51] <didrocks> let's wish him the best for his next endover :)
[13:51] <hellsworth> i wish you all the best willcooke
[13:51] <kenvandine> just wish i could buy him another beer :)
[13:52] <tkamppeter> Lots of people are helping us that it will go on in the future:
[13:52] <tkamppeter> https://drive.google.com/drive/folders/1KWZTTXxB7nDCFtYIC6aUF36zN0lv0T7I
[13:52] <kenvandine> seb128: i hope you are buying drinks tonight :)
[13:52] <marcustomlinson> best of luck willcooke
[13:53] <tkamppeter> all the best, willcooke!
[13:53] <kenvandine> tkamppeter: where are those pictures from?
[13:53] <seb128> kenvandine, sure, you should come :)
[13:53] <tkamppeter> kenvandine, GSoC Mentor Summit this weekend.
[13:54] <kenvandine> oh... right there in the folder name :)
[13:54] <tkamppeter> These people have mentored students, so that we get new great people into free software community.
[13:55] <tkamppeter> I am the one in the white OpenPrinting t-shirt in the middle.
[13:55] <kenvandine> ok, last call for other business?
[13:55] <Laney> yes
[13:55] <kenvandine> tkamppeter: nicely placed, right in the middle
[13:55] <kenvandine> :)
[13:56] <tkamppeter> In the video in the end you see that it is shot with a drone.
[13:56] <Laney> kenvandine: can you pls own fixing https://launchpadlibrarian.net/447954589/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz in one way or another?
[13:56] <Laney> Wimpress and seb128 were looking into it
[13:56] <Laney> but not sure anyone got very far
[13:56] <kenvandine> sure
[13:57] <hellsworth> what is that a build log of?
[13:57] <kenvandine> focal image
[13:57] <seb128> Martin though it was lack of stable/ubuntu-20.04 tracks enabling
[13:57] <Laney> yes, it's not that though
[13:57] <seb128> but Laney is pretty sure it's not
[13:57] <seb128> we didn't poke further
[13:57] <kenvandine> it's definately not
[13:58] <seb128> so kenvandine is welcome to look :)
[13:58] <kenvandine> i'll talk to mvo
[13:58] <Laney> thx
[13:58] <kenvandine> it downloaded both of those snaps
[13:58] <Laney> it worked yesterday
[13:58] <kenvandine> Laney: is there a bug to track this?
[13:58] <Laney> no
[13:58] <kenvandine> oh interesting
[13:59] <kenvandine> Laney, seb128: I'll chase it down
[13:59] <kenvandine> any more business?
[13:59] <kenvandine> Laney: can you dig up a build log from yesterday's image?
[14:00] <kenvandine> let's wrap up and save that for after the meeting
[14:00] <kenvandine> #endmeeting
[14:00] <meetingology> Meeting ended Tue Oct 22 14:00:49 2019 UTC.
[14:00] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-10-22-13.30.moin.txt
[14:01] <marcustomlinson> thx
[14:02] <Laney> the index is here https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/focal/ubuntu/
[14:02] <didrocks> thx
[14:02] <willcooke> thanks for the well wishes all.
[14:07] <kenvandine> Laney: thanks
[14:11] <kenvandine> mvo: can you help look at seed validation issues in focal image builds?
[14:13] <kenvandine> there is a newer revision of the calculator snap since the last successful image build
[14:13] <kenvandine> but it connects to the same content provider
[14:13] <kenvandine> which it thinks is missing
[14:14] <mvo> kenvandine: looking, what snapd version is used?
[14:15] <kenvandine> 2.41+19.10.1
[14:15] <kenvandine> same version that succeeded
[14:15] <kenvandine> build failed https://launchpadlibrarian.net/447954589/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz
[14:15] <kenvandine> last success https://launchpadlibrarian.net/447812945/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz
[14:16] <kenvandine> which was yesterday
[14:16] <kenvandine> there are newer revisions of gnome-calculator and gnome-characters today
[14:16] <kenvandine> gnome-calculator is what's failing
[14:16] <mvo> kenvandine: gnome-calculator from edge?
[14:16] <kenvandine> but those default providers are the same and the revisions for those haven't changed
[14:16] <kenvandine> stable
[14:16] <mvo> kenvandine: ok
[14:16] <mvo> kenvandine: indeed, strange
[15:48] <seb128> kenvandine, mvo, did the discussion stopped or moved to some other channel?
[15:48] <mvo> seb128: I started looking but have no idea right now
[15:48] <seb128> Laney, do you know how the glib/autopkgtest failure from the week before release resolved itself?
[15:48] <mvo> seb128: I'm asking in the team before I digg deeper
[15:49] <seb128> mvo, k, thx
[15:50] <Laney> it worked after a retry
[15:51] <seb128> Laney, I mean do you have any idea where the issue was coming from?
[15:51] <seb128> it was not a simple retry, retries failed consistently for a while (see http://autopkgtest.ubuntu.com/packages/g/glib2.0/eoan/i386)
[15:52] <seb128> Laney, I'm asking because I opened an upstream issue and I would like to follow up/close with something better than 'it automagically stopped failing no idea why/what changed'
[15:54] <Laney> no, I tried it locally and it worked, then I tried it on scalingstack manually and it worked, then I retried from autopkgtest and it worked
[15:54] <Laney> if I have to guess it's some shit to do with removing the i386 kernel
[16:02] <seb128> I though it might be but I don't understand how it autoresolved then
[16:02] <seb128> oh well...
[16:04] <Laney> yeah
[16:04] <Laney> just couldn't get to a broken situation to have a look at all
[16:19] <seb128> jamesh, kenvandine, I see that error coming back in journal log from random bugs,
[16:19] <seb128> xdg-desktop-por[2912]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed
[16:19] <seb128> is that a known issue/something we should look at?
[16:56] <seb128> Trevinho, the rls post on discourse, you updated the status of the first bug assigned to you (thanks!) but there are some others bellow :)
[16:57] <Trevinho> seb128: my ctrl-f only was finding that :o
[16:58] <Trevinho> ah, actually... damn I thought it was mentioned in each name
[16:58] <Trevinho> in each bug, the na,e
[16:58] <Trevinho> name*
[17:08] <seb128> :-)
[17:47] <kenvandine> hellsworth: FYI https://code.launchpad.net/~ubuntu-desktop/+snap/gnome-3-34-1804
[17:47] <kenvandine> i had it built a couple of hours ago
[17:47] <kenvandine> it's in edge
[17:51] <hellsworth> oh nice!
[17:52] <hellsworth> thank you, kenvandine. i built it this morning to make sure it built ok with the new build snap changes and i guess i should have asked you to launch a proper build to get it into edge.