Recently active topics in Wuala tagged with fail

Delete failed. The error message provided is:
java.lang.NegativeArraySizeException

NOW WHAT?

I cannot upload files to Wuala -> crash
I cannot delete files from Wuala -> crash

I have never seen any program before with so many crashes

Also deleted the "local2" folder and Wuala still keeps uploading
if clicking on "stop all" -> crash

What does "inviting ... failed" mean?
Why? How can I retry again? Why does my message disappear? I have to retype everything now.

Unfortunately my linux box (Fedora) wont start Wuala anymore. I get the following message:

./wuala
Wuala Loader 2008-08-13
No known command found in '-installed'


A few days ago it worked perfectly fine.

the about dialogbox always fails to check for a new version, since many days now. no matter how often the wuala client is being restarted, no matter on what networks the wuala clients runs. no matter if firewall, nat, completely open.....

Ich habe eine große Datei runtergeladen, wollte die kurz nach Beendigung des Downloadvorgangs in einen Ordner auf meinem Rechner kopieren und Wuala fängt an die ganze Datei neu zu laden.
Ziemlich ärgerlich bei ca. 650 mb

In den Dateiinfos steht jetzt auch wieder: Heruntergeladen: 4%.

Grüße Katana

hi there,

lately i get a lot of these errors in the about dialobox (win32, latest builds) on networks with upnp routers when wuala client wants to check if theres a newer build out there...

if i close logout/restart wuala it downloads the latest build anyways even if the check in the about box failed.

would be great if the checking for a new build would be more reliable (maybe other protocol, triggering it directly with a button or a url and so on....)

maybe it has also to do with congested networks (even the local lan or the gateway to the inet), or nat-overloads at the gateway or such thing.

somehow i suspect that the versioncheck is also performed by means of udp rather than a tcp check of a browsing of some url/xml/file because the failed message turns up so very quickly/instantly on the client... there seems to be no timeout or something.

thanks.