| 5 Nov 2025 |
 ElvishJerricco | You're gonna have to paste the full output | 05:17:56 |
 miocasa | In reply to @miocasa:matrix.org
Command not found Not command not found, my bad | 05:18:04 |
| miocasa | Ok | 05:18:14 |
 jasi 🏳️⚧️ | This has been handled here https://github.com/NixOS/nixpkgs/pull/458325 | 16:02:35 |
 Heitor Augusto | Cool! | 16:03:34 |
|  Capypara joined the room. | 21:10:12 |
| Capypara | Hi! Just learned this channel exists: Does anybody else with 48 under NixOS have he issue that for all XWayland apps the cursor turns into a generic small "default" Xorg cursor and that the cursor breaks for some apps that use custom cursor rendering (it turns invisible)? I had this issue all throughout 25.05, I know it was an upstream GNOME bug at first, but apperantly fixed in mutter 48.1 or 48.2 and I didn't have it under Arch anymore. | 21:11:58 |
| Capypara | * | 21:13:36 |
| 6 Nov 2025 |
| jasi 🏳️⚧️ | I think this should be fixed upstream, I know this may be related to how some xwayland apps don't function with the experimental xwayland native scaling feature | 02:07:32 |
 Fabián Heredia | Hi, was testing staging-next with new GNOME and I think I hit a bug of a systemd ordering cycle.
https://github.com/NixOS/nixpkgs/issues/459304
Added some details to an issue on nixpkgs, I think I will have some time to tinker on the weekend but if someone can/wants to work on this before then I would appreciate it. ty for the work on upgrading GNOME for 25.11 <3 | 23:47:24 |
| 9 Nov 2025 |
|  ghpzin (moved to @ghpzin:envs.net) changed their display name from ghpzin to ghpzin (moved to @ghpzin:envs.net). | 15:03:34 |
| 10 Nov 2025 |
|  zitrone joined the room. | 01:23:11 |
|  kachick joined the room. | 14:24:17 |
| 11 Nov 2025 |
|  enzu.ru changed their profile picture. | 21:41:53 |
| 12 Nov 2025 |
|  Inayet changed their display name from inayet to Inayet. | 12:39:05 |
| Capypara | Redacted or Malformed Event | 18:37:38 |
| Capypara | Redacted or Malformed Event | 18:39:16 |
| 13 Nov 2025 |
| ElvishJerricco | (updated today and now this issue appears to be gone so I guess someone fixed something :P) | 21:06:05 |
| 15 Nov 2025 |
| Capypara | Hi! Tried building GNOME 49 together with Jovian (SteamOS-like NixOS), there is some sort of conflict, but I can't figure out where exactly its coming from. Somebody have a clue or ideas on how to debug? All it's giving me is a user unit conflict with no further logging than:
ln: failed to create symbolic link '/nix/store/01q6wg55brqjyf0rjxrgg34gp48d0df9-user-units/orca.service': File exists
| 11:28:59 |
| Capypara | * Hi! Tried building GNOME 49 (nixos-unstable) together with Jovian (SteamOS-like NixOS), there is some sort of conflict, but I can't figure out where exactly its coming from. Somebody have a clue or ideas on how to debug? All it's giving me is a user unit conflict with no further logging than:
ln: failed to create symbolic link '/nix/store/01q6wg55brqjyf0rjxrgg34gp48d0df9-user-units/orca.service': File exists
| 11:30:37 |
| ElvishJerricco | Capypara: so, I think the bug actually is a nixos thing not really related to gnome | 12:05:12 |
| ElvishJerricco | well, "bug" | 12:05:55 |
| ElvishJerricco | it seems like we were previously fine with service files colliding from different systemd.packages and now we're not | 12:06:17 |
| ElvishJerricco | I suspect it'll be the buildEnv thing that changed in the last staging cycle | 12:06:33 |
| ElvishJerricco | oh, lol, no I'm wrong. We've always errored when two systemd.packages tried to have the same unit files. I somehow completely glossed over the fact that we now add orca to systemd.packages when we didn't before. | 14:08:22 |
| ElvishJerricco | Capypara: So this is actually a Jovian bug :P | 14:08:37 |
| ElvishJerricco | because Jovian's steamos-manager is also providing orca.service | 14:09:09 |
| ElvishJerricco | (K900: why is it doing that?) | 14:09:30 |
 K900 | It's trying to use a custom one | 14:09:48 |
| K900 | I'm not entirely sure what the difference is | 14:09:53 |
