bug: Syncthingtray started before tray #3416

budimanjojo · 2022-11-15T08:35:59Z

Are you following the right branch?

My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

I have searched the existing issues

Issue description

Related ref: #2968

I can't get syncthingtray with either i3 or sway. It will work if I restart the service with systemctl --user restart syncthingtray after the system started.
This is what I have in my home-manager config:

services.syncthing = {
  enable = true;
  tray.enable = true;
};

If I put services.syncthing.tray.command = "syncthingtray --wait", the tray icon will never show up too which is weird.

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
- host os: `Linux 5.15.77, NixOS, 22.11 (Raccoon), 22.11.20221113.fc07622`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.11.0`
- nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

The text was updated successfully, but these errors were encountered:

exzombie · 2022-11-18T11:17:53Z

I bet this is related to #2878, can you confirm?

budimanjojo · 2022-11-19T01:46:01Z

@exzombie Thanks! I don't have theming issue. And I just tried installing pkgs.gnome-icon-theme and sadly the problem persists.

ref: nix-community/home-manager#3416

stale · 2023-02-17T01:59:43Z

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.

liff · 2023-07-27T19:42:03Z

Not stale, I encountered the exact same problem.

liff · 2023-07-27T20:01:38Z

Related upstream issue: Alexays/Waybar#1090.

stale · 2023-10-28T17:07:53Z

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.

brianmay · 2023-10-29T00:29:57Z

I have a kludge to fix this:

systemd.user.services.syncthingtray.Service.ExecStart = pkgs.lib.mkForce
    "${pkgs.bash}/bin/bash -c '${pkgs.coreutils}/bin/sleep 5; ${pkgs.syncthingtray-minimal}/bin/syncthingtray'";

I think this is a real issue that needs to be fixed, the problem is going to be getting consensus - particularly with upstream packages - on how to fix it.

stale · 2024-01-27T07:01:10Z

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.

exzombie · 2024-01-27T10:32:00Z

If people are relying on kludges, it's not fixed yet.

I've recently played around a bit with HM+systemd tray handling. I don't use syncthing myself, so I can't test this service specifically. But looking at its user unit file, everything looks ok. Are you guys using a separate bar/tray application, or the one built into i3/sway? AFAICT, external tray applications will be started before tray.target and syncthingtray will be started after tray.target, so things should work. The problem is that the WM (and it's builtin bar) is started last, after all the systemd services. In that case, the only proper solution (apart from switching to a separate bar application) is to start your tray apps not as a systemd service, but from the WM.

Protarios · 2024-03-11T20:44:44Z

I have the same issue. I thought it might be related to using a quite old low power computer (Manjaro in Intel NUC 7i3BNH), as it works great on another installation of Manjaro on an up-to-date CPU.

--wait fixes the issue for me, but it seems to be kind of a dirty workaround.

TeChn4K · 2024-04-25T07:20:27Z

Not stale please

stale · 2024-07-26T08:40:58Z

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.

brianmay · 2024-08-08T00:27:09Z

I tried a different hack. I set services.syncthing.tray.enable to false, then then set wayland.windowManager.sway.startup to [{ command = "${pkgs.syncthingtray-minimal}/bin/syncthingtray"; }]; (and similar for i3).

Unfortunately, it does not work, I get the error from swaythingtray that the tray hasn't started yet.

Which isn't really surprising, but thought I should mention it here.

KucharczykL · 2025-01-03T06:05:59Z

My kludge that actually works is adding this to my config:

 home-manager.users.lukas.systemd.user.services.syncthingtray = {
      Service.ExecStart = lib.mkForce "${pkgs.syncthingtray}/bin/syncthingtray --wait";
    };

Perhaps it should be changed it https://github.com/nix-community/home-manager/blob/master/tests/modules/services/syncthing/linux/tray.nix?

sumnerevans · 2025-01-08T17:28:32Z

PRs welcome. Probably just need to edit this:

home-manager/modules/services/syncthing.nix

Line 729 in fcc4259

ExecStart = "${pkgs.syncthingtray-minimal}/bin/syncthingtray";

, but not sure.

brianmay · 2025-01-08T20:27:33Z

In the first message the reporter said that adding --wait didn't help. But that was in 2022. Maybe different now in 2025?

brianmay · 2025-01-08T20:37:44Z

Will test and report back here.

brianmay · 2025-01-09T23:24:07Z

Early days, but --wait does seem to work for me right now.

budimanjojo added bug triage Issues or feature request that have not been triaged yet labels Nov 15, 2022

budimanjojo assigned berbiche, rycee and sumnerevans Nov 15, 2022

budimanjojo added a commit to budimanjojo/nix-config that referenced this issue Nov 24, 2022

feat(syncthing): wait 5 seconds before starting the tray

8669317

ref: nix-community/home-manager#3416

stale bot added the status: stale label Feb 17, 2023

stale bot removed the status: stale label Jul 27, 2023

stale bot added the status: stale label Oct 28, 2023

stale bot removed the status: stale label Oct 29, 2023

stale bot added the status: stale label Jan 27, 2024

stale bot removed the status: stale label Mar 11, 2024

stale bot added the status: stale label Jul 26, 2024

stale bot removed the status: stale label Aug 8, 2024

sumnerevans added the pinned Prevent marking as stale label Jan 8, 2025

Jdogzz linked a pull request Jan 8, 2025 that will close this issue

syncthing: have tray wait for bar to load #6290

Open

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

bug: Syncthingtray started before tray #3416

bug: Syncthingtray started before tray #3416

budimanjojo commented Nov 15, 2022

exzombie commented Nov 18, 2022

budimanjojo commented Nov 19, 2022

stale bot commented Feb 17, 2023

liff commented Jul 27, 2023

liff commented Jul 27, 2023 •

edited

Loading

stale bot commented Oct 28, 2023

brianmay commented Oct 29, 2023

stale bot commented Jan 27, 2024

exzombie commented Jan 27, 2024

Protarios commented Mar 11, 2024 •

edited

Loading

TeChn4K commented Apr 25, 2024

stale bot commented Jul 26, 2024

brianmay commented Aug 8, 2024

KucharczykL commented Jan 3, 2025

sumnerevans commented Jan 8, 2025

brianmay commented Jan 8, 2025

brianmay commented Jan 8, 2025

brianmay commented Jan 9, 2025

bug: Syncthingtray started before tray #3416

bug: Syncthingtray started before tray #3416

Comments

budimanjojo commented Nov 15, 2022

Are you following the right branch?

Is there an existing issue for this?

Issue description

Maintainer CC

System information

exzombie commented Nov 18, 2022

budimanjojo commented Nov 19, 2022

stale bot commented Feb 17, 2023

liff commented Jul 27, 2023

liff commented Jul 27, 2023 • edited Loading

stale bot commented Oct 28, 2023

brianmay commented Oct 29, 2023

stale bot commented Jan 27, 2024

exzombie commented Jan 27, 2024

Protarios commented Mar 11, 2024 • edited Loading

TeChn4K commented Apr 25, 2024

stale bot commented Jul 26, 2024

brianmay commented Aug 8, 2024

KucharczykL commented Jan 3, 2025

sumnerevans commented Jan 8, 2025

brianmay commented Jan 8, 2025

brianmay commented Jan 8, 2025

brianmay commented Jan 9, 2025

liff commented Jul 27, 2023 •

edited

Loading

Protarios commented Mar 11, 2024 •

edited

Loading