Arch Linux User Repository

I have reverted to 4.2 until I find the issue

Looks like this is a disguised -bin package. Should be recreated as rofi-greenclip-bin.

The last update crashes with:

systemd-coredump[314885]: [🡕] Process 314881 (greenclip) of user 1000 dumped core.

 Module /usr/bin/greenclip without build-id.
 Stack trace of thread 314881:
 #0  0x0000000000000000 n/a (n/a + 0x0)
 ELF object binary architecture: AMD x86-64

Commit ad355c5e0866 (with greenclip 4.2) works as expected. Worth reporting upstream if others are affected as well.

FYI, I have to modify the service to add a delay on restart, because systemd try to start greenclip too quickly. The unit is configured to start After=display-manager.service, but I use a console login manager, which does not provide this service, so it's the likely cause.

systemd log and error:

Jan 14 05:38:54 hostname systemd[1303]: Started Greenclip agent.
Jan 14 05:38:54 hostname systemd[1303]: greenclip.service: Scheduled restart job, restart counter is at 1.
Jan 14 05:38:54 hostname systemd[1303]: Started Greenclip agent.
Jan 14 05:38:54 hostname greenclip[1358]: X display not available. Please start Xorg before running greenclip
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Scheduled restart job, restart counter is at 2.
Jan 14 05:38:55 hostname systemd[1303]: Started Greenclip agent.
Jan 14 05:38:55 hostname greenclip[1435]: X display not available. Please start Xorg before running greenclip
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Scheduled restart job, restart counter is at 3.
Jan 14 05:38:55 hostname systemd[1303]: Started Greenclip agent.
Jan 14 05:38:55 hostname greenclip[1448]: X display not available. Please start Xorg before running greenclip
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Scheduled restart job, restart counter is at 4.
Jan 14 05:38:55 hostname systemd[1303]: Started Greenclip agent.
Jan 14 05:38:55 hostname greenclip[1450]: X display not available. Please start Xorg before running greenclip
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Scheduled restart job, restart counter is at 5.
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Start request repeated too quickly.
Jan 14 05:38:55 hostname systemd[1303]: greenclip.service: Failed with result 'start-limit-hit'.
Jan 14 05:38:55 hostname systemd[1303]: Failed to start Greenclip agent.

Adding a delay on restart fix the issue.

.config/systemd/user/greenclip.service.d/override.conf
[Service]
RestartSec=3s

You need to clean your cache if the checksum fails. Don't know how to avoid this issue, so if you have a magic solution, feel free to tell me.

Bumped pkgrel to force build clean, but the checksum is correct.

  1 rofi-greenclip                   (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> A
:: Deleting (1/1): /home/erebe/.cache/yay/rofi-greenclip
:: Downloaded PKGBUILD (1/1): rofi-greenclip
  1 rofi-greenclip                   (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: (1/1) Parsing SRCINFO: rofi-greenclip
==> Making package: rofi-greenclip 3.4-5 (Tue 29 Dec 2020 09:35:50 PM CET)
==> Retrieving sources...
  -> Downloading greenclip...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   633  100   633    0     0   1850      0 --:--:-- --:--:-- --:--:--  1850
100 2976k  100 2976k    0     0  1300k      0  0:00:02  0:00:02 --:--:-- 1968k
  -> Found greenclip.service
==> Validating source files with sha256sums...
    greenclip ... Passed
    greenclip.service ... Passed

Same here.

  -> Found greenclip
  -> Found greenclip.service
==> Validating source files with sha256sums...
    greenclip ... FAILED
    greenclip.service ... Passed
==> ERROR: One or more files did not pass the validity check!
error downloading sources: rofi-greenclip