bug: clipman service results in errors in the journal on copy

[jnsgruk]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [X] I have searched the existing issues

Issue description

I'm using the clipman module (along with sway), and I noticed that in my journal I have lots of entries as such:

Apr 13 12:27:07 loki wl-paste[545663]: 2023/04/13 12:27:07 error running wl-copy: exit status 1
Apr 13 12:27:29 loki wl-paste[545698]: 2023/04/13 12:27:29 error running wl-copy: exit status 1
Apr 13 12:27:44 loki wl-paste[545714]: 2023/04/13 12:27:44 error running wl-copy: exit status 1

I get one of these messages every time I copy something (i.e. press Ctrl+C). The copy does seem to work, however, so not a blocking issue.

Maintainer CC

@DamienCassou @rycee

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.2.10, NixOS, 23.05 (Stoat), 23.05.20230412.6b70761`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[jnsgruk]

Testing at the command line with wl-copy, I seem to be able to trigger the same error with echo "foo" | wl-copy, but not with echo "foo" | wl-copy -p.

[DamienCassou]

/cc @jwygoda

[stale[bot]]

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.