You are not logged in.
Pages: 1
Okay, so I really like Gnome and after the last update it got borked lol I couldn't find a solution but figured maybe it had something to do with the whole systemd upgrade thing so decided to say screw it and reinstall everything. "and wow has the install process changed lol" anyhow my dropbox service will not start automatically. I followed the instructions at https://wiki.archlinux.org/index.php/Dr … ng_Dropbox and still nothing. Funny enough the instructions have me create a dropboxd.service file which I did, however it will only start with systemctl start dropboxd" when the .service is omitted. Its good that I can get it to work however systemctl enable dropboxd does not work and anytime I restart I have to run systemctl start dropboxd. Any ideas on why this isn't working would be appreciated.
[Edit] tried it again, now I can use the dropboxd.service rather than just dropboxd but it still has the same problem. I actually have to run systemct1 stop dropboxd.service than systemct1 start dropboxd.service everytime I start up to get it running.
Last edited by kc3 (2012-11-02 00:15:38)
Offline
My system is on systemd and dropbox starts no problem using a startup item from gnome-session-properties (command is "dropboxd").
I did get the "connecting..." error (on my laptop, using NetworkManager) so have it check for an active network connection until it starts by using the second script from the wiki.
Two suggestions:
1) check directory permissions as per the wiki
2) what does running "dropboxd" in a terminal reveal?
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | ThinkPad X1 | ASUS ux303ua | Surface Laptop 2 | Minisforum UM780
Offline
Checked permissions already and again as well
when I run dropboxd in the terminal after a fresh reboot it tells me "Another instance of Dropbox (551) is running!" though it's not loaded (not syncing, no icon etc) and I have to actually systemctl stop and start it again for it to work.
[edit] I systemctl disabled it and re-added it into gnome-session-properties and it now works, thanks ![]()
Last edited by kc3 (2012-11-02 00:15:12)
Offline
Pages: 1