Package Details: jitsi 2.11.5633-1

Git Clone URL: https://aur.archlinux.org/jitsi.git (read-only, click to copy)
Package Base: jitsi
Description: An audio/video SIP VoIP phone and instant messenger written in Java (formerly SIP-Communicator)
Upstream URL: https://desktop.jitsi.org/Main/HomePage
Licenses: Apache
Submitter: psychedelicious
Maintainer: SanskritFritz
Last Packager: figue
Votes: 372
Popularity: 0.000025
First Submitted: 2011-05-11 11:22 (UTC)
Last Updated: 2020-12-12 16:22 (UTC)

Dependencies (3)

Required by (0)

Sources (3)

Pinned Comments

figue commented on 2020-12-12 17:04 (UTC) (edited on 2021-01-03 19:13 (UTC) by figue)

I've built with jdk8... Like this:

env JAVA_HOME=/usr/lib/jvm/java-8-openjdk PATH=/usr/lib/jvm/java-8-openjdk/jre/bin:$PATH makepkg -sic

But if you want to execute jitsi, it's better to set it globally:

archlinux-java set java-8-openjdk

See pinned comment.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 24 Next › Last »

notuxius commented on 2017-03-01 07:03 (UTC) (edited on 2017-03-01 07:42 (UTC) by notuxius)

not compiling with jre7/jdk7 (that is selected by default for apache-ant dependency in pacman) - and compiling with jre8/jdk8 errors upon build: -pre-version: version: BUILD FAILED /tmp/yaourt-tmp-not/aur-jitsi/src/jitsi/build.xml:454: Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK. It is currently set to "/usr/lib/jvm/java-8-openjdk/jre" Total time: 2 seconds ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build jitsi.

<deleted-account> commented on 2017-02-28 18:44 (UTC)

Login with Google caused NoClassDefFoundError (icq works fine): java.lang.NoClassDefFoundError: org/xbill/DNS/TextParseException at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:731) at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:478) at net.java.sip.communicator.util.account.LoginManager$RegisterProvider.run(LoginManager.java:434) Caused by: java.lang.ClassNotFoundException: org.xbill.DNS.TextParseException at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.felix.framework.ExtensionManager$ExtensionManagerWiring.getClassByDelegation(ExtensionManager.java:1010) at org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1595) at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1525) at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79) at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018) at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

ibauersachs commented on 2017-02-28 18:34 (UTC)

Whoever is maintainging this: the startup classpath changed from 2.8 to 2.10 and causes the login failures. You'll need to adapt the jitsi.sh script, look at the script for Debian (resources/install/debian/jitsi.sh.tmpl) for an example.

Rhinoceros commented on 2017-02-28 10:05 (UTC)

@xdevla Hmm… bizarre. I just tried on my wife's system, with only java-7-openjdk and java-8-openjdk/jre (default) installed, and it failed there too. And obviously a few other people in this thread have that problem too. FWIW I tried building with the four javas that you had installed (I had previously been missing java-8-jdk), with java-8-jre/jre as default again. It still failed.

xdevla commented on 2017-02-28 09:39 (UTC)

Yep, I tried to build the package with the four environments and all were success (however throwing some warning here and there).

Rhinoceros commented on 2017-02-28 09:32 (UTC)

@xdevla Do you mean with java-8-jre/jre as default instead?

xdevla commented on 2017-02-28 09:29 (UTC)

Compiles fine at my side with those four environments : java-7-openjdk java-8-jdk java-8-jre/jre java-8-openjdk/jre (default)

Rhinoceros commented on 2017-02-28 09:21 (UTC)

2.10.5550-2 still fails if you have java-8-jre/jre selected as the default. You can fix it by hard-coding java-7-openjdk in the PKGBUILD. --- PKGBUILD 2017-02-28 20:20:09.182314322 +1100 +++ PKGBUILD.fix 2017-02-28 20:18:02.484618050 +1100 @@ -24,7 +24,7 @@ # append the build revision to the jitsi version sed -i "s/0\.build\.by\.SVN/build.${pkgver}/" src/net/java/sip/communicator/impl/version/NightlyBuildID.java . /etc/profile.d/apache-ant.sh - ant rebuild + JAVA_HOME=/usr/lib/jvm/java-7-openjdk/jre ant rebuild } package() {

xris commented on 2017-02-28 03:48 (UTC)

Just installed jitsi on my arch machine and I am unable to log into my xmpp dukgo account - have no problem logging into this on other computers with jitsi (fedora / osx) and other apps (pidgin). See no useful info in journalctl. The app seemed to install/launch ok. Only get this error: "An error occurred while logging in with account: User name: xxxxxx@dukgo.com, Server name: Jabber:dukgo.com."

DEATH commented on 2017-02-27 14:02 (UTC) (edited on 2017-02-27 14:14 (UTC) by DEATH)

Does anyone else have issues signing in to their accounts since latest update (2017-02-27 05:53)?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 24 Next › Last »