Wuala startet nicht und gibt folgende Fehlermeldung aus:

Aus irgendeinem Grund ist Wuala bei mir abgestürzt und beim Versuch es neu zu starten kriege ich nur folgende Fehlermeldung:

Build: Linux 163

App: Domain Application, user: User1
(Data Application, prim id: 104.130.0.3, ip: /87.183.25.56:7560 (global)

(Common Application Linux 163))

Date: 01.09.2008

OS: Linux 1.6.0_06 Sun Microsystems Inc.

Memory: 254 MB max 4.8 MB free 14 MB total
Local Host: user1/127.0.1.1
Running for: 18s 32ms

Exception: java.lang.Exception: com.wuala.common.exception.ApplicationRuntimeException
at aM.e.a(Z:161)
at com.wuala.common.exception.ApplicationRuntimeException.createReport(Z:62)
at dr.a.<init>(Z:34)
at com.wuala.presentation.r.b(Z:427)
at com.wuala.presentation.r.a(Z:298)
at com.wuala.presentation.r.a(Z:106)
at com.wuala.platform.Wuala.launch(Z:22)
at com.wuala.loader2.Loader2.startInstance(Loader2.java:60)
at com.wuala.loader2.Loader2.start(Loader2.java:44)
at com.wuala.loader2.Loader2.main(Loader2.java:106)
Caused by: com.wuala.common.exception.ApplicationRuntimeException
... 6 more
Caused by: java.lang.NullPointerException
at bD.a.setVisible(Z:178)
at bD.i.d(Z:134)
at bD.i.<init>(Z:49)
at fl.b.<init>(Z:62)
at p.d.<init>(Z:124)
at com.wuala.presentation.o.a(Z:270)
at com.wuala.presentation.C.run(Z:281)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at com.wuala.presentation.r.a(Z:267)
... 5 more

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

com.wuala.common.exception.ApplicationRuntimeException
at com.wuala.presentation.r.a(Z:298)
at com.wuala.presentation.r.a(Z:106)
at com.wuala.platform.Wuala.launch(Z:22)
at com.wuala.loader2.Loader2.startInstance(Loader2.java:60)
at com.wuala.loader2.Loader2.start(Loader2.java:44)
at com.wuala.loader2.Loader2.main(Loader2.java:106)
Caused by: java.lang.NullPointerException
at bD.a.setVisible(Z:178)
at bD.i.d(Z:134)
at bD.i.<init>(Z:49)
at fl.b.<init>(Z:62)
at p.d.<init>(Z:124)
at com.wuala.presentation.o.a(Z:270)
at com.wuala.presentation.C.run(Z:281)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at com.wuala.presentation.r.a(Z:267)
... 5 more

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

java.lang.NullPointerException
at bD.a.setVisible(Z:178)
at bD.i.d(Z:134)
at bD.i.<init>(Z:49)
at fl.b.<init>(Z:62)
at p.d.<init>(Z:124)
at com.wuala.presentation.o.a(Z:270)
at com.wuala.presentation.C.run(Z:281)
at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
at com.wuala.presentation.r.a(Z:267)
at com.wuala.presentation.r.a(Z:106)
at com.wuala.platform.Wuala.launch(Z:22)
at com.wuala.loader2.Loader2.startInstance(Loader2.java:60)
at com.wuala.loader2.Loader2.start(Loader2.java:44)
at com.wuala.loader2.Loader2.main(Loader2.java:106)

Thread: main</init></init></init></init></init></init></init></init></init></init>

 

I’m frustrated

Inappropriate? Delete or Edit until someone replies)

Reply to this problem

7 people have this problem

I have this problem, too! Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.

The best solutions from the company

The best solutions from everyone

Get Satisfaction loves Zappos because they care about customer service.

• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Deelkar replied on September 01, 2008 17:05

  Completely cleaning up anything to do with wuala does not help. Neither does a reinstall

   

  I’m frustrated
  this solves the problem
  1 Comment Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove

  Deelkar commented on September 01, 2008 17:06

  Sorry, wir sind hier bei deutsch. Also neu installieren, löschen von .config/Wuala.cfg, und komplett alles runterlöschen und neu installieren hilft nix (Delete or Edit for 15 minutes)
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  frumble replied on September 01, 2008 18:01

  Leute - ich werde *SEHR*, *SEHR* BÖSE, wenn das bedeutet, dass ich Wuala wieder von Hand neuinstallieren darf und nachher meine Onlinezeit wieder bei 0 ist!!

   

  I’m furious!
  this solves the problem
  1 Comment Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove

  Bugreport, (Employee), commented on September 02, 2008 13:00

  Machine.dat sichern und nach der Neuinstallation wieder einspielen, wo liegt das Problem? (Delete or Edit for 15 minutes)
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  reggler replied on September 01, 2008 19:20

  I dunno. When I look at the errors it appears to be a problem with your java install. If I was you, I'd start with reinstalling the latest jre from www.java.com.

   

  I’m trying to brighten up the atmosphere a little
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  reggler replied on September 01, 2008 19:22

  also make sure that there's no more java process running with "ps ax | grep java" - if there is, kill it with "kill -9 PID"

   

  I’m not sure what's going on there
  this solves the problem
  1 Comment Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove

  areinwarth commented on September 01, 2008 19:42

  I must admit that I don' like java myself; nevertheless this is no reason at all to shoot a SIGKILL on that poor process without testing if a SIGTERM, SIGHUP or a SIGINT does its job. Please remember that a process killed via SIGKILL is not able to do any housekeeping before it dies, like closing file handles or opened ports.
  
  man 7 signal might help. (Delete or Edit for 15 minutes)
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Deelkar replied on September 01, 2008 20:12

  Andere Java Programme laufen einwandfrei. Nur wuala semmelt ab.
  Other java programs run without problems, only wuala is affected.

   

  I’m frustrated
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  kork replied on September 01, 2008 20:16

  Ging mit Build 163 los. 165 fixt es auch nicht. Windows geht. Bitte guckt euch das mal an!

   

  I’m annoyed
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  hoyo replied on September 01, 2008 20:32

  same problem!
  ich hab das selbe problem dammich !!

   

  I’m frustrated
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Franselbaer replied on September 01, 2008 20:35

  Hi, i'm a Linux User (MINT Elyssa / From Ubuntu 8.04) and have exactly the same Problem since the autoupdate to 163 and the auto restart after. I dont have new Java Packets installed nor updated. My Version is:
  
  java version "1.6.0_06"
  Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
  Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing)
  
  Please Help

   

  
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Happy replied on September 01, 2008 20:59

  Hi, eben hat es ein Update gegeben und nun kann ich wuala auch nicht mehr starten :'(
  After wuala-Update this evening, i can't start wuala :'(
  Kubuntu Linux gutsy
  java version "1.6.0_03"
  Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
  Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)
  
  Pls help

   

  I’m frustrated and sad
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Happy replied on September 01, 2008 21:40

  Ein Freund hat mit Kubuntu hardy das selbe Problem :(
  With Kubuntu hardy the same problem :(
  das nochmal zur Info hier

   

  I’m I’m frustrated and sad
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  SmartBlug replied on September 01, 2008 21:44

  v167 on linux seems to work since 1 minute
  PC97 also on Vista 64b

   

  I’m confident
  this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  Happy replied on September 01, 2008 21:52

  v167 works :)

   

  I’m happy
  2 people say this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  frumble replied on September 01, 2008 22:19

  Hui, wie haben die das jetzt gemacht, Wuala lief doch gar nicht mehr?
  
  Da hätte ich einen Feature Request an das Team: Einen standalone Updater, der komplett vom Hauptprogramm getrennt gestartet werden kann, wenn Wuala mal wieder geext wurde und man es sonst neuinstallieren müsste. Geht vielleicht auf Windows und OS X einfach, aber die Linux-Version ist immer ein riesen Ding, das ich nicht ganz verstehe.

   

  I’m happy
  this solves the problem
  1 Comment Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove

  areinwarth commented on September 02, 2008 07:02

  > Geht vielleicht auf Windows und OS X einfach, aber die
  > Linux-Version ist immer ein riesen Ding, das ich nicht ganz
  > verstehe.
  
  Ist doch eigentlich sogar noch einfacher als unter Windows:
  
  - von http://wua.la/en/launch die Linux-Version von wuala downloaden
  - entpacken ...
  - und die 3 Dateien nach ~/wuala verschieben (Delete or Edit for 15 minutes)
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  frumble replied on September 02, 2008 09:37

  Bei mir nicht, weil ich das auf einer separaten Partition laufen lasse und den " -basepath"-Parameter nutzen muss und ich weiß aus Erfahrung, dass das immer recht komisch ist...
  this solves the problem
  6 Comments Add a comment This solves the problem I no longer think this solves the problem
• 
  Remove

  Deelkar commented on September 02, 2008 10:52

  warum brauchst du "-basepath"? (Delete or Edit for 15 minutes)
• 
  Remove

  areinwarth commented on September 02, 2008 11:29

  Aus readme.txt:
  ~/wuala/ Default program directory. Start Wuala with -basepath PATH
  if you want it to use another one. (Delete or Edit for 15 minutes)
• 
  Remove

  bagelcat, (Employee), commented on September 02, 2008 13:28

  Ich mach das mit nem kleinen softlink. find ich irgendwie praktischer die folder da hin zu linken wo ich die daten haben will und die einstellungen unangetastet zu lassen. Ausserdem leg ich so die cache daten und die fragments in verschiedenen partitions ab...;) (Delete or Edit for 15 minutes)
• 
  Remove

  areinwarth commented on September 02, 2008 13:51

  dito, wobei ich mir bewusst bin, dass das halt nicht der "offizielle Weg" ist :) (Delete or Edit for 15 minutes)
• 
  Remove

  bagelcat, (Employee), commented on September 02, 2008 14:05

  kann es für einen *nix *nux user etwas ofizielleres geben als sein system mit shell-befehlen auf den eigenen Bedarf zu konfigurieren? Die Benutzung von Programmoptionen für sowas ist doch eigentlich nur für die faulen. :D (Delete or Edit for 15 minutes)
• 
  Remove

  Bugreport, (Employee), commented on September 02, 2008 14:15

  Frickelpack, elendiges! :-P (Delete or Edit for 15 minutes)
• 
  Remove Inappropriate?

  Delete or Edit for 15 minutes

  poet replied on September 03, 2008 15:54

  v167 funktioniert wieder. Schön.

   

  I’m happy
  1 person says this solves the problem
  Add a comment This solves the problem I no longer think this solves the problem

Reply to poet's problem

What's the status of this problem? Choose... Not a problem We're aware of it We're working on it Solved

(Some HTML allowed)

Uploading image...

Done! The image has been added to your reply. Close

Choose a file:

The image must be a GIF, JPEG, or PNG that is smaller than 2MB.

Cancel upload

Insert an image URL:

Mark this as a "best solution" at the top of the page

How does this make you feel?

I'm (x)