| 27 May 2025 |
 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 |
| Leonardo Santiago | * any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which almost all mention 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:27:32 |
| Leonardo Santiago | * any tips? I've taken a look into every issue in discourse mentioning gnome-keyring, which almost all mention using different desktop managers/login managers, but nothing there did the trick, as I'm on gdm. 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:27:43 |
| Andrew | Need a couple more days. | 19:03:45 |
| jasi 🏳️⚧️ changed their display name from normalcea to normalcea 🏳️⚧️. | 21:28:09 |
| 30 May 2025 |
| Andrew | https://github.com/Schneegans/Burn-My-Windows/issues/520 | 21:43:22 |
| Andrew | well well well, what do we have here | 21:43:35 |
| Andrew | At least now I know what I need to disable. | 22:13:55 |
| 31 May 2025 |
| Andrew | I actually found some other extension that leaks memory. I hoped there would be only one. | 19:19:09 |
| jasi 🏳️⚧️ | In reply to @andrew15_5:matrix.org
I actually found some other extension that leaks memory. I hoped there would be only one. Is it another extension that adds graphical effects to shell? | 19:33:22 |
| jasi 🏳️⚧️ | similar to bmw? | 19:33:28 |
| Andrew | idk | 19:33:52 |
| Andrew | might be | 19:34:24 |
| Andrew | * idk yet | 19:34:32 |
| Andrew | I guess I only enabled compiz-windows-effect and native-window-placement, plus custom theme. | 19:37:33 |
| Andrew | so if last one is anything to go by, then the second would be compiz | 19:38:01 |
| 2 Jun 2025 |
|  Sean Thawe joined the room. | 22:47:52 |
