You are not logged in.
Maybe you didn't understand what is my problem... that is not running it, but running it at the startup. I already have dropbox from the AUR.
Is there a special reason for which I have to remove all the packages relative to Dropbox, and then re-install dropbox package from the AUR? I will move back to the 1st post of this topic.
Last edited by rdm (2012-06-13 19:19:27)
Offline
Yes. Reinstall from scratch, using makepkg and not some AUR helper like yaourt or some shit.
"Start Dropbox on system startup" will be checked by default and it will create ~/.config/autostart/dropbox.desktop.
You don't need to dick around with anything else.
I'm telling you this because you're getting:
[riccardo@server1 ~]$ which dropbox
/usr/bin/dropboxInstead of:
$ which dropbox
which: no dropbox in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/qt/bin)
$ which dropboxd
/usr/bin/dropboxdAnd like hokasch said, that is not the dropbox package from the AUR. You're getting:
[riccardo@server1 ~]$ ps -ef | grep dropbox
riccardo 811 1 0 12:09 ? 00:00:08 /home/riccardo/.dropbox-dist/dropbox
riccardo 1204 939 0 12:28 pts/0 00:00:00 grep dropboxInstead of:
$ ps -ef | grep dropbox
dspider 9042 765 0 22:18 pts/1 00:00:02 /opt/dropbox/dropbox
dspider 10678 765 0 22:25 pts/1 00:00:00 grep dropboxI have no idea what you installed. "/home/riccardo/.dropbox-dist/dropbox" ?
Are you even running Arch Linux or are you just trolling?
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
I am very confused by this thread...
Are you just wanting to delay the start of dropbox until after you get an internet connection?? Thats what I gathered from your first post, if so you the 'sleep 30 && dropbox'
Offline
Removed all dropbox packages; deleted all the "shit" I made; re-installed dropbox package from the AUR; checked the start option in the Dropbox preferences window. It runs automatically at boot, but when Internet is up, it is still trying to connect.
We got back to the first post. What shall I do now? ![]()
Last edited by rdm (2012-06-13 20:35:32)
Offline
$ pkill dropboxd
$ dropboxd &If you still have a gray icon, check the account. See if you can log in from https://www.dropbox.com and that you use the same username and password for the Dropbox client.
And set the proxy settings to "No proxy" from the Preferences menu.
Last edited by DSpider (2012-06-13 20:56:35)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
What happens if you quit it once, then start it again? Does it connect?
I say this because I have the same problem when I'm using the broadband at home, but it works flawlessly at my college. So maybe it's an issue with the internet connection and not dropbox...
Offline
I can sign in with my account both on https://www.dropbox.com/ and with my dropbox application. Infact I can successfully connect if I kill dropbox, which started at login, and then I re-run dropboxd. I really don't know why if I run it manually, then it wait for an Internet connection and then sign me in; if run at login, instead, it's always connecting.
However, I set "No proxy" in the preferences window; before, in the "Account" preferences, I had also clicked on "Unlink This Computer" and I'd re-done all the set up for my account. With all this stuff, everything is like before.
So maybe it's an issue with the internet connection and not dropbox...
Really? Can you explain better? Perhaps that may be my case, though I don't hope so very much... ![]()
P.S. Sometimes, when I manually type "dropboxd &" and the connection is quite low, like this
[root@server1 riccardo]# iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:"xxx"
Mode:Managed Frequency:2.437 GHz Access Point: xxx
Bit Rate=1 Mb/s Tx-Power=19 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:xxx
Power Management:off
Link Quality=36/70 Signal level=-74 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:3 Invalid misc:22 Missed beacon:0, dropbox is always on "Connecting...", just as when it run at login.
Last edited by rdm (2012-06-14 08:44:56)
Offline
Ok, so it's a wireless connection... Try wicd.
Also: https://wiki.archlinux.org/index.php/Be … tc.2Fhosts
Errors in this entry may cause poor network performance and/or certain programs to open very slowly, or not work at all. This is a very common error for beginners.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
There is an old bug with dropbox failing to connect if there is no internet connection
when it starts (hence the tips in the wiki). Dropbox bugtracking is horrible, no idea if it was ever fixed properly.
The simplest workaround you can try is to go into gnome-session-properties and replace the dropbox entry with e.g. "sleep 60 && dropboxd" to delay dropbox startup. Or use the post-connection hooks (nm/wicd dispatcher scripts, netcfg's POST_UP) to start dropbox.
PS: what happened to all your different dropbox installs. Did you find out how the one in dropbox-distro started? And how did the /usr/bin/dropbox happen, can you check with pacman -Qo what package owns it?
Last edited by hokasch (2012-06-14 11:25:51)
Offline
And how did the /usr/bin/dropbox happen, can you check with pacman -Qo what package owns it?
[riccardo@server1 ~]$ pacman -Qo /usr/bin/dropbox
/usr/bin/dropbox is owned by dropbox-cli 1-12Well, here's what I did:
I unchecked the start option in the Dropbox preferences window, and then I installed dropbox-cli. My idea was to create a Bash script (drop.sh) which will start in the background at my login: it will check for an Internet connection and then, if dropbox won't be running, it will run that. The script is:
#!/bin/bash
while true; do
ping -c 1 www.google.com > /dev/null 2>&1
if [ "$?" = 0 ]; then
dropbox status | egrep 'isn|Connecting' > /dev/null 2>&1
if [ "$?" = 0 ]; then
dropbox stop > /dev/null 2>&1
dropbox start > /dev/null 2>&1
fi
fi
sleep 2 > /dev/null 2>&1
doneNow, the strange thing is that the script works, except when it runs at login. When I type "drop.sh &" (which is in ~/scripts, included in my PATH) the script does all I told it to do, whether it's run before or after an Internet connection: it will always wait. But normally it should run at login; in fact here's ~/.bash_profile :
#
# ~/.bash_profile
#
[[ -f ~/.bashrc ]] && . ~/.bashrc
drop.sh &
if [[ -z $DISPLAY ]] && ! [[ -e /tmp/.X11-unix/X0 ]] && (( EUID )); then
xinit
fiWhen GNOME starts, I can see the dropbox icon in the notification area, and it says "Connecting...". But when I connect to the Access Point, and once I've run dhcpcd and Internet is up... the icon disappears! ![]()
Thus every time I check what is happening, every time I get:
[riccardo@server1 ~]$ dropbox status
IdleWhat???
![]()
What is 'Idle'? Oh no, it seemed so perfect... ![]()
Offline
Well, here's what I did:
[...]
But you removed your script from bash profile in the meantime, right? To run dropbox as daemon you should probably use this.
Anyway, for the functionality you want the only thing you should have installed from AUR is dropbox. Make sure everything else (dropbox-cli, any custom entries in bahshprofeil/rc.conf etc) is removed. Try with the sleep command to delay dropbox start. If that fixes your problem, a better workaround would be using dispatcher scripts. There is even one in the Aur (for networkmanager) which should get you started.
Offline
For my second time just use the sleep method. Save your self the headache.
'sleep 35 && dropboxd' in the Gnome sessions or in your .xinitrc. <-- Don't use gnome so I'm not sure the later will work.
┌─[jarvis][watson][~]
└──╼ cat .xstart
sleep 35 && dropboxd &
wicd-client --tray &
mpd &
awesome^^ Works everytime. ![]()
Last edited by doug piston (2012-06-14 22:39:43)
Offline
Save your self the headache.
Well, actually I don't know why you tell me to "sleep" when I can't know if I'll connect in 30, 60, 120 seconds...
Even because I have a wireless connection, and I manually connect to the AP (I've tried to install wicd to connect automatically: what a disaster! After installed and done the first reboot, my wireless card wasn't able to see any wireless AP at all! I had to remove it). Thus, if anyone could explain me how to do all this automatism...
To run dropbox as daemon you should probably use this.
Doesn't work. I installed the package, rebooted the system and... nothing. Then I also tried to add "dropboxd" to the DAEMONS array in /etc/rc.conf and... nothing; or better, in the second case I see that /opt/dropbox/dropbox is running, but there isn't the icon in the GNOME notification area, and neither when I connect to the Internet it works (even though I set up the configuration file /etc/conf.d/dropbox.conf as this one:
# The user that the Dropbox binary will run as (usually your system user account)
DROPBOX_USER='riccardo'
# The path to dropboxd (usually /usr/bin/dropboxd)
DROPBOXD_PATH='/usr/bin/dropboxd'
# Path to the real Dropbox binary (usually /opt/dropbox/dropbox)
DROPBOX_PATH='/opt/dropbox/dropbox'Perhaps I haven't understood well how to let dropbox-daemon work as it should...
Last edited by rdm (2012-06-15 09:45:22)
Offline
Anyway, for the functionality you want the only thing you should have installed from AUR is dropbox. Make sure everything else (dropbox-cli, any custom entries in bahshprofeil/rc.conf etc) is removed.
Perhaps I haven't understood well how to let dropbox-daemon work as it should...
?!
Dont use that daemon package. Remove everything dropbox related. Install 'dropbox', and only 'dropbox' from aur. Dropbox never connecting if it is started without an active net connection present should be considered a bug. Take it upstream (good luck with that though as last time I checked they did not use a bugtracker).
If you connect automatically at startup, try with the sleep workaround and see if it fixes your issue. As has been mentioned a dozen times now in this thread and in the linked forum search, you can start dropbox automatically after you connect to the internet. How that will work out in practice depends on how you connect to the net...
Last edited by hokasch (2012-06-15 11:06:31)
Offline
Thus, if anyone could explain me how to do all this automatism...
wicd-cursesScroll to the network of your choice arrow to your right once and select 'Automatically connect to this network.' If setting up wicd was a nightmare...
Offline
I did it at last!
![]()
Simply with this script
#!/bin/bash
while true; do
ping -c 1 www.google.com > /dev/null 2>&1
if [ "$?" -eq 0 ]; then
pgrep dropbox*
if [ "$?" -eq 1 ]; then
dropboxd > /dev/null 2>&1
fi
fi
sleep 2 > /dev/null 2>&1
donerun from gnome-session-properties. ![]()
Thanks to all of you, of course! ![]()
Offline
Don't forget to mark it as solved (by editing the first post).
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline