Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nextcloud-client: start upon switch #697

Closed
teto opened this issue Apr 30, 2019 · 7 comments
Closed

nextcloud-client: start upon switch #697

teto opened this issue Apr 30, 2019 · 7 comments

Comments

@teto
Copy link
Collaborator

teto commented Apr 30, 2019

so I just added services.nextcloud-client.enable = true; to my config. Was expecting to see nextcloud-client popup into my tray but it didn't (using i3). What's the systemd parameter I should change to make it working ? I can submit a PR.

@rycee
Copy link
Member

rycee commented May 12, 2019

Hmm, I don't see anything obviously wrong with the current definition of the systemd unit. What does systemctl --user status nextcloud-client say? And perhaps journalctl --user -u nextcloud-client.service.

@teto
Copy link
Collaborator Author

teto commented May 13, 2019

hum also noticed it doesn't work with the system proxy. The process doesn't have http_proxy in its environment even though I set it via the nixos networking.proxy option.
I might have a look when I get more time next week.

NB: I checked if upstream provided a service but not yet. For future reference:
nextcloud/desktop#728

@teto
Copy link
Collaborator Author

teto commented May 20, 2019

@rycee any reason we should not inherit nixos sessionVariables in systemd's user services ? or I should just add nixos.config.networking.proxy.envVars to the sessionVariables when nixos is detected ?

@benneti
Copy link

benneti commented Jan 15, 2021

I think I might have a solution for one of your problems, namely adding the following (in home-manager.users.your-user):

    systemd.user.services.nextcloud-client = {
      Service.ExecStartPre = lib.mkForce "${pkgs.coreutils}/bin/sleep 15";
      Unit = {
        After = lib.mkForce [ "graphical-session.target" ];
        PartOf = lib.mkForce [  ];
      };
    };

In detail, for me (using gnome) was that apparently nextcloud started to early such that libindicator was not setup and running already.
To make sure it is running I needed to add the sleep and for the sleep to actually do something usefull and not only create a black screen it was necessary to remove the service from the graphical-session.target and for it to be clean I actually want to start it after the graphical-session not graphical-session-pre.target .

@stale
Copy link

stale bot commented Apr 28, 2021

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close 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

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, 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.

1 similar comment
@stale
Copy link

stale bot commented Jul 27, 2021

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close 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

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, 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.

@stale stale bot added the status: stale label Jul 27, 2021
@stale stale bot closed this as completed Aug 3, 2021
@augustebaum
Copy link

https://nostalebots.xyz/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants