Systemd fail

[bphd]

~/myFolder $ grive -a
[...]
Finished !
[...]
~ $ systemctl --user enable grive@$(systemd-escape myFolder).service
systemctl --user start grive@$(systemd-escape myFolder).service
Failed to enable unit: Unit file [email protected] does not exist.
Failed to start [email protected]: Unit [email protected] not found.

~ $ systemctl --user status g
gala-x11.service                         gnome-session-failed.target              gnome-session.target                     gpg-agent-extra.socket                   gvfs-goa-volume-monitor.service
gala-x11.target                          gnome-session-initialized.target         gnome-session-wayland.target             gpg-agent.service                        gvfs-gphoto2-volume-monitor.service
gamemoded.service                        gnome-session-manager.target             gnome-session-x11-services-ready.target  gpg-agent.socket                         gvfs-metadata.service
gcr-ssh-agent.service                    gnome-session-monitor.service            gnome-session-x11-services.target        gpg-agent-ssh.socket                     gvfs-mtp-volume-monitor.service
gcr-ssh-agent.socket                     gnome-session-pre.target                 gnome-session-x11.target                 graphical-session-pre.target             gvfs-udisks2-volume-monitor.service
glib-pacrunner.service                   gnome-session-restart-dbus.service       gnome-terminal-server.service            graphical-session.target                 
gnome-remote-desktop.service             gnome-session-shutdown.target            gnome-user-share-webdav.service          gvfs-afc-volume-monitor.service          
gnome-session-failed.service             gnome-session-signal-init.service        gpg-agent-browser.socket                 gvfs-daemon.service

[Tuuuukka]

I'm getting this too now, don't know what has happened, but the service seems to be gone. Since there hasn't been any activity for months in this issue, I guess it might not be solved any time soon.

[lusacramento]

O mesmo aqui. consegui sincronizar desconsiderando os comandos: systemctl --user enable grive@$(systemd-escape google-drive).service systemctl --user start grive@$(systemd-escape google-drive).service

e utilizando os comandos, na seguinte ordem: systemctl --user enable grive-timer@$(systemd-escape google-drive).timer systemctl --user start grive-timer@$(systemd-escape google-drive).timer systemctl --user enable grive-changes@$(systemd-escape google-drive).service systemctl --user start grive-changes@$(systemd-escape google-drive).service

fonte: https://askubuntu.com/questions/1011854/how-to-enable-users-systemd-timers-and-services-for-grive2

[jankatins]

My guess is, that this should be fixed by https://github.com/vitalif/grive2/commit/48f5f0e52f87b35f9f77987c8a699dab48ff9256

[jankatins]

At least on my system the units are installed now: this can be closed.

[bphd]

It's not your issue afaik