[07:19] <didrocks> good morning
[07:20] <duflu> Morning didrocks
[07:28] <didrocks> hey duflu!
[07:38] <jibel> good morning
[07:39] <duflu> Hi jibel
[07:39] <jibel> Hi duflu didrocks
[07:50] <didrocks> salut jibel
[07:53] <oSoMoN> good morning desktoppers
[07:55] <duflu> Morning oSoMoN
[08:01] <oSoMoN> hey duflu
[08:20] <didrocks> hello oSoMoN
[08:21] <oSoMoN> salut didrocks
=== maclin1 is now known as maclin
[08:36] <willcooke> morning all
[08:37] <didrocks> hey willcooke
[08:37] <willcooke> Had a report that Bionic isn't rendering the Ubuntu Light and Ubuntu Thin font correctly.  Anyone else seen that?
[08:40] <oSoMoN> good morning willcooke
[08:41] <didrocks> I need to upgrade to it first, still on artful to quietly hack the Shell :p (but planned to upgrade just after FOSDEM)
[08:42] <willcooke> I wonder if duflu  has noticed, likely if anyone did he did :)
[08:42] <oSoMoN> same here, haven't upgraded yet, although I was planning on doing so this week
[08:43] <duflu> willcooke, if it's not the default theme then I haven't looked in a very long time
[08:51] <willcooke> :)
[08:52] <duflu> willcooke, where's the report?
[08:56] <willcooke> duflu, in my email from sabdfl :)  I'll open a bug
[08:56] <willcooke> duflu, any ideas which project I should open it against?  The font itself?
[08:56] <willcooke> GNOME Shell?
[08:56] <duflu> willcooke, depends /how/ it looks wrong
[08:56] <willcooke> duflu, ack. I'll fire up a VM and take a look
[08:56]  * willcooke also hasn't upgraded to B
[08:56] <willcooke> I've got it in a VM though
[08:57] <duflu> It's what all the cool people are doing
[08:59] <duflu> "libinput-test-suite-runner must be run as root"
[08:59]  * duflu runs it as root
[08:59]  * duflu sees machine turn off
[08:59] <willcooke> heh
[09:02] <seb128> good morning desktopers
[09:02] <willcooke> woah, keyboard is messed up in my VM all of a sudden
[09:02] <willcooke> hey seb128
[09:02] <didrocks> salut seb128, bien rentré ?
[09:02] <willcooke> (oh, maybe I had a key stuck down)
[09:02] <seb128> hey willcooke didrocks
[09:02] <seb128> didrocks, oui, merci
[09:02] <Laney> yooooooooooo
[09:02] <seb128> hey Laney
[09:03] <didrocks> hey Laney
[09:04] <duflu> sup Laney
[09:05] <Laney> hey seb128 didrocks duflu
[09:05] <seb128> hey duflu
[09:05] <Laney> good weekends???
[09:05] <Laney> seb128: good travel back?
[09:05] <oSoMoN> morning seb128, Laney
[09:05] <seb128> lut oSoMoN
[09:06] <seb128> Laney, yeah, much better than on the way there :) I managed to sleep for a good part of the flight and to watch one movie
[09:06] <didrocks> rainy week-end, but good
[09:06] <didrocks> you?
[09:09] <seb128> not rainy here, but cold!
[09:10] <seb128> didn't do much, time to get back/unpack/etc it was already 3pm on saturday
[09:10] <seb128> we walked a bit around yesterday and played some games later on, that's about it
[09:12] <Laney> nothing stressful, good!
[09:12] <Laney> we went to the indoor snowsports place not too far away
[09:12] <Laney> had a snowboarding lesson
[09:12]  * Laney fell over about 1000 times
[09:12] <Laney> hey oSoMoN!
[09:14] <oSoMoN> hey Laney
[09:25] <flexiondotorg> Morning desktopers
[09:25] <seb128> hey flexiondotorg
[09:28] <duflu> Morning flexiondotorg
[09:28] <duflu> tjaalton, I got impatient :) - https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1696929/comments/24
[09:28] <ubot5> Ubuntu bug 1696929 in libinput (Ubuntu Bionic) "Touchpads are unresponsive and laggy for small finger movements" [High,In progress]
[09:40] <tjaalton> duflu: heh, very well
[09:41] <frechdachs69> Q: is someone here who has successfully automated 16.04 desktop installation using preseed?
[09:46] <willcooke> duflu, I expect its this bug: https://bugs.launchpad.net/ubuntu-font-family/+bug/1512111
[09:46] <ubot5> Ubuntu bug 1512111 in ubuntu-font-family-sources (Ubuntu) ""Ubuntu Light" font has heavier weight than "Ubuntu"" [Medium,In progress]
[10:01] <willcooke> Laney, any ideas what the bug number was for the previous time we fixed that? ^
[10:05] <Laney> do you mean https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1048600 ?
[10:05] <ubot5> Ubuntu bug 1048600 in ubuntu-font-family-sources (Ubuntu Quantal) "[FFe] Restore "Ubuntu Medium" weights in Ubuntu's binary .deb" [High,Fix released]
[10:05] <willcooke> ahhhh
[10:07] <Laney> The font itself hasn't changed since xenial
[10:07] <Laney> so if there's a problem it's probably in the stack somewhere
[10:07] <willcooke> ack, thanks Laney
[10:10] <Laney> I can't tell a difference in that that correct / wrong file (https://launchpadlibrarian.net/344539285/test.html) :(
[10:10] <Laney> https://imgur.com/a/HO2Zy
[10:11] <willcooke> odd
[10:11] <willcooke> This is what I see on A
[10:11] <willcooke> https://imgur.com/a/27Y0X
[10:12] <willcooke> Laney, Are you using Firefox?
[10:12] <Laney> yeh
[10:13] <willcooke> ah ah
[10:13] <willcooke> yeah, looks fine in Firefox, wrong in Cr.*
[10:13] <Laney> the bug said it was wrong everywhere fonts are rendered
[10:16] <Laney> https://imgur.com/a/yBIly
[10:18] <willcooke> So Cr. specific then?
[10:18] <willcooke> I can make stuff light in Libre Office ok
[10:18] <Laney> that's the only place that I can see it being wrong
[10:18] <Laney> epiphany looks ok too
[10:18] <Laney> maybe could try an older version of chromium or something
[10:19] <duflu> willcooke, bug updated
[10:21] <oSoMoN> willcooke, so the font is rendered incorrectly in chromium only?
[10:21] <willcooke> oSoMoN, starting to look that way
[10:21] <willcooke> thanks duflu
[10:21] <duflu> AFAIK the bug is invalid
[10:21] <duflu> AFAICT
[10:22] <Laney> yeah I'm not sure local('Ubuntu Light') is a thing
[10:22] <Laney> firefox doesn't actually render it 'lighter' AFAICS
[10:22] <duflu> Yeah "Ubuntu Light" doesn't exist. You want "Ubuntu" and then select Style=Light, which CSS can't do
[10:26] <duflu> Exit stage left
[11:09] <willcooke> woo, first proper lock up in Artful
[11:10] <willcooke> Jan 22 11:07:11 farnsworth kernel: [10943.367760] gnome-shell[1929]: segfault at 80 ip 00007f781fed83dc sp 00007ffe6f613e88 error 4 in libmutter-cogl-1.so[7f781fe97000+a5000]
[11:10] <willcooke> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
[11:10] <willcooke> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
[11:10] <willcooke> sorry, pasted too much
[11:12] <Trevinho> willcooke: mhmh, interesting... any core file?
[11:13] <willcooke> Trevinho, I've got a .crash - you want that somewhere?
[11:13] <Trevinho> willcooke: yeah please
[11:13] <Trevinho> (snap install transfer, transfer /var/crash/fooo.crash) :)
[11:16] <willcooke> Trevinho, transfer not working, how about worm hole?
[11:16] <willcooke> oh wiaty
[11:16] <willcooke> it's a problem reading the file
[11:17] <willcooke> because its a crash file I assume
[11:17] <willcooke> Trevinho, k, fixed
[11:18] <willcooke> Trevinho, done
[11:26] <andyrock> hey all
[11:28] <czajkowski> andyrock: morning
[11:28] <seb128> hey andyrock! how are you? had a good w.e?
[11:28] <seb128> hey czajkowski
[11:28] <andyrock> hey seb128
[11:28] <andyrock> good enough
[11:28] <andyrock> what about you?
[11:30] <seb128> I'm good thanks :)
[11:36] <Trevinho> seb128: we did some cooking challenge, Pasta e fagioli (his work) vs Lampredotto (my "baby" ) :-D
[11:37] <Trevinho> (again we're in the same city, Torino)
[11:37] <seb128> who won?
[11:39] <andyrock> seb128: do you need to ask to know that? :D
[11:39] <seb128> andyrock, congrats! :)
[11:40] <seb128> not surprising, Trevinho doesn't even know Carbonara has cream
[11:40] <seb128> :)
[11:40] <Trevinho> :_(
[11:40] <Trevinho> the belly won for sure!
[11:44] <Laney> let's hire a kitchen at the next sprint
[11:45]  * Laney wants to watch this magic in person
[11:45] <Laney> hey Trevinho e andyrock
[11:45] <Trevinho> hi Laney
[11:45] <Trevinho> I was actually thinking the same... :-D
[11:46] <Laney> :D
[11:46] <Laney> I got a pasta maker for christmas
[11:46] <Laney> need teaching by an expert :-)
[11:47] <Laney> end up making a mess everywhere with the super long pasta on the smaller settings
[12:02] <Trevinho> Laney: oh, I got one too... The philips one or a manual one?
[12:02] <czajkowski> I'm getting hungry now thinking of spaghatti carbonara
[12:03] <Laney> Trevinho: one of those normal manual ones
[12:03] <Trevinho> spaghetti *alla* carbonara... :)
[12:03] <Trevinho> Laney: ahhh.. Ok, so for egg-based pasta recipes I guess
[12:04] <Laney> yeh
[12:05] <Laney> tasty tasty egg
[12:05] <czajkowski> Trevinho: :)
[12:06] <Trevinho> Laney: cool... You can also make Ravioli or Lasagne with that... The classic recipe here is just 1egg every 100grams of flour, but it can vary if more people are coming might add an extra egg every 400, 500g
[12:07] <Trevinho> And speaking of pasta, it's time for that here... see you :)
[12:09] <seb128> Trevinho, enjoy!
[12:13] <willcooke> andyrock, do you have a link to your work on disks hiding loop devices?  I want to mention it in the newsletter.
[12:14] <andyrock> https://github.com/storaged-project/udisks/pull/460
[12:14] <andyrock> I'm trying to understand right now why there is this failing test that looks unreleated but it's blocking the work
[12:15] <willcooke> thanks andyrock
[12:15] <andyrock> they said they're going to do that but it has been 12 days already
[12:16] <willcooke> ack
[12:22] <jbicha> good morning
[12:24] <seb128> hey jbicha, how are you?
[12:24] <jbicha> good
[12:24] <jbicha> could you subscribe the bugs team to dconf (being renamed from d-conf) and orca (in bionic NEW, renaming from gnome-orca)?
[12:24] <seb128> andyrock, did you try to ping them?
[12:24] <andyrock> nope, I'll do if I'm not able to reproduce the problem locally slowing down the system
[12:27] <seb128> jbicha, done
[12:28] <jbicha> seb128: thanks, do you think we should reassign all the d-conf bugs to dconf?
[12:28] <andyrock> why in ubuntu the file /etc/os-release  does not have a CPE_NAME entry?
[12:29] <jbicha> dconf already has a dozen bugs that were initially misfiled there since the d-conf name wasn't intuitive
[12:29] <seb128> jbicha, I wouldn't bother, but maybe it you triage/look which ones are still current
[12:29] <jbicha> ok
[12:29] <seb128> jbicha, also the old name is what needs to be used still for < bionic issues
[12:30] <jbicha> yes, there needs to be a d-conf task if anyone wants to do an SRU there
[12:31] <jbicha> seb128: could you accept orca from the bionic new queue? (it was uploaded in December)
[12:31] <seb128> jbicha, I can add to my review queue yes
[12:32] <seb128> is that blocking other work?
[12:32] <jbicha> no, it just would be nice to finish up the rename
[12:33] <seb128> k
[12:38] <Laney> bah, ctrl-enter posts on discourse
[12:38]  * Laney thought it might insert a new bullet
[12:50] <seb128> Laney, unsure what you consider "making any perfect-enemy-of-good type of mistake?" in the text you quoted, my point was basically that any workflow/infra change at this point of the cycle would be a distraction by its nature
[12:50] <Laney> hi seb128
[12:51] <seb128> there is no quality/solution being ready aspect in that comment
[12:51] <Laney> nothing in your comment, don't worry
[12:51] <seb128> hey Laney :)
[12:51] <Laney> I can forsee a situation where we don't switch away from bzr though until the new thing is super great
[12:52] <seb128> which is already the case today from what has been said, so all good :)
[12:53] <Laney> not sure if trolling
[12:53] <seb128> I think it's more that the people who are familiar with the solution and its advantage haven't really done any effort to onboard others/the team
[12:53] <seb128> out of telling them how great it is and how much they miss out by not having it
[12:53] <Laney> ok, I thought that we were being asked to list advantages
[12:54] <Laney> that's what I got from your message anyway
[12:54] <Laney> please tell me why this is good
[12:54] <seb128> well, it's good to tell us why it's so great
[12:54] <Laney> so I tried to do that...
[12:54] <seb128> no, I think it's good that we know about the pro/advantages
[12:54] <seb128> I think that's part of the issues, those who are familiar with the workflow assume that others are as well or will see the value by themselve
[12:55] <seb128> which might be true for some, but I think there is also value by summarizing what we find good and motivates the choices, for those less involved in the tools choices
[12:55] <seb128> or who don't find things to be that obvious
[12:55] <seb128> so thanks for doing that summary :)
[12:57] <jbicha> seb128 or anyone: feel free to do a Debian update and we can help you with Salsa
[12:57] <jbicha> gnome-calendar and gnome-photos have new 3.26 versions that need packaging
[12:59] <seb128> jbicha, that feels backward
[12:59] <seb128> I'm not asking for any change, if you want me to switch you should be one doing the job of convincing and documenting why
[12:59] <jbicha> take a look at https://wiki.debian.org/Gnome/Git for more information about how to do the update
[13:00] <seb128> I'm not interested, Ive enough to do
[13:00] <seb128> but thanks
[13:00] <Laney> :/
[13:00] <seb128> again, if you expect people to switch you need to be the one doing the convincing
[13:00] <jbicha> you're not interested in packaging GNOME updates any more??
[13:00] <seb128> I am, but I've a perfectly working workflow for those
[13:00] <jbicha> the proper way to update gnome-photos since it's synced is with the Debian workflow
[13:01] <seb128> I'm not interested in gnoime-photos
[13:01] <seb128> we are not using it
[13:01] <jbicha> unless there was a particular need to be in a hurry (like an impending freeze or something), this upload was wrong IMO because it wasn't proposed to Debian
[13:01] <jbicha> https://launchpad.net/ubuntu/+source/gnome-system-monitor/3.26.0-1ubuntu1
[13:02] <seb128> come on
[13:02] <jbicha> (I did notice a bit later and pushed it to Debian so that it's in sync now)
[13:02] <jbicha> it's not like you don't have Debian upload rights…
[13:03] <seb128> unsure if you are trying to convince me of changing my workflow, but you are going to wrong way about it
[13:03] <seb128> you are making me want to argue back rather than agree with you there
[13:04] <seb128> anyway I agree with you than in ideal world our packages would be in sync with Debian and changes go to Debian first
[13:04] <seb128> in practice people are busy and not familiar with the team/toosl/flow involved
[13:04] <seb128> which sure we can work on fixing
[13:05] <seb128> but you are not going people over by telling them off
[13:05] <jbicha> I created a wiki page and I and others in #debian-gnome are volunteering to help you learn the workflow
[13:06] <seb128> good to know
[13:06] <seb128> let's see who in our contributors use the option
[13:07] <seb128> we can maybe see at the end of the cycle how many people went that way and learnt the new workflow/contributed back on the gnome channel rather than on launchpad
[13:07] <Laney> you think it should just be an organic thing?
[13:08] <seb128> I doubt the current onboarding approach is going to bring many people over
[13:09] <seb128> by nature most people just focus on what they are doing and don't get out of their way to learn new tools/ways until they feel the need imho
[13:09] <seb128> and I'm not sure most of us feel that need
[13:09] <seb128> that's all I'm saying
[13:10] <Laney> ok, I'll not bother spending much energy on pushing for this then
[13:10] <seb128> now we are way to transition
[13:10] <seb128> including forcing people to swallow it even if they don't want to
[13:10] <seb128> or helping them onboard
[13:10] <seb128> I'm not sure what would be the best way though
[13:13] <seb128> Laney, don't let my comment stop you, others might be interested
[13:14] <Laney> I think it'd have to be a "we are using this new workflow" now kind of thing to work properly
[13:14]  * didrocks still thinks that doing a git-upstream based workflow is the right thing to do. Unsure we should investigate ubuntu-git/debian-git before this cycle feature freeze though (I for sure won't have time for this at least)
[13:14] <Laney> IMO though - having people using different things all over the place wouldn't be optimally productive
[13:14] <Laney> I thought that we had broad agreement on switching to a git-based thing, but I was mistaken there
[13:14] <seb128> yeah
[13:14] <didrocks> but just for the sake of gbp pq, I'm in favor of this :)
[13:15] <seb128> Laney, I  don't think anyone ever did the work to try to figure out what are the needs and want or people in ubuntu-desktop
[13:15] <didrocks> then, once we are done in feature-land rush, we can properly try the different approach, evaluate pros and cons and take a decision which can be effective in the LTS+1 dev cycle
[13:16] <didrocks> I guess that comes with some examples:
[13:16] <didrocks> 1. merging from debian
[13:16] <didrocks> 2. updating to a new upstream version
[13:16] <didrocks> 3. editing an existing patch and sending it upstream
[13:16] <didrocks> 4. creating a new patch
[13:16] <didrocks> just showing examples and documented commands so that people have a feeling
[13:16] <seb128> Laney, things got discussed in Debian and people went ahead assuming it would do it for us as well, which might be true or not be ....
[13:17] <seb128> we have no data to work from
[13:17] <jbicha> seb128: are you unconvinced about a git workflow too?
[13:17] <Laney> I think I'm actually arguing for this approach rather than forcing it upon anyone
[13:17] <didrocks> (ah, and 5. how a contributor can propose a change)
[13:18] <didrocks> Laney: well, what you tell is right, the day we take a decision, everyone will have to comply, we can't have one part in bzr, the other in git, the last one in-no-vcs…
[13:18] <Laney> Right
[13:18] <Laney> But I'm not saying "we should do this"
[13:18] <seb128> jbicha, I don't know, I've no pre-made idea, I know that I find git hard to use as an user and I found full-source checkouts heavy in the past, so I would have to play with a suggested solution to see how it feels
[13:19] <didrocks> oh, correct (I think we should do it, but just not "now" ;))
[13:19] <jbicha> didrocks: I think the status quo right now is "part in bzr, part in git, part in no-vcs"
[13:19] <Laney> I don't really understand what the big misstep was - to me this was the start of a discussion
[13:20] <didrocks> jbicha: yeah, and and I agree that's not sustainable in the long term
[13:20] <seb128> Laney, I don't think there is any misstep, the only thing we are pushing back on is the "let's switch today" that jbicha suggested
[13:21] <seb128> it just feel the timing is wrong and that we lack of onboarding/preparation for that
[13:22] <seb128> +1 on what didrocks said, let's wait for at least ff of this cycle, not get distracted of the work we are focussing on
[13:22] <seb128> and we need to create content/examples and win people over by doing a proper job at showing them why they want it
[13:22] <jbicha> I haven't been doing as many merges in the past couple weeks because of it being unclear which VCS I should push the Ubuntu changes to
[13:22] <seb128> it's clear though
[13:22] <seb128> the one in debian/control
[13:23] <seb128> which atm are either bzr branches or no vcs usually
[13:23] <seb128> you can even create a branch on salsa for your use if you want, just don't make it our official vcs yet
[13:25] <jbicha> what about for a no-vcs, non-main package like gnome-builder?
[13:26] <seb128> do what you want
[13:26] <didrocks> the thing is that it may become out of sync, the "post-ff" thing is that people won't have the time to learn the new workflow at this stage of the cycle
[13:26] <seb128> worth things people who disagree just dput without commiting to the vcs you self decided on
[13:27] <seb128> which is likely what I would do if I had to land something in a package where you decided that one needs a salsa account to commit his changes
[13:27] <Laney> Take me up on my offer to do some tutorials at ++$sprint
[13:27] <Laney> if didrocks knows gbp-pq already maybe he can do one too ;-)
[13:27] <didrocks> sure!
[13:27] <jbicha> it takes a few seconds to create a Salsa account at https://signup.salsa.debian.org/
[13:28] <didrocks> and I think we just write a wiki page with some typical day-by-day use case
[13:28] <jbicha> as for permissions, you just have to ask the right person :)
[13:28] <didrocks> as (I?) think I did when we moved to debian/ only branch
[13:28] <seb128> jbicha, that's where you loose people over
[13:28] <didrocks> jbicha: learning a new workflow isn't a few seconds
[13:28] <didrocks> let's be honest on that :)
[13:28] <seb128> I would have no idea who would be the "right person"
[13:29] <seb128> and contributors shouldn't have to figure that out
[13:29] <jbicha> the "right person" is log in to Salsa, visit the repo or the group and click Request Access
[13:29] <seb128> Laney, but yeah, let's have some team sessions/walkthrough and gather feedback in budapest
[13:30] <jbicha> or you can ping someone in IRC if you prefer
[13:47] <willcooke> didrocks, do you have a link to the upstream PR for #1716432?
[13:47] <willcooke> (window titles not centered)
[13:47] <didrocks> willcooke: sure, https://bugzilla.gnome.org/show_bug.cgi?id=792354
[13:47] <ubot5> Gnome bug 792354 in general "panel: center date entry with workarea" [Normal,New]
[13:48] <willcooke> didrocks, merci!  Also, "new sound options in settings" is that > 100% volume?
[13:48] <didrocks> willcooke: Allan seems to have some seconds thoughts on it if you read the threads and may be willing to accept, didn't hear back though despite my last comment
[13:50] <willcooke> ack
[13:50] <willcooke> lets see
[13:51] <willcooke> didrocks, "sound options in settings" is > 100%?
[13:51] <willcooke> oh
[13:51] <willcooke> wait
[13:51] <willcooke> maybe we're talking cross purposes
[13:51] <didrocks> sounds like it
[13:51] <willcooke> was your comment "Allan seems to have some second thoughts" re: sound or centering windows?
[13:51] <didrocks> yo umention window titles not centered
[13:52] <didrocks> ah, on centering windows
[13:52] <willcooke> kk
[13:52] <didrocks> the first answer was "no"
[13:52] <didrocks> then, seeing a screen capture, he finds it weird indeed
[13:52] <willcooke> got it
[14:32] <kenvandine> oSoMoN, no replies to your g_app_info_launch_default_for_uri topic :/
[14:33] <oSoMoN> nope indeed, I guess no one has hit the same issue yet
[14:34] <kenvandine> i'm sure firefox isn't the only consumer of that api, so they will eventually
[14:38] <seb128> oSoMoN, what topic?
[14:40] <oSoMoN> seb128, https://forum.snapcraft.io/t/opening-a-local-file-with-its-default-application/3493
[14:40] <seb128> oSoMoN, thanks
[14:40] <kenvandine> hey seb128!
[14:40] <seb128> hey kenvandine
[14:42] <seb128> brb, changing location
[14:44] <Laney> oSoMoN: does the OpenFile/OpenURI portal help you there? (once those work)
[14:46] <GunnarHj> Hi jbicha, can you possibly help to get ibus-libpinyin updated (and with that possible to be MIR'ed).
[14:46] <GunnarHj> https://irclogs.ubuntu.com/2018/01/16/%23ubuntu-desktop.html#t13:47
[14:47] <jbicha> happyaron: would you like to help with the ibus-libpinyin update?
[14:48] <oSoMoN> Laney, I guess that depends on whether g_app_info_launch_default_for_uri will be rewritten to use those?
[14:48] <oSoMoN> btw I'm not seeing any doc for OpenFile here: https://github.com/flatpak/xdg-desktop-portal/tree/master/data
[14:49] <jbicha> GunnarHj: yes, I can help. Please remind me if it looks like I might have forgotten :)
[14:51] <jbicha> didrocks: I replied to LP: #1713171 , not sure if you're subscribed there
[14:51] <ubot5> Launchpad bug 1713171 in gnome-todo (Ubuntu) "[MIR] gnome-todo" [Undecided,Incomplete] https://launchpad.net/bugs/1713171
[14:52] <oSoMoN> Laney, https://github.com/flatpak/xdg-desktop-portal/blob/master/README.md says that « the OpenFile portal is working well as a backend for the GtkFileChooserNative API », so it doesn't look like what I'm after
[14:52] <Laney> https://git.gnome.org/browse/glib/tree/gio/gappinfo.c#n740
[14:53] <GunnarHj> jbicha: In bug #1735362, comment #16 and #17, I explained what I think should be done. Two syncs and one upload with a (temporary) Ubuntu delta.
[14:53] <ubot5> bug 1735362 in ibus-libpinyin (Ubuntu) "Replace ibus-sunpinyin with ibus-libpinyin" [Medium,In progress] https://launchpad.net/bugs/1735362
[14:55] <Laney> well line 759 specifically
[14:55] <Laney> :-)
[14:55] <didrocks> jbicha: oh, great that changed! I downloaded it on artful without checking the update, thanks! looking
[14:56] <oSoMoN> Laney, oh wow, I forgot that more often than not the code is the doc :)
[14:56]  * didrocks reviews directly https://launchpadlibrarian.net/348923851/gnome-todo_3.26.1-0ubuntu4_3.26.2-2.diff.gz thus
[14:56] <oSoMoN> all settled then, only have to wait for portals
[14:57] <Laney> poor jamesh
[14:58] <didrocks> jbicha: +  * Bump Breaks/Replaces for package split so that Ubuntu can sync now
[14:58] <didrocks> but I don't see any "Replaces"
[14:58] <didrocks> only Breaks:
[14:58] <didrocks> which I think wouldn't work well on upgrade
[14:58] <didrocks> (as you splitted the package)
[15:00] <jbicha> ok, I'll add the Replaces to Debian too
[15:04] <didrocks> jbicha: added some more comments as well
[16:16] <jbicha> jackpot51: hi, I'm updating gnote in Debian. We should add 'pop' here too right? https://git.gnome.org/browse/gnote/commit/?id=74304ee
[18:48] <willcooke> night all
[20:08] <s10gopal> https://bugs.freedesktop.org/show_bug.cgi?id=104737 please help me
[20:08] <ubot5> Freedesktop bug 104737 in DRM/AMDgpu "amdgpu module does not bind to 1002:6660 R5 M330" [Major,New]
[20:11] <s10gopal> https://bugs.freedesktop.org/show_bug.cgi?id=104737 please help me
[20:11] <ubot5> Freedesktop bug 104737 in DRM/AMDgpu "amdgpu module does not bind to 1002:6660 R5 M330" [Major,Resolved: notabug]
=== kennyloggins is now known as CoderEurope
[20:26] <jackpot51> jbicha: Yes, `pop` should be added there as well
[20:26] <jackpot51> Thanks very much!
[20:38] <jbicha> jackpot51: GNOME bug 792796 It will probably get into Ubuntu whenever we get gnote 3.28
[20:38] <ubot5> Gnome bug 792796 in main "gschema: Add 'pop' to client-side-decorations default list" [Normal,New] http://bugzilla.gnome.org/show_bug.cgi?id=792796
[21:56] <jackpot51> Great!
=== mmstick_ is now known as mmstick