| 22 May 2026 |
 winston | the backport for this hasn't been merged yet, don't think anything's blocking it https://github.com/NixOS/nixpkgs/pull/522872 | 19:18:00 |
|  Jon Hermansen changed their display name from jonhermansen to Jon Hermansen. | 19:18:39 |
| winston | also I managed to make gnome-remote-desktop configurable from Settings 🙂
https://github.com/NixOS/nixpkgs/pull/523122 | 19:28:39 |
| winston | I played around with another solution of having a declarative config as a nixos module, that'd be an alternative, but this PR is closer to how it works on other distros | 19:29:49 |
| 24 May 2026 |
 André Lima | Hi, I'm not sure if anyone has brought this up already, but my IBus daemon seems to be crashing in the login screen. I see this line in the logs, followed by the coredump
ibus-daemon[4192]: mkdir is failed in: /run/gdm/.cache/ibus: Permission denied | 15:04:06 |
| André Lima | I'm also seeing problems with wireplumber, and gsd-xsettings. They all expect /run/gdm to be writeable, I guess. I'm still able to log in, so not very serious | 15:06:49 |
| André Lima | Also, has anyone had any Bluetooth issues after upgrading to GNOME 50? My bluetooth is no longer working, it seems | 15:08:24 |
| André Lima | Okay, it seems it's a kernel regression: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bluetooth/bluetooth/+/e3ac0d9f1a205f33a43fba3b79ef74d2f604c78b | 15:24:44 |
 emily | cc winston | 15:56:02 |
| winston | the fix for this should land in nixos-unstable soon https://nixpkgs-tracker.ocfox.me/?pr=521789 | 15:57:21 |
| André Lima | Awesome, thank you! | 15:57:57 |
| emily | winston: you're overdue a PR to the teams list at this point :) | 15:58:20 |
| winston | this might actually be a kernel related issue, I've seen other people talk about it (something about a mediatek driver?), bluetooth works fine for me | 15:58:35 |
| winston | hope it works itself out for you, otherwise we'll need to look into that | 15:58:46 |
| André Lima | Yep, it seems like it is a kernel issue, I'm already building a patched kernel to test it out | 15:59:12 |
| winston | how do I do that? I thought it was managed via GitHub API/teams | 15:59:36 |
| André Lima | https://github.com/NixOS/nixpkgs/blob/556e57ad06c7526d4ecd68da513b6e6ba2664ca8/maintainers/team-list.nix#L322 winston | 16:01:03 |
| André Lima | Why are there teams with no members though? Like systemd, GNOME, and many others? | 16:01:29 |
| André Lima | * | 16:01:34 |
| winston | yeah I saw that, I assumed I have to get added to https://github.com/orgs/NixOS/teams/gnome | 16:01:42 |
| winston | I think its an abstraction so you can @ teams instead of each member individually | 16:02:09 |
| winston | for reviews etc | 16:02:15 |
| emily | those are in github-teams.json. it's confusing. the workflow is not very good. I'm not super happy about it :/ | 16:04:29 |
| emily | I preferred when changes to teams always went through a GitHub PR workflow, because that's the standard we use for everything… pinging maintainers out of band to do it and then it goes in a batch update PR is weird | 16:05:02 |
| emily | keeping it in sync with GitHub is good but it would be nice if it worked the other way around (put up PR, it gets blocked by CI until the GitHub change is effected) | 16:05:21 |
| winston | ah I see, and changes to that JSON will then sync people on github? | 16:06:12 |
| emily | well, that part could still be manual | 16:06:20 |
| emily | I think you can do it now by opening a PR to github-teams.json and pinging the team, and then a maintainer can add you | 16:06:30 |
| emily | IIRC that's not the flow you're "meant" to do with the new system but it's the only one that makes sense to me :P | 16:06:40 |
| winston | gotcha, I'll do that :)
definitely wanna help out with GNOME 51 so we won't have to rush it as hard | 16:07:03 |
