[jitsi-users] Re: jitsi dns problem


#1

i installed latest nightly build on debian wheezy in order to check if
dns query bug is fixed, but the result was that jitsi now prints lots of
errors at startup and then nothing happens. perhaps the nightly build
package is missing some package dependencies.

-- juha

$ jitsi
org.osgi.framework.BundleException: Unresolved constraint in bundle [108]: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [25]: Unable to resolve 25.0: missing requirement [25.0] package; (package=net.java.sip.communicator.service.gui) [caused by: Unable to resolve 110.0: missing requirement [110.0] package; (package=org.jitsi.service.resources) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [28]: Unable to resolve 28.0: missing requirement [28.0] package; (package=org.jitsi.service.fileaccess) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [29]: Unable to resolve 29.0: missing requirement [29.0] package; (package=net.java.sip.communicator.util) [caused by: Unable to resolve 25.0: missing requirement [25.0] package; (package=net.java.sip.communicator.service.gui) [caused by: Unable to resolve 110.0: missing requirement [110.0] package; (package=org.jitsi.service.resources) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [91]: Unable to resolve 91.0: missing requirement [91.0] package; (package=net.java.sip.communicator.util) [caused by: Unable to resolve 25.0: missing requirement [25.0] package; (package=net.java.sip.communicator.service.gui) [caused by: Unable to resolve 110.0: missing requirement [110.0] package; (package=org.jitsi.service.resources) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [92]: Unable to resolve 92.0: missing requirement [92.0] package; (package=org.jitsi.service.configuration) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [89]: Unable to resolve 89.0: missing requirement [89.0] package; (package=org.jitsi.service.configuration) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [90]: Unable to resolve 90.0: missing requirement [90.0] package; (package=net.java.sip.communicator.util) [caused by: Unable to resolve 25.0: missing requirement [25.0] package; (package=net.java.sip.communicator.service.gui) [caused by: Unable to resolve 110.0: missing requirement [110.0] package; (package=org.jitsi.service.resources) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle net.java.sip.communicator.impl.dns [88]: Unable to resolve 88.0: missing requirement [88.0] package; (package=org.jitsi.util) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [79]: Unable to resolve 79.0: missing requirement [79.0] package; (package=net.java.sip.communicator.util) [caused by: Unable to resolve 25.0: missing requirement [25.0] package; (package=net.java.sip.communicator.service.gui) [caused by: Unable to resolve 110.0: missing requirement [110.0] package; (package=org.jitsi.service.resources) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [9]: Unable to resolve 9.0: missing requirement [9.0] package; (package=org.jitsi.service.configuration) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [10]: Unable to resolve 10.0: missing requirement [10.0] package; (package=org.jitsi.service.version) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [11]: Unable to resolve 11.0: missing requirement [11.0] package; (package=org.jitsi.util) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [2]: Unable to resolve 2.0: missing requirement [2.0] package; (package=org.jitsi.service.configuration) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle [3]: Unable to resolve 3.0: missing requirement [3.0] package; (package=org.jitsi.service.configuration) [caused by: Unable to resolve 108.0: missing requirement [108.0] package; (package=gnu.java.zrtp) [caused by: Unable to resolve 102.0: missing requirement [102.0] package; (package=org.bouncycastle.asn1)]]
  at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564)
  at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
  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:679)
...


#2

Hi,

I am having the exact same problem with the current nightly build
(2.1.4566.10773-1) on ubuntu 12.04 amd64.

Cheers, Benjamin

i installed latest nightly build on debian wheezy in order to check
if dns query bug is fixed, but the result was that jitsi now prints
lots of errors at startup and then nothing happens. perhaps the
nightly build package is missing some package dependencies.

-- juha

$ jitsi org.osgi.framework.BundleException: Unresolved constraint
in bundle [108]: Unable to resolve 108.0: missing requirement
[108.0] package; (package=gnu.java.zrtp) [caused by: Unable to
resolve 102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[25]: Unable to resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[28]: Unable to resolve 28.0: missing requirement [28.0] package;
(package=org.jitsi.service.fileaccess) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[29]: Unable to resolve 29.0: missing requirement [29.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[91]: Unable to resolve 91.0: missing requirement [91.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[92]: Unable to resolve 92.0: missing requirement [92.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[89]: Unable to resolve 89.0: missing requirement [89.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[90]: Unable to resolve 90.0: missing requirement [90.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
net.java.sip.communicator.impl.dns [88]: Unable to resolve 88.0:
missing requirement [88.0] package; (package=org.jitsi.util)
[caused by: Unable to resolve 108.0: missing requirement [108.0]
package; (package=gnu.java.zrtp) [caused by: Unable to resolve
102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[79]: Unable to resolve 79.0: missing requirement [79.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[9]: Unable to resolve 9.0: missing requirement [9.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[10]: Unable to resolve 10.0: missing requirement [10.0] package;
(package=org.jitsi.service.version) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[11]: Unable to resolve 11.0: missing requirement [11.0] package;
(package=org.jitsi.util) [caused by: Unable to resolve 108.0:
missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[2]: Unable to resolve 2.0: missing requirement [2.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[3]: Unable to resolve 3.0: missing requirement [3.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679) ...


#3

(+bcc: users)

I am moving this to the dev list.

This is most likely related to our latest changes and the bouncy castle
un-fork effort.

Werner, Ingo, would you guys be able to have a look or are you waiting
for the GitHub migration (which I am hoping will finally happen this
weekend).

···

On 16.04.13, 14:54, Benjamin Eltzner wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am having the exact same problem with the current nightly build
(2.1.4566.10773-1) on ubuntu 12.04 amd64.

Cheers, Benjamin

i installed latest nightly build on debian wheezy in order to check
if dns query bug is fixed, but the result was that jitsi now prints
lots of errors at startup and then nothing happens. perhaps the
nightly build package is missing some package dependencies.

-- juha

$ jitsi org.osgi.framework.BundleException: Unresolved constraint
in bundle [108]: Unable to resolve 108.0: missing requirement
[108.0] package; (package=gnu.java.zrtp) [caused by: Unable to
resolve 102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[25]: Unable to resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[28]: Unable to resolve 28.0: missing requirement [28.0] package;
(package=org.jitsi.service.fileaccess) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[29]: Unable to resolve 29.0: missing requirement [29.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[91]: Unable to resolve 91.0: missing requirement [91.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[92]: Unable to resolve 92.0: missing requirement [92.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[89]: Unable to resolve 89.0: missing requirement [89.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[90]: Unable to resolve 90.0: missing requirement [90.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
net.java.sip.communicator.impl.dns [88]: Unable to resolve 88.0:
missing requirement [88.0] package; (package=org.jitsi.util)
[caused by: Unable to resolve 108.0: missing requirement [108.0]
package; (package=gnu.java.zrtp) [caused by: Unable to resolve
102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[79]: Unable to resolve 79.0: missing requirement [79.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[9]: Unable to resolve 9.0: missing requirement [9.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[10]: Unable to resolve 10.0: missing requirement [10.0] package;
(package=org.jitsi.service.version) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[11]: Unable to resolve 11.0: missing requirement [11.0] package;
(package=org.jitsi.util) [caused by: Unable to resolve 108.0:
missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[2]: Unable to resolve 2.0: missing requirement [2.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[3]: Unable to resolve 3.0: missing requirement [3.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679) ...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRbUnZAAoJEK27BRz67lmpLvwP/3KdA+yI5gNk34aRcpFyAdEt
C/Gq7FV2I3ejtIBtD6Zn/dAeqWQFlYpVZvVpaFTgi2uxVzi38EE3RZh5fqi5uSGJ
yu/mP0fYFByaSZw5GNbtCmuq+64j2RwSbkl9EH7G6TlI3FnmSOCv6Ta0qadB7chl
N8bGP13L2ZOJaagPH+6X3DWSpKlBaAeq+1JqNR8KfBzU+ScZyZE4HbimdEvRk9vc
tF4IAsT6OHkBRmfL8fjMwDz/4jaOwlRZU9740QJ6XspsL5J9oJ9d6ZjSZf6va+cJ
cT1t6vLWmT+5dAE67ZekRogCbiAKgP7DRcNTFG+nQhVDBmhecFys4Zyyi7CYfE9E
SyHH183AzjOcgPG9knFl9x6XfaT4kA4kTs67NHp7LHgCeMRRix3vo9UpT9kEosOg
r3H4OT3pAYW7b52TaZxQ9EWGjCjgX4pVMFrNcmYujrGhVi+BU9AOxPX4Rm9JnVsk
+bsgmozP4+pZGfFChzliM+Br74hacf3pw5G0Py/jG3XpVe1Y9EiPlZznnchpdcrS
T+HSZef9/wk/OEMG5XtH3dwjxuY2Sc8G/ZLap1vN/jEVhTwiNeCHZMWZo3NakXXA
y4nPVb0D/tuqxizh+bd3XvJCXrswVu28psZrT6Tnre1T3batbsVDiYgrhmYbvIUg
snC8ZXkE7oj5DuIFA7Lm
=slU1
-----END PGP SIGNATURE-----

--
https://jitsi.org


#4

I am moving this to the dev list.

This is most likely related to our latest changes and the bouncy castle
un-fork effort.

Werner, Ingo, would you guys be able to have a look or are you waiting
for the GitHub migration (which I am hoping will finally happen this
weekend).

The trunk is okay as far as I can tell, I'm looking with Damian why the
build doesn't contain the bouncycastle and bccontrib jars. The task to copy
them is definitely present in the build.xml.

Ingo


#5

I am moving this to the dev list.

This is most likely related to our latest changes and the bouncy castle
un-fork effort.

Werner, Ingo, would you guys be able to have a look or are you waiting
for the GitHub migration (which I am hoping will finally happen this
weekend).

The trunk is okay as far as I can tell, I'm looking with Damian why the
build doesn't contain the bouncycastle and bccontrib jars. The task to copy
them is definitely present in the build.xml.

Ingo

The un-forking (split) was done last weekend and works so far on most systems :slight_smile: .

It's a problem on Ubuntu which is based on Debian and we did this un-fork (split)
because of the very specific Debian installation.

This un-forking may trigger some problems in the future. If Debian changes the BC
library and this BC library contains modified API then Jtisi may have to modify it's
modules as well. AFAIK such an API change already happened not long ago.

Werner

···

Am 16.04.2013 15:11, schrieb Ingo Bauersachs:

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 173 44 37 659
PGP key: 82EF5E8B
.


#6

Hi,

this is fixed in latest build.

Thanks for the report
damencho

···

On Tue, Apr 16, 2013 at 3:54 PM, Benjamin Eltzner <b.eltzner@gmx.de> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I am having the exact same problem with the current nightly build
(2.1.4566.10773-1) on ubuntu 12.04 amd64.

Cheers, Benjamin

i installed latest nightly build on debian wheezy in order to check
if dns query bug is fixed, but the result was that jitsi now prints
lots of errors at startup and then nothing happens. perhaps the
nightly build package is missing some package dependencies.

-- juha

$ jitsi org.osgi.framework.BundleException: Unresolved constraint
in bundle [108]: Unable to resolve 108.0: missing requirement
[108.0] package; (package=gnu.java.zrtp) [caused by: Unable to
resolve 102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[25]: Unable to resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[28]: Unable to resolve 28.0: missing requirement [28.0] package;
(package=org.jitsi.service.fileaccess) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[29]: Unable to resolve 29.0: missing requirement [29.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[91]: Unable to resolve 91.0: missing requirement [91.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[92]: Unable to resolve 92.0: missing requirement [92.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[89]: Unable to resolve 89.0: missing requirement [89.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[90]: Unable to resolve 90.0: missing requirement [90.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
net.java.sip.communicator.impl.dns [88]: Unable to resolve 88.0:
missing requirement [88.0] package; (package=org.jitsi.util)
[caused by: Unable to resolve 108.0: missing requirement [108.0]
package; (package=gnu.java.zrtp) [caused by: Unable to resolve
102.0: missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[79]: Unable to resolve 79.0: missing requirement [79.0] package;
(package=net.java.sip.communicator.util) [caused by: Unable to
resolve 25.0: missing requirement [25.0] package;
(package=net.java.sip.communicator.service.gui) [caused by: Unable
to resolve 110.0: missing requirement [110.0] package;
(package=org.jitsi.service.resources) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]]]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[9]: Unable to resolve 9.0: missing requirement [9.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[10]: Unable to resolve 10.0: missing requirement [10.0] package;
(package=org.jitsi.service.version) [caused by: Unable to resolve
108.0: missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[11]: Unable to resolve 11.0: missing requirement [11.0] package;
(package=org.jitsi.util) [caused by: Unable to resolve 108.0:
missing requirement [108.0] package; (package=gnu.java.zrtp)
[caused by: Unable to resolve 102.0: missing requirement [102.0]
package; (package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[2]: Unable to resolve 2.0: missing requirement [2.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679)
org.osgi.framework.BundleException: Unresolved constraint in bundle
[3]: Unable to resolve 3.0: missing requirement [3.0] package;
(package=org.jitsi.service.configuration) [caused by: Unable to
resolve 108.0: missing requirement [108.0] package;
(package=gnu.java.zrtp) [caused by: Unable to resolve 102.0:
missing requirement [102.0] package;
(package=org.bouncycastle.asn1)]] at
org.apache.felix.framework.Felix.resolveBundle(Felix.java:3564) at
org.apache.felix.framework.Felix.startBundle(Felix.java:1797) 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:679) ...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRbUnZAAoJEK27BRz67lmpLvwP/3KdA+yI5gNk34aRcpFyAdEt
C/Gq7FV2I3ejtIBtD6Zn/dAeqWQFlYpVZvVpaFTgi2uxVzi38EE3RZh5fqi5uSGJ
yu/mP0fYFByaSZw5GNbtCmuq+64j2RwSbkl9EH7G6TlI3FnmSOCv6Ta0qadB7chl
N8bGP13L2ZOJaagPH+6X3DWSpKlBaAeq+1JqNR8KfBzU+ScZyZE4HbimdEvRk9vc
tF4IAsT6OHkBRmfL8fjMwDz/4jaOwlRZU9740QJ6XspsL5J9oJ9d6ZjSZf6va+cJ
cT1t6vLWmT+5dAE67ZekRogCbiAKgP7DRcNTFG+nQhVDBmhecFys4Zyyi7CYfE9E
SyHH183AzjOcgPG9knFl9x6XfaT4kA4kTs67NHp7LHgCeMRRix3vo9UpT9kEosOg
r3H4OT3pAYW7b52TaZxQ9EWGjCjgX4pVMFrNcmYujrGhVi+BU9AOxPX4Rm9JnVsk
+bsgmozP4+pZGfFChzliM+Br74hacf3pw5G0Py/jG3XpVe1Y9EiPlZznnchpdcrS
T+HSZef9/wk/OEMG5XtH3dwjxuY2Sc8G/ZLap1vN/jEVhTwiNeCHZMWZo3NakXXA
y4nPVb0D/tuqxizh+bd3XvJCXrswVu28psZrT6Tnre1T3batbsVDiYgrhmYbvIUg
snC8ZXkE7oj5DuIFA7Lm
=slU1
-----END PGP SIGNATURE-----


#7

Juha Heinanen writes:

i installed latest nightly build on debian wheezy in order to check if
dns query bug is fixed, but the result was that jitsi now prints lots of
errors at startup and then nothing happens. perhaps the nightly build
package is missing some package dependencies.

nightly build from april 17 worked and i was able to verify that
autodiscovery of sip proxy/registrar from dns worked.

presence is still not cleaning all subscriptions at shutdown.

-- juha


#8

Well, this applies to any debian dependancy and it's one of the reasons for
us dragging our feet for so long brfore getting into this.

Of course, we could always make our dependencies target a specific version
... we'll see how it goes

Emil
--sent from my mobile

···

On Apr 17, 2013 8:48 AM, "Werner Dittmann" <Werner.Dittmann@t-online.de> wrote:

Am 16.04.2013 15:11, schrieb Ingo Bauersachs:
>> I am moving this to the dev list.
>>
>> This is most likely related to our latest changes and the bouncy castle
>> un-fork effort.
>>
>> Werner, Ingo, would you guys be able to have a look or are you waiting
>> for the GitHub migration (which I am hoping will finally happen this
>> weekend).
>
> The trunk is okay as far as I can tell, I'm looking with Damian why the
> build doesn't contain the bouncycastle and bccontrib jars. The task to
copy
> them is definitely present in the build.xml.
>
> Ingo
>

The un-forking (split) was done last weekend and works so far on most
systems :slight_smile: .

It's a problem on Ubuntu which is based on Debian and we did this un-fork
(split)
because of the very specific Debian installation.

This un-forking may trigger some problems in the future. If Debian changes
the BC
library and this BC library contains modified API then Jtisi may have to
modify it's
modules as well. AFAIK such an API change already happened not long ago.

Werner

>

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 173 44 37 659
PGP key: 82EF5E8B


#9

Hi,

jitsi indeed runs again, thanks for the quick fix. However, it seems
that otr is not working properly with xmpp in the current nightly
build 2.1.4569.10776-1. (I used to have problems sporadically in the
past, so if nothing related to otr has been touched since 04-09 this
is probably some interoperability problem.)

Cheers, Benjamin

···

Hi,

this is fixed in latest build.

Thanks for the report damencho

On Tue, Apr 16, 2013 at 3:54 PM, Benjamin Eltzner
<b.eltzner@gmx.de> wrote: Hi,

I am having the exact same problem with the current nightly build
(2.1.4566.10773-1) on ubuntu 12.04 amd64.

Cheers, Benjamin


#10

Juha Heinanen writes:

> i installed latest nightly build on debian wheezy in order to check if
> dns query bug is fixed, but the result was that jitsi now prints lots of
> errors at startup and then nothing happens. perhaps the nightly build
> package is missing some package dependencies.

nightly build from april 17 worked and i was able to verify that
autodiscovery of sip proxy/registrar from dns worked.

Glad to hear this!

presence is still not cleaning all subscriptions at shutdown.

Right, we haven't changed anything there so that's to be expected.

We'll try to squeeze it in, during the following weeks. Everyone, this
should be a particularly easy hack, so if you've always wanted to get your
hands into Jitsi, the is a good way to start.

Cheers,
Emil

···

On Apr 17, 2013 3:48 PM, "Juha Heinanen" <jh@tutpro.com> wrote:

-- juha


#11

Hi,

starting build 4584 subscriptions for events(presence.winfo and
message-summary) should be cleared at shutdown. You can give it a try.

Regards
damencho

···

On Wed, Apr 17, 2013 at 4:47 PM, Juha Heinanen <jh@tutpro.com> wrote:

Juha Heinanen writes:

i installed latest nightly build on debian wheezy in order to check if
dns query bug is fixed, but the result was that jitsi now prints lots of
errors at startup and then nothing happens. perhaps the nightly build
package is missing some package dependencies.

nightly build from april 17 worked and i was able to verify that
autodiscovery of sip proxy/registrar from dns worked.

presence is still not cleaning all subscriptions at shutdown.

-- juha


#12

Hi all,

Thanks Werner for the change. And the deb is fixed now.
Yesterday while discussing with Ingo and trying to update the deb
source package we discovered that the lib in debian is not osgi
enabled. I already drop a note to the maintainer of the package as
they have added version 1.48 into experimental recently and 1.46 is
into unstable.
I'm not sure where we should file a request for this feature, if
anyone has a better view, please drop a note.

Thanks
damencho

···

On Wed, Apr 17, 2013 at 9:52 AM, Emil Ivov <emcho@jitsi.org> wrote:

Well, this applies to any debian dependancy and it's one of the reasons for
us dragging our feet for so long brfore getting into this.

Of course, we could always make our dependencies target a specific version
... we'll see how it goes

Emil
--sent from my mobile

On Apr 17, 2013 8:48 AM, "Werner Dittmann" <Werner.Dittmann@t-online.de> > wrote:

Am 16.04.2013 15:11, schrieb Ingo Bauersachs:
>> I am moving this to the dev list.
>>
>> This is most likely related to our latest changes and the bouncy castle
>> un-fork effort.
>>
>> Werner, Ingo, would you guys be able to have a look or are you waiting
>> for the GitHub migration (which I am hoping will finally happen this
>> weekend).
>
> The trunk is okay as far as I can tell, I'm looking with Damian why the
> build doesn't contain the bouncycastle and bccontrib jars. The task to
> copy
> them is definitely present in the build.xml.
>
> Ingo
>

The un-forking (split) was done last weekend and works so far on most
systems :slight_smile: .

It's a problem on Ubuntu which is based on Debian and we did this un-fork
(split)
because of the very specific Debian installation.

This un-forking may trigger some problems in the future. If Debian changes
the BC
library and this BC library contains modified API then Jtisi may have to
modify it's
modules as well. AFAIK such an API change already happened not long ago.

Werner

>

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 173 44 37 659
PGP key: 82EF5E8B

.


#13

Damian Minkov writes:

starting build 4584 subscriptions for events(presence.winfo and
message-summary) should be cleared at shutdown. You can give it a try.

hi, i gave 4585 a test and now all presence subscriptions and publish
were properly cleared at jitsi shutdown.

thank you very much,

-- juha
.


#14

i just noticed while doing more presence tests that sometimes when i
shutdown jitsi, it sends un-publish without e-tag, for example:

Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: 51973 (51973), Dst Port: sip (5060), Seq: 18816, Ack: 18253, Len: 727
Session Initiation Protocol
    Request-Line: PUBLISH sip:jh@test.fi SIP/2.0
    Message Header
        Call-ID: 2feeebde285670f4203f105d45863e39@0:0:0:0:0:0:0:0
        CSeq: 6 PUBLISH
        Max-Forwards: 70
        Content-Type: application/pidf+xml
        Contact: "Juha" <sip:jh@192.98.102.10:51973;transport=tcp;registering_acc=test_fi>
        User-Agent: Jitsi2.1.4585.10814Linux
        Expires: 0
        Event: presence
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-28a05ff9c981a2e4ea0c8dbe64e48db1
        Content-Length: 0

previous publish did have SIP-If-Match with e-tag and 200 ok to it had
SIP-ETag header with e-tag.

the un-publish at shutdown (above) does not contain SIP-If-Match with
e-tag which is a bug:

   When updating previously published event state, PUBLISH requests MUST
   contain a single SIP-If-Match header field identifying the specific
   event state that the request is refreshing, modifying or removing.
   This header field MUST contain a single entity-tag that was returned
   by the ESC in the SIP-ETag header field of the response to a previous
   publication.

-- juha

···

From: "Juha" <sip:jh@test.fi>;tag=55a233c6
        To: "Juha" <sip:jh@test.fi>


#15

Can you somehow detect during installation if the Debian BC lib is OSGI
enabled or not? If it's not OSGI enabled - use our own BS lib which
of course needs to be in the Jitsi package. This way we may resolve
some later issue if Debian updates the BC lib etc.

Werner

Hi all,

Thanks Werner for the change. And the deb is fixed now.
Yesterday while discussing with Ingo and trying to update the deb
source package we discovered that the lib in debian is not osgi
enabled. I already drop a note to the maintainer of the package as
they have added version 1.48 into experimental recently and 1.46 is
into unstable.
I'm not sure where we should file a request for this feature, if
anyone has a better view, please drop a note.

Thanks
damencho

Well, this applies to any debian dependancy and it's one of the reasons for
us dragging our feet for so long brfore getting into this.

Of course, we could always make our dependencies target a specific version
... we'll see how it goes

Emil
--sent from my mobile

<SNIP --- SNAP>

This un-forking may trigger some problems in the future. If Debian changes
the BC
library and this BC library contains modified API then Jtisi may have to
modify it's
modules as well. AFAIK such an API change already happened not long ago.

...

···

Am 17.04.2013 08:58, schrieb Damian Minkov:

On Wed, Apr 17, 2013 at 9:52 AM, Emil Ivov <emcho@jitsi.org> wrote:

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 173 44 37 659
PGP key: 82EF5E8B
.


#16

Hi,

no way, as we need to have only sources - no binary included. And we
should not embed sources which are already present in debian. For now
the only exception that was made is portaudio cause we have some big
patches in it. But we will remove and this one.
I'm not sure will they update the current 1.48 so I will make we
always use it as osgi adding the manifest from our sources. There is a
trick we use there: we create folder with the name of the current
bundle jar, put a manifest and classpath entry in it and just add a
link to the original /usr/share/java jar file :slight_smile: this way no matter
bundle or not we will use it as such.

Regards
damencho

···

On Wed, Apr 17, 2013 at 10:15 AM, Werner Dittmann <Werner.Dittmann@t-online.de> wrote:

Can you somehow detect during installation if the Debian BC lib is OSGI
enabled or not? If it's not OSGI enabled - use our own BS lib which
of course needs to be in the Jitsi package. This way we may resolve
some later issue if Debian updates the BC lib etc.

Werner

Am 17.04.2013 08:58, schrieb Damian Minkov:

Hi all,

Thanks Werner for the change. And the deb is fixed now.
Yesterday while discussing with Ingo and trying to update the deb
source package we discovered that the lib in debian is not osgi
enabled. I already drop a note to the maintainer of the package as
they have added version 1.48 into experimental recently and 1.46 is
into unstable.
I'm not sure where we should file a request for this feature, if
anyone has a better view, please drop a note.

Thanks
damencho

On Wed, Apr 17, 2013 at 9:52 AM, Emil Ivov <emcho@jitsi.org> wrote:

Well, this applies to any debian dependancy and it's one of the reasons for
us dragging our feet for so long brfore getting into this.

Of course, we could always make our dependencies target a specific version
... we'll see how it goes

Emil
--sent from my mobile

<SNIP --- SNAP>

This un-forking may trigger some problems in the future. If Debian changes
the BC
library and this BC library contains modified API then Jtisi may have to
modify it's
modules as well. AFAIK such an API change already happened not long ago.

...

--
----------------------------------------------
Werner Dittmann Werner.Dittmann@t-online.de
Tel +49 173 44 37 659
PGP key: 82EF5E8B


#17

Hi,

when doing the tests locally we can see the SIP-ETag in publish
messages on shutdown.
You say it happens from time to time? Did you noticed when it is
happening, can you give some steps to reproduce the issue?

Regards
damencho

···

On Wed, Apr 24, 2013 at 10:03 AM, Juha Heinanen <jh@tutpro.com> wrote:

i just noticed while doing more presence tests that sometimes when i
shutdown jitsi, it sends un-publish without e-tag, for example:

Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: 51973 (51973), Dst Port: sip (5060), Seq: 18816, Ack: 18253, Len: 727
Session Initiation Protocol
    Request-Line: PUBLISH sip:jh@test.fi SIP/2.0
    Message Header
        Call-ID: 2feeebde285670f4203f105d45863e39@0:0:0:0:0:0:0:0
        CSeq: 6 PUBLISH
        From: "Juha" <sip:jh@test.fi>;tag=55a233c6
        To: "Juha" <sip:jh@test.fi>
        Max-Forwards: 70
        Content-Type: application/pidf+xml
        Contact: "Juha" <sip:jh@192.98.102.10:51973;transport=tcp;registering_acc=test_fi>
        User-Agent: Jitsi2.1.4585.10814Linux
        Expires: 0
        Event: presence
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-28a05ff9c981a2e4ea0c8dbe64e48db1
        Content-Length: 0

previous publish did have SIP-If-Match with e-tag and 200 ok to it had
SIP-ETag header with e-tag.

the un-publish at shutdown (above) does not contain SIP-If-Match with
e-tag which is a bug:

   When updating previously published event state, PUBLISH requests MUST
   contain a single SIP-If-Match header field identifying the specific
   event state that the request is refreshing, modifying or removing.
   This header field MUST contain a single entity-tag that was returned
   by the ESC in the SIP-ETag header field of the response to a previous
   publication.

-- juha


#18

Damian Minkov writes:

when doing the tests locally we can see the SIP-ETag in publish
messages on shutdown.
You say it happens from time to time? Did you noticed when it is
happening, can you give some steps to reproduce the issue?

i have seen the missing e-tab problem twice, but i don't know how to
reproduce it. below are two consecutive publish messages with replies
when it happened last time.

jitsi was shut down about 3 minutes after the previous publish that had
expire time of 300 sec. so the publication was still in effect at
shutdown and jitsi should have included SIP-If-Match header in the
request.

-- juha

No. Time Source Destination
Protocol Length Info
    488 09:48:51.014358000 192.98.102.10 192.98.102.10 SIP 836 Request: PUBLISH sip:jh@test.fi

Frame 488: 836 bytes on wire (6688 bits), 836 bytes captured (6688 bits) on interface 0
Linux cooked capture
Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: 51973 (51973), Dst Port: sip (5060), Seq: 17548, Ack: 17294, Len: 768
Session Initiation Protocol
    Request-Line: PUBLISH sip:jh@test.fi SIP/2.0
    Message Header
        Call-ID: b611a4767b6b91f8ba8577df0bd76d17@0:0:0:0:0:0:0:0
        CSeq: 5 PUBLISH
        Max-Forwards: 70
        Content-Type: application/pidf+xml
        Contact: "Juha" <sip:jh@192.98.102.10:51973;transport=tcp;registering_acc=test_fi>
        User-Agent: Jitsi2.1.4585.10814Linux
        Expires: 300
        Event: presence
        SIP-If-Match: a.1366783811.10758.18.0
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-cb8c08e296a0db203769f12126816b25
        Content-Length: 0

No. Time Source Destination Protocol Length Info
    494 09:48:51.131706000 192.98.102.10 192.98.102.10 SIP 498 Status: 200 OK

Frame 494: 498 bytes on wire (3984 bits), 498 bytes captured (3984 bits) on interface 0
Linux cooked capture
Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: sip (5060), Dst Port: 51973 (51973), Seq: 17294, Ack: 18316, Len: 430
Session Initiation Protocol
    Status-Line: SIP/2.0 200 OK
    Message Header
        Call-ID: b611a4767b6b91f8ba8577df0bd76d17@0:0:0:0:0:0:0:0
        CSeq: 5 PUBLISH
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-cb8c08e296a0db203769f12126816b25
        Expires: 300
        SIP-ETag: a.1366783811.10757.7.1
        Server: OpenXg Presence/XCAP Server (4.0.0 (x86_64/linux))
        Content-Length: 0

No. Time Source Destination Protocol Length Info
    510 09:51:47.062123000 192.98.102.10 192.98.102.10 SIP 795 Request: PUBLISH sip:jh@test.fi

Frame 510: 795 bytes on wire (6360 bits), 795 bytes captured (6360 bits) on interface 0
Linux cooked capture
Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: 51973 (51973), Dst Port: sip (5060), Seq: 18816, Ack: 18253, Len: 727
Session Initiation Protocol
    Request-Line: PUBLISH sip:jh@test.fi SIP/2.0
    Message Header
        Call-ID: 2feeebde285670f4203f105d45863e39@0:0:0:0:0:0:0:0
        CSeq: 6 PUBLISH
        Max-Forwards: 70
        Content-Type: application/pidf+xml
        Contact: "Juha" <sip:jh@192.98.102.10:51973;transport=tcp;registering_acc=test_fi>
        User-Agent: Jitsi2.1.4585.10814Linux
        Expires: 0
        Event: presence
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-28a05ff9c981a2e4ea0c8dbe64e48db1
        Content-Length: 0

No. Time Source Destination Protocol Length Info
    515 09:51:47.068393000 192.98.102.10 192.98.102.10 SIP 463 Status: 400 Invalid request

Frame 515: 463 bytes on wire (3704 bits), 463 bytes captured (3704 bits) on interface 0
Linux cooked capture
Internet Protocol Version 4, Src: 192.98.102.10 (192.98.102.10), Dst: 192.98.102.10 (192.98.102.10)
Transmission Control Protocol, Src Port: sip (5060), Dst Port: 51973 (51973), Seq: 18253, Ack: 19543, Len: 395
Session Initiation Protocol
    Status-Line: SIP/2.0 400 Invalid request
    Message Header
        Call-ID: 2feeebde285670f4203f105d45863e39@0:0:0:0:0:0:0:0
        CSeq: 6 PUBLISH
        Via: SIP/2.0/TCP 192.98.102.10:51973;branch=z9hG4bK-363837-28a05ff9c981a2e4ea0c8dbe64e48db1
        Server: OpenXg Presence/XCAP Server (4.0.0 (x86_64/linux))
        Content-Length: 0

···

From: "Juha" <sip:jh@test.fi>;tag=57eef935
        To: "Juha" <sip:jh@test.fi>
        From: "Juha" <sip:jh@test.fi>;tag=57eef935
        To: "Juha" <sip:jh@test.fi>;tag=2c15998813993a5f2698a8693042e46f-dc09
        From: "Juha" <sip:jh@test.fi>;tag=55a233c6
        To: "Juha" <sip:jh@test.fi>
        From: "Juha" <sip:jh@test.fi>;tag=55a233c6
        To: "Juha" <sip:jh@test.fi>;tag=2c15998813993a5f2698a8693042e46f-9241


#19

there is at least one way to reproduce the publish with missing e-tag
issue:

- make jitsi user subscribe someone else for presence

- change user's presence properties, e.g., default subscription duration
  and click next/sign in.

- quit jitsi

quit will result in un-publish without e-tag.

-- juha