[01:25] <pieq> Morning!
[01:48] <duflu> Morning pieq 
[04:37] <KGB-2> gnome-shell signed tags c0ed44d Marco Trevisan ubuntu/3.38.4-1ubuntu2 * gnome-shell Debian release 3.38.4-1ubuntu2 * https://deb.li/3deuc
[04:37] <KGB-2> gnome-shell ubuntu/master cdbc545 Marco Trevisan (Treviño) debian/patches/ series keyboard-Fix-suggestions-box.patch * debian/patches: Fix suggestions box actor population in non-latin languages * https://deb.li/uRmC
[04:37] <KGB-2> gnome-shell ubuntu/master e043fd9 Marco Trevisan (Treviño) debian/patches/ gdm-Count-fingerprint-authentication-failures-in-fail-cou.patch series authPrompt-Handle-Escape-key-to-cancel-ongoing-verificati.patch gdm-Limit-verification-cancellations-to-be-conform-to-all.patch * debian/patches: Enable to use Escape to cancel auth requests (with li
[04:37] <KGB-2> GNOMEmits) * https://deb.li/ipoQG
[04:38] <KGB-2> gnome-shell ubuntu/master 482447f Marco Trevisan (Treviño) debian/patches/ (12 files in 2 dirs) * debian/patches: Refresh * https://deb.li/WRsl
[04:38] <KGB-2> gnome-shell ubuntu/master 335a3bf Marco Trevisan (Treviño) debian/changelog * Update changelog * https://deb.li/3ZoFI
[04:38] <KGB-2> gnome-shell ubuntu/master 16798f0 Marco Trevisan (Treviño) debian/changelog * Finalise changelog * https://deb.li/AmUE
[04:47] <KGB-2> mutter signed tags 2a4d669 Marco Trevisan ubuntu/3.38.4-1ubuntu2 * mutter Debian release 3.38.4-1ubuntu2 * https://deb.li/fpnD
[04:47] <KGB-2> mutter ubuntu/master 02aaf06 Marco Trevisan (Treviño) debian/patches/61-mutter.rules-Enable-KMS-modifiers-for-Raspberry-P.patch * debian/patches: Refresh * https://deb.li/3YRdz
[04:47] <KGB-2> mutter ubuntu/master 50eea03 Marco Trevisan (Treviño) debian/patches/ (6 files) * debian/patches: Backport workspace fixes from upstream gnome-3-38 branch * https://deb.li/34l7R
[04:47] <KGB-2> mutter ubuntu/master 783aa1b Marco Trevisan (Treviño) debian/patches/ series build-Use-Xwayland-pkg-config-if-available.patch xwayland-Check-for-listenfd-option.patch * debian/patches: Use -listenfd to invoke XWayland if available * https://deb.li/ijeVv
[04:47] <KGB-2> mutter ubuntu/master b08c52f Marco Trevisan (Treviño) debian/changelog * Update changelog * https://deb.li/iRNn
[04:48] <KGB-2> mutter ubuntu/master cee5908 Marco Trevisan (Treviño) debian/changelog * Finalise changelog * https://deb.li/32oP7
[04:58] <KGB-2> gnome-shell-extension-appindicator signed tags 4ca65f6 Marco Trevisan ubuntu/33.1-0ubuntu0.20.04.2 * gnome-shell-extension-appindicator Debian release 33.1-0ubuntu0.20.04.2 * https://deb.li/3rtMl
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 6872544 Marco Trevisan * pushed 6 commits (first 5 follow) * https://deb.li/3VpmF
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 9ba7357 Marco Trevisan (Treviño) debian/patches/ series Register-the-StatusNotifierWatcher-as-soon-as-possible.patch * debian/patches: Register the StatusNotifierWatcher as soon as possible * https://deb.li/D43i
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 12654eb Marco Trevisan (Treviño) debian/patches/ series util-Properly-call-logger-static-method.patch * debian/patches: Ensure we call proper method during logging * https://deb.li/3RRJh
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 909a1e0 Marco Trevisan (Treviño) debian/patches/ series indicatorStatusIcon-Handle-scroll-events-on-label-too-not.patch * debian/patches: Handle scroll events on indicator label * https://deb.li/TlK2
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 75d4baf Marco Trevisan (Treviño) debian/patches/ series statusNotifierItem-Emit-signals-about-removed-items-on-de.patch statusNotifierWatcher-Emit-the-uniqueId-when-emitting-Un-.patch * https://deb.li/i3eaC
[04:59] <KGB-2> debian/patches: Emit expected signals / arguments when (un)registering indicators
[04:59] <KGB-2> gnome-shell-extension-appindicator ubuntu/focal 79ab819 Marco Trevisan (Treviño) debian/changelog * Update changelog * https://deb.li/QlRg
[05:00] <Trevinho> RAOF: I've-reuploaded  gnome-shell-extension-appindicator to focal ^
[05:01] <RAOF> 🎉
[06:32] <oSoMoN> good morning desktoppers
[07:15] <duflu> Morning oSoMoN 
[07:16] <marcustomlinson> morning oSoMoN & duflu
[07:16] <duflu> Hi marcustomlinson 
[07:19] <didrocks> good morning
[07:19] <jamesh> hi oSoMoN, duflu, marcustomlinson, didrocks 
[07:19] <duflu> Hi jamesh 
[07:19] <duflu> and morning didrocks 
[07:19] <marcustomlinson> hey jamesh & didrocks
[07:20] <cpaelzer> Hi Desktop people o/ - I seem to have gnome-keyring-daemon and kdewallt5 fight over https://specifications.freedesktop.org/secret-service/latest/
[07:20] <cpaelzer> maybe one of you can help me to resolve the following situation
[07:21] <cpaelzer> I'm mostly on gnome (normal 20.04) these days but use a few (nostalgic) kde apps - those pull in  libkf5wallet-bin as a dependency
[07:21] <cpaelzer> now I see both running /usr/bin/gnome-keyring-daemon as well as /usr/bin/kwalletd5
[07:21] <cpaelzer> what I see is that an app using e.g. python-keyring gets values from gnome-keyring (which is what I want) if an entry is in there
[07:22] <cpaelzer> but if no entry is in gnome-keyring it wants to create a new stroage, and that spins up kdewallet
[07:22] <cpaelzer> I've checked the key stores and found that gnome-keyring has various entries (good) and kdewallet is completely empty (also good)
[07:22] <cpaelzer> I'd now want to just shut up kdewallet and have only gnome-keyring to answer to the secretstorage requetss
[07:23] <cpaelzer> uninstalling won't work as then it removes the KDE apps I'd want to use
[07:23] <cpaelzer> killing kdewallet5 only makes it respawn on the dbus request
[07:24] <cpaelzer> What would be the way to configure my environment so that dbus only activates and asks gnome-keyring ?
[07:25] <didrocks> hey jamesh, dufl, marcustomlinson and cpaelzer 
[07:27] <cpaelzer> If I check org.freedesktop.Secret in d-feet I see that the pid of gnome-keyring-daemon is backing that dbus endpoint - so how/why is it even bothering with kdewallet :-/
[07:29] <marcustomlinson> sounds like kde apps being naughty and poking kdewallet some other way
[07:29] <marcustomlinson> what if you just add your secrets to both wallets
[07:29] <cpaelzer> marcustomlinson: doesn't seem like other poking, kwallet5 spawns on use of python3 keyrings
[07:29] <cpaelzer> and then I see the dbus-daemon start it
[07:30] <cpaelzer> dbus-daemon[9697]: [session uid=1000 pid=9697] Activating service name='org.kde.kwalletd5' requested by ':1.7449' (uid=1000 pid=39984 comm="python3 /home/paelzer/bin/lp-test-ppa ppa:ci-train" label="unconfined")
[07:30] <cpaelzer> adding the secrets to both will be the fallback, but I must admit I want to understand what is going on :-)
[07:40] <didrocks> it would be interesting to see the returned value of check_service_availability() in secretstorage/__init__.py to ensure it’s on
[07:41] <didrocks> I do see it loading all backends, but I don’t see where the priority, where multiple endpoints are available, is defined
[07:42] <didrocks> ah, it’s def _detect_backend(limit=None):
[07:43] <didrocks> if you force PYTHON_KEYRING_BACKEND to "keyring.backends.SecretService.Keyring" (I guess?) what happens?
[07:43] <cpaelzer> I think I tried this (but will do so again to be sure) but the problem is that both (gnome keyring and kwallet5) implement that backend
[07:45] <didrocks> kwallet implements KeyringBackend, both from what are see, and so, you have 2 backends:
[07:45] <didrocks> keyring.backends.kwallet.DBusKeyring -> kwallet
[07:45] <didrocks> keyring.backends.SecretService.Keyring -> GNOME secret
[07:45] <didrocks> if I’m correct, I don’t know that code :)
[07:45] <cpaelzer> awesome, let me try ...
[07:45] <didrocks> the weird part is that without the env variable or config file, the order is using the max(all_priorities)
[07:46] <didrocks> GNOME one is 5
[07:46] <cpaelzer> didrocks: that worked!
[07:46] <didrocks>         if "KDE" in os.getenv("XDG_CURRENT_DESKTOP", "").split(":"):
[07:46] <didrocks>             return 5.1
[07:46] <didrocks>         return 4.9
[07:46] <cpaelzer> it still starts kwallet5, but I see the entry added to gnome-keyring and work from there on
[07:46] <didrocks> and so, on GNOME env you should have the GNOME one by default :/
[07:46] <didrocks> cpaelzer: yeah, it seems it’s pinging it to see if it’s available when loading all backend
[07:46] <didrocks> so it will always be started from what I see
[07:46] <cpaelzer> makes sense
[07:46] <didrocks> great that it works, but still, there is a bug
[07:46] <cpaelzer> having another process isn't a problem
[07:47] <cpaelzer> but I don't see how kwallet got perference in my case then
[07:47] <didrocks> let’s rule out the config first
[07:47] <cpaelzer> let me check os.getenv("XDG_CURRENT_DESKTOP
[07:47] <didrocks> do you have a keyringrc.cfg file?
[07:47] <cpaelzer> >>> os.getenv("XDG_CURRENT_DESKTOP")
[07:47] <cpaelzer> 'ubuntu:GNOME'
[07:47] <didrocks> yeah, expected thus
[07:48] <didrocks> keyring_cfg = os.path.join(platform.config_root(), filename), whatever platform.config_root() is :p
[07:48] <cpaelzer> didrocks: now that you asked me to set keyring.backends.SecretService.Keyring I have a ~/.local/share/python_keyring/keyringrc.cfg - I didn't have one before
[07:48] <didrocks> interesting
[07:48] <didrocks> so you won’t need the env variable anymore
[07:48] <didrocks> try still deleting that file and let’s see the automagic priorities maybe?
[07:49] <cpaelzer> when the file is deleted I'm back at where I was - it will ask kwallet
[07:49] <didrocks> can you print the returned value of def priority() in SecretService.py?
[07:50] <didrocks> and while you are at it, the priority from kwallet.py?
[07:50] <cpaelzer> one question I've found that "if any keystore has the key:value it uses this" - only when "key:value is not found" then for creation of a new store it iwll pick kwallet
[07:50] <didrocks> ah, it may iterates over stores
[07:50] <didrocks> and the last one is used for the new value?
[07:51] <cpaelzer> yeah and "if found, return this"
[07:51] <cpaelzer> but the prio counts when creating a new one
[07:51] <didrocks> yeah, but the correct behaviour should be "still iterates over all of them, none found -> store in first"
[07:51] <didrocks> well, at least, sounds sensible to me
[07:52] <jamesh> didrocks: fyi, this was the snapd polkit design stuff I was working on: https://forum.snapcraft.io/t/proposal-add-polkit-and-polkit-agent-interfaces-to-snapd/23876?u=jamesh -- might be useful if you ever need to snap any of the polkit-using deamons you're working on
[07:53] <didrocks> jamesh: will definitively have a look! Thanks for the link
[07:53] <cpaelzer> didrocks: I'll look at the returned priorities and let you know
[07:54] <didrocks> cpaelzer: thanks :) 
[07:54]  * didrocks goes back to Go :)
[07:55] <cpaelzer> SECRET PRIO 5
[07:55] <cpaelzer> KDE PRIO 4.9
[07:55] <cpaelzer> didrocks: so as expected KDE<GNOME
[07:55] <jamesh> does kwallet not implement SecretService these days?
[07:56] <jamesh> (one of the spec developers is a KWallet developer)
[07:56] <didrocks> cpaelzer: yeah, I guess the issue is, as you told, on unknown key, iterating over all of them and storing in the last found if nothing matches… (could worth an upstream bug)
[07:57] <cpaelzer> didrocks: could you tell me in which project you'd expect that to be filed?
[07:57] <didrocks> jamesh: at least, on our python3- binding, it’s using the dedicated bus address
[07:58] <didrocks> cpaelzer: I would say to the python3-keyring binding (it sems to be https://github.com/jaraco/keyring)
[07:58] <jamesh> didrocks: I wonder if it even needs to?
[07:58] <didrocks> seems*
[07:58] <didrocks> jamesh: the python binding may be out of date though and maybe that’s the only guilty part?
[08:00] <jamesh> perhaps
[08:03] <Laney> sup
[08:03] <didrocks> hey Laney 
[08:06] <duflu> o/ Laney
[08:10] <seb128> goood morning desktopers
[08:15] <duflu> Hi seb128 
[08:15] <seb128> hey duflu , how are you?
[08:16] <duflu> seb128, pleasantly average. You? Also do you want to join the Pi meeting in 14 minutes?
[08:16] <seb128> duflu, I'm alright, had a solid night for a change! I could join if you think I would be useful there?
[08:17] <seb128> is there any agenda?
[08:17] <duflu> seb128, no agenda and actually I don't contribute in half the meetings. So maybe don't worry
[08:17] <seb128> feel free to add me as optional to those
[08:17] <didrocks> hey seb128 
[08:17] <seb128> lut didrocks, comment ça va ?
[08:18] <didrocks> ça va bien, et toi ?
[08:19] <Laney> hey didrocks duflu seb128 
[08:19] <Laney> happy final freeze day
[08:19] <seb128> is it alright? wooot, I didn't realize!
[08:19] <seb128> where did the cycle go?
[08:22] <Laney> on looking after kids and having a cold :p
[08:23] <cpaelzer> didrocks: case already exists https://github.com/jaraco/keyring/issues/496
[08:26] <cpaelzer> didrocks: FYI for the next one that asks, there is a report on backends and prios
[08:26] <cpaelzer> $ python -m keyring --list-backends
[08:26] <cpaelzer> keyring.backends.SecretService.Keyring (priority: 5)
[08:26] <cpaelzer> keyring.backends.kwallet.DBusKeyring (priority: 4.9)
[08:26] <cpaelzer> keyring.backends.chainer.ChainerBackend (priority: 10)
[08:26] <cpaelzer> keyring.backends.fail.Keyring (priority: 0)
[08:27] <didrocks> yeah, so clearly what we expect under that environment
[08:27] <cpaelzer> indeed
[08:33] <seb128> oSoMoN, so webkitgtk migrated without the portal depends, weird one...
[09:03] <waveform> duflu, if I can come up with a solid reproduction case for the embedded-browser-window-tearing thing is there a particular package that would best to file a bug against?
[09:04] <duflu> waveform, depends on which browser and whether the bug is local to mutter/gnome-shell.
[09:04] <duflu> waveform, if you log a bug against 'xorg' like the rest of the world does then I will see it <eyes roll>
[09:06] <waveform> duflu, hmm - I'm assuming it's a browser given it's the body of the help window (which I assume is just some embedded html renderer thingy), but I can't say I know what it actually is -- anyway, I'll let you know if I come up with something useful -- and thanks for the discussion on the call just now -- most enlightening!
[09:06] <duflu> waveform, a screenshot, photo or video should be enough to direct me
[09:09]  * duflu bets the problem is a software buffer tearing locally (GTK3)
[09:09] <waveform> duflu, that I can certainly do -- this is the "Lights Off" game help after clicking on the "Basics" link: https://imgur.com/a/JexAdDf
[09:09] <duflu> Oh that's not tearing. I would class that under corruption :O
[09:10] <duflu> Maybe a bad stride or unexpected tiling format
[09:10] <duflu> waveform, Wayland session?
[09:10] <waveform> the initial page (with all the links) works absolutely fine, but always seems to break after clicking a link
[09:10] <waveform> yup, wayland session
[09:11] <waveform> (can screenshot the settings/about page if you'd like but it does state "Wayland" under there)
[09:11] <duflu> waveform, yeah it looks like I just need to add a new pixel format to the list of supported formats that use modifiers/tiling
[09:12] <duflu> waveform, I will investigate and hopefully fix it, just need a bug ID
[09:13] <waveform> okay, I'll open one and ping you with the link -- would mutter be right for this?
[09:13] <duflu> waveform, yes. But before you do, I should ask if you have enabled the kms-modifiers option manually yet?
[09:14] <waveform> yup, gsettings get org.gnome.mutter experimental-features returns ['kms-modifiers']
[09:14] <duflu> log out and in again?
[09:14] <waveform> okay, just a mo
[09:14] <duflu> If it still happens after that then yes a new mutter bug please
[09:16] <oSoMoN> seb128, weird indeed, but good that it migrated. 
[09:17] <waveform> yup, still happening -- ooh, just found another place where it happens (was just wondering where else embedded browsers might be used and the "Google" option under settings / online accounts displays the same issue). Anyway, I'll open a bug under mutter - thanks!
[09:17] <duflu> waveform, thanks. Yes I thought only needing one new format was overly optimistic
[09:27] <waveform> duflu, filed: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1924251
[09:28] <duflu> Fun. Thanks waveform 
[09:40] <seb128> duflu, I'm going to do a bluez upload to get that keyboard pairing segfault fix in before freeze today
[09:40] <duflu> seb128, thanks. I wasn't going to push it but it sounds helpful for sure
[09:41] <duflu> seb128, it's in the git hirsute branch
[09:41] <duflu> in case you didn't notice yet
[09:41] <seb128> I did notice but thanks :)
[09:42] <seb128> duflu, though you have a released revision in there that didn't get uploaded and I was sort of arguing against reviewing it
[09:42] <seb128> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792
[09:42] <duflu> seb128, no problem... I am experienced at rewriting git history
[09:42] <duflu> seb128, should I remove that?
[09:43] <seb128> k, I will just upload the segfault fix for now
[09:43] <seb128> I don't think the postinst change is appropriate at this point, it has risk for little benefit
[09:43] <duflu> seb128, whatever is easiest. I can resync git tomorrow
[09:43] <seb128> k, let's do that
[09:43] <seb128> I will upload and let you rewrite the history
[09:43] <seb128> thanks
[09:44] <duflu> There's no need to delete/rewrite history so long as the eventual tagged revision is accurate. I can just revert the bit we don't release
[09:44] <seb128> ack
[09:45] <duflu> That's why there is no new tag yet
[11:10] <pstolowski> luna: hi, could you please point me at the fix you mentioned in https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1922293 ?
[11:10] <ubot3> Launchpad bug 1922293 in snapd (Ubuntu) "Snaps appear broken on 21.04 Beta with ZFS" [High, Fix Released]
[14:01] <Laney> don't like all this delta we're stacking up in shell/mutter 😬
[14:18] <sil2100> seb128: hey! I see that you last updated the yelp package - is it latest up-to-date with all translations and such for release?
[14:56] <hellsworth> good morning desktopers
[15:16] <marcustomlinson> hey hellsworth
[15:16] <hellsworth> hi there marcustomlinson 
[15:24] <Wimpress> Hello desktoppers o/
[15:25] <Wimpress> How's the release shaping up? :)
[15:29] <hellsworth> hi there Wimpress !
[15:29] <hellsworth> (i don't feel qualified to respond on the state of the release but seems fine to me)
[16:35] <KGB-0> gdm ubuntu/master d67c469 Marco Trevisan * pushed 10 commits (first 5 follow) * https://deb.li/3e6oF
[16:35] <KGB-0> gdm ubuntu/master a8879b8 Marco Trevisan (Treviño) debian/changelog * debian/changelog: Remove bad entry meant to be in ubuntu side only * https://deb.li/3c3U0
[16:36] <KGB-0> gdm ubuntu/master b120a0d Marco Trevisan (Treviño) debian/ gdm3.gdm-smartcard-pkcs11-exclusive.pam gdm3.gdm-smartcard-sssd-exclusive.pam gdm3.gdm-smartcard-sssd-or-password.pam * debian/gdm3.gdm-smartcard-*: Do not set user_readenv=1 in pam_env.so * https://deb.li/3FLpc
[16:36] <KGB-0> gdm ubuntu/master 90e71bd Marco Trevisan (Treviño) debian/patches/ series display-factory-Correctly-return-from-idle-callback.patch * debian/patches: Correctly return from idle callback * https://deb.li/2qCI
[16:36] <KGB-0> gdm ubuntu/master c3ad5bd Marco Trevisan (Treviño) debian/ gdm3.gdm-smartcard-pkcs11-exclusive.pam gdm3.gdm-smartcard-sssd-exclusive.pam gdm3.gdm-smartcard-sssd-or-password.pam * debian/gdm3.gdm-smartcard-*: Ignore invalid user errors on pam_succeed_if.so * https://deb.li/3h6MA
[16:36] <KGB-0> gdm ubuntu/master d32be2e Marco Trevisan (Treviño) debian/ gdm3.gdm-smartcard-pkcs11-exclusive.pam gdm3.gdm-smartcard-sssd-exclusive.pam gdm3.gdm-smartcard-sssd-or-password.pam * debian/gdm3.gdm-smartcard-*: Check for /nologin only when an user is defined * https://deb.li/8aGe
[17:17] <KGB-2> gdm ubuntu/master 71e4985 Iain Lane debian/changelog * Finalise changelog * https://deb.li/3VWAn
[22:39] <KGB-2> glib tags f28c5a1 Simon McVittie upstream/2.68.1 * Upstream version 2.68.1 * https://deb.li/NmfM
[22:39] <KGB-2> glib upstream/latest ef83cad Simon McVittie * pushed 19 commits * https://deb.li/3zmZU
[22:39] <KGB-2> glib pristine-tar 1f984a4 Simon McVittie glib2.0_2.68.1.orig.tar.xz.delta glib2.0_2.68.1.orig.tar.xz.id * pristine-tar data for glib2.0_2.68.1.orig.tar.xz * https://deb.li/33L4n