| 27 Jan 2024 |
x10an14 |  Download 2024-01-27T17:12:59,957996789+01:00.png | 16:13:44 |
K900 | It is | 16:15:27 |
K900 | Well | 16:15:28 |
K900 | Not really necessary for Plasma itself | 16:15:35 |
K900 | But necessary for drkonqi, the crash reporting tool | 16:15:44 |
K900 | And we don't have a module option to disable it | 16:15:54 |
K900 | Though maybe we should? | 16:15:59 |
x10an14 | Maybe, yeah. I dunno. Seems like the "main" culprit for the required compilation time? | 16:20:01 |
x10an14 |  Download 2024-01-27T17:19:30,186922346+01:00.png | 16:20:08 |
K900 | It should be cached on nix-community | 16:20:18 |
K900 | All of it, that is | 16:20:34 |
x10an14 | Hummm, maybe I should start adding nix-community cache then | 16:24:34 |
| @lehmanator:gnulinux.club removed their profile picture. | 16:55:18 |
| @lehmanator:gnulinux.club removed their display name Sam Lehman. | 17:02:42 |
| @lehmanator:gnulinux.club left the room. | 17:05:43 |
x10an14 | So, plasma6 (wayland) through nur/kde2nix fixes both Divinity Original Sin 2 Definitive Edition + Baldurs Gate 3. I guess it's a sway thing then... | 17:36:47 |
K900 | This makes me wonder | 17:40:13 |
K900 | Is your Sway from the same nixpkgs as the rest? | 17:40:28 |
K900 | I know you said you tried | 17:44:11 |
K900 | But this smells like libgbm mismatch | 17:44:16 |
x10an14 | In reply to @k900:0upti.me Is your Sway from the same nixpkgs as the rest? I think so. This is the sway binary I use (this is configured in home-manager, same nix codebase, but completely unconnected to nixos, beyond sharing same flake inputs):
programs.bash.profileExtra = let
systemd-cat = "${pkgs.systemd}/bin/systemd-cat";
sway = "${config.wayland.windowManager.sway.package}/bin/sway";
in ''
if [ -z $DISPLAY ] && [ "$(tty)" = "/dev/tty4" ]; then
# https://wiki.archlinux.org/title/Sway#Automatically_on_TTY_login
exec ${systemd-cat} --identifier=sway ${sway}
fi
'';
| 17:44:58 |
K900 | Do you maybe have different versions of the flake activated though | 17:45:28 |
K900 | That could also do it | 17:45:32 |
x10an14 | This is my sway config on the nixos side of same flake inputs-sharing nix-repo:
_:
# Sway specific stuffs (fixes that must be system based - instead of home-manager based)
{
# Allow Wayland stuff to use OpenGL
# (Anything installed via Home-Manager needs a new switch for this to take effect)
hardware.opengl.enable = true;
# Necessary according to Nixos Wiki for Sway under HM:
security.polkit.enable = true;
# Allow swaylock to unlock machine;
# necessary due to: https://github.com/NixOS/nixpkgs/issues/143365
programs.sway.enable = true;
# Allow screensharing:
services.pipewire = {
enable = true;
alsa.enable = true;
pulse.enable = true;
};
xdg.portal = {
enable = true;
wlr.enable = true;
# Don't enable unless sway.wrapperFeatures.gtk is also enabled
# extraPortals = [pks.xdg-desktop-portal-gtk];
# gtkUsePortal = true;
};
# Enable icons for say, Gnome applications
xdg.icons.enable = true;
}
| 17:45:53 |
x10an14 | In reply to @k900:0upti.me Do you maybe have different versions of the flake activated though No, I always do sudo nixos-rebuild switch; home-manager switch. And I do the nix flake check --log-format internal-json -vvv |& nom --json before I activate either. | 17:46:57 |
K900 | Well I guess the other option is just "Sway broke Proton" | 17:47:21 |
K900 | Which feels like a thing that should have been caught | 17:47:29 |
x10an14 | Well, I made sure to do this now that we updated, to avoid this pitfall at least. Not gonna say I'm perfect and never make mistakes. | 17:47:31 |
K900 | But at this point | 17:47:46 |
K900 | Wew | 17:47:46 |