This is because of bug 894302
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270692
Title:
Adding SIP account fails
To manage notifications about this bug go to:
I have no explanation yet why this happens, but switching away from the
dialog to any other window and then back makes it functional. Contrary
to comment #2, this also happens when built using ant make.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug 894302 was fixed on 24 Mar 2014 and with liblog4j1.2-java
(1.2.17-4ubuntu3) Jitsi now starts correctly, adding a SIP account is
also fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270692
The Jitsi version should not matter. Could you please verify that the
package liblog4j1.2-java is version 1.2.17-4ubuntu2? I haven't had the
time yet to install a new Trusty VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's still a bug in the log4j manifest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270692
Title:
Adding SIP account fails
To manage notifications about this bug go to:
The mandatory attribute Bundle-SymbolicName: log4j is still missing
from the manifest and the fix is therefore incomplete.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894302
Title:
jar files do
Lars, I've just reinstalled Ubuntu's Jitsi package on amd64 and I cannot
reproduce the problem with verifying the certificate nor with resolving
the java dependency (using both Gnome Flashback and Ubuntu Default
Desktop).
In any case, the above problems would be (a) completely bug(s). If you
can
Public bug reported:
Squid's latest stable upstream version is currently 3.5.6 and fixes
important bugs, such as the inability to fall back to IPv4 if a websites
IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid-
cache.org/squid-users/11/58389.html). Please update the package from
Public bug reported:
Squid's latest stable upstream version is currently 3.5.6 and fixes
important bugs, such as the inability to fall back to IPv4 if a websites
IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid-
cache.org/squid-users/11/58389.html). Please update the package from
This also affects .ova cloud-image deployments on ESXi/vSphere, not surprising
since it's similar to what John describes in comment 15. I think this is caused
by the kernel parameter console=ttyS0 and the underlying VM having no serial
port. This should not fail cloud-init and a similar bug was
Public bug reported:
The cross pkg-config packages don't exist anymore, but mk-sbuild still attempts
to install it for cross-compilations.
pkg-config-$target_tuple was removed in
https://salsa.debian.org/toolchain-team/gcc-defaults/-/commit/b1e452e249846782e25dc29f62762ebc23ca1633
and hirsute
*** This bug is a duplicate of bug 1966881 ***
https://bugs.launchpad.net/bugs/1966881
** This bug has been marked a duplicate of bug 1966881
Package pkg-config-riscv64-linux-gnu missing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is/was a duplicate of 1964670
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966881
Title:
Package pkg-config-riscv64-linux-gnu missing
To manage notifications about this bug go to:
13 matches
Mail list logo
