Version 133/linux does not start anymore
Getting this error, and the version before worked fine:
java.lang.NullPointerException
at com.wuala.application.alphacompatibility.a.<init>(Z:63)
at com.wuala.application.alphacompatibility.ApplicationInfoWrapper.getInitialUpdater(Z:34)
at t.w.<init>(Z:29)
at com.wuala.presentation.r.a(Z:103)
at com.wuala.platform.Wuala.launch(Z:21)
at com.wuala.platform.Wuala.launch2(Z:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
at com.wuala.loader.Loader.main(Loader.java:134)
Shutting down...
java.lang.RuntimeException: java.lang.NullPointerException
at com.wuala.loader.Loader.run(Loader.java:69)
at com.wuala.loader.Loader.main(Loader.java:134)
Caused by: java.lang.NullPointerException
at com.wuala.application.alphacompatibility.a.<init>(Z:63)
at com.wuala.application.alphacompatibility.ApplicationInfoWrapper.getInitialUpdater(Z:34)
at t.w.<init>(Z:29)
at com.wuala.presentation.r.a(Z:103)
at com.wuala.platform.Wuala.launch(Z:21)
at com.wuala.platform.Wuala.launch2(Z:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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>
java.lang.NullPointerException
at com.wuala.application.alphacompatibility.a.<init>(Z:63)
at com.wuala.application.alphacompatibility.ApplicationInfoWrapper.getInitialUpdater(Z:34)
at t.w.<init>(Z:29)
at com.wuala.presentation.r.a(Z:103)
at com.wuala.platform.Wuala.launch(Z:21)
at com.wuala.platform.Wuala.launch2(Z:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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)
at com.wuala.loader.Loader.main(Loader.java:134)
Shutting down...
java.lang.RuntimeException: java.lang.NullPointerException
at com.wuala.loader.Loader.run(Loader.java:69)
at com.wuala.loader.Loader.main(Loader.java:134)
Caused by: java.lang.NullPointerException
at com.wuala.application.alphacompatibility.a.<init>(Z:63)
at com.wuala.application.alphacompatibility.ApplicationInfoWrapper.getInitialUpdater(Z:34)
at t.w.<init>(Z:29)
at com.wuala.presentation.r.a(Z:103)
at com.wuala.platform.Wuala.launch(Z:21)
at com.wuala.platform.Wuala.launch2(Z:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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>
3 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 more people who report this problem, the more it gets noticed.
-
Inappropriate?heh i agree.
wuala is seriously hosed on loonix with this recent build. not even reinstalling (reapplying) the current tgz file from the wuala website helps anything.
is there any quality assurance team over at caleido at all or are they simply pushing out the buggy alpha bits as they please? ;)
i wonder if anyone tests anything over there ;p
scnr :D
-
Inappropriate?At some point (I think it may have been one of the versions just before 133), I received instructions in an error message to download an unpack http://wua.la/files/wuala.tar.gz
Try that, and restart.
I use the -nogui sometimes as well. That may or may not be when I received the helpful error message, but you could also try with/without the -nogui parameter.
At least now it starts, but there are other problems:
http://wua.la/Wuala+Community/Bugs/In...
-
Inappropriate?134 isnt any better either.
restarting 133 upgraded to 134 apparently (wualacmd) but it still doesnt really connect/start.
wtf is wrong :(
I’m frustrated
-
Inappropriate?Yeah, this is kind of frustrating. Esp. when versions prior to 133 were working fine. I guess it would be cool thing if wuala notified me about a new version and lets me decide wether I want to upgrade. You could also mark certain versions as "necessary updates" which a user has to do and still force the upgrade. But when things might break I'd like to have the choice.
I’m pissed, alpha-tester
Loading Profile...




