[00:06] <KGB-2> mutter ubuntu/master c1afb90 Marco Trevisan * pushed 145 commits (first 5 follow) * https://deb.li/rMAg
[00:06] <KGB-2> mutter ubuntu/master adbe09a Olivier Fourdan src/compositor/meta-window-actor-x11.c * window-actor/x11: Cache the frame bounds * https://deb.li/3IZhl
[00:06] <KGB-2> mutter ubuntu/master dbecb93 Laurent Bigonville src/compositor/compositor.c * compositor: Only include meta-window-actor-wayland.h when building with wayland * https://deb.li/XOix
[00:06] <KGB-2> mutter ubuntu/master 2cc8061 Olivier Fourdan src/core/keybindings.c * keybindings: Mask out the reserved modifiers mask * https://deb.li/ikJcE
[00:06] <KGB-2> mutter ubuntu/master b80b465 Jonas Dreßler clutter/clutter/cogl/clutter-stage-cogl.c * clutter/stage-cogl: Fix painting the redraw clip with the damage region * https://deb.li/tOjn
[00:06] <KGB-2> mutter ubuntu/master 858c12e Jonas Ådahl clutter/clutter/ clutter-paint-context-private.h clutter-paint-context.c clutter-stage.c * clutter/paint-context: Add paint flag * https://deb.li/3rJ87
[03:21] <callmepk> good morning
[04:04] <duflu> Hi callmepk 
[04:19] <jibel> good morning 
[04:25] <duflu> Hi jibel 
[04:40] <callmepk> Hi duflu and jibel 
[06:15] <didrocks> good morning
[06:24] <duflu> Morning didrocks 
[06:27] <didrocks> hey duflu 
[06:53] <oSoMoN> good morning desktoppers
[06:54] <duflu> Hi oSoMoN 
[06:54] <oSoMoN> hey duflu 
[06:58] <didrocks> hey oSoMoN, duflu 
[06:59] <didrocks> not enough sleep, already told hey to duflu :)
[06:59] <duflu> didrocks, same so I did not notice :D
[06:59] <didrocks> heh
[08:01] <Laney> hey hey!
[08:04] <GunnarHj> Good morning all!
[08:04] <GunnarHj> I pushed a tiny g-c-c commit to both groovy and focal branches but without uploading, assuming that more will come also on focal. Suppose that's a reasonable assumption.
[08:13] <duflu> Hi Laney and GunnarHj 
[08:14] <GunnarHj> Hello duflu
[08:17] <seb128> hey Laney, GunnarHj, duflu
[08:17] <seb128> lut didrocks, oSoMoN
[08:17] <seb128> how is everyone?
[08:17] <seb128> GunnarHj, yes, good assumption, and there is already a SRU uploaded so best to wait for that one to clear up
[08:18] <seb128> we have quite some fixing to do on g-c-c so I expect several SRUs before .1
[08:18] <didrocks> salut seb128, hey Laney, GunnarHj 
[08:19] <didrocks> ça va :) et toi ?
[08:19] <seb128> ça va bien :)
[08:19] <seb128> didrocks, pas trop fatigué? 
[08:19] <GunnarHj> didrocks: Här är det fina fisken.
[08:20] <Laney> hey duflu seb128 didrocks GunnarHj 
[08:20] <didrocks> seb128: non, c’est pas trop moi qui est le plus à plaindre pour l’instant :)
[08:20] <seb128> :-)
[08:20] <Laney> sunny day
[08:20] <Laney> planted sweet peas out this morning
[08:20] <Laney> is good
[08:20] <Laney> unless they get eaten by a slug
[08:20] <seb128> nice
[08:21] <seb128> I should try to do things in the morning but atm I struggle to get out of bed and then it's work time
[08:21] <Laney> yeah bed is a tempting place a lot of the time /o\
[08:28] <RAOF> You just need a small child to climb in at 4am. That makes the bed less appealing!
[08:33] <GunnarHj> sil2100: I think I saw a notification about a reply from you, but I don't see it in HexChat.
[08:41] <oSoMoN> good morning Laney, GunnarHj, seb128, didrocks 
[08:44] <ricotz> good morning desktopers
[08:54] <Laney> hey oSoMoN 
[09:08] <seb128> Laney, so yeah, disabling fractional scaling with 125% selected (single screen, intel, on the xps) immediatly change the resolution, but it's weird, it 'underscale' for me
[09:08] <Laney> yep
[09:08] <seb128> UI is smaller than if I select 100%
[09:08] <Laney> it's buggy after you do that too
[09:08] <seb128> ?!
[09:09] <Laney> I would guess that is two bugs to file
[09:10] <duflu> If you file any then please add a screenshot so I can quickly tell if one is a duplicate
[09:10] <duflu> We have lots of bugs
[09:10] <seb128> Laney, yes, the 'unscale too low' is a shell side issue, I get the same if I reset the gsettings key with g-c-c closed
[09:11] <duflu> seb128, do you mean shrunken?
[09:11] <seb128> so it's not g-c-c just going to apply a random mode because it gets confused by the list changing
[09:11] <seb128> duflu, yes, scaling is lower than 100%
[09:12] <seb128> resolution is 3072x1728 according to xrandr
[09:12] <duflu> seb128, yeah I see that sometimes. The root window size is left bigger than the monitor resolution. Sometimes it occurs in panning mode though, so the desktop appears cropped
[09:12] <seb128> where the panel/normal screen is 1920x1080
[09:12] <duflu> Yep
[09:13] <seb128> do we have a bug tracking that already?
[09:13] <duflu> seb128, kind of... the same bug but in cropped mode, not scaled
[09:13] <seb128> do you have the bug number?
[09:13] <duflu> seb128, bug 1875285
[09:14] <Laney> let's rls tag a few things to look at later
[09:14] <seb128> poor marco :p
[09:15] <seb128> but yeah
[09:15] <Laney> that bug looks a bit different
[09:15] <Laney> robert can take the g-c-c bits I guess
[09:15] <duflu> seb128, in theory you can adjust that to anything:  xrandr --fb WIDTHxHEIGHT
[09:15] <seb128> right
[09:15] <duflu> seb128, yes that bug happens on Intel too so is a good one for Marco
[09:21] <seb128> jamesh, Laney, robert_ancell, weekly status reminder
[09:21] <Laney> I did it?!?!!?
[09:21] <seb128> Trevinho, as well
[09:21] <seb128> Laney, https://discourse.ubuntu.com/t/desktop-team-updates-monday-4th-may-2020/15890 ?
[09:22] <Laney> weird
[09:22] <Laney> hopefully discourse saved it
[09:22] <duflu> It usually does
[09:22] <seb128> usually it does
[09:22] <duflu> Does usually it
[09:22] <seb128> it does usually
[09:23] <duflu> two more
[09:23] <seb128> :)
[09:24] <Laney> yes there it was
[09:27] <Laney> Prelude Data.List> map (concat . intersperse " ") . permutations $ words "yes there it was"
[09:27] <Laney> ["yes there it was","there yes it was","it there yes was","there it yes was","it yes there was","yes it there was","was it there yes","it was there yes","it there was yes","was there it yes","there was it yes","there it was yes","was yes there it","yes was there it","yes there was it","was there yes it","there was yes it","there yes was it","was yes it there","yes was it there","yes it was 
[09:27] <Laney> there","was it yes there","it was yes there","it yes ...
[09:27] <Laney> ... was there"]
[09:30] <Laney> https://paste.ubuntu.com/p/CVT9Hw9Rtv/
[09:30] <Laney> productised
[09:31] <seb128> :p
[09:31] <seb128> Laney, s/plymouth/accountsservice :)
[09:32] <Laney> yeah
[09:32] <seb128> Laney, that's powerful script magic the permutation thing :p
[09:32] <Laney> haskell man
[09:32] <Laney> it's the way
[09:33] <seb128> :)
[09:35] <Laney> I'll file the instant apply bug if nobody else did
[09:38] <seb128> Laney, please do, thx
[09:46] <Laney> if someone else do the small size one, and maybe duflu can nominate one/some for 'nvidia is borked' issues
[09:47] <duflu> Laney, I've been triaging them for hours, days
[09:47] <duflu> But there's no bug for the shrinkage issue yet
[09:48] <duflu> Perhaps I'll just swap out my video cards again and make dinner
[09:48] <Laney> that's OK, we can file it
[09:48] <Laney> but I think we should also have a bug rls-ff-incoming tagged for things like 'you get a blank screen when selecting scaling sometimes'
[09:50] <seb128> Laney, we rls-ff-notfixed https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403 at the time but I think we have enough confirmation now than we should revisit
[09:50] <Laney> think so
[09:51] <Laney> so maybe put that one back to incoming
[09:52] <duflu> It's the second hottest one... https://bugs.launchpad.net/ubuntu/+bugs?field.tag=xrandr-scaling&orderby=-heat&start=0
[09:54] <Laney> I wonder if I saw that 200% one too
[09:54] <Laney> it did feel big to me
[09:55] <sil2100> GunnarHj: did you get my last messages?
[09:55] <duflu> Laney what you see at that time is actually the cropping bug 1875285
[09:56] <Laney> ah, could be
[09:56] <Laney> sounds worth tagging too
[09:57] <Laney> Filing the shrinky one also
[09:57] <Laney> then I'll get back to other things
[09:59] <duflu> The shrinking/cropping issue happens on Intel too, sometimes. And I suspect may be part of the cause of the other issues. So would be great for Marco to look at
[10:00]  * duflu returns to Intel graphics and feels relieved 
[10:03] <Laney> yeah seb128 said he saw it on non-nvidia
[10:05] <Laney> done bug #1876894
[10:23] <GunnarHj> sil2
[10:24] <GunnarHj> sil2100: Yes, and replied.
[10:29] <Trevinho> mh, that shrinking I think just happens as the driver doesn't really scale down
[10:51] <seb128> Trevinho, hey! it's weird though, that happens if you turn off fractional scaling in gsettings, not if you see scaling to 100% in settings
[12:17] <seb128> Trevinho, weekly status update? ;)
[13:00] <Trevinho> seb128: yeah sorry I already wrote a draft then I wanted to finish the gjs update
[13:01] <seb128> Trevinho, no worry, what is block the gnome-shell update? (at least to groovy), Debian got those uploaded last week, is there anything blocking us?
[13:02] <Trevinho> seb128: I wanted to handle few fixes on the xrandr patch too and while testing I had an issue with the 2-in-1 I've here, so... this lead to some more fixes.
[13:03] <seb128> Trevinho, I would recommend to not do too much, there are some important fixes in .2 users are waiting for, best to do what is ready and another round a week later
[13:03] <seb128> Trevinho, you are doing your typical 'be side tracked by fixing one little bit more before claiming being done'
[13:04] <seb128> Trevinho, often you end up being still fixing one more issue a week later when you do that :)
[13:04] <Trevinho> sure sure, but some are easy enough while redoing uploads might take some extra time
[13:04] <Trevinho> well the one I fixed was easy enough until i didn't start testing that lead to 1.5k new lines xD 
[13:05] <Trevinho> but that's done at least, but since I wasn't sure it was a regression it took some more time initially
[13:05] <seb128> lol
[13:05] <seb128> don't rewrite gnome-shell in a SRU patch!
[13:05] <Trevinho> no, no... not adding either to the SRU for now
[13:05] <Trevinho> waiting for upstream ack first
[13:05] <seb128> do you think there any chance your fixes address some of the nvidia scaling problems?
[13:05] <Trevinho> for that
[13:06] <Trevinho> while for the xrandr could be, but a bit hard to figure
[13:06] <Trevinho> without actual testing :/
[13:30] <seb128> oh oh oh
[13:30] <seb128> it's meeting time!
[13:30] <kenvandine> indeed!
[13:30] <seb128> #startmeeting Desktop Team Weekly Meeting - 2020-05-05
[13:30] <meetingology> Meeting started Tue May  5 13:30:43 2020 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:31] <seb128> Roll call:  didrocks, duflu (out), heather, jamesh (out), jibel, kenvandine, laney, marcustomlinson (out), oSoMoN, tkamppeter, trevinho, robert_ancell (out), callmepk
[13:31] <Trevinho> o/
[13:31] <kenvandine> o/
[13:31] <callmepk> o/
[13:31] <oSoMoN> o/
[13:31] <marcustomlinson> \o
[13:31] <hellsworth> o/
[13:31] <Laney> |O|
[13:31] <seb128> wooot, let's get started
[13:32] <seb128> #topic rls-bb-bug
[13:33] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:33] <seb128> no desktop entry
[13:33] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:33] <seb128> everything assigned, wooot
[13:34] <seb128> I'm going to skip -ee from now on, I don't think it makes sense to accept new things for that serie at this point
[13:34] <kenvandine> makes sense
[13:34] <seb128> we can still on special cases but probably doesn't need to be in the meeting
[13:34] <seb128> #topic rls-ff-bug
[13:34] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[13:35] <seb128> there are some 'noise' item (incomplete/already discussed&assigned), I will skip those
[13:35] <seb128> bug #1876891
[13:36] <seb128> I think it's an issue we should fix but I wouldn't consider it as rls target
[13:36] <seb128> it's a pretty specific case to pick a scaled value and then turn scaling off while it's selected
[13:37] <seb128> and the impact is limited, scaling is wrong but you still have a display so it's easy enough to change the value in the UI
[13:37] <Laney> is it?
[13:37] <Laney> pick scaling, decide you don't want it, later want it again
[13:37] <seb128> let's say we didn't get any report so far
[13:37] <Laney> at that point you get the old value before you picked whatever you want at the new point
[13:37] <seb128> I'm not discussing it's a bug, agreed it's not a nice behaviour
[13:38] <seb128> it just didn't get reported/mentioned by other users yet and is easy to recover from
[13:38] <seb128> anyway, that's my reasoning for giving a -1
[13:38] <hellsworth> it seems like it should be fixed but maybe not super urgent
[13:38] <seb128> I'm happy to be overulled
[13:38] <Laney> here's what I think
[13:38] <Laney> it's crap behaviour
[13:38] <Trevinho> the problem is that we can't know the actual scaling value before activating it
[13:38] <kenvandine> i'd say we want it fixed for .1
[13:38] <Laney> and it's crap bugs that *we* introduced in a distro patch
[13:38] <Laney> we should have a high bar for quality there
[13:38] <Trevinho> so not really possible to do this... The only option is not to scale by default probably
[13:39] <Laney> so I think we should be holding ourselves to a high standard here and accepting things like this
[13:39] <seb128> Trevinho, well, from the settings the control could be smart enough to change the value to an int one before doing the gsettings toggling
[13:39] <hellsworth> Laney makes a good argument.. i'm switching sides
[13:40] <seb128> still, we don't have data showing that users noticed/that it's a thing people do
[13:40] <Trevinho> seb128: mh, *could* but it goes through the DBusAPI so need to be consequent, so may still cause some visual lag
[13:40] <seb128> anyway
[13:40] <seb128> vote?
[13:40] <seb128> -1 from me
[13:40] <kenvandine> +1 from me
[13:40] <Trevinho> by default it would pick an integer value though
[13:40] <Trevinho> only if the user changed it previously it's a fractional, and imho this is fine
[13:41] <hellsworth> +1
[13:41] <Trevinho> -1
[13:41] <Laney> +1
[13:41] <oSoMoN> +1
[13:41] <seb128> k, nominating
[13:41] <seb128> kenvandine, do you think Robert can take on it since he added the UI?
[13:41] <seb128> and it's g-c-c
[13:41] <kenvandine> he's got other time sensitive stuff
[13:42] <kenvandine> but it might be a quick fix
[13:42] <seb128> unsure what would be a nice behaviour there
[13:42] <Trevinho> not sure, unless we want 3 clicks to get it active
[13:42] <Laney> I don't get why you have to fiddle with the value mutter knows about, it's just not connecting directly to the gsetting
[13:42] <seb128> maybe simply disabling the off switch if a scaled value is selected?
[13:42] <Trevinho> like -> toggle -> apply -> set scaling -> done
[13:42] <Laney> it's completely fine to remember the previous setting, just don't apply it until they press apply
[13:43] <Laney> so you can have a chance to change it
[13:43] <Trevinho> no way unless we implement changing monitor.xml from g-c-c
[13:43] <Trevinho> which isn't something we want
[13:43] <seb128> maybe should just disable the toggle if a scaled value is selected?
[13:44] <Trevinho> only option is to add other dbus APIs which I decided not to do not to move away from upstream 
[13:44] <Laney> discuss after
[13:44] <seb128> right
[13:44] <oSoMoN> yeah
[13:44] <Laney> hopefully without the 'no way' kind of things
[13:45] <seb128> bug #1876894
[13:45] <seb128> I vote +1 to this one
[13:46] <Trevinho> +1
[13:46] <hellsworth> +1
[13:47] <Trevinho> ah, wait... MIGHT be WONTFIX for some things unfortnuately... as it depends on their toolkits
[13:47] <Trevinho> like it's for qt (telegram) and sometimes firefox
[13:47] <seb128> hum?
[13:47] <Trevinho> same is already when you switch from 100% to 200%
[13:47] <seb128> for me it's 
[13:47] <seb128>  start session
[13:47] <Laney> it works if you first pick 100% and then press apply
[13:47] <seb128> -enable scaling, 125%
[13:47] <seb128> disable the key
[13:47] <seb128> and g-c-c is underscale
[13:48] <seb128> resolution is 3200 in xrandr
[13:48] <seb128> instead of 1900
[13:48] <seb128> pick 100% and it's fine
[13:48] <Trevinho> ah ok, that's fine then. g-c-c issue thouhg.
[13:48] <Trevinho> not mutter, I can look at that.
[13:49] <seb128> not g-c-c
[13:50] <seb128> anyway, let's talk about this after the meeting
[13:50] <Trevinho> k
[13:50] <RoyK> I have an old laptop that hasn't been update for a while and I wanted to update it now, finding it's running 19.04 and nothing seems to want to update. Do I have to change repos?
[13:51] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[13:51] <seb128> bug #1866088
[13:51] <oSoMoN> RoyK, we're in the middle of a team meeting here, hold on for a few minutes if you don't mind
[13:52] <seb128> that's fix commited
[13:52] <seb128> assigning to Marco, it's pending review in the focal queue
[13:52] <RoyK> oSoMoN: np
[13:53] <seb128> bug #1876334	
[13:55] <seb128> jibel, you nominated that one, should be assigned to you or Didier?
[13:56] <seb128> assuming they will :p
[13:56] <seb128> #topic rls-gg-bug
[13:56] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-incoming-bug-tasks.html
[13:57] <seb128> no new bug on that list, either discussed or things to clean out as I said earlier
[13:57] <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-gg-tracking-bug-tasks.html
[13:57] <seb128> fix commited ones
[13:57] <seb128> #topic update_excuses_by_team.html#desktop-packages
[13:58] <seb128> Laney, want to do that one or should I? (I review the list earlier so I can do if you are not on top of it atm)
[13:58] <seb128> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[13:58] <Laney> I didn't look, feel free
[13:58] <seb128> k
[13:58] <seb128> fonts-teluguvijayam: needs a MIR
[13:58] <seb128> I will do that, standard/easy font one
[13:59] <seb128> some libreoffice issues, hopefully only usual armhf retries, some are queued let's see next week if it's still an issue
[13:59] <seb128> libutempter needs investigating, I was going to poke at it
[13:59] <seb128> gdk-pixbuf is failing but the tests are new / just been added in Debian
[13:59] <seb128> the failures don't happen in Debian thoguh
[13:59] <seb128> anyone interested to poke at that?
[14:00] <seb128> libsoxr is a bit puzzling, it failed in focal and now again, failing to find pkg-config on i386, but it has one successful try on groovy which I don't explain
[14:01] <seb128> it looks like it's not set up for crossbuild, dunno how it worked that one time :/
[14:01] <oSoMoN> gdk-pixbuf: can do once I'm done with the firefox release and other things
[14:01] <seb128> oSoMoN, thanks
[14:01] <seb128> I will trello cards thing for reminder
[14:02] <seb128> libsoxr would be nice to make cross build friendly if anyone want to poke, but meanwhile I mp a hint to reset the result on i386 I think
[14:02] <seb128> it's not a regression
[14:02] <seb128> a
[14:02] <seb128> and that's it for proposed migration
[14:02] <seb128> #topic AOB
[14:02] <seb128> any other topic?
[14:03] <Laney> some items were mentioned on one of the incoming lists which we keep skipping
[14:03] <Laney> anything we can do to get those off?
[14:05] <seb128> yes, I will get them off for next week, I had delayed assuming the .2 upload would clear off the list for us
[14:05] <seb128> but that is taking time, we should probably just accept nomination for things pending upload to get them off the list
[14:05] <Laney> cool thanks!
[14:06] <seb128> np!
[14:06] <Laney> yeah I usually nominate and assign when uploading SRUs
[14:06] <Laney> for all the bugs fixed in that
[14:06] <seb128> right
[14:06] <seb128> thanks for pointing it out :)
[14:06] <seb128> anything else?
[14:06] <Laney> not from me
[14:07] <seb128> (sorry, got some ping/side discussion going which created a bit of delay on the meeting)
[14:07] <seb128> thanks everyone!
[14:07] <seb128> #endmeeting
[14:07] <meetingology> Meeting ended Tue May  5 14:07:10 2020 UTC.  
[14:07] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-05-05-13.30.moin.txt
[14:07] <hellsworth> thanks
[14:07] <oSoMoN> thanks
[14:07] <oSoMoN> that's unfortunate, I was going to answer to RoyK's question…
[14:08] <Laney> seb128: I don't see your merge proposal to the hints, link?
[14:08] <Laney> Trevinho: soooooo are you saying that the UI is constructed from values that mutter gives you, and that these are different depending on whether that feature is enabled?
[14:09] <Trevinho> Laney: yep
[14:09] <Laney> sad
[14:09] <Trevinho> also might be enabled then you change hw or screen and it changes...
[14:09] <Laney> it's like keyed by some identifier?
[14:10] <seb128> Laney, sorry, I've it in a tab, going to submit in a minute
[14:15] <Trevinho> Laney: what you mean? These values are provided once you tell mutter you support fractional values... So, in such cases it gives you a list of valid resolutions/scales and based on this we build the UI. so it would be impossible for g-c-c to guess them
[14:15] <Laney> right
[14:15] <Trevinho> also because you could change resolution and set other scaling
[14:16] <Trevinho> one option, that I suggested at the sprint, was to just keep this key on all the times, and then we have another UI option to show or not non-scaling
[14:16] <Trevinho> that would fix also the other issue
[14:16] <Trevinho> but i think it may be too late for this
[14:16] <Laney> if you have the key on, and pick an integer value, is it shortcutting out all of the fractional code?
[14:17] <Trevinho> yep
[14:17] <Laney> that might be one way to do it then
[14:17] <Trevinho> not all, but basically it's behaving the same
[14:17] <Laney> if no performance impact *cough duflu*
[14:18] <Trevinho> nope because in such case would just use scaling of 1 of the X11 side and X in the widget side of things
[14:19] <parclytaxel> Hello?
[14:19] <Laney> it sounds like to fix it in the other way you'd need a new mode peeking api
[14:19] <Laney> which does indeed sound like more divergence than we want ideally
[14:20] <parclytaxel> I've been pointed here by an Inkscape developer
[14:20] <parclytaxel> Inkscape 1.0's been released, and that other developer said I should ask you when you are going to package Inkscape for Ubuntu
[14:21] <parclytaxel> Are you planning to do it in the next few days? I'm not seeing 1.0 in the native repository, although it's available as a snap
[14:21] <kenvandine> parclytaxel: it is already
[14:21] <kenvandine>   latest/stable:    1.0-5b275a35d9-2020-05-03     2020-05-04 (7601) 148MB -
[14:21] <kenvandine> the snap
[14:21] <seb128> parclytaxel, install the snap
[14:21] <kenvandine> published by inkscape
[14:22] <parclytaxel> I already have the snap. But it isn't really "native", like Firefox
[14:22] <seb128> you mean?
[14:22] <kenvandine> native?  
[14:22] <seb128> the deb is udpated in the new Ubuntu serie, https://launchpad.net/ubuntu/+source/inkscape/1.0~rc1-4
[14:22] <parclytaxel> The snap doesn't use Ubuntu fonts for the dialogs and such
[14:22] <kenvandine> snap is the preferred way
[14:22] <seb128> unsure if we will SRU to focal, I expect it's too much change for a SRU
[14:22] <parclytaxel> SRU?
[14:23] <seb128> stable release update
[14:23] <seb128> e.g for focal
[14:23] <seb128> stable updates usually include fixes, not big changes
[14:23] <parclytaxel> The 0.92.5 version that is in the standard repos does use Ubuntu fonts
[14:23] <seb128> that's why snaps are great, you can get newer apps if you wish :)
[14:23] <seb128> that sounds like a bug in the snap to fix
[14:23] <kenvandine> parclytaxel: that's a bug then... 
[14:24] <parclytaxel> but the other Inkscape dev said "we don't control the Ubuntu repos"
[14:24] <kenvandine> right, they don't
[14:24] <seb128> Laney, Trevinho, if you guys come to a conclusion, can you comment on the bug? I'm unsure that's a bug for Robert to fix or what we technically do with it at this point
[14:24] <kenvandine> parclytaxel: but they do the snap
[14:25] <kenvandine> parclytaxel: the snap is published by the inkscape team 
[14:25] <kenvandine> parclytaxel: can you please file a bug at https://gitlab.com/inkscape/inkscape/-/issues
[14:25] <Trevinho> seb128: ideally would be -> migrate users with that key enabled to another key, and keep that on all the times.
[14:25] <kenvandine> parclytaxel: and if you give me the link i can probably fix it myself
[14:26] <parclytaxel> alright, I'm going to file a bug
[14:26] <seb128> Trevinho, I doubt you will see Robert do that work
[14:26] <Trevinho> Laney: you think to something like that as well?
[14:26] <kenvandine> parclytaxel: thanks!
[14:27] <seb128> jibel, I've assigned you the zsys bug since you targetted it, feel free to reassign to Didier or delete the target if those are better resolution
[14:27] <Trevinho> I'm ok to take it, probably worth to decide if we want migrate all or just who enabled already
[14:27] <seb128> Trevinho, please don't get distracted from the .2 updates, the dock fixes and the nvidia scaling (if you can help duflu)
[14:27] <seb128> then you can have a look to that if you wish
[14:28] <Trevinho> yeah, I have already enough meat so not a super prio for me :)
[14:28] <Trevinho> so if someone takes it I'm fine
[14:28] <seb128> well it's rls accepted now...
[14:28] <seb128> but yeah, let's do in priority order
[14:29] <Laney> Trevinho: why another key? can stop g-c-c ever removing that from the list, and set the mode at the ui level instead no?
[14:29] <Laney> like disable becomes queue a change to 100%
[14:29] <Laney> and filter the values, and enable becomes unfilter the values
[14:30] <Trevinho> Laney: how do you know whether is active at startup?
[14:30] <Laney> first startup?
[14:32] <Trevinho> Laney: ok, I see what you mean
[14:32] <Trevinho> so in order to make apply work yes can be an option
[14:32] <Laney> ah, was writing some pseudocode but ok :p
[14:34] <Trevinho> so, should be fine... we just queue a revert back to the suggested integer when disabling the toggle
[14:36] <Laney> https://paste.ubuntu.com/p/PXVTjQj592/
[14:37] <Laney> also, agreed it could come after the other rls bugs
[14:38] <Trevinho> Laney: I would have just one case though, when you enable and it was enabled already set to something non-100 it would set it immediately, no?
[14:39] <Trevinho> ah, ok well if we reset no. that's ok
[14:41] <Laney> :>
[14:43] <kenvandine> parclytaxel: i just tested and i'm definitely getting the ubuntu font in the inkscape dialogs
[14:44] <parclytaxel> kenvandine: I'm still typing out my bug report. While yes, there are instances of the Ubuntu font in most places, the bottom status bar does not use it
[14:44] <parclytaxel> I will show you the link when I have submitted it
[14:44] <kenvandine> ok
[14:45] <kenvandine> please include a screenshot
[14:45] <kenvandine> my both status bar looks right
[14:50] <parclytaxel> kenvandine: here you go https://gitlab.com/inkscape/inbox/-/issues/2659
[14:54] <parclytaxel> you got it kenvandine?
[14:55] <kenvandine> parclytaxel: just a minute
[14:58] <seb128> Laney, https://code.launchpad.net/~seb128/britney/libsoxr-reset-version/+merge/383423 , sorry took me a bit to get back to it
[14:59] <Laney> thx!
[14:59] <parclytaxel> this actually looks like a decent IRC channel
[15:00] <seb128> parclytaxel, :)
[15:01] <Laney> don't have the energy to merge as
[15:01]  * Laney cherry picks
[15:02] <parclytaxel> (decent in relation to #ubuntu - that channel is flooded with one-timers)
[15:03] <parclytaxel> lemme reboot my system because I've done quite some package installing and uninstalling