[00:27] <xclaesse[m]> Hi, I'm testing Ubuntu 22.04, one issue I have is my wired networkd device does not appear. Wifi works fine. Is that a known issue? Any workaround possible?
[00:29] <sarnold> xclaesse[m]: this channel is more for development; #ubuntu-next will have more folks familiar with common support needs
[00:29] <sarnold> xclaesse[m]: some kernel modules are commonly stuffed into an 'extra' package
[00:30] <sarnold> xclaesse[m]: it might be worth blindly installing that package, reboot, and see if things get happy
[00:30] <sarnold> apt-cache search linux module extra    might help figure out hte name, I don't know it off-hand
[00:31] <xclaesse[m]> It is installed: linux-modules-extra-5.15.0-23-generic
[00:32] <xclaesse[m]> Thanks for pointing to the other chan, I'll repost :)
[00:35] <sarnold> dang, I hoped for an easy win :)
[05:53] <jibel> Good morning 
[05:53] <oSoMoN> good morning desktoppers
[05:55] <duflu> Hi jibel and oSoMoN 
[05:56] <oSoMoN> hey duflu 
[06:07] <jibel> duflu, is bug 1967901 the only report you saw with qxl ?
[06:07] <ubottu> Bug 1967901 in linux (Ubuntu) "[qxl] Xorg fails to start with 'Screen(s) found, but none have a usable configuration.'" [Undecided, Incomplete] https://launchpad.net/bugs/1967901
[06:07] <jibel> if so it's surprising because on my machine qxl is the default
[06:09] <duflu> jibel, I linked to two other QXL bugs in yours, but they sound different
[06:17] <duflu> jibel, best I can tell the QXL Xorg driver found the qxl kernel driver, loaded, found it was incompatible and then unloaded
[06:47] <didrocks> good morning
[06:48] <jibel> salut didrocks 
[06:53] <didrocks> salut jibel 
[07:15] <tjaalton> checking for qxl_drm.h... no
[07:16] <tjaalton> I think that's why qxl fails
[07:20] <tjaalton> it is detected on debian
[07:20] <tjaalton>         KMS:                      no
[07:20] <tjaalton> so yeah, I'll pull a patch from fedora to fix that..
[07:24] <seb128> goood morning desktopers
[07:24] <seb128> hey tjaalton, how are you?
[07:24] <tjaalton> hi, fine thanks
[07:25] <seb128> tjaalton, do you plan to land the libx11 update before release? or if not should we try to cherrypick some fixes?
[07:25] <tjaalton> seb128: that was the goal yes
[07:25] <tjaalton> there was some regression in 1.7.4 that got quickly fixed and released as 1.7.5
[07:26] <tjaalton> haven't seen any reports on debian since uploading it on sunday, so I guess we're good
[07:26] <seb128> time for a sync then? ;)
[07:26] <tjaalton> yup
[07:27] <tjaalton> 1.7.3 actually fixed some firefox crashers, but there were some regressions that I was waiting for those to get fixed before attempting to bring it in
[07:28] <tjaalton> synced
[07:28] <seb128> let's hope 1.7.5 is in shape then
[07:28] <seb128> thanks :)
[07:28] <tjaalton> uploaded a new xkeyboard-config yesterday
[07:28] <tjaalton> to sid
[07:28] <tjaalton> let's wait for a few days for that
[07:29] <tjaalton> and uploaded some updates for intel opencl stack to experimental, will sync those once they're ready
[07:29] <tjaalton> those are purely universe stuff
[07:32] <tjaalton> also asked the new wacom maintainer to bump the epoch so we could sync the driver, but he's going by the book and requires to open a thread on debian-devel about ...
[07:32] <tjaalton> +it
[07:32] <seb128> :-/
[07:33] <tjaalton> maybe I'll just fakesync it for jammy
[07:34] <seb128> tjaalton, and the mesa/webkit/wayland issue, I did bisect and commented on https://gitlab.freedesktop.org/mesa/mesa/-/issues/6236 , do you have anyone you can try to nag about it?
[07:34] <ubottu> Issue 6236 in mesa/mesa "webkitgtk blank webview with mesa 22 and Intel Comet Lake" [Opened]
[07:34] <tjaalton> I noticed
[07:35] <tjaalton> not sure where to poked, though I did add a comment to the original MR
[07:35] <tjaalton> *poke
[07:35] <didrocks> salut seb128, tjaalton 
[07:35] <tjaalton> yo
[07:36] <seb128> thx
[07:36] <seb128> didrocks, lut, en forme ?
[07:36] <didrocks> ça va, debug de stacktrace de bon matin, et toi ?
[07:36] <seb128> ça va :)
[08:09] <oSoMoN> salut didrocks, jibel, seb128 
[08:27] <seb128> oSoMoN, salut, en forme ?
[08:28] <oSoMoN> seb128, ça va, et toi?
[08:29] <seb128> oSoMoN, ça va !
[08:58] <KGB-2> xdg-desktop-portal-gnome Sebastien Bacher 304097 * commented merge request !2 * https://deb.li/71eE
[09:24] <oSoMoN> Trevinho, I identified the mutter commit that caused the dnd regression in the firefox snap (bug #1964541), I could use some help to figure out exactly why this is causing the regression, and if it's a bug in mutter or something that needs patching in firefox
[09:24] <ubottu> Bug 1964541 in firefox (Ubuntu) "Cannot rearrange Firefox (snap) browser tabs/bookmarks in gnome-shell 42 (Wayland session)" [Medium, Confirmed] https://launchpad.net/bugs/1964541
[09:52] <oSoMoN> Trevinho, note that in the corresponding merge request, I see a comment (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2122#note_1325253) that makes me think the problem might be with mutter: « I agree this is a less trigger-happy variant than that, at the expense of false negatives. »
[09:52] <ubottu> Merge 2122 in GNOME/mutter "core: Change behavior of 'application is alive' checks (motion event counter)" [Merged]
[09:53] <jamesh> Wimpy: I was looking into the auto-connect problems for your Ubuntu Mate snap theme here: https://github.com/snapcore/snapd-desktop-integration/issues/10 -- from the look of it, the snap needs a store assertion to enable auto-connection/greedy plugs
[09:53] <ubottu> Issue 10 in snapcore/snapd-desktop-integration "Doesn't connect interfaces automatically" [Open]
[09:53] <Wimpy> jamesh: o/
[09:54] <Wimpy> jamesh: Is "greedy plugs" what I should be requesting?
[09:54] <jamesh> Wimpy: the usual process for this is  to request the assertion on the forum. You could use https://forum.snapcraft.io/t/auto-connect-and-greedy-plug-behaviour-for-for-gtk-common-themes-and-gtk-theme-traditionalhumanized-snaps/19113?u=jamesh as a template for what to request.
[09:55] <jamesh> Wimpy: we still don't really have solid policy or automatic review for theme snaps, but you seem like a trustworthy fellow
[09:55] <jamesh> :-)
[09:55] <Wimpy> jamesh: Thank for the info. I'll get on that.
[09:55] <Wimpy> fossfreedom: See above. You'll need to do the same for your theme snaps.
[09:57] <fossfreedom> Umm... OK. Feel like a bit of copy paste discourse posting
[09:58] <jamesh> Wimpy: we don't do any manual plug connection when installing the theme snaps, since (a) that bypasses the store's policy, and (b) wouldn't help when you install new app snaps.
[09:59] <jamesh> once the store assertion is available, it should all just work automatically
[10:06] <cnihelton> Hi, everyone!
[10:09] <oSoMoN> hey cnihelton 
[10:16] <Wimpy> jamesh: Any changes required to snapcraft.yaml to support this?
[10:16] <ack> hi, any hints on how I could debug this issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727 ? It's pretty annoying as it randomly happens while working
[10:16] <ubottu> Launchpad bug 1967727 in linux (Ubuntu) "Random screen blanks with 'CPU pipe B FIFO underrun' error" [Undecided, Confirmed]
[10:17] <jamesh> Wimpy: If your theme snap works when you manually connect it to app snaps, then you shouldn't require any more changes
[10:19] <Wimpy> jamesh: OK, manual connection works.
[10:19] <Wimpy> Anything need requesting for the icon snaps?
[10:20] <jamesh> You'd need a similar snap declaration for the icon snaps
[10:20] <Wimpy> Thanks.
[10:20] <Trevinho> oSoMoN: interesting... Let me see 
[10:21] <jamesh> I don't have a specific example of what to request, but it should be fairly obvious from the GTK theme version
[10:23] <Trevinho> oSoMoN: specifically is the 2nd or 1st commit of the MR? 
[10:24] <Wimpy> jamesh: Thank for your help. I'm writing the post now...
[10:24] <oSoMoN> Trevinho, https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2122/diffs?commit_id=26676a829e74859488154cd8c45de1d0b629f3ca
[10:24] <ubottu> Merge 2122 in GNOME/mutter "core: Change behavior of 'application is alive' checks (motion event counter)" [Merged]
[10:25] <oSoMoN> Trevinho, specifically, the changes to src/core/events.c
[10:25] <oSoMoN> (I locally distro-patched mutter to revert these changes (the second hunk), and the issue was gone)
[10:26] <jamesh> Wimpy: awesome! It'll be great to have this ready on the LTS.
[10:27] <Trevinho> oSoMoN: I see, do we have a tinier reproducer than Firefox? As it would be nice to figure out what the app is doing too 
[10:28] <oSoMoN> Trevinho, not much smaller, but I observed that dragging selected text in the gedit snap also doesn't work
[10:29] <Trevinho> Oh indeed helps though 
[10:29] <oSoMoN> gotta reboot to test downgrading a package, back in a moment
[10:29] <fossfreedom> jamesh: I am a little confused... I am looking at the gtk-common-themes snapcraft.yaml on gnome gitlab and I can't see the allow-auto-connection bits ... I want to make sure I have added that correctly for our two snaps I.e. https://github.com/UbuntuBudgie/gtk-theme-pocillo-snap/blob/main/snap/snapcraft.yaml
[10:30] <Trevinho> oSoMoN: will try in a bit, my biggest problem was to get the snaps working in my dev environment 
[10:30] <jamesh> fossfreedom: it's not part of the snapcraft.yaml. You're essentially requesting a special permission from the store, similar to if you wanted your snap to auto-connect to cameras or microphones
[10:31] <jamesh> fossfreedom: in this case, it is permission to have your snap's content shared with snaps asking for gtk-3-themes, icon-themes, etc.
[10:31] <fossfreedom> Ah. OK reverting. And will kind of copy paste your discourse post. Thx.
[10:33] <Wimpy> jamesh: Here's my request. I think it is correct.
[10:33] <Wimpy> https://forum.snapcraft.io/t/auto-connect-and-greedy-plug-behaviour-for-gtk-theme-yaru-mate-and-icon-theme-yaru-mate/29443
[10:33] <Wimpy> fossfreedom: Some bioler plate for you :-) ^
[10:34] <fossfreedom> Cheers :)
[10:34] <jamesh> fossfreedom: in short, there a policy file describing how plugs/slots can be connected, which can be seen by running "snap debug base-declaration"
[10:35] <jamesh> fossfreedom: the store can deliver per-snap overrides for that policy as part of a snap-declaration assertion
[10:37] <Trevinho> oSoMoN: will try to play more with it in a bit, my biggest problem was to get the snaps working in my dev environment 
[10:55] <bittin> good afternoon
[11:03] <oSoMoN> good afternoon bittin 
[12:08] <jbicha> good morning
[12:54] <bdrung> hi, i'll try to fix https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/comments/68 and figured out that there is a discrepancy between the org.gnome.desktop.input-sources sources setting and the gnome keyboard applet. can someone assist there?
[12:54] <ubottu> Launchpad bug 1875062 in ubiquity (Ubuntu Focal) "[20.04] Keyboard layout not enabled immediately during installation when typing username/password" [High, Triaged]
[13:31] <KGB-2> gnome-control-center ubuntu/master a759b86 Sebastien Bacher debian/patches/ubuntu/Allow-tweaking-some-settings-for-Ubuntu-Dock.patch * Use the correct gettext function in the ubuntu panel for context strings * https://deb.li/31ngI
[13:32] <oSoMoN> good morning jbicha 
[14:03] <Trevinho> oSoMoN: while i noticed that gedit dnd is indeed broken it seems to be broken also on unconfined gedit under wayland, isn't it?
[14:05] <oSoMoN> let me check
[14:06] <oSoMoN> Trevinho, not here. dnd of text selection works for /usr/bin/gedit, it doesn't for /snap/bin/gedit
[14:09] <Trevinho> oSoMoN: ok it was consistent for me, but yeah, indeed that line is the gulty one... let me see if I can get the root cause
[14:11] <oSoMoN> cool, thanks for your help on this!
[14:12] <Trevinho> the only thing is that when the app is not confined... if I disable that check. then I get an "hanging dialog"
[14:14] <oSoMoN> right, my "patch" is probably not the right solution, merely a way to point out where the problem originated
[14:14] <Trevinho> sure sure
[14:27] <Trevinho> oSoMoN: lovely... normal gedit running in gdb is not affected, while running outside gdb is....
[14:27] <oSoMoN> that's clearly a timing issue
[14:37] <Trevinho> oSoMoN: yeah, so it seems
[14:43] <Trevinho> oSoMoN: something like this  seems enough, but still would like to get closer to the root cause... as also drag events should keep the window "alive"...
[14:43] <Trevinho> https://www.irccloud.com/pastebin/4mj5YCu4/mutter.diff
[14:46] <Trevinho> oSoMoN: I've the same issue also on unconfined apps in my jhbuild environment though.. just as simple as dnd on nautilus folders... 
[14:49] <seb128> Trevinho, hey, do you need sponsoring for the portal update? I don't think you replied to my msg earlier?
[14:50] <Trevinho> seb128: I saw your comment on the MR, but no questions, was it? :D
[14:50] <Trevinho> seb128: however, yeah please if you can handle that?
[14:50] <Trevinho> given I couldn't upload it would need some external intervention anywahs
[14:50] <Trevinho> anyways*
[14:51] <Trevinho> speaking of it, who should I ping to get those components under the desktop umbrella?
[14:51] <seb128> bdrung, unsure if someone replied but maybe GunnarHj would know about bug #1875062 and input-sources
[14:51] <ubottu> Bug 1875062 in ubiquity (Ubuntu Focal) "[20.04] Keyboard layout not enabled immediately during installation when typing username/password" [High, Triaged] https://launchpad.net/bugs/1875062
[14:52] <seb128> Trevinho, it's a DMB thing which I'm on now so I will figure that out, I also mentioned that in the query earlier when I asked about sponsoring :p
[14:52] <bdrung> seb128, thanks. I haven't got a reply get.
[14:57] <jbicha> seb128: could you look into getting the upload permission packagesets before the jammy release? as a test case, gnome-screenshot should switch to the ubuntu-budgie packageset
[14:57] <seb128> jbicha, do you have any guidance on how the refresh is done? like how did you figure out where screenshot would go?
[14:59] <jbicha> I never directly managed the packagesets when I did a term years ago on the DMB but you can try https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase#Packagesets
[14:59] <KGB-2> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366211 * running (extract-source: running; piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; build: created)
[14:59] <jbicha> seeded-in-ubuntu gnome-screenshot    says only Ubuntu Budgie ships it now
[15:00] <seb128> jbicha, but it's in universe so does it need to be in a set?
[15:00] <seb128> or is anything on a flavor added to the corresponding set?
[15:01] <seb128> I should start by reading that page before asking more questions right?
[15:01] <jbicha> yes, because David is not a MOTU yet :)
[15:01] <seb128> he should :p
[15:01] <jbicha> fossfreedom: ^
[15:04] <KGB-2> xdg-desktop-portal-gnome signed tags 062ef55 Sebastien Bacher ubuntu/42.0.1-1ubuntu2 * xdg-desktop-portal-gnome Debian release 42.0.1-1ubuntu2 * https://deb.li/XzO2
[15:05] <KGB-2> xdg-desktop-portal-gnome ubuntu/master 2ad7fc6 Sebastien Bacher debian/changelog * upload to Ubuntu * https://deb.li/iknmC
[15:05] <KGB-0> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366213 * pending (blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; extract-source: pending; piuparts: created; build: created)
[15:05] <KGB-0> xdg-desktop-portal-gnome pipeline Sebastien Bacher 366213 * running (extract-source: running; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; piuparts: created; build: created)
[15:05] <seb128> Trevinho, ^
[15:05] <GunnarHj> bdrung: I saw your comments and your ongoing investigation sounds really interesting to me. Sounds like we will soon be able to address the root cause of that long standing issue.
[15:06] <Trevinho> seb128: lovely, thanks!
[15:06] <GunnarHj> bdrung: As regards your question, I'm not sure I'm qualified to help, but bug #1956916 comes to mind.
[15:06] <ubottu> Bug 1956916 in gnome-control-center (Ubuntu) "Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session" [High, Confirmed] https://launchpad.net/bugs/1956916
[15:06] <seb128> GunnarHj, hey, the ubiquity changes got merged and uploaded :-) also I fixed the gcc translation issue
[15:07] <GunnarHj> seb128: Great, you have earned a gold star. :)
[15:07] <Trevinho> oSoMoN: AH! I think I found where we're stopping the drag to happen...
[15:10] <GunnarHj> bdrung: What I mean is that there are issues where gnome-shell and XKB don't play well together. May or may not be relevant.
[15:37] <bdrung> GunnarHj, if this problem is related to wayland, I can test if it can be reproduced on X11.
[15:39] <GunnarHj> bdrung: Yes, knowing that might be useful.
[15:40] <GunnarHj> bdrung: Btw, let's continue our conversation on the bug report.
[15:41] <bdrung> the login screen of the ubuntu live image does not provide a way to change to X11. do i need to install some package for it?
[15:42] <bdrung> GunnarHj, i would prefer to continue the conversation here and only put stuff in the ticket that is relevant (to avoid clutter the ticket with noise)
[15:53] <Trevinho> oSoMoN: ok this seems likely the proper solution.. .even though the serial isn't changing on drags, so could be avoided at times... but still. More to come in a GNOME Issue
[15:53] <Trevinho> https://www.irccloud.com/pastebin/qdw2DfCJ/foo.diff
[15:54] <oSoMoN> great!
[15:54] <Trevinho> would probably nice to understand who is calling back meta_display_pong_for_serial on the snap implementation to `meta_display_pong_for_serial` but...
[15:55] <Trevinho> oSoMoN: give a check if that works there too please :)
[15:55] <oSoMoN> Trevinho, will do in a moment
[15:56] <Trevinho> upstream would probably need more cleanups (like wrapping stuff up more, but that's the point imho)
[15:58] <GunnarHj> bdrung: Ok, that works too. :)
[16:00] <bdrung> GunnarHj, something really fishy is going on. i tried the live system without my gsetting patch. now "gsettings get org.gnome.desktop.input-sources sources" returns "[('xkb', 'us'), ('xkb', 'au'), ('xkb', 'cm'), ('xkb', 'gb')]".
[16:05] <oSoMoN> Trevinho, I applied your patch instead of mine and rebuilt mutter packages here, installed locally and this appears to fix the bug as intended, at least dragging tabs in the firefox snap works. Good job!
[16:05] <oSoMoN> ship it!
[16:06] <Trevinho> ehe, well upstream work will be slower :)
[16:10] <GunnarHj> bdrung: Yeah, that's odd, but please note that the bug isn't really about the live session, but about the behavior in the installer. You wouldn't see all those input sources at first login if you completed the installation, so investigating details in the live session may be a dead end.
[16:23] <bdrung> GunnarHj, i have to revise my last comment in the bug report. "gsettings set org.gnome.desktop.input-sources sources" is called once. but the result is still the same: the gnome keyboard applet in the live session does not show the new entries.
[16:23] <bdrung> btw, is "gsettings set org.gnome.desktop.input-sources sources" the correct way to change the keyboard layout?
[16:32] <GunnarHj> bdrung: That's equivalent to manipulating the list of input sources in Settings. But I think it changes the effective input source only if the command means that the previously effective input source is removed through the command.
[16:34] <GunnarHj> bdrung: So, yes, you shouldn't expect that only *adding* an entry changes the effective layout.
[16:54] <bdrung> GunnarHj, it is probably not required for the installer to change the layout. the layout should just be added to the list and gnome should notice the keyboard layout change done via setxkbmap
[16:57] <GunnarHj> bdrung: But using setxkbmap is not sufficient to make GNOME recognize the layout.
[16:57] <bdrung> GunnarHj, what needs to be done to make GNOME recognise the layout?
[16:58] <bdrung> "gsettings set org.gnome.desktop.input-sources sources" followed by setxkbmap?
[16:58] <GunnarHj> bdrung: Consider this example, assuming this list to start with:
[16:58] <GunnarHj> $ gsettings get org.gnome.desktop.input-sources sources
[16:58] <GunnarHj> [('xkb', 'de'), ('xkb', 'se'), ('xkb', 'us')]
[16:58] <GunnarHj> And the effective layout, i.e. the layout shown in the input source indicator, is "de". Then if I do:
[16:58] <GunnarHj> $ gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'se'), ('xkb', 'us')]"
[16:58] <GunnarHj> the effective layout is instantly changed to Swedish. But the reason for that is that I effectively removed the German layout.
[17:01] <GunnarHj> bdrung: Now a stupid question: Is ubiquity really working in a GNOME DE environment?
[17:03] <bdrung> I am using the jammy-desktop-amd64.iso for testing - this is a GNOME live system. is there a command to shows the session details?
[17:05] <GunnarHj> bdrung: The live session is indeed GNOME, but I'm talking about the installer itself. Assume that you click "Install Ubuntu" at the welcome screen and never enter a live session. Which kind of environment are you in then?
[17:05] <bdrung> GunnarHj, how about a video call? then I can show it to you hands on.
[17:05] <bdrung> GunnarHj, all my tests are done in the GNOME session by clicking "Try Ubuntu".
[17:08] <GunnarHj> bdrung: And I'm not confident that the live session is representative for the environment used for the installation phase. But I'm not sure; I'm not really familiar with the ubiquity code.
[17:09] <GunnarHj> bdrung: Sure, a video call may help.
[17:14] <KGB-2> gnome-nettool upstream/latest fb75227 Jeremy Bicha * pushed 273 commits (first 5 follow) * https://deb.li/iWwMl
[17:14] <KGB-2> gnome-nettool upstream/latest 38eb075 Daniel Korostil po/uk.po * Update Ukrainian translation * https://deb.li/iM4I
[17:14] <KGB-2> gnome-nettool upstream/latest dce0cc3 Yuri Chornoivan help/uk/uk.po * Update Ukrainian translation * https://deb.li/3QDzA
[17:14] <KGB-2> gnome-nettool upstream/latest 314526f AsciiWolf pixmaps/icons/scalable/apps/gnome-nettool.svg * Fix scalable icon * https://deb.li/3VIs0
[17:15] <KGB-2> gnome-nettool upstream/latest d54dd27 Germán Poo-Caamaño pixmaps/icons/scalable/apps/gnome-nettool.svg * Merge branch 'icon-fix' into 'master' * https://deb.li/DJjz
[17:15] <KGB-2> gnome-nettool upstream/latest 730fada Jwtiyar Nariman po/ LINGUAS ckb.po * Add Central Kurdish translation * https://deb.li/3Ruvs
[17:15] <KGB-2> gnome-nettool pristine-tar 7fa463e Jeremy Bicha gnome-nettool_42.0.orig.tar.xz.delta gnome-nettool_42.0.orig.tar.xz.id * pristine-tar data for gnome-nettool_42.0.orig.tar.xz * https://deb.li/T8Rv
[17:15] <bdrung> GunnarHj, I sent you a PM for the video call.
[17:31] <Trevinho> oSoMoN: so... apparently, it would needed to bump gtk in the firefox snap... or well, fix the issue in gtk for 20.04... quite annoying, so for now I suppose we'll bring that patch in the distro only
[17:33] <oSoMoN> Trevinho, ack, I saw your comment
[17:33] <oSoMoN> we'll need a fix in time for 22.04, as the issue is very visible with the firefox snap
[17:34] <Trevinho> yeah, I'll defintely include something in mutter, but meanwhile please get the platform snap ready for that too
[17:34] <oSoMoN> so a mutter distro-patch for 22.04 sounds like the easiest and quickest solution for now, and then backport that gtk fix to 20.04 and have it included in the gnome platform snap
[17:34] <Trevinho> yeah, fair enough
[17:36] <Trevinho> also I had a local libgdk version that was older than that... due why i was affected in my jhbuild... Which was lucky :)
[18:14] <seb128> Trevinho, oSoMoN, the platform snaps builds gtk from source and doesn't use the focal deb
[18:15] <oSoMoN> ah, that makes it easier to cherry-pick a patch, that's good news
[18:15] <seb128> yes, it's easy to get one in stable before release I think
[20:04] <KGB-2> libadwaita signed tags bb19d92 Jeremy Bicha ubuntu/1.1.0-1ubuntu2 * libadwaita-1 Debian release 1.1.0-1ubuntu2 * https://deb.li/3Z7ZM
[20:04] <KGB-2> libadwaita pipeline Jeremy Bicha 366301 * running (extract-source: running; piuparts: created; blhc: created; autopkgtest: created; lintian: created; reprotest: created; test-crossbuild-arm64: created; test-build-all: created; test-build-any: created; build source: created; build i386: created; build: created)
[20:20] <KGB-0> libadwaita pipeline Jeremy Bicha 366301 * [15 minutes and 14 seconds] failed (piuparts: success; reprotest: failed; autopkgtest: success; test-build-any: success; test-build-all: success; lintian: failed; test-crossbuild-arm64: failed; blhc: success; build i386: success; build: success; build source: success; extract-source: success)