Under "Trade Storage" in the Options window, the average online time is not not updated until you save the options. This means to check your average online time you need to open the options windows, save the options (which closes the window), and open the window a second time. It was also extremely confusing as a new user because I never saw my online time increasing, which made me frustrated because I thought I'd never hit the 17% needed to share storage.
iTunes changed a file, Wuala displayed a dialog saying it failed to upload that change and now file is lost because it was supposedly never completely uploaded. The dialog stated the file was not in /tmp but I certainly didn't remove it.
This isn't the first time this has happened to me and it certainly wouldn't be a problem if I was allowed to mount readonly. (I'm on OSX 10.5.4)
I'm really starting to not like your product because of this continuing problem. I'm sure iTunes is doing something weird but you should certainly handle it.
Unter osx (10.5 aktuell) sind Dateien im nfs-mount die Umlaute oder Sonderzeichen enthalten tote links. Man kann auf die nicht direkt üas nfs-volume zugreifen.
.. Die Dateien werden mit ihrem Namen bis zum Umlaut angezeigt und "verschwinden" bei einem Klick drauf.
Und debian werden die Umlaute oder Sonderzeichen zwar als Fragezeichen angezeigt, aber man kann trotzdem zugreifen.
Ich bin mir jetzt nicht sicher, ob das ein osx-Problem ist mit allen nfs-volumes ist. Ich hatte nur den Eindruck, dass es ein paar Versionen früoch nicht so war. Da kann ich mich aber komplett irren. :D
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.
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 ...
sometimes wuala is missing its tray icon (win32). sometimes when auto-logon to windows xp (for example autologin with tools like powertoys/tweakui) is activated, the wuala trayicon cant be created/registered as the traybar (explorer.exe components or such) havent been started yet.
im not into win32 api details, but i think i remember that with at least winxp and later windows builds new methods and calls have been implemented into windows to recreated/redraw/register the tray icons and tray-related stuff in case explorer.exe / desktop crashes or restarts and things like that.
please make wuala work properly with the windows tray area or at least add a real quit/shutdown icon on the wuala logon window, as wuala can only be exited properly with rightclick on the traybaricon and "exit" there for example when wuala is logged out. when the traybar icon is missing, there is only the really unclean and hardcore killing way of the wuala.exe process left for quitting wuala, which isnt really nice i suppose.
also, wuala doesnt react properly to wm_quit message that i tried to send with process.exe tool from beyondlogic guys.
C:\>process -q wuala.exe
Command Line Process Viewer/Killer/Suspender for Windows NT/2000/XP V2.03
Copyright(C) 2002-2003 Craig Peacock beyondlogic org
Sending PID 832 'wuala.exe' WM_CLOSE Message. Timeout is 60 seconds.
wuala.exe (PID 832) failed to respond to WM_CLOSE. Terminating Now.
Sending PID 832 'wuala.exe' WM_CLOSE Message. Timeout is 60 seconds.
wuala.exe (PID 832) has been closed successfully.
so maybe you guys can add proper wm_close message handling of the wuala main app, or fix the traybar/trayicon handling or add a real shutdown/exit function also to the logon-window or the main wuala window too.
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.
Woala states that it is offline. The Computer is definitifly online (I'm writing right now on it) Also the connection check gives the responses mentiont further down. Restarting wuala does not help.
Connection check:
Prürbindung...
Externe Adresse gemä Server A: /85.181.xx.yy:7516
Externe Adresse gemä Server B: /85.181.xx.yy:7516
/85.181.xx.yy:7516 akzeptiert eingehende Verbindungen.
Congratulations, your connection is suitable for trading storage!
For most image files, when I attempt to start download. I get an error dialog that says: "java.lang.OutOfMemoryError: Java head space". During the first 30 minutes or so I didn't have this problem.
They're all rather small files, being images. Restarting wuala doesn't help. increasing the limit for memory jvm can use from 256 to 512 makes no difference.
According to top (and gexmap) wuala is only using 77 megabytes of memory. There is also nearly 1GB of memory "free" so that can't be a problem either.
I'm running wuala alpha linux 65 on a debian testing system with java installed from sun-java6-jre package.
> java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode)
Update: The problem seems to occur on images, not on music or videos. Some images seem to work. I can't figure out a pattern though.
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?
I'm using Wuala now for a week. I'm getting the status "Online", no problem, but only the yellow one. Sometimes, very rare, it gets the green one. But that happen maybe two times since i downloaded Wuala.
It's not able to connect with the external IP and if i try to test it, I'm only get this result:
Prürbindung...
Problem: Could not contact ping server A
Port is forwoarded on my router and i'm not using any firewall! Someone may has an idea??
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.
Hello community,
Im using wuala now about a week and this tool is very great. I use it to Backup my personal Data such as pictures.
However, I have a Problem when im uploading many files. During the uploading process does wuala suddenly stop to upload the file and i have to press the button pause to stopp the uploading process for the File. Afterwards wuala starts to upload the other Files.
This situation did now happen 4 times to me and i think it is a bug in the product.
Is this already a known bug?
Thanks for Feedback.
Sorry for my grammer misteacks ;)