| 27 May 2025 |
 uep | these days i'm not sure anything would use xwayland, and I'd like to know about it if it did, but I haven't disabled it | 08:55:15 |
| uep | not even for x11 forwarding that I recall using in a long time, mostly waypipe is fine | 08:56:47 |
 Grimmauld (any/all) | I run sway with a custom tmux-inspired window switcher. Hitting tab gives me all the into on window/workspace/display, including whether it runs xwayland or xdg_shell. These days steam is the only thing running xwayland. | 09:03:14 |
| Grimmauld (any/all) | And freecad, by default - needs freecad-qt6 or freecad-wayland... | 09:04:01 |
 jasi 🏳️⚧️ | Isn't Nvidia one of the main reasons for people still on Xorg nowadays? | 15:55:20 |
| jasi 🏳️⚧️ | There's no real data on this either so 🥲 | 15:55:46 |
 SigmaSquadron | a11y is also a big reason afaik. | 16:45:33 |
| jasi 🏳️⚧️ | In reply to @sigmasquadron:matrix.org
a11y is also a big reason afaik. Yes, that too, but that's a desktop-agnostic issue, not just related to GNOME | 17:26:23 |
| jasi 🏳️⚧️ | I think DIY distributions like NixOS should still offer the xorg session until it's fully deprecated in upstream. | 17:28:24 |
| jasi 🏳️⚧️ | It also allows for nixpkgs to alert users of GNOME xorg session removal | 17:28:59 |
| jasi 🏳️⚧️ | Since afaik the release notes for 25.05 do not mention this so nixpkgs would be rug-pulling users who do use the xorg session if it were to happen in 25.11 | 17:31:59 |
| jasi 🏳️⚧️ | I also believe that plasma 6 still allows users to explicitly select the xorg session. | 17:32:48 |
| jasi 🏳️⚧️ | That's just my thoughts | 17:34:06 |
 Alyssa Ross | I don't believe the release notes are expected to predict every breaking change that will happen in the following release. That's what that release's notes are for. | 17:34:14 |
| SigmaSquadron | In reply to @normalcea:matrix.org
I also believe that plasma 6 still allows users to explicitly select the xorg session. since plasma 6.4, that's only possible if kwin-x11 is installed, otherwise the session is broken. | 17:34:30 |
| SigmaSquadron | but it's still installed by default until upstream KDE tells distros to stop shipping it, which will only happen in Plasma 7. | 17:35:22 |
| jasi 🏳️⚧️ | In reply to @sigmasquadron:matrix.org
since plasma 6.4, that's only possible if kwin-x11 is installed, otherwise the session is broken. I see | 17:35:52 |
|  matrixrooms.info mod bot (does NOT read/send messages and/or invites; used for checking reported rooms) joined the room. | 20:02:13 |
| 28 May 2025 |
 Andrew | Good news: I finally faced this issue again. Bad news: idk which extension it is: burn-my-windows, compiz-windows-effect. | 16:07:56 |
| Andrew | I also don't know if there are any other ones that are bad. | 16:18:30 |
| Andrew | * I also don't know if there are any other ones that are bad. But at least I got something after all this time. | 16:18:44 |
 K900 | Well turn them off one by one and see? | 16:34:09 |
 Leonardo Santiago | hi | 17:19:13 |
| Leonardo Santiago | for some reason the default gnome keyring is not unlocking on login, neither by password nor by fingerprint (and the password should be the same as the login one) | 17:19:57 |
| Leonardo Santiago | it does do it on my desktop, but on my laptop it does not | 17:20:17 |
| Leonardo Santiago | both are nixos with almost exactly the same definitions, modulo some hardware differences | 17:20:37 |
| Leonardo Santiago | I'm seeing this weird error in journalctl -b | egrep -i "keyring|pam" that I'd like to blame it on, but I don't know what's happening
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Couldn't move process 2719 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope': No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Failed to add PIDs to scope's control group: No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2719.scope: Failed with result 'resources'.
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: PID 2718 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope', skipping: No such process
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: No PIDs left to attach to the scope's control group, refusing.
mai 28 14:16:47 larissa systemd[2642]: app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope: Failed with result 'resources'.
| 17:22:07 |
| Leonardo Santiago | nor which logs would be helpful to debug | 17:22:20 |
| Leonardo Santiago | any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which are by using different desktop managers/login managers, but nothing there did the trick. these (I believe) are the relevant settings I have set:
services.gnome = {
gnome-browser-connector.enable = true;
gnome-keyring.enable = true;
gnome-online-accounts.enable = true;
};
security.pam.services = {
login.enableGnomeKeyring = true;
gdm.enableGnomeKeyring = true;
gdm-autologin.enableGnomeKeyring = true;
gdm-fingerprint.enableGnomeKeyring = true;
gdm-password.enableGnomeKeyring = true;
};
| 17:25:26 |
| Leonardo Santiago | * any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which are by using different desktop managers/login managers, but nothing there did the trick. these (I believe) are the relevant settings I have set (pam ones are me trying to fix it to no avail) o:
services.gnome = {
gnome-browser-connector.enable = true;
gnome-keyring.enable = true;
gnome-online-accounts.enable = true;
};
security.pam.services = {
login.enableGnomeKeyring = true;
gdm.enableGnomeKeyring = true;
gdm-autologin.enableGnomeKeyring = true;
gdm-fingerprint.enableGnomeKeyring = true;
gdm-password.enableGnomeKeyring = true;
};
| 17:25:47 |
