nix-community / home-manager

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

bug: some xfce panel plugins don't work unless defined in systemPackages #4317

Open novoid opened 1 year ago

novoid commented 1 year ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

This is a copy from a stale issue from https://github.com/NixOS/nixpkgs/issues/89302 which has a verbose description of the issue of not seeing several xfce panel plugins when used with Home-Manager.

I do think that this issues is more related to home-manager (this issue) than to NixOS/nixpkgs in general (the other issue).

I'm not the original author of that issue but I was also affected by it: https://github.com/novoid/nixos-config/issues/2 https://github.com/novoid/nixos-config/issues/3 https://github.com/novoid/nixos-config/issues/4 https://github.com/novoid/nixos-config/issues/5

My affected setup: https://github.com/novoid/nixos-config/tree/e4e4795d464611e13fc8ffbc9a6f6822d1e1986b

Fixed in my setup by moving the list of xfce packages including the add-ons/plugins from homemanager/xfce.nix to configuration.nix (NixOS without/outside of Home-Manager) and then the missing plugins were visible in the xfce panel.

Fixed via https://github.com/novoid/nixos-config/commit/dd68aa7f2d93eb5d9a9f1f5758c7cee7dde4f19b

Maintainer CC

@muscaln

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.42, NixOS, 23.05 (Stoat), 23.05.20230801.bd836ac`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
stale[bot] commented 11 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.

novoid commented 11 months ago

From all I've read, this issue rather looks like an conceptual issue related to the integration of XFCE. I'm not an expert but it seems that this could represent and underlying issue which is not that easy/quick to fix.

Correct me if I'm wrong.

However, configuring xfce using Nix does seem to work randomly which results in a lot of try and error.

stale[bot] commented 8 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.