| 15 Aug 2023 |
Jan Tojnar | * Hmm, looks like a regression. Just tested the example from https://github.com/NixOS/nixpkgs/pull/76591#pullrequestreview-336927961 in VM and I do not see the layout listed in Control Center on either Wayland session or X11. | 02:26:51 |
Jan Tojnar | * Hmm, looks like a regression. Just tested the example from https://github.com/NixOS/nixpkgs/pull/76591#pullrequestreview-336927961 in VM and I do not see the layout listed in Control Center on either Wayland session or X11. | 02:35:28 |
Jan Tojnar | Ugh, the link was just broken and i TOFU'd GitLab’s 403 page. But even after updating it and confirming g-c-c sees the XKB_CONFIG_ROOT variable and the path in it contains the custom file, it still is not listed in either session | 02:37:01 |
| @onefjef:matrix.org joined the room. | 03:39:58 |
| @10leej:matrix.org left the room. | 19:33:54 |
maxine (they/them) | bobby285271 Jan Tojnar fyi it looks like my holiday plans overlap with most of the cycle of 45 so the only thing I can say is I'll be unable to contribute until the week final tarballs should start dropping. Sorry about that - I'll do what I can when I'm back. | 19:53:50 |
maxine (they/them) | Gonna at least bump NM before I leave Friday | 19:54:04 |
Jan Tojnar | hmm, I am leaving too (for the next two weeks) so I am afraid I will not be much help either, I want to finish reviewing the dconf module PR but 45 will have to wait until September | 21:05:17 |
Jan Tojnar | at worse, we will delay the bump a bit | 21:05:50 |
Jan Tojnar | anyway, enjoy your vacation, maxine | 21:06:07 |
maxine (they/them) | Thanks. I guess there might be more work left for 45 in September than I thought so I'll hopefully have something to help with after all 😅 | 22:28:02 |
| 16 Aug 2023 |
| @nielsk:x-hain.de joined the room. | 05:49:47 |
Jan Tojnar | well, Bobby already has done a lot in the short while so we will see 😻 | 22:26:37 |
Jan Tojnar | we will probably want to cherry pick https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3186 in the meanwhile | 22:27:14 |
| 17 Aug 2023 |
Jan Tojnar | Last call for reviewing the dconf module PR. Would be especially great if people could test the usability. | 21:55:50 |
Jan Tojnar | IMO it is probably the most important GNOME-related change in the past few years. | 21:56:28 |
| 18 Aug 2023 |
@ThorHop:matrix.org |  Download tenor_gif3271887152278896702.gif | 20:48:26 |
@ThorHop:matrix.org | Where 45 beta? | 20:48:31 |
| 20 Aug 2023 |
bobby285271 | In reply to @jtojnar:matrix.org we will probably want to cherry pick https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3186 in the meanwhile I am fine to rebase the GNOME 45 branch later, just one question, will this fix the esc hack in nixosTests.gnome? (I have a branch for it and for some reason the test did not pass for me at least in the first 90 seconds 🤔) | 04:14:20 |
@palasso:matrix.org | Hello. I am using home-manager as a NixOS module in 23.05. I have been trying to set a clock in GNOME Shell's world clocks and GNOME clocks app via dconf.settings but I haven't found a solution. Specifically, I can see the clock in GNOME Shell in "World Clocks" (when clicking at the date/time on the top panel, a pop-up appears and below the calendar it has a "World Clocks") but when I click on it and opens the GNOME Clocks app it doesn't show any clock. This is where I am at:
{ lib, ... }:
let
# dconf location for weather, clocks etc.
dconfLocation = { city, ICAO_code, x, y }: with lib.hm.gvariant; [ (mkVariant (mkTuple [ (mkUint32 2) (mkVariant (mkTuple [ city ICAO_code true [ (mkTuple x) ] [ (mkTuple y) ]])) ])) ];
# Berlin: [<(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>]
berlin = dconfLocation {
city = "Berlin";
ICAO_code = "EDDT";
x = [0.91746141594945008 0.23241968454167572];
y = [0.91658875132345297 0.23387411976724018];
};
in
{
# Export dconf settings into a nix file: `dconf dump / | dconf2nix > dconf.nix`
# Use `dconf watch /` to track stateful changes you are doing, then set them here.
dconf.settings = {
"org/gnome/shell/world-clocks".locations = berlin;
# [{'location': <(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>}]
"org/gnome/clocks".world-clocks = with lib.hm.gvariant; [ [ (mkDictionaryEntry [ "location" (builtins.head berlin) ]) ] ];
};
}
I presume I am doing something wrong in "org/gnome/clocks".world-clocks. Are there any ideas how I can resolve that issue?
| 07:47:23 |
@palasso:matrix.org | * Hello. I am using home-manager as a NixOS module in 23.05. I have been trying to set a clock in GNOME Shell's world clocks and GNOME clocks app via dconf.settings but I haven't found a solution. Specifically, I can see the clock in GNOME Shell in "World Clocks" (when clicking at the date/time on the top panel, a pop-up appears and below the calendar it has a "World Clocks") but when I click on it and opens the GNOME Clocks app it doesn't show any clock. This is where I am at:
# home.nix
{ lib, ... }:
let
# dconf location for weather, clocks etc.
dconfLocation = { city, ICAO_code, x, y }: with lib.hm.gvariant; [ (mkVariant (mkTuple [ (mkUint32 2) (mkVariant (mkTuple [ city ICAO_code true [ (mkTuple x) ] [ (mkTuple y) ]])) ])) ];
# Berlin: [<(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>]
berlin = dconfLocation {
city = "Berlin";
ICAO_code = "EDDT";
x = [0.91746141594945008 0.23241968454167572];
y = [0.91658875132345297 0.23387411976724018];
};
in
{
# Export dconf settings into a nix file: `dconf dump / | dconf2nix > dconf.nix`
# Use `dconf watch /` to track stateful changes you are doing, then set them here.
dconf.settings = {
"org/gnome/shell/world-clocks".locations = berlin;
# [{'location': <(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>}]
"org/gnome/clocks".world-clocks = with lib.hm.gvariant; [ [ (mkDictionaryEntry [ "location" (builtins.head berlin) ]) ] ];
};
}
I presume I am doing something wrong in "org/gnome/clocks".world-clocks. Are there any ideas how I can resolve that issue?
| 07:48:23 |
@palasso:matrix.org | * Hello. I am using home-manager as a NixOS module in 23.05. I have been trying to set a clock in GNOME Shell's world clocks and GNOME clocks app via dconf.settings but I haven't found a solution. Specifically, I can see the clock in GNOME Shell in "World Clocks" (when clicking at the date/time on the top panel, a pop-up appears and below the calendar it has a "World Clocks") but when I click on it and opens the GNOME Clocks app it doesn't show any clock. This is where I am at:
# home.nix
{ lib, ... }:
let
# dconf location for weather, clocks etc.
dconfLocation = { city, ICAO_code, x, y }: with lib.hm.gvariant; [ (mkVariant (mkTuple [ (mkUint32 2) (mkVariant (mkTuple [ city ICAO_code true [ (mkTuple x) ] [ (mkTuple y) ]])) ])) ];
# Berlin: [<(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>]
berlin = dconfLocation {
city = "Berlin";
ICAO_code = "EDDT";
x = [0.91746141594945008 0.23241968454167572];
y = [0.91658875132345297 0.23387411976724018];
};
in
{
# Export dconf settings into a nix file: `dconf dump / | dconf2nix > dconf.nix`
# Use `dconf watch /` to track stateful changes you are doing, then set them here.
dconf.settings = {
"org/gnome/shell/world-clocks".locations = berlin;
# [{'location': <(uint32 2, <('Berlin', 'EDDT', true, [(0.91746141594945008, 0.23241968454167572)], [(0.91658875132345297, 0.23387411976724018)])>)>}]
"org/gnome/clocks".world-clocks = with lib.hm.gvariant; [ [ (mkDictionaryEntry [ "location" (builtins.head berlin) ]) ] ];
};
}
I presume I am doing something wrong in "org/gnome/clocks".world-clocks as "org/gnome/shell/world-clocks".locations seems to work. Are there any ideas how I can resolve that issue?
| 09:02:32 |
Jan Tojnar | In reply to @bobby285271:matrix.org I am fine to rebase the GNOME 45 branch later, just one question, will this fix the esc hack in nixosTests.gnome? (I have a branch for it and for some reason the test did not pass for me at least in the first 90 seconds 🤔) If it is a proper fix, it might. But I have not looked into the details yet. I can only say I have not noticed any of the annoyances when using it on work laptop for two days. | 10:07:01 |
| @alper-celik:matrix.org joined the room. | 16:51:30 |
vcunat | Quick question for gnome shell extensions - is it normal to find non-determinism in their interactions? | 16:55:10 |
vcunat | It's like different things happen when they get loaded in different order or something. | 16:55:32 |
vcunat | * Quick question for gnome shell extensions - is it common to find non-determinism in their interactions? | 16:55:51 |
vcunat | (I don't expect this is a NixOS-specific thing, though.) | 16:56:20 |
| 21 Aug 2023 |
uep | I mean, it doesn't surprise me, it's a twisty maze of javascript hooks manipulating state | 00:13:33 |
uep | and it's pretty easy to get conflicts deliberately between extensions that both want to do something similar, like say tiling managers that catch various window events and push new resizing events. So there can surely be less-intentional and less-intuitive interactions between others. | 00:18:49 |