[02:57] <Trevinho> jbicha: would you mind to backport this commit https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1758224 ?
[02:57] <ubot5> Ubuntu bug 1758224 in gtk+3.0 (Ubuntu) "Scaled gtk theme assets are ignored in HiDPI" [High,Triaged]
[02:57] <Trevinho> err https://gitlab.gnome.org/GNOME/gtk/commit/e36b629c367fa11e6e544ff8b8203bcf29ec73ee
[03:16] <duflu> Trevinho, thanks for the bionic theme update... I'm seeing a 1px gap between bubble menus and their arrow though. Is that new?
[03:16] <Trevinho> duflu: just more visible now
[03:16] <Trevinho> duflu: but it's already fixed
[03:16] <duflu> Also the colour of the arrow is different to the bubble
[03:16] <duflu> slightly
[03:16] <Trevinho> duflu: there are two reviews if you want to check/approve them, I can land them straigth away
[03:29] <duflu> Trevinho, if there are screenshots then I'll probably review them straight away :D
[03:31] <duflu> Although I would also be happy if you got some sleep
[03:50] <Trevinho> duflu: yeah, now that i'm done with another fix, i'm going...
[03:51] <Trevinho> duflu: and fix is this one
[03:51] <Trevinho> https://usercontent.irccloud-cdn.com/file/QZ2WV3hG/image.png
[06:48] <didrocks> good morning
[06:49] <tsimonq2> o/ didrocks
[06:53] <duflu> Hi didrocks, tsimonq2
[06:59] <didrocks> hey tsimonq2, duflu
[07:00] <tsimonq2> o/
=== ecloud_wfh is now known as ecloud
=== pstolowski|afk is now known as pstolowski
=== ochosi_ is now known as ochosi
[08:39] <willcooke> hoy
[08:43]  * duflu doesn't understand but waves to willcooke
[08:43] <willcooke> o/
[08:43] <willcooke> right, now I'm going again.  Dr's bbiab
[08:43] <didrocks> hey willcooke
[08:43] <jibel> hola everyone
[08:45] <duflu> Hi jibel
[08:52] <didrocks> hey jibel
[08:58] <jibel> Laney, jbicha re design change in ubiquity, I agree with acheronuk and tsimonq2 and won't merge until the KDE frontend is updated too.
[09:01] <Laney> hi
[09:02] <ShriHari> hi laney
[09:03] <didrocks> oh, only the GTK frontend was updated?
[09:03] <didrocks> not what I mentioned during the team meeting with jbicha
[09:04] <duflu> Hi hi Laney
[09:07] <Laney> jibel: ok, but I agree with jbicha that it's not introducing a regression
[09:07] <Laney> and if he's not willing to do the work then I guess we don't get the change
[09:08] <tsimonq2> Laney: It's a UX regression of anything.
[09:08] <tsimonq2> s/of/if/
[09:08] <Laney> what?
[09:08] <Laney> that change is not
[09:09] <tsimonq2> One frontend gets new sections and radio boxes and the other gets a terser section of text.
[09:09] <Laney> It already has the previous UI
[09:09] <Laney> The UI is not changing
[09:09] <Laney> Therefore the UI is not regressing
[09:09] <seb128> Laney, the description is
[09:09] <seb128> there is a string change
[09:09] <Laney> You might think it's worse than the GTK one, but it is not regressing versus what it currently has
[09:09] <Laney> no?
[09:09] <Laney> hey seb128
[09:09] <seb128> hey Laney
[09:09] <seb128> sorry, I'm half back, need to catch a train in a bit
[09:09] <tsimonq2> It is a regression
[09:10] <seb128> Laney, see https://launchpadlibrarian.net/361682891/kde-front-end-before.png vs https://launchpadlibrarian.net/361682873/kde-front-end-after.png
[09:10] <seb128> the substring/description
[09:10] <seb128> I didn't notice it at first either
[09:11] <tsimonq2> Also, why only put one frontend closer to spec?
[09:11] <seb128> otherwise I agree there is no reason we should force people to update the kde frontend when they change the gtk one, but in this case it makes a string used less nice
[09:11] <seb128> tsimonq2, because that spec is our GTK desktop  one
[09:11] <seb128> kubuntu team could have different intend
[09:11] <tsimonq2> Hm. OK.
[09:11] <seb128> like not being interested by minimal desktop
[09:11] <tsimonq2> No, we have the option.
[09:11] <seb128> also you can't force our team to take the cost of maintaining flavors
[09:12] <didrocks> good morning seb128
[09:12] <tsimonq2> That's fine, but why weren't we involved before release team acked?
[09:12] <duflu> Hi seb128
[09:12] <tsimonq2> Kubuntu was an afterthought at best.
[09:13] <Laney> I think the release team said to check with Kubuntu, which is what happened, no?
[09:13] <jibel> Indeed but they should both sync so a change in a flavor doesn't have a negative impact on another flavour
[09:13] <tsimonq2> Laney: I interpreted your comment as an ACK, was that incorrect?
[09:13] <Laney> It was ACK but check with Kubuntu, which is what happened.
[09:13] <acheronuk> not volunteering here, but a brief hack at it this morning: https://i.imgur.com/8ku1e9E.png
[09:14] <Laney> So you weren't afterthoughted.
[09:14] <Laney> You were perithoughted
[09:14] <willcooke> back
[09:15] <tsimonq2> I guess I'm just personally wondering why we weren't involved before the MP was made so we could have had the opportunity to introduce the code.
[09:15] <tsimonq2> I'll accept perithought. :P
[09:15] <tsimonq2> s/personally //
[09:17] <tsimonq2> acheronuk might work on something, but until then, I NACK on the grounds of not having a Qt equivalent there.
[09:19] <Laney> Qt equivalent isn't a fair thing to ask for
[09:19] <Laney> Not making the UX regress is - sorry for not noticing that straight away
[09:20] <tsimonq2> Not from the Desktop Team; I understand that.
[09:20] <tsimonq2> But we should still have the opportunity.
[09:20] <tsimonq2> And I'd argue that it should be done in one upload.
[09:20] <Laney> It can be, but there's no reason it needs to be
[09:21] <tsimonq2> Kubuntu's installer regresses
[09:21] <Laney> Feeling a bit circular now, sorry
[09:21] <tsimonq2> I'd be surprised if the Release Team ACKs despite regressions.
[09:22] <tsimonq2> No problem. I think I've made my point. :)
[09:22] <acheronuk> tsimonq2: I may carry on with it later, but not 100% certain on correctness of what I have done or doing
[09:23]  * didrocks feels that fixing it will take less time than this conversation TBH
[09:23] <tsimonq2> Probably.
[09:24] <tsimonq2> acheronuk: ACK, feel free to share your WIP and I'll be happy to peer review.
[09:26] <acheronuk> ok. jibel jbicha etc, is there a particular reason this needs to be landed before the weekend? I would assume not, and Kubuntu or whoever else can have the weekend to get something sorted?
[09:27] <acheronuk> that is of course unless someone else with more skill feels like kindly knocking it out quickly today
[09:31] <Laney> j_bicha was trying to make UIF
[09:32] <Laney> acheronuk: thx for working on the fix
[09:33] <acheronuk> and UIF came into effect yesterday without this getting in I assume?
[09:33] <Laney> I think notification would have been nice, even if I don't agree we should in principle block on changes on both side
[09:33] <Laney> yes
[09:33] <Laney> it's missed it now
[09:34] <acheronuk> Laney: it would have been nice and collaborative to get a "we are working on these changes, would you like to contribute equivalents for the KDE front end?"
[09:34] <acheronuk> but things do get done in a hurry at times like this
[09:35] <acheronuk> I'll busy most of rest of workday, but can look more tonight
[09:36] <acheronuk> *be busy
[09:36] <jibel> acheronuk, nothing other that giving enough time to translators to update the strings
[09:37] <acheronuk> jibel: ok. so a few extra days will no cause significant issues there? as long as it is just days
[09:40] <jibel> it depends on your definition of "few" :) the translation deadline for Ubiquity is in 3 weeks. It'd be nice to leave as much time as possible to translate and verify the UI
[09:42] <acheronuk> jibel: well as I said, hopefully by Monday. if it takes longer than that I would be (a) very surprised and (b) give it up as a bad job
[09:43] <jibel> acheronuk, Monday is okay, thanks for working on this.
[09:44] <acheronuk> ok :)
[09:46] <seb128> hey didrocks duflu
[09:46] <Laney> a happy ending ... ?
[09:48] <seb128> tsimonq2, not implementing the same new options Ubuntu decide to give (or remove) isn't a regression but a choice
[09:48] <didrocks> if I knew that would have triggered that amount of polemic, I wouldn't have implemented it in the KDE variant at first :(
[09:49] <seb128> acheronuk, tsimonq2, what's the point to delay Ubuntu improvements landing just because other flavors need to catch up? Things should land when ready, not be blocked on "if we can't have our cake you are not geting yours either" reasons
[09:50] <seb128> didrocks, yeah, teaching you for trying to help :)
[09:51] <Laney> think we can probably draw a line now ...
[09:51] <Laney> hugs to one and all
[09:52] <didrocks> yeah! ;)
[09:53] <acheronuk> didrocks: it's very much appreciated that you did
[09:54] <Laney> going to london for the weekend
[09:54] <Laney> just found out it's the oxford / cambridge boat race
[09:54] <Laney> maybe i should go spectate
[09:55] <didrocks> Laney: is it a thing where you sit for 3 hours to wait for all of them passing by you in like… 10s? ;)
[09:55] <Laney> #sport
[09:56] <Laney> probably a huge crowd too
[09:56] <didrocks> yeah
[09:56] <Laney> I saw there is the oxford / cambridge goat race on the same day
[09:56] <Laney> that one might be better
[09:56] <seb128> I'm in Paris atm, next to gare de l'est
[09:56] <seb128> they locked down one side of the station because there is a leftover box outside
[09:56] <Laney> seb128: get to nord, take the eurostar, we'll hang out
[09:56] <seb128> they are having the anti-bomb robot getting ready :)
[09:57] <didrocks> seb128: close your hears when they will make it explode
[09:57] <seb128> Laney, haha, in fact I'm going to Nord but taking the Thalys :p
[09:57] <didrocks> last time at gare de Lyon (in Paris thus :p), it made a lot of noise
[09:57] <seb128> didrocks, thanks, I'm in my hotel some streets away now with some luck they clear it out before I go
[09:58] <didrocks> yeah, you should be fine :)
[10:23] <ackk> tkamppeter, hi, is there anything more I could debug about https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1731417 ?
[10:23] <ubot5> Ubuntu bug 1731417 in hplip (Ubuntu) "Installed network printer removed automatically when turned off" [Undecided,Confirmed]
[10:53] <jbicha> acheronuk: I suggest changing the sidebar title from "Prepare" to "Software" to better match the new page title at
[10:53] <jbicha> https://launchpadlibrarian.net/361682873/kde-front-end-after.png
[10:55] <acheronuk> jbicha: I was using the old vesrion in a live session to quickly test modify. if you changed that title string in your revision/template, I think it will be carried over when I apply the changes on top of yours
[10:56] <acheronuk> if it doesn't, I will change it
[10:57] <jbicha> yeah, GTK+ doesn't use a one-word page title like that so that's a KDE-specific change
[11:04] <willcooke> Laney, jibel - just attached a "no grain" version of the wallpaper.  Now 1.6MB!!! And looks sharper IMO.
[11:04] <willcooke> https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1758089
[11:04] <ubot5> Ubuntu bug 1758089 in ubuntu-wallpapers (Ubuntu) "18.04 default wallpapers" [Undecided,New]
[11:05] <Laney> willcooke: ta duck
[11:08] <amano> didrocks, c-lobrano told me on the Ubuntu community HUB that there was a Mutter toggle to open new windows in the middle of the screen instead of the top left corner. I think that opening in the middle would be much preferable visually. Having the window in the top left by default creates a very dark area there for the Community theme with the dark headerbar and the dark topbar crammed together. And in the very top left corner
[11:11] <didrocks> amano: hum, interesting, mind opening a bug against mutter as a whishlist so that I keep that in mind (and linking here)?
[11:11] <didrocks> they don't open on the top left corner for me, but currently in a multiscreen env
[11:13] <amano> I will open a bug for you :)
[11:14] <didrocks> thx! :)
[11:14] <c-lobrano> amano, didrocks it's center-new-windows under /org/gnome/mutter
[11:15] <c-lobrano> it works with new windows only, I noticed that some apps stay opened in background so position does not change (like nautilus, gnome software, ...)
[11:20] <didrocks> good hint :)
[11:20] <jbicha> interesting, does that work ok for dual-monitors?
[11:21] <jbicha> ricotz: it looks like you added the center-new-windows setting. Do you know why it's not enabled by default?
[11:30] <jbicha> didrocks: I assume you saw https://code.launchpad.net/~jbicha/ubuntu-seeds/minimal-remove-totem/+merge/341921 and have just been busy?
[11:32] <seb128> Thalys first class space at the train station is crap
[11:32] <seb128> like internet, but port filtered, no imap/irc/vpn, welcome to soviet union
[11:41] <didrocks> jbicha: no, I didn't see it, just approved it, are you handling the merge + upload?
[11:42] <jbicha> I can push, yes, it doesn't need an actual ubuntu-meta deb upload, right?
[11:44] <didrocks> jbicha: shouldn't, yeah
[11:44] <jbicha> done
[11:54] <amano_> didrocks, https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1758314
[11:54] <ubot5> Ubuntu bug 1758314 in mutter (Ubuntu) "[Whishlist] Open new windows in the middle of the screen" [Undecided,New]
[11:57] <jibel> willcooke, just 10x smaller ;)
[11:58] <willcooke> :)
[11:58] <jibel> now if you convert to 4k and optimize a bit that should be reasonable
[11:58] <willcooke> You think 4k is enough?  Should be, right?
[12:00] <tkamppeter> ackk, sorry, I have overlooked that you have posted your files in the bug report. I am looking into it now.
[12:00] <ackk> tkamppeter, thanks
[12:01] <willcooke> jibel, uploaded a 4k version to the bug.  Only 652k now \o/
[12:01] <jibel> You think 8k is common?
[12:02] <jibel> it's good, artful was 607K
[12:03] <Nafallo> supported for five years. the question is surely if 8k is enough by then end of 2023? ;-)
[12:03] <didrocks> ackk: thx!
[12:03] <jibel> supported doesn't mean it's common
[12:03] <Nafallo> in 2023... :-)
[12:03] <jibel> we'll SRU a new wallpaper then
[12:04] <Nafallo> now, that makes sense to me indeed :-)
[12:04] <jibel> and since telemetry will give us that info ....
[12:04] <Nafallo> 4k is starting to become common fwiw.
[12:04] <jibel> willcooke, 552K
[12:05] <didrocks> amano_: thx! (still thanks, ackk though ;))
[12:05] <willcooke> jibel, did you crush it some more?
[12:07] <jibel> willcooke, yes with optipng
[12:08] <Laney> I'd usually do all this you know
[12:08] <Laney> but thanks for helping
[12:09] <amano_> jbicha, I saw that the gnome-terminal package carries a debian distro patch to use the scrollbar background colour from the theme. in practice the terminal scrollbar background is always dark for me. That looks ok with the default terminal theme but it looks slightly wrong with bright themes. Can you consider dropping the patch to have a standard scrollbar with the next terminal upload?
[12:09] <jbicha> jibel: have you ever tried zopfli? we use it to compress the pngs for fonts-noto-color-emoji (but it makes the build take a long time)
[12:09] <jbicha> amano_: have you tried building gnome-terminal without the patch?
[12:10] <jibel> jbicha, no I didn't; I'm used to this tool but I'll try
[12:10] <amano_> nope, not yet
[12:10] <ackk> tkamppeter, fwiw it seems that disabling bonjour on the printer might be a workaround for the issue
[12:11] <ackk> although it'd be nice to be able to have it on
[12:11] <mgedmin> oh is that why gnome-terminal's scroollbar has this weird 1px white border that sticks out on Adwaita?
[12:11] <jbicha> amano_: ok, I believe the patch is needed for Ubuntu's default themes
[12:19] <willcooke> jibel, if Laney's happy, want to add it to the bug?
[12:19] <jibel> willcooke, I did
[12:21] <willcooke> oh yeah
[12:21] <willcooke> thanks
[12:30] <jibel> We'd need a marmot for the slideshow of the installer too. Should we reuse this one or design will provide another one?
[12:30] <jibel> willcooke, ^
[12:31] <jibel> usually it's done on release week ...
[12:32] <jibel> the earlier, the less report we'll receive telling it is not the right animal
[12:36] <willcooke> jibel,  I have one
[12:36] <willcooke> I'm waiting on a couple of changes and will upload
[12:40] <jibel> willcooke, okay, thanks
[12:53] <Trevinho> seb128: hey, we need to get this https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1758224 (see commit linked there), want me to do a debdiff or anyone else can handle it?
[12:53] <ubot5> Ubuntu bug 1758224 in gtk+3.0 (Ubuntu) "Scaled gtk theme assets are ignored in HiDPI" [High,Triaged]
[12:55] <seb128> Trevinho, hey, I saw that, I can handle it
[13:02] <Trevinho> seb128: thanks, it's quite bothering... bad thing was that I noticed it, I found the issue, wrote the fix... and then... It was already fixed in the past two weeks, but I didn't git pull in the mean time -_-
[13:08] <seb128> Trevinho, that happens indeed :/
[13:11] <ricotz> jbicha, it was meant to not change the current behaviour and providing this option which is used by e.g. elementaryOS
[13:12] <jbicha> ricotz: have you asked GNOME Design about changing the behavior?
[13:12] <ricotz> jbicha, no
[13:13] <jbicha> ok
[13:13] <ricotz> the goal of that commit was to provide this feature for 3rd party users of libmutter ;)
[13:15] <ackk> tkamppeter, attached avahi outut as requested
[13:17] <jbicha> I'm asking in #gnome-design now…
=== amano_ is now known as amano
=== marco is now known as Guest47662
[13:53] <flocculant> willcooke: any more thoughts on the long time to desktop thing ?
[13:58] <willcooke> flocculant, jibel has been looking at it.  There is a new release of snapd which we think might help.  jibel - did you test it yet?
[13:59] <flocculant> snapd? I guess you're looking at something else then lol
[14:00] <flocculant> timeout's I see on ubuntu and xubuntu are bluetooth issues
[14:00] <flocculant> anyway - what do I know lol
[14:03] <jibel> willcooke, the new version just allows to delay the refresh of snap packages. There is still the issue with decompressing the snaps during boot and several timeouts like bug 1750846 for gsd or bluez like flocculant reported
[14:03] <ubot5> bug 1750846 in gnome-settings-daemon (Ubuntu Bionic) "several g-s-d services are timing out when booting a live session" [High,New] https://launchpad.net/bugs/1750846
[14:07] <flocculant> aah cool - different thing then - I was confused for a bit there :)
[14:07] <flocculant> cheers jibel
[14:37] <kenvandine> translated xdg-user-dirs https://imgur.com/a/8EeUK
[14:37] <kenvandine> woot
[14:38] <kenvandine> using the gedit snap
[14:42] <Laney> nice
[14:42] <Laney> what's the fix?
[14:46] <seb128> back online
[14:53] <kenvandine> https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103
[14:53] <kenvandine> Laney, that's the fix
[14:53] <kenvandine> hey seb128!
[14:53] <kenvandine> translated xdg-user-dirs https://imgur.com/a/8EeUK
[14:54] <jbicha> seb128: just wondering, what IRC client do you use?
[14:54] <Laney> kenvandine: you have permission to read those?
[14:55] <kenvandine> Laney, yes
[14:55] <kenvandine> we didn't in the past
[14:55] <kenvandine> but we do now
[14:56] <seb128> hey kenvandine
[14:56] <seb128> jbicha, xchat-gnome
[14:56] <seb128> jbicha, why?
[14:56] <seb128> kenvandine, nice
[14:57] <jbicha> seb128: LP: #1758163
[14:57] <ubot5> Launchpad bug 1758163 in xchat-gnome (Ubuntu) "Please remove xchat-gnome from Ubuntu (again)" [Undecided,Fix released] https://launchpad.net/bugs/1758163
[14:58] <jbicha> seb128: this is what happens when you're not around ;)
[14:58] <jbicha> have you tried polari?
[14:58] <seb128> jbicha, not this cycle
[14:59] <seb128> I should give it another try, maybe it improved
[15:00] <seb128> jbicha, that bug is a joke, "it is too much of a maintenance overhead"
[15:00] <jbicha> it probably didn't change much recently
[15:00] <seb128> it's not like we had lot of fixing to do on it in recent cycles
[15:00] <jbicha> I thought the hexchat bug was a joke too! :|
[15:01] <seb128> it feels like that has been a reaction to the xchat-gnome removal bug
[15:02] <seb128> but it's a bit ridiculous to kick out a gtk3 client as "unmaintained" and putting forward a gtk2 one as an alternative solution
[15:02] <jbicha> Steve said he'd reaccept xchat-gnome if someone wants to upload it and maintain it https://irclogs.ubuntu.com/2018/03/23/%23ubuntu-devel.html#t03:50
[15:03] <seb128> jbicha, was it a trolling bug or do you have a real motivation to try to clear than one out, out of the stack of old unmaintained craps in universe
[15:03] <mdeslaur> I filed the hexchat bug in an attempt to get someone to finally take on moving it to gtk3
[15:04] <jbicha> well you heard about the xchat removal bug controversy, right? xchat-gnome is pretty similar (presumably in worse shape actually)
[15:04] <seb128> I did read about this one
[15:04] <seb128> anyway, I don't really care either way
[15:04] <seb128> if somebody reupload xchat-gnome good
[15:04] <seb128> otherwise I'm probably going to snap it and use that
[15:05] <jbicha> I like the idea of Snaps for old stuff we don't want in the distro any more
[15:05] <seb128> those removals are ridiculous, there are tons of packages more outdated and less useful than xchat-gnome in  universe
[15:05] <seb128> why not going to try to get those out first...
[15:05] <mdeslaur> well, I want xchat-gnome in the distro, which is why I've been maintaining it in the first place
[15:05] <seb128> wfm
[15:05] <seb128> and good that some people find hexchat good for them
[15:06] <seb128> it doesn't work for me, I find the UI not easy to "read" and none of the available colors/settings make it look clean/easy to me
[15:06] <seb128> while xchat-gnome is
[15:06] <jbicha> I am working on removing packages from Debian (libgnome depends these days). It just takes a long time with Debian processes and "maintainers"
[15:07] <mdeslaur> removing packages that still build and work is a disservice to users
[15:08] <seb128> especially when they work, have users and are not depending on outdated techs we want to get out
[15:08] <seb128> anyway
[15:08] <seb128> don't hate on softwares just because you don't use them :)
[15:08] <seb128> on that note, enough said on the topic for me
[15:13] <jbicha> mdeslaur: packages that have been removed from Debian should have an Ubuntu maintainer to stay in Ubuntu
[15:15]  * mgedmin tried very hard to migrate from the nice xchat-gnome to the promising polari, but in the end switched to irssi because of all the polari problems
[15:16] <juliank> polari looks nice
[15:17] <juliank> mgedmin: I could only setup connection to bouncer with mc-tool because both polari and empathy lacked options...
[15:17] <juliank> I'm thinking about writing a GTK+3 HIG WeeChat relay client
[15:23] <Laney> jbicha: any reason not to merge xdg-user-dirs?
[15:24] <jbicha> Laney: I don't understand what we're doing with translations and maybe that should be pushed upstream
[15:24] <jbicha> but if you want to merge, go for it
[15:26] <Laney> Trevinh_o's got his fix up for sponsoring and that would be one way to get it
[15:26] <Laney> thx
[15:27] <Laney> seb128: do you just download https://translations.launchpad.net/ubuntu/bionic/+source/xdg-user-dirs/+pots/xdg-user-dirs/+export and use `quilt shell' or something to copy it over?
[15:29] <seb128> Laney, yeah, I download, rename the files from somethiong_LO.po to LO.po, copy over and diff -Nru old new basically
[15:29] <seb128> and update LINGUAS to list the new/added locales
[15:30] <seb128> jbicha, we just import the translations from launchpad
=== jbicha_ is now known as jbicha
[15:32]  * Laney makes tea while waiting for the tarball to arrive
[15:33] <jbicha> if we upstream the translations, maybe we could just turn off translations in LP for the package and point translators to https://translationproject.org/domain/xdg-user-dirs.html
[15:36] <seb128> you can argue that for any translations made on launchpad for any source
[15:36] <seb128> we could yes
[15:37] <seb128> but then we loose an ease-to-contribute/easier-integration point from Ubuntu
[15:37] <jbicha> but most packages don't require this manual handling which slows down updates
[15:37] <jbicha> maybe we could do it for Chaotic Camel
[15:39] <seb128> I've no strong opinion
[15:39] <seb128> upstreaming the changes is not easy since we don't speak all the languages to argue of the value/difference
[15:40] <seb128> not easy to decide who between upstream and launchpad translators has the best variant and why
[15:40] <seb128> but we could just decide next cycle to close those and tell translators to report bugs upstream for their improvement
[15:40] <seb128> maybe send upstream new locales translations
[15:40] <seb128> since we have a few of those
[16:10] <Laney> seb128: does https://paste.ubuntu.com/p/jdrrkV8ysk/ look like I did it right?
[16:13] <jibel> Trevinho, this fix for grey item on dark grey background introduced a regression, now I've comboboxes with light grey on light grey
[16:18] <jibel> Trevinho, https://imgur.com/a/uwlL1
[16:18] <jibel> biab
[16:19] <Trevinho> jibel: weird but thanks... I'll add to the list
[16:24] <kenvandine> Trevinho, would you mind taking a look at https://github.com/ubuntu/snapcraft-desktop-helpers/pull/103
[16:24] <Trevinho> ok
[16:24] <kenvandine> Trevinho, thx
[16:24] <Trevinho> oh, that is now available? :-)
[16:24] <kenvandine> Trevinho, yes!
[16:26] <Trevinho> kenvandine: so couple of things...
[16:27] <Trevinho> We should probably add support for moving the data we added in $SNAP_HOME to these locations now, no? Otherwise users might lose track of stuff from within the snap
[16:27] <Trevinho> also.... [ -f ]  is it working now? Since in the past it wasn't enough to check if we had access
[16:27] <Trevinho> as it was gettting false postives
[16:27] <Trevinho> there's a bug somewhere about test not working properly
[16:28] <Trevinho> I had to use a different check (which was... I need to look :D)
[16:28] <kenvandine> i'd be interested in better ways to check :)
[16:30] <Trevinho> kenvandine: in snap shell if you do `test -f /home/$USER/.config/monitors.xml && cat /home/$USER/.config/monitors.xml` it will fail for example
[16:30] <Trevinho> on cat...
[16:30] <Trevinho> so let me look I think I had a branch
[16:30] <kenvandine> ok
[16:31] <Trevinho> bug is https://bugs.launchpad.net/snappy/+bug/1748510
[16:31] <ubot5> Ubuntu bug 1748510 in Snappy "shell's test gives false positive on readability of files" [Undecided,New]
[16:31] <Trevinho> but I didn't post the workaround there mhmhmh
[16:32] <Trevinho> kenvandine: I used this
[16:32] <Trevinho> if (! head -c0 "$XCOMPOSEFILE" &> /dev/null); then ......
[16:33] <Trevinho> that wont' actually read anything but will do an `open()`
[16:34] <Trevinho> kenvandine: also... with such change what will happen is that the XDG_DATA_DIRS will be set relative to $SNAP_HOME (referring to that to $HOME) when you're inside a snap, so it's not enough... Also an user might have set those vars to somewhere that is not readable by snap
[16:34] <Trevinho> So...
[16:35] <Trevinho> You should go through each of them and check if we've acecess
[16:36] <Trevinho> if we have you've to create the dirs that are referred inside the $SNAP_HOME.... Ie. for each XDG_DIR*  that in that file we refer to as $HOME/foobar you've to create the relative $SNAP_HOME/foobar as symlink to the actual location.
[16:37] <Trevinho> because for example qt inside a snap what will try to do  is reading that file, replace $HOME with what is defined as $HOME in that context...
[16:38] <Trevinho> then for dirs that instead are defined as full paths, you need to check access
[16:38] <Trevinho> if those tests fail, you just create the $SNAP_HOME/$XDG_DIR_* and use that
[16:38] <Trevinho> another option
[16:39] <Trevinho> is to read that file...
[16:39] <Trevinho> and then regenerate a new one that points to the same dirs (if possible) but considering that the $HOME is not aymore the user $HOME
[16:40] <Trevinho> this has to be redone everytime we start a snap, though... or check if the file has changed since the last time we regenerated it (better).
[16:40] <Trevinho> as if user changes something this won't be reflected...
[16:40] <Trevinho> So... yeah, finally I think this is the best option :)
[16:41] <Trevinho> sorry thinking at loud voice, but at leasts you can follow (I hope) my mental process
[16:41] <kenvandine> i think so
[16:51] <Trevinho> kenvandine: I think I've added better comments in the review :)=
[16:51] <kenvandine> Trevinho, thanks!
[16:52] <Trevinho> I hope I didn't miss something
=== pstolowski is now known as pstolowski|afk
[17:22] <Laney> ffs
[17:22] <Laney> gnome-keyring is going crazy on my laptop
[17:23] <Laney> ok I don't have the new patches
[17:24] <jbicha> Laney: I had to reboot when gnome-keyring started hogging CPU, I haven't had it again in a few days :(
[17:28] <Laney> jbicha: that was with the current version?
[17:29] <jbicha> yes, did you apt upgrade gnome-keyring today?
[17:29] <Laney> doing it now
[17:29] <Laney> but if you had it, I'm guessing this particular bug is not fixed
[17:29] <Laney> but maybe rebooting will be good to me ...
[17:29] <Laney> I don't have the dbgsyms to get a backtrace and now it's upgraded
[17:33] <Laney> still bad
[17:37] <Trevinho> damn... I've a talk to do tomorrow and still slides to write xD
[17:56] <Laney> works after deleting from seahorse and re-adding
[17:56] <Laney> seb128: I'm just going to upload that xdg-user-dirs thing, sorry if it's buggy - we can fix next week
[17:57]  * Laney makes Trevinho happy
[17:57] <Laney> Trevinho: who's the talk to?
[17:57] <willcooke> happy weekend all.  Good luck Trevinho .
[17:57] <willcooke> London on Monday, won't be around in the morning
[17:58] <Laney> stupid yak shaving meant I didn't get bluetooth debugging info
[17:59] <Laney> I originally just restarted to get pulseaudio being more verbose :(
[18:00] <Laney> anyway I'm off too to watch/not watch the boat race
[18:00] <Laney> laters
=== alan_g is now known as alan_g|EOW
[18:11] <didrocks> enjoy/don't enjoy Laney :)
[18:45] <Trevinho> Laney: https://merge-it.net/
[18:51] <seb128> Laney, sorry you missed me by a few minutes, looks fine to me
[18:52] <seb128> have a nice w.e desktopers