!XQQVyIbcAcHFvzmcTl:nixos.org

NixOS GNOME

390 Members
A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...)91 Servers

Load older messages

SenderMessageTime
27 May 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (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:grapevine.grimmauld.deGrimmauld (any/all)And freecad, by default - needs freecad-qt6 or freecad-wayland...09:04:01
@normalcea:matrix.orgjasi 🏳️‍⚧️ Isn't Nvidia one of the main reasons for people still on Xorg nowadays? 15:55:20
@normalcea:matrix.orgjasi 🏳️‍⚧️There's no real data on this either so 🥲15:55:46
@sigmasquadron:matrix.orgSigmaSquadrona11y is also a big reason afaik.16:45:33
@normalcea:matrix.orgjasi 🏳️‍⚧️
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
@normalcea:matrix.orgjasi 🏳️‍⚧️ I think DIY distributions like NixOS should still offer the xorg session until it's fully deprecated in upstream. 17:28:24
@normalcea:matrix.orgjasi 🏳️‍⚧️ It also allows for nixpkgs to alert users of GNOME xorg session removal 17:28:59
@normalcea:matrix.orgjasi 🏳️‍⚧️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.1117:31:59
@normalcea:matrix.orgjasi 🏳️‍⚧️I also believe that plasma 6 still allows users to explicitly select the xorg session.17:32:48
@normalcea:matrix.orgjasi 🏳️‍⚧️That's just my thoughts17:34:06
@qyliss:fairydust.spaceAlyssa 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:matrix.orgSigmaSquadron
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:matrix.orgSigmaSquadronbut 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
@normalcea:matrix.orgjasi 🏳️‍⚧️
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
@deeok:matrix.orgmatrixrooms.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
@andrew15_5:matrix.orgAndrew Good news: I finally faced this issue again. Bad news: idk which extension it is: burn-my-windows, compiz-windows-effect. 16:07:56
@andrew15_5:matrix.orgAndrewI also don't know if there are any other ones that are bad.16:18:30
@andrew15_5:matrix.orgAndrew* 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:0upti.meK900Well turn them off one by one and see?16:34:09
@o-santi:matrix.orgLeonardo Santiagohi17:19:13
@o-santi:matrix.orgLeonardo Santiagofor 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
@o-santi:matrix.orgLeonardo Santiagoit does do it on my desktop, but on my laptop it does not17:20:17
@o-santi:matrix.orgLeonardo Santiagoboth are nixos with almost exactly the same definitions, modulo some hardware differences17:20:37
@o-santi:matrix.orgLeonardo 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
@o-santi:matrix.orgLeonardo Santiagonor which logs would be helpful to debug17:22:20
@o-santi:matrix.orgLeonardo 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
@o-santi:matrix.orgLeonardo 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
@o-santi:matrix.orgLeonardo 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
@o-santi:matrix.orgLeonardo 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

Show newer messages

Back to Room ListRoom Version: 6