ClearFoundation Tracker - ClearOS
View Issue Details
0012881ClearOSapp-dropbox - Dropboxpublic2017-02-01 13:252017-05-03 08:30
trialanderror 
bchambers 
normalblockalways
closedfixed 
7.2.0 
7.3.1 Updates 
0012881: Only 1 user can link and synchronize
After linking one account with dropbox with the problems described in issue 0012871 no other user can link to its account due to the message "Dropbox service is busy initializing another user."

Waiting for days has no effect, rebooting the machine has no effect.

If you uninstall/install the dropbox-app another user will be able to link but the first has lost its link of course...

Here is the output of the service status
(/var/run/dropbox.pid does not exist):

[root@clearos7 ]# systemctl -l status dropbox.service
? dropbox.service - LSB: start and stop dropbox
   Loaded: loaded (/etc/rc.d/init.d/dropbox)
   Active: activating (start) since Mi 2017-02-01 21:19:23 CET; 1min 37s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 12510 ExecStart=/etc/rc.d/init.d/dropbox start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/dropbox.service
           ??12526 /mnt/daten/home/test-s/.dropbox-dist/dropbox-lnx.x86_64-18.4.32/dropbox /newerversion test-s

Feb 01 21:19:23 clearos7.test.local systemd[1]: Starting LSB: start and stop dropbox...
Feb 01 21:19:23 clearos7.test.local runuser[12511]: pam_unix(runuser:session): session opened for user test-s by (uid=0)
Feb 01 21:19:23 clearos7.test.local dropbox[12510]: Starting dropbox[ OK ]
Feb 01 21:19:23 clearos7.test.local systemd[1]: PID file /var/run/dropbox.pid not readable (yet?) after start.
No tags attached.
related to 0012911closed bchambers Migrate to systemd with per user unit file: 
Issue History
2017-02-01 13:25trialanderrorNew Issue
2017-02-02 04:05bchambersRelationship addedrelated to 0012911
2017-02-03 13:16bchambersAssigned To => bchambers
2017-02-03 13:16bchambersStatusnew => acknowledged
2017-02-03 13:17bchambersStatusacknowledged => confirmed
2017-02-03 13:17bchambersStatusconfirmed => resolved
2017-02-03 13:17bchambersFixed in Version => 7.3.1 Updates
2017-02-03 13:17bchambersResolutionopen => fixed
2017-05-03 08:30user2Statusresolved => closed

There are no notes attached to this issue.