in the readme file for the linux distro it says to add an entry to fstab, but it specifies noauto. It only worked for me after I removed that option.

Trading space like mad on linux:

Wuala>tradeStats
Average online time: 29.00%
Current limit: 30 GB
Last update: 16:09
Locally stored data (according to the other users): 4 GB
Earned storage: 8.9 GB
Earned storage is split among 1 users of this computer

But:

Wuala>showQuota
Quota: 3 GB
File Sizes: 88 MB
Base: 1 GB
Friend earned: 1 GB
Node earned: 0 B
Given: 1 GB
Content use: 0 B
List use: 88 MB
Earned: Earned: 0 B from 0 different nodes
Purchased: 0 B

That's linux v119. I restarted the client 1.5 hours ago, logged off and back on - and still the quota does not reflect my trading status. The windows client also doesn't show any increase in quota.

Could you fix that, please? Like that trading is not as rewarding is it could be :-(

(yes, I've seen the "Quota's not updated" question, but it's not yet fixed, so I thought I'd report it as what I think it is: a problem).

linux client: built-in NFS server fails with "cannot create file: unknown error 526" when copying a file with 2097197226 bytes to ~/wuala/...

Client version: v119, quota 3GB, fstab entry:
localhost:/wuala /home/[username]/wuala/direct nfs defaults,users,noauto,rsize=8192,wsize=8192,timeo=14,intr,nolock,soft,nfsvers=3,mountvers=3,port=26184,mountport=26183

Double-clicking at the exact same file on the windows (GUI) client I get "The file has not been completely uploaded. Please try again later or contact its owner".

So it's maybe just an issue with user interaction / timeout: the file is requested to be uploaded but that just takes a while, and the OS tries to tell the user that it hasn't arrived yet. Is that the correct interpretation? Could that be fixed / clarified? I took the fstab entry from your FAQ, so don't blame me for the timeout value :-)

I'm using wualacmd under CentOS and I'm having problems accessing a file on this host (it seems to work fine from others).

When I try to cat the file from the NFS mount I get error "Input/output error" and in the client a few seconds later it gives "Wuala>Problem: java.io.FileNotFoundException: /home/wuala_mnt/wuala/wuala/Data/Local2/Large/979CAC0490BD16645B30A41ADA4671554AF0FF6C"

The file causing this is http://wua.la/Linux+Updates/CentOS/5/... (which is in my public group).

Chris.

It seems I couldn't load wuala under GNU/Linux 64 bits.
I've got an error when I try ./wuala in a console.

The error :
Using config file /home/my_username/.config/wualarc
Updating to version 106 ..................Shutting down...
java.lang.RuntimeException: java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.swt.widgets.Display
at com.wuala.loader.Loader.run(Loader.java:69)
at com.wuala.loader.Loader.main(Loader.java:134)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.swt.widgets.Display
at org.eclipse.swt.widgets.Widget.isValidSubclass(Unknown Source)
at org.eclipse.swt.widgets.Decorations.checkSubclass(Unknown Source)
at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
at org.eclipse.swt.widgets.Shell.<init>(Unknown Source)
at com.wuala.obfuscated.fd.a(Z:407)
at com.wuala.platform.Wuala.launch2(Z:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at com.wuala.loader.starter.ReflectiveWrapper.invoke(ReflectiveWrapper.java:38)
at com.wuala.loader.starter.ApplicationWrapper.launch(ApplicationWrapper.java:19)
at com.wuala.loader.Loader.run(Loader.java:63)
... 1 more
</init></init></init></init>

I'm getting this error with one of the files of a directory I put into Wuala last night. All files from the same directory uploaded correctly (According to the Wuala client on that PC). All Files are basically of the same type (avi videos, around 300 Megs).

The above message instantly pops up when trying to download the entire folder. The other files can all be downloaded successfully.

client: linux 106 (both uploader and downloader)

Since I have updated to alpha v.105 (Linux) I am having problems with my connection. It is o.k. for about a minute and then the status turns to yellow and shortly afterwards to red. After a few minutes I get a good connection again, but then it shuts down again and the whole procedure repeats itself. While the connection is down I can't even ping my wlan-router. After shutting down wuala, it takes about a minute and then I can ping my wlan-router again. I have already turned off the file system integration, but that doesn't do any good.

My wuala doesn't start anymore
I had it running unattended over the weekend and it seems to have choked on the v101 update. Now when I try to start it from the desktop it just does nothing, starting from the console (running "wuala/wuala") just gives me:
Updating to version 101 ............Shutting down...
This is 100% reproducible
on another pc with almost the same setup it starts w/o problems (same gentoo version, intel multicore)

Hmm. Mir ist die letzten drei Tage etwas aufgefallen, dass ein Bug sein köe..

Wuala scheint nach einem restart nur einige Stunden lang Daten in den Fragment2 Ordner zu laden. Lasse ich wuala durchlaufen, zeigt die aktuellste Datei irgendwann eine Changetime so zwischen 6 und 12 Stunden nach den Neustart von Wuala an. Danach werden augenscheinlich keine weiteren Daten mehr geladen.

Gleichzeitig bleibt die Onlinezeit "still stehen". Das Teil lät auf nem rootserv und ist daher immer an, wenn es nicht abstü:) Es ist 2 Tage nach meinem Heimsystem installiert worden. Auf dem linux-System sind nun (seit ca. 3 Tagen in denen ich darauf achte gleichbleibend) 54%. Mein Heimsystem ist bereits bei 68%...

Da stimmt was nicht..
Ich hab mal heute stopTrading/Start Trading eingegeben (ein Tipp aus einem anderen Thread). Mal schaun, ob das etwas bringt. Aber habt bitte mal ein Auge von der Entwicklerseite her darauf.

Die interne IP wird von Wuala stäig falsch abgebildet. Es steht 192.168.122.1 statt 192.168.1.5 da. Dadurch kann weder der Router noch irgend eine andere Verbindung gefunden werden, die einen ordnungsgemän Datentransfer erlaubt. Ein im selben Netz eingebundener Windows Rechner hat kein Problem. Dort klappt auch das UPnP.

MfG,
Rhys

In der auktuellen linux-version scheint sich ein fehler eingeschlichen zu haben. Bisher konnte ich via cp usw files aus dem Netzwerklaufwerk heraus kopieren (lät als nogui). Nun sagt wuala
"java.lang.NullPointerException"
.. ging auch mit dem Befehl feedback raus