Unanswered problems in Wuala

Nach der ersten Installation wollte ich das mit Skype verbinden, aber das stürzt ab.
Der Fehlerberichtssendendialog stürzt mit ab, so dass ich euch das leider nicht schicken konnte.

Und danach startet es garnicht mehr.



Wenn ich das MacBook neustarte, geht es wieder, bis ich es nochmal mach, mit Skype.

Ich habs jetzt neu installiert und nix mit Sjype gemacht, und jetzt gehts.


Wuala Absturz auf OS X mit Skype from davidak on Vimeo.

Oder hier:
http://wua.la/davidak/Public/Wuala+Ab...

Das mögt ihr bestimmt lieber :D

Und so sieht das dan aus.
Bei Vimeo gibts auch mein Original Video in 1280x1024.

Falls jemand interessiert, was ich auf dem Desktop hab.

HAR HAR

Ich hab ein Problem bei der Installation...
Das kommt sofort nach diesem "Ausführen" - Datei-Öffnen-Sicherheitswarnung Fenster...
Mein Betriebssystem: Vista 64 Bit
Aktuellste Java Version ist installiert.

I tried to install wua.la on a laptop with only 800 mb free space on C: (win xp), wua.la complains and tells me I should set the working directory to another drive with more free space.
When I set it to D: (which has > 20 gb free space) wua.la asks for a restart and I accept. When wua.la restarts, it simply forgets the new setting, starts complaining about space on C:
I can't seem to change anything about it

I was invited to Wuala on Friday. I invited a few friends of my own as well, but between Friday and Sunday I got numerous blue screens of death on my Win XP machine while Wuala was running and uploading my files. I turned Wuala off and the problem disappeared, but then so did my use for Wuala. The blue screen of death error message made these references:

*** STOP: 0X0000008E (0XC0000005, 0XBA448C5A, 0XB37418FC,0X00000000)
*** TDI.SYS - Address BA448C5A base at BA448000, DateStamp 41107d33

Have you seen this before?

Thank you,

Gabi

Bei der Installation auf einem Laptop mit XP verschwindet das signin-Fenster, bevor ich Eingaben machen kann. Installation wird nicht komplett ausgeführt. Firewall ist hierrür sogar ausgeschaltet.
Auf einem Desktop funktioniert alles einwandfrei. Kann also nicht mit dem Netz oder Router zu tun haben.

Wuala crashes after some seconds.
This error comes up:

Closed by user

Build: PC 68

App: Domain Application, user: xxx

(Data Application, prim id: 240.38.0.2, ip: /xxx (bad, mediated over /xxx)(confirmed)

(Common Application Alpha PC 68))

Date: 21.07.2008

OS: Windows XP 1.6.0_03 Sun Microsystems Inc.

Memory: 248 MB max 32 MB free 49 MB total
Local Host: xxx
Running for: 1min 1s

Exception: java.lang.Exception: com.wuala.common.exception.ApplicationRuntimeException: Closed by user

at aV.e.a(Z:178)

at com.wuala.common.exception.ApplicationRuntimeException.createReport(Z:65)

at com.wuala.obfuscated.w.<init>(Z:34)

at com.wuala.presentation.q.b(Z:392)

at com.wuala.presentation.q.a(Z:264)

at com.wuala.presentation.q.a(Z:103)

at com.wuala.platform.Wuala.launch(Z:16)

at com.wuala.loader2.Loader2.startInstance(Loader2.java:65)

at com.wuala.loader2.Loader2.start(Loader2.java:53)

at com.wuala.loader2.Loader2.main(Loader2.java:116)

Caused by: com.wuala.common.exception.ApplicationRuntimeException: Closed by user

at com.wuala.obfuscated.R.a(Z:235)

at com.wuala.obfuscated.R.execute(Z:1)

at gnu.trove.TIntObjectHashMap.forEachEntry(TIntObjectHashMap.java:430)

at com.wuala.obfuscated.ac.R(Z:244)

at com.wuala.obfuscated.W.a(Z:241)

at fT.a.GQ(Z:151)

at fT.b.doRun(Z:66)

at aH.d.run(Z:34)

Caused by: quickbase.exception.DatabaseClosedDatabaseException: Closed by user

at quickbase.SingleMapDatabase.closeDB(SingleMapDatabase.java:379)

at com.wuala.obfuscated.ac.c(Z:166)

at com.wuala.obfuscated.X.a(Z:47)

at com.wuala.obfuscated.W.a(Z:127)

at fT.a.GQ(Z:140)

... 2 more

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

com.wuala.common.exception.ApplicationRuntimeException: Closed by user

at com.wuala.obfuscated.R.a(Z:235)

at com.wuala.obfuscated.R.execute(Z:1)

at gnu.trove.TIntObjectHashMap.forEachEntry(TIntObjectHashMap.java:430)

at com.wuala.obfuscated.ac.R(Z:244)

at com.wuala.obfuscated.W.a(Z:241)

at fT.a.GQ(Z:151)

at fT.b.doRun(Z:66)

at aH.d.run(Z:34)

Caused by: quickbase.exception.DatabaseClosedDatabaseException: Closed by user

at quickbase.SingleMapDatabase.closeDB(SingleMapDatabase.java:379)

at com.wuala.obfuscated.ac.c(Z:166)

at com.wuala.obfuscated.X.a(Z:47)

at com.wuala.obfuscated.W.a(Z:127)

at fT.a.GQ(Z:140)

... 2 more

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

quickbase.exception.DatabaseClosedDatabaseException: Closed by user

at quickbase.SingleMapDatabase.closeDB(SingleMapDatabase.java:379)

at com.wuala.obfuscated.ac.c(Z:166)

at com.wuala.obfuscated.X.a(Z:47)

at com.wuala.obfuscated.W.a(Z:127)

at fT.a.GQ(Z:140)

at fT.b.doRun(Z:66)

at aH.d.run(Z:34)

Thread: main</init>

Wua.la keeps downloading a phantom file. I don't have any file in the "downloading" view and I can't seem to cancel it. Already rebooted and restartet wua.la :-/

follow wuala install instructions for linux, then when starting the client, do:
./wualacmd
(wuala starts, updates to current revision)
./wualacmd help
(wuala connects to running instance which displays help output)
./wualacmd login username password
(ofcourse use real user name and real password)
(Does just return to command line)
ps auwxf
(shows 2 java processes with wuala, one with the login command line, one without)

this state doesn't change for several minutes unless TERM signal sent to java process.
if wuala is not terminated every other command results in "socket already in use"

see also "Configuring wuala on headless linux server impossible"

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.

timemachine crashes while copying wua.la cache:

14.07.08 16:50:21 /System/Library/CoreServices/backupd[2826] Error: (-36) copying /Users/Shared/WualaSharedData/Data/Local2/Large/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to (null)
14.07.08 16:50:21 /System/Library/CoreServices/backupd[2826] Error: (-36) copying /Users/Shared/WualaSharedData/Data/Local2/Large/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to /Volumes/Samsung/Backups.backupdb/Imotep/2008-07-14-025115.inProgress/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Macintosh HD/Users/Shared/WualaSharedData/Data/Local2/Large
14.07.08 16:50:21 /System/Library/CoreServices/backupd[2826] Stopping backup.
14.07.08 16:50:21 /System/Library/CoreServices/backupd[2826] Error: (-8062) copying /Users/Shared/WualaSharedData/Data/Local2/Large/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx to /Volumes/Samsung/Backups.backupdb/Imotep/2008-07-14-025115.inProgress/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/Macintosh HD/Users/Shared/WualaSharedData/Data/Local2/Large

(i replaced all hashes with xxxx )

After i delete /Users/Shared/WualaSharedData/Data/Local2 i was able to finish my backup.

Today I cleared my cache and all of my files were gone, too. That's bad, because my own files get maintained rather regulary, and when they're gone from my account, who guarantees me that my whole file can be reconstructed from the pieces that are in the wild.

so there should be 2 "clear cache" buttons. one for the things i uploaded and the other one for the stuff i downloaded from others. I need the second type of button 1000 times the occasions iI need the first type

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.

Server nicht gefunden... am Montag 30.6. ca 5pm!

Safari kan de server niet vinden.
Safari kan de pagina 'http://s3.amazonaws.com/WualaMAC/wuala_mac_alpha.dmg' niet openen omdat de server 's3.amazonaws.com' onvindbaar is.

Ich habe auf meinem System (XP) das Problem, dass es trotz ausreichendem Speicherausbau nach dem Öffnen relativ vieler Browser-Fenster irgendwann verstopft ist, wenn keine Handles mehr zur Verfügung stehen. Das heisst, es lässt sich nichts mehr starten oder öffnen, egal was.

Wuala konsumiert schon allein beim Start um die 2000 Handles (zum Vergleich: eMule etwa 300), sodass sich das Problem erheblich verschärft, wenn Wuala gestartet ist.

Die Anzahl verwendeter Handles sollte dringend reduziert werden!

Ich habe auf meinem System (XP) das Problem, dass es trotz ausreichendem Speicherausbau nach dem Öffnen relativ vieler Browser-Fenster irgendwann verstopft ist, wenn keine Handles mehr zur Verfügung stehen. Das heisst, es lässt sich nichts mehr starten oder öffnen, egal was.

Wuala konsumiert schon allein beim Start um die 2000 Handles (zum Vergleich: eMule etwa 300), sodass sich das Problem erheblich verschärft, wenn Wuala gestartet ist.

Die Anzahl verwendeter Handles sollte dringend reduziert werden!

Wenn ich Dateien von meinen Dateien einer Gruppe hinzufüge kommt folgende Fehlermeldung:

http://www.abload.de/img/wuala_errord...

Diese kommt aber nicht nur einmal, sondern teilweise mehr als 6-7 mal auf einmal.

Wuala wouldn't start from a directory with spaces in it.

I fixed it by changing the startup script to deal with it - here's the patch for it:

1 dwt@dwcp ~ % diff -u /Volumes/wuala_mac_alpha/Wuala.app/Contents/MacOS/wuala /Applications\ Meine/Network/File-Sharing/p2p/Wuala.app/Contents/MacOS/wuala
--- /Volumes/wuala_mac_alpha/Wuala.app/Contents/MacOS/wuala 2007-10-02 14:34:02.000000000 +0200
+++ /Applications Meine/Network/File-Sharing/p2p/Wuala.app/Contents/MacOS/wuala 2008-06-15 17:10:41.000000000 +0200
@@ -1,8 +1,8 @@
#!/bin/sh
# find the directory containing this script
-macosdir=`/usr/bin/dirname $0`
+macosdir=`/usr/bin/dirname "$0"`
#echo $macosdir
-cd $macosdir
+cd "$macosdir"

# change to java directory
cd ../Resources/java
@@ -10,27 +10,28 @@
# make sure that shared directories exist
if [ ! -d "/Users/Shared/WualaSharedData/Program" ]
then
-echo creating shared program directory
-mkdir -p "/Users/Shared/WualaSharedData/Program"
-chmod a+w "/Users/Shared/WualaSharedData/Program"
-cp Program/* /Users/Shared/WualaSharedData/Program
-chmod a+w /Users/Shared/WualaSharedData/Program/*
+ echo creating shared program directory
+ mkdir -p "/Users/Shared/WualaSharedData/Program"
+ chmod a+w "/Users/Shared/WualaSharedData/Program"
+ cp Program/* /Users/Shared/WualaSharedData/Program
+ chmod a+w /Users/Shared/WualaSharedData/Program/*
fi
if [ ! -d "/Users/Shared/WualaSharedData/Updater" ]
then
-echo creating shared updater directory
-mkdir "/Users/Shared/WualaSharedData/Updater"
-chmod a+w "/Users/Shared/WualaSharedData/Updater"
-cp Updater/* /Users/Shared/WualaSharedData/Updater
-chmod a+w /Users/Shared/WualaSharedData/Updater/*
+ echo creating shared updater directory
+ mkdir "/Users/Shared/WualaSharedData/Updater"
+ chmod a+w "/Users/Shared/WualaSharedData/Updater"
+ cp Updater/* /Users/Shared/WualaSharedData/Updater
+ chmod a+w /Users/Shared/WualaSharedData/Updater/*
fi

# copy files necessary for the updater to run
-cp /Users/Shared/WualaSharedData/Program/swt.jar /Users/Shared/WualaSharedData/Updater/swt.jar
-cp /Users/Shared/WualaSharedData/Program/libswt*.jnilib /Users/Shared/WualaSharedData/Updater/
+cp Program/swt.jar /Users/Shared/WualaSharedData/Updater/swt.jar
+cp Program/libswt*.jnilib /Users/Shared/WualaSharedData/Updater/
+
if [ -f /Users/Shared/WualaSharedData/Program/Wuala_Updater.jar ]
then
-mv /Users/Shared/WualaSharedData/Program/Wuala_Updater.jar /Users/Shared/WualaSharedData/Updater/WualaUpdater.jar
+ mv /Users/Shared/WualaSharedData/Program/Wuala_Updater.jar /Users/Shared/WualaSharedData/Updater/WualaUpdater.jar
fi

# start updater for the first time

the wuala is dont work properly the program work just after the install but if i close the program and try to reopen the exe file she dont work

Tag Leute,
jedes mal wenn ich Wuala starte, Kommt kurz der Login / Willkommen Screen und das Tray Icon. Nach ca 1sek stürzt das Programm ab. Ohne Fehlermeldung oder sonst was. Ich hab schon versucht es zu de/reinstallieren, neugestartet hat aber nichts gebracht.
Mein System: WinXP Pro SP3 mit den neusten Updates.
Was kann ich machen?

Nächstes Problem! Ich habe weder an meinem Router, an meiner Firewall, an Wuale etwas geändert...trotzdem heißt es plötzlich "mein Rechner ist nicht zum beitragen von speicher geeignet" ???

"Es wird versucht, einen UPnP Router zu finden...
UPnP Router gefunden: http://192.168.220.1:49152/gatedesc.xml
Port-Forwarding konnte erfolgreich eingerichtet werden, die Internetverbindung wird erneut getestet...
'/77.132.185.219:7413' akzeptiert eingehende Verbindungen von zuvor kontaktierent Adressen.
Ihre Verbindung ist für das Tauschen von Speicherplatz nicht geeignet.
Bitte aktivieren Sie UPnP auf Ihrem Router/Firewall oder konfigurieren Sie diesen so, dass eingehende UDP Verbindungen auf Port 7.413 für diesen Computer gestattet sind. Danach kann es nötig sein, Ihren Router und/oder Wuala neu zu starten."