[jitsi-users] aspiring user, having problems

Toni_Mueller · 2015-01-19 21:02:03 UTC

Hi,

I am trying to use Jitsi, but without much success. I tried different
versions of Jitsi and Debian, but my best result so far is getting a
window like depicted in the attached screenshot without a stack trace.

The combination where I get no traceback:

* Debian Jessie/amd64
* Jitsi 2.5.5065-1

Still, as you can see from the attached screenshot, the result is
underwhelming. Also, the "Options" menu jumps to the left side of the
screen everytime I click something.

A combination that yields a lot of stack traces, but otherwise mostly
behaves the same way, is a recent Jitsi on Wheezy. But I had equally bad
success with older versions of Jitsi.

On Wheezy, I did not manage to register an account using Jitsi with a
locally running ejabberd, but had no problems doing so with PSI.

I understand that I should post stack traces to this list, too, right?

Kind regards,
--Toni++

Danny_van_Heumen · 2015-01-20 19:55:39 UTC

Hi Toni,

Yes, you can post the stack traces that you have.

I am running on Jessie AMD64 too. I mostly compile and run from source,
but haven't had any of the issues that you describe. So, I am curious to
the stack traces that you may have.

What desktop engine/window manager are you running?

Regards,
Danny

···

On 19-01-15 22:02, Toni Mueller wrote:

Hi,

I am trying to use Jitsi, but without much success. I tried different
versions of Jitsi and Debian, but my best result so far is getting a
window like depicted in the attached screenshot without a stack trace.

The combination where I get no traceback:

* Debian Jessie/amd64
* Jitsi 2.5.5065-1

Still, as you can see from the attached screenshot, the result is
underwhelming. Also, the "Options" menu jumps to the left side of the
screen everytime I click something.

A combination that yields a lot of stack traces, but otherwise mostly
behaves the same way, is a recent Jitsi on Wheezy. But I had equally bad
success with older versions of Jitsi.

On Wheezy, I did not manage to register an account using Jitsi with a
locally running ejabberd, but had no problems doing so with PSI.

I understand that I should post stack traces to this list, too, right?

Kind regards,
--Toni++

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

Toni_Mueller · 2015-01-21 23:19:54 UTC

Hi Danny,

Yes, you can post the stack traces that you have.

well, I have to produce new ones.

I am running on Jessie AMD64 too. I mostly compile and run from source,

Uh... I don't feel able to do that right now.

but haven't had any of the issues that you describe. So, I am curious to
the stack traces that you may have.

My stack traces appear under Wheezy, not Jessie. The picture is the same
for both versions, though.

What desktop engine/window manager are you running?

I am running a plain awesome.

Kind regards,
--Toni++

···

On Tue, Jan 20, 2015 at 08:55:39PM +0100, Danny van Heumen wrote:

Toni_Mueller · 2015-01-30 16:46:01 UTC

Hi Danny,

> I am running on Jessie AMD64 too. I mostly compile and run from source,

Uh... I don't feel able to do that right now.

now I have done that. Please see:

$ jitsi
17:38:43.335 SEVERE: [10] util.launchutils.SipCommunicatorLock.getRandomBindAddress().283 Failed to obtain a list of the local interfaces.
java.net.SocketException: Cannot assign requested address
  at java.net.NetworkInterface.getAll(Native Method)
  at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:286)
  at net.java.sip.communicator.util.launchutils.SipCommunicatorLock.getRandomBindAddress(SipCommunicatorLock.java:278)
  at net.java.sip.communicator.util.launchutils.SipCommunicatorLock.lock(SipCommunicatorLock.java:178)
  at net.java.sip.communicator.util.launchutils.SipCommunicatorLock.tryLock(SipCommunicatorLock.java:162)
  at net.java.sip.communicator.launcher.SIPCommunicator.main(SIPCommunicator.java:150)
Failed to lock SIP Communicator's configuration directory.
Try launching with the --multiple param.
$ jitsi --multiple
17:39:24.448 SEVERE: [10] impl.netaddr.NetworkConfigurationWatcher.<init>().74 Error checking network interfaces
java.net.SocketException: Cannot assign requested address
  at java.net.NetworkInterface.getAll(Native Method)
  at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:286)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.checkNetworkInterfaces(NetworkConfigurationWatcher.java:337)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.<init>(NetworkConfigurationWatcher.java:71)
  at net.java.sip.communicator.impl.netaddr.NetworkAddressManagerServiceImpl.addNetworkConfigurationChangeListener(NetworkAddressManagerServiceImpl.java:557)
  at net.java.sip.communicator.impl.dns.DnsUtilActivator.serviceChanged(DnsUtilActivator.java:345)
  at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
  at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
  at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
  at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3890)
  at org.apache.felix.framework.Felix.access$000(Felix.java:79)
  at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:728)
  at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
  at org.apache.felix.framework.Felix.registerService(Felix.java:2979)
  at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:313)
  at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:287)
  at net.java.sip.communicator.impl.netaddr.NetaddrActivator.start(NetaddrActivator.java:83)
  at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
  at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1822)
  at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1192)
  at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:266)
  at java.lang.Thread.run(Thread.java:662)
17:39:24.449 SEVERE: [10] impl.netaddr.NetworkConfigurationWatcher.initialFireEvents().157 Error checking network interfaces
java.net.SocketException: Cannot assign requested address
  at java.net.NetworkInterface.getAll(Native Method)
  at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:286)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.initialFireEvents(NetworkConfigurationWatcher.java:112)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.addNetworkConfigurationChangeListener(NetworkConfigurationWatcher.java:88)
  at net.java.sip.communicator.impl.netaddr.NetworkAddressManagerServiceImpl.addNetworkConfigurationChangeListener(NetworkAddressManagerServiceImpl.java:559)
  at net.java.sip.communicator.impl.dns.DnsUtilActivator.serviceChanged(DnsUtilActivator.java:345)
  at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871)
  at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733)
  at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662)
  at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3890)
  at org.apache.felix.framework.Felix.access$000(Felix.java:79)
  at org.apache.felix.framework.Felix$2.serviceChanged(Felix.java:728)
  at org.apache.felix.framework.ServiceRegistry.registerService(ServiceRegistry.java:107)
  at org.apache.felix.framework.Felix.registerService(Felix.java:2979)
  at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:313)
  at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:287)
  at net.java.sip.communicator.impl.netaddr.NetaddrActivator.start(NetaddrActivator.java:83)
  at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
  at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1822)
  at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1192)
  at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:266)
  at java.lang.Thread.run(Thread.java:662)
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
17:39:27.780 SEVERE: [10] impl.netaddr.NetworkConfigurationWatcher.initialFireEvents().157 Error checking network interfaces
java.net.SocketException: Cannot assign requested address
  at java.net.NetworkInterface.getAll(Native Method)
  at java.net.NetworkInterface.getNetworkInterfaces(NetworkInterface.java:286)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.initialFireEvents(NetworkConfigurationWatcher.java:112)
  at net.java.sip.communicator.impl.netaddr.NetworkConfigurationWatcher.addNetworkConfigurationChangeListener(NetworkConfigurationWatcher.java:88)
  at net.java.sip.communicator.impl.netaddr.NetworkAddressManagerServiceImpl.addNetworkConfigurationChangeListener(NetworkAddressManagerServiceImpl.java:559)
  at net.java.sip.communicator.plugin.reconnectplugin.ReconnectPluginActivator.start(ReconnectPluginActivator.java:216)
  at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:629)
  at org.apache.felix.framework.Felix.activateBundle(Felix.java:1904)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1822)
  at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1192)
  at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:266)
  at java.lang.Thread.run(Thread.java:662)

At this point, I see the all-grey main window, as indicated in the
screenshot I posted, and that's it. This happens with

$ dpkg -l jitsi
Desired=Unknown/Install/Remove/Purge/Hold

···

On Wed, Jan 21, 2015 at 11:19:54PM +0000, Toni Mueller wrote:

On Tue, Jan 20, 2015 at 08:55:39PM +0100, Danny van Heumen wrote:
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)

/ Name Version Architecture

+++-============================-======================-============
ii jitsi 2.5.5065-1 amd64

Kind regards,
--Toni++