Zekr in Arch Linux
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zekr |
New
|
Undecided
|
Unassigned |
Bug Description
I have a fresh Bridge Linux (based on Arch Linux) installed and tried zekr.
[yfdogan@bridge ~]$ zekr.sh
Exception in thread "main" java.lang.
at net.sf.
at net.sf.
at net.sf.
at net.sf.
Caused by: java.lang.
at java.net.
at java.net.
at java.security.
at java.net.
at java.lang.
at sun.misc.
at java.lang.
... 4 more
[yfdogan@bridge ~]$
Any idea?
You din't seem to have swt.jar in your java classpath. If you can pause the
process and tell us result of:
ps aux | grep java
Regards,
Mohsen
On Sat, Apr 7, 2012 at 8:02 PM, Yusuf Faruk DOGAN <email address hidden>wrote:
> Public bug reported: NoClassDefFound Error: zekr.common. config. GlobalConfig. <clinit> (GlobalConfig. java:34) zekr.common. runtime. Naming. <clinit> (Naming. java:21) zekr.engine. log.Logger. <clinit> (Logger. java:44) zekr.ZekrMain. <clinit> (ZekrMain. java:32) ClassNotFoundEx ception: org.eclipse.swt.SWT URLClassLoader$ 1.run(Unknown Source) URLClassLoader$ 1.run(Unknown Source) AccessControlle r.doPrivileged( Native Method) URLClassLoader. findClass( Unknown Source) ClassLoader. loadClass( Unknown Source) Launcher$ AppClassLoader. loadClass( Unknown Source) ClassLoader. loadClass( Unknown Source) /bugs.launchpad .net/bugs/ 976013 /bugs.launchpad .net/zekr/ +bug/976013/ +subscriptions
>
> I have a fresh Bridge Linux (based on Arch Linux) installed and tried
> zekr.
>
>
> [yfdogan@bridge ~]$ zekr.sh
> Exception in thread "main" java.lang.
> org/eclipse/swt/SWT
> at
> net.sf.
> at net.sf.
> at net.sf.
> at net.sf.
> Caused by: java.lang.
> at java.net.
> at java.net.
> at java.security.
> at java.net.
> at java.lang.
> at sun.misc.
> at java.lang.
> ... 4 more
> [yfdogan@bridge ~]$
>
>
> Any idea?
>
> ** Affects: zekr
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to Zekr.
> https:/
>
> Title:
> Zekr in Arch Linux
>
> To manage notifications about this bug go to:
> https:/
>