hi there,

a main problem with the wuala project as whole is, that there is far too little information on technical details, far too little documentation and real information given by the developers.

people often wonder why the wuala software behaves this or the other way, search for solutions that are sometimes no real problems if the behaviour would be properly documented.

i started up some older build (winxp) wuala client after a while of downtime and it upgraded itself.
after logging in to the wuala network (username) the wuala client now works heavily on the wuala database files in probably reoganisation tasks (fragmentsxx.db and COMP-fragmentsxx.db files being messed with the whole time)

anyways so it literally took ages for this client to finish, and the connection status icon was yellow all the time. only after a long while, and when finally the insane diskactivity has finished, the connection status icon went green again.

ctrl+alt+d _shownetworkstats displayed that it wasnt connected to any supernodes during this period, hence the yellow icon i presume.

what makes me wonder if this is a neccessary behviour, that the client cant properly connect to the network until its finished with its database overhaul. maybe some multithreading designs could help, or maybe its just really the need to bring the database into a consistant and up-to-date state again before being able to add and fetch chunks of data again to and from it.

it would really be great if the wuala team could document its piece of software much more in detail.

Cosmetic issue:
From the FS integration check dialog you cannot read that some checks might take a while to....
http://wua.la/iwein/Images/screenshot...

This is on Ubuntu 8, Gnome

setTradingLimit seems to have a problem (Version Linux v126):

Usage: setTradingLimit AMOUNT_IN_GB (max. 100 GB)
Wuala>setTradingLimit 500GB
Problem: For input string: "500GB"
Shutting down...
Commandline Ended, cause java.io.InterruptedIOException

(I know I was stupid, but wuala should not exit just because a cast returns a null pointer. :)

I can't add anyone as a friend. I always get this error:
http://wua.la/nmat/Documents/public/t...

I tried this both on windows and mac. Any ideia?

Some few Versions ago I noticed that it is no longer possible to put pictures on (private) groups - why?

hi there,

apparently there is a new feature during startup, named database cleanup. defragmentation of the datastorage or such.

interestingly i have never seen this window up til now, but it comes up during every restart of the wuala client (win32, b446).

is this the normal behaviour?

ich habe eine gruppenanfrage bekommen für eine gruppe in der ich kein mitglied bin.

wua.la/wxi_/gruppenanfrage

hi there,

some while back i inserted an openoffice file into the wuala datastore.

somewhen later i edited the file with openoffice. then saved it inside openoffice. the file in the wuala data store has the new content and changes. but the timestamp in the wuala gui (win32) still shows the original filedates and timestamps for both inserted and last modified.

bug? fix? thanks.

hallo,

hab das ganze zwar schon als frage gepostet aber nun wächst es sich langsam zum problem aus:

trotz der meldung
'... akzeptiert eingehende Verbindungen.
Gratulation, Ihre Verbindung ist für das Tauschen von Speicherplatz geeignet!'
fällt der graph unter den 'schwellenwert' auf 16 % online-zeit und das macht mich sehr traurig ... war ja schon fast bei 22 % ... nun ist seit tagen das speicher-tauschen nicht mehr möglich.
es ist mir ja auch möglich durch die wuala-welt zu surfen, daten rauf- und runterzuladen ...
bin also 100%ig online! trotzdem sinkt der online-graph gleichbleibend seit tagen stetig gen keller ...

help blees!

hallo people,
i have a problem and that is that when I start Wuala it connects to my account and than i get an error message and i can not start the porgramm. Do someone know what I can do to fix this problem?

Wuala stopped working after I just installed the very latest version of Java, JRE 6u6, and crashes right away at startup with a "NoClassDefFoundError".

I've sent the error report.

hi there,

during my recent upload tests via filesystem integration method (see other thread http://getsatisfaction.com/wuala/topi... ) i somewhen realized that there are hugeloads of files in %temp%\wuala\ which wasnt the case in former builds of wuala.

there are also two directories in there (download and upload)

in the actual %temp%\wuala\ folder there seem to be a very big number of "original" files which i was trying to upload into the wuala store it seems.

the filenames have been changed somewhat to

hexnumber-originalfilename.extension

example:
f3edab22-mypicture.jpg
(hexnumber is maybe some hash/crc/crc32 or something)
the files are unencrypted, so i can actually use them with the appropriate application as they all hold the actual data (pictures, and so on....)

is this some bug? anyway related to my other thread? i suppose this is a huge security risk as even with reboots, wuala clients shutdown/restart these folders dont seem to go away or dont get empied nor cleaned up and the files can be seen by "anybody" who has access to the physical machine.

this is really weird. anyone else having this behaviour? win32/winxp that is. wuala426

lately i have experimented with wuala and fileintegration on win32 (xp) and latest wuala builds (426). i was copying whole cd contents (different files, loads of folder structures) into a semi-private (group/friendshared(only 1 friend as an example/test)) to the wuala network drive (w: for example).

the copying went normally, but only some days after (this happened first some days ago, but i verified it today with other content (CDs)) i realized that the uploaded wuala content of the folder i copied the files into wasnt exactly the same as my original sources. some bytes/megabytes were missing, and i tracked down some of the files/folders that were created but only with filesize=0 (zero), or were missing completely.

i was copying the stuff with the help of total commander, so not the basic builtin explorer.exe functions, nor commandline copy stuff...

i might try some more of this stuff at a later time.

the missing/incomplete files dont seem to follow any certain rules or patterns, there are simply some folders that are completely identical/complete and some files are missing or come with zero size.

totalcommander never complained that it couldnt write to w: or anything else like that.

i was manually looking for the differences, found the missing/incomplete files and was overwriting the files on the wuala store again.

after these second tries and overwriting procedure the wuala store was eventually finally complete and identical to my source material.

i guess that some of the queues in the wuala client, the pending transactions, the chunk-creation and distribution or related functions and parts of the wuala client program are still lacking robustness.

please take a look at this and do your own tests with lots of files/folders and different objectsizes.
thanks.

When you have Fusion running on the Mac, there are 2 extra network interfaces: vmnet1 and vmnet8. For some reason, Wuala is using these as the origination IP address instead of using en0/en1 depending on which one is up.

How can I kick Wuala into using the current default IP interface?

Thanks,

Wout.

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)

It happens each time i start Wuala with the 424 build.

Build: WualaPC 424
App: Domain Application, user: Protoss
(Data Application, prim id: 190.16.0.3, ip: /24.30.152.85:9008 (global)
(Common Application Alpha WualaPC 424))
Date: May 12, 2008
OS: Windows XP 1.6.0_05 Sun Microsystems Inc.
Memory: 331 MB max 14 MB free 86 MB total
Local Host: q6600/192.168.1.115
Running for: 2min 40s

Exception: java.lang.Exception: com.wuala.common.exception.ApplicationRuntimeException
at com.wuala.obfuscated.nk.a(Z:169)
at com.wuala.common.exception.ApplicationRuntimeException.createReport(Z:62)
at com.wuala.obfuscated.RS.<init>(Z:30)
at com.wuala.obfuscated.fa.a(Z:286)
at com.wuala.obfuscated.fa.a(Z:160)
at com.wuala.obfuscated.fa.a(Z:117)
at com.wuala.platform.Wuala.launch(Z:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.wuala.starter.ReflectiveWrapper.invoke(ReflectiveWrapper.java:38)
at com.wuala.starter.ApplicationWrapper.launch(ApplicationWrapper.java:19)
at com.wuala.starter.WualaStarter.startWuala(WualaStarter.java:117)
at com.wuala.starter.WinWualaStarter.startWuala(WinWualaStarter.java:88)
at com.wuala.starter.WualaStarter.run(WualaStarter.java:35)
at com.wuala.starter.WinWualaStarter.run(WinWualaStarter.java:76)
Caused by: com.wuala.common.exception.ApplicationRuntimeException
at com.wuala.obfuscated.aea.uncaughtException(Z:21)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.Thread.dispatchUncaughtException(Unknown Source)
Caused by: java.lang.NullPointerException
at com.wuala.common.rmi.exception.RemoteException.isTreatAsConnectionProblem(Z:105)
at com.wuala.obfuscated.q.a(Z:60)
at com.wuala.obfuscated.Tz.HK(Z:113)
at com.wuala.obfuscated.CM.xG(Z:144)
at com.wuala.obfuscated.CM.run(Z:126)

--------------------------------------------

com.wuala.common.exception.ApplicationRuntimeException
at com.wuala.obfuscated.aea.uncaughtException(Z:21)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.Thread.dispatchUncaughtException(Unknown Source)
Caused by: java.lang.NullPointerException
at com.wuala.common.rmi.exception.RemoteException.isTreatAsConnectionProblem(Z:105)
at com.wuala.obfuscated.q.a(Z:60)
at com.wuala.obfuscated.Tz.HK(Z:113)
at com.wuala.obfuscated.CM.xG(Z:144)
at com.wuala.obfuscated.CM.run(Z:126)

--------------------------------------------

java.lang.NullPointerException
at com.wuala.common.rmi.exception.RemoteException.isTreatAsConnectionProblem(Z:105)
at com.wuala.obfuscated.q.a(Z:60)
at com.wuala.obfuscated.Tz.HK(Z:113)
at com.wuala.obfuscated.CM.xG(Z:144)
at com.wuala.obfuscated.CM.run(Z:126)

Thread: Main Thread</init>

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.