Hi, I am not sure when this began happening but after a recent update I believe, dropbox is no longer syncing. It just gives the message “starting” and hangs there if I do dropbox-cli status. If I start from the command line, it loads fg extensions until it reaches the line
It just hangs there at that point. Thanks in advance for any help. I will provide inxi output in a reply.
I tried a number of different fixes, including deleting .dropbox and .drobbox-dist as well as following the uninstall instructions at the dropbox site.
It also fails when installed as a flatpak through bauh.
I have run yay -Syu dropbox dropbox-cli nemo-dropbox and chosen the clean build option but I am trying with your options right now. thanks for the quick answer.
I then ran yay $(pacman -Qoq /usr/lib/python3.10) --rebuild
this ran with no screen output, which in yay often means nothing happened. Was there supposed to be output showing what was being done?
Since neither of those had an effect, I am holding off for the moment on cleanbuilding everything else because everything else is still working. I am fairly familiar with the AUR. I didn’t mention it explicitly because I posted in the AUR section of the board.
I have cleaned out cruft and rebuilt my whole installed AUR.
I ran a modification of the command you gave overnight. I modified my sudo time out from five minutes to 3600 minutes and ran the command as follows to be mostly but not quite unattended:
yay -Sua $(pacman -Qmq) --rebuild --noprovides --answerdiff None --answerclean All --mflags --noconfirm
it went overnight and then some.
I manually fixed or removed anything that kicked up errors.
Just for good luck I rebooted at that point. Everything up to date in main repos and foreign.
All the programs that worked are now rebuilt but dropbox still hangs at the line:
yay -Sua $(pacman -Qoq /usr/lib/python3.10) --rebuild
This time it kicked up a list of 359 items to rebuild, the vast majority of them in the main repos and about a dozen in the AUR. Dropbox was not one of the programs in this list. I did not and probably will not execute this command as it looks like a system-borking thing to do, and the system works except for Dropbox. Going through that list, I did find the following which seems to be related to the fg extension Dropbox hangs on:
Python has not upgraded to 3.11 yet, which @ cscs thought was the case, which is probably why the command output 359 programs:
rich[~]$ python --version
Python 3.10.10
Is Dropbox looking for 3.11 maybe?
Finally, I downgraded Dropbox to the March 30 snapshot in the AUR GitHub to restore a version that I know was working at that time. Same error with it hanging on “starting” and the last thing to happen was loading fg extension PyQt5.QtDBus.so.
Pretty stumped by this, the only thing that seems sure is that it is something to do with python qt5 and dbus rather than Dropbox itself. I do need to get Dropbox running again, so any further insights would be welcome.
Are you up to date?
All the above was assuming you were and on a branch other than stable.
If you are on stable then yes … python is still 3.10.
(seeing your profile … it appears you are on Stable branch)
Make sure to run first:
sudo pacman -Syu
Or … in the case of needing to sort mirrors:
sudo pacman-mirrors -f8 && sudo pacman -Syyu
But … to get back to the branch thing.
This is likely the cause of your error in the first place … the AUR is targeted at Arch … manjaro stable, especially at times like right now … is rather behind. So incompatibility with some of the AUR is expected. When the next major update (and python 3.11) come then you should be able to interact with it more normally for a time. Of course this and you would be better served by using another branch if you intend to use the aur … and apparently so profusely.
I have had problems with the unstable branch that led to reinstalls. I have been using Manjaro since pretty much the day it came out, and use the aur in such a way that if something fails there I can generally fix it delete it or wait. Dropbox is an exception to that in that it is pretty much a requirement for my work, so having it fail is a must fix. I can get by for a little bit by backing up locally until I get it fixed, since I am done with going into work for the summer and fall (yay, sabbatical!) and can get things to Dropbox manually if I need to. I have this mentioned at the AUR too to see if anyone else is having the problem, but I am at risk there of getting my head bit off if they figure out I’m on Manjaro! I guess I’ll wait to see what happens next release. Thanks for the help.
There’s an option for that. I also use batch install.
--sudoloop
Loop sudo calls in the background to prevent sudo from timing out during long builds.
--batchinstall
When building and installing AUR packages instead of installing each package after building, queue each package for install. Then once either all
packages are built or a package in the build queue is needed as a dependency to build another package, install all the packages in the install queue.
