nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.36k stars 1.7k forks source link

bug: sway's xwayland is overriding system's xwayland which breaks fontDir #4840

Open RamKromberg opened 6 months ago

RamKromberg commented 6 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

As detailed here, the way that home-manager's sway module hard-codes pkgs.xwayland means that the system's xwayland package can't be* used when it's recompiled to point to "/run/current-system/sw/share/X11/fonts". So, xfig, ddd and a few other ancient x11 programs that depend on X to provide them with fonts instead of fontconfig or their widget kit (old motif programs but a few pure-x11 ones as well) are stuck with very limited font selection.

Maintainer CC

Scrumplex alexarice sumnerevans sebtm oxalica

System information

- system: `"x86_64-linux"`
- host os: `Linux 6.6.7, NixOS, 23.11 (Tapir), 23.11.1918.40c3c94c2412`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.18.1`
- channels(root): `"home-manage-23.11.tar.gz, home-manager-23.11.tar.gz, nixos-23.11, nixpkgs-23.11, small-23.11-small, stable-23.11, unstable, unstable-small"`
- channels(luser0): `""`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
stale[bot] commented 3 months ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.