Stable Build 30.4.22

This is a Bug Report + Idea

#1 IDEA:

Hey, how about having your "autoupgrader" script test the target platform for dependencies before foisting a lousy upgrade down paying customers throats and breaking their production machines which support millions of users.

#2 Nobody on the production machines uses QT, nor has X access, so why is QT being depended on when no DISPLAY environment is set?

#3 Thanks for forcing GLIBC 2.9 requirements down, 2.9 adds little to no value over earlier and more common 2.6 except minor syntactic sugar.  So of course the autoupgraded dropbox couldnt start in the middle of my testing services for no apparent reason, except after wasting an hour of my time, I discover it's because it doesn't like 2.6 anymore.  So I use our custom 2.9 build, and thats when I discover it complaining about your QT lib too:

ImportError: /root/.dropbox-dist/dropbox-lnx.x86_64-30.4.22/libQt5Core.so.5: undefined symbol: g_main_context_push_thread_default

Why is a commandline instance calling out to QT and then failing?

#4 IDEA

How about stopping telling us about "permission errors?"  The only solution you have is to reinstall, which ultimately wipes the Dropbox directory and wastes our paid bandwidth downloading 200G of data that was already excluded.

I am VERY ANGRY.  This "agile" development method produces software that ranges between awful to absolutely abysmal, filled with halfwit, un-back-tested assumptions that ultimately waste customer time and money.  

#5 IDEA

Hey, how about using multiple virtual machines in different configurations to backtest all platforms at once?  Then your dev team would have instantaneous feedback about what breaks.

#6 IDEA

Hey, how about having the dropbox app report the libraries in use to HQ, so you guys know how many users you're screwing over with each unbaked update.