Adding SIP account fails

Bug #1270692 reported by Luke Faraone
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
jitsi (Ubuntu)
Incomplete
High
Rolf Leggewie

Bug Description

STR:

1. File → New Account
2. Network: SIP
3. Enter credentials

At this time, clicking "add" doesn't cause any change in the UI.

4. Click "Advanced"
5. Specify a SIP proxy manually
6. Click "next"
7. Click "sign in"

What should happen: The account is added to the list of accounts and is signed in.

What does happen: The account doesn't show up in the list of accounts, and does not appear to be signed in.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: jitsi 2.4.4997-1ubuntu1
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jan 19 23:01:08 2014
ExecutablePath: /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
InstallationDate: Installed on 2013-03-18 (308 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
PackageArchitecture: all
SourcePackage: jitsi
UpgradeStatus: Upgraded to trusty on 2013-11-23 (57 days ago)

Revision history for this message
Luke Faraone (lfaraone) wrote :
Revision history for this message
Luke Faraone (lfaraone) wrote :

This also fails when I try to sign in from the initial splash screen with no ~/.jitsi.

Changed in jitsi (Ubuntu):
importance: Undecided → High
Revision history for this message
Luke Faraone (lfaraone) wrote :

I am, however, able to sign in with XMPP, so its not entirely busted.

Revision history for this message
Ingo Bauersachs (ibauersachs) wrote :

This is because of bug 894302

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jitsi (Ubuntu):
status: New → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

bug 894302 is supposed to be fixed since yesterday. Can you guys please verify if you still experience this problem in trusty?

Changed in jitsi (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Lars Noodén (larsnooden) wrote :

Neither the wizard nor the add new account menu make any progress. The situation described above in #1 still exists.

It could be that an old version of jitsi is in the Trusty repository:

$ apt-cache policy jitsi
jitsi:
  Installed: 2.4.4997-1ubuntu1
  Candidate: 2.4.4997-1ubuntu1
  Version table:
 *** 2.4.4997-1ubuntu1 0
        500 http://fi.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Ingo Bauersachs (ibauersachs) wrote :

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.

Revision history for this message
Lars Noodén (larsnooden) wrote :

$ apt-cache policy liblog4j1.2-java
liblog4j1.2-java:
  Installed: 1.2.17-4ubuntu2
  Candidate: 1.2.17-4ubuntu2
  Version table:
 *** 1.2.17-4ubuntu2 0
        500 http://fi.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
        100 /var/lib/dpkg/status

This is not in a VM but is 32-bit not 64

$ uname -a
Linux lubuntu 3.13.0-16-generic #36-Ubuntu SMP Tue Mar 4 23:06:51 UTC 2014 i686 i686 i686 GNU/Linux

Changed in jitsi (Ubuntu):
status: Incomplete → New
Revision history for this message
Ingo Bauersachs (ibauersachs) wrote :

There's still a bug in the log4j manifest.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jitsi (Ubuntu):
status: New → Confirmed
Revision history for this message
Ingo Bauersachs (ibauersachs) wrote :

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.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Luke, does this work for you now?

Changed in jitsi (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: Confirmed → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Lars, how about you?

Revision history for this message
Lars Noodén (larsnooden) wrote :

I can add an account on AMD64 using 2.5.5175-1 and on i386 using 2.5.5168-1 I can make and receive calls on i386. I'm still looking into whether the AMD64 can actually receive calls, but that would be a separate issue.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Lars, thank you for reporting back. The packages you mentioned are not Ubuntu packages and are actually packaged VERY differently. So, that information is not helpful to determine the state of the Ubuntu packages.

Between, you and me, I'd always be very careful with upstream packaging their own software. Coders do not always understand packaging very well. And sometimes simple mistakes can have wide-ranging effects and even screwing up your whole OS. Again, the jitsi upstream packages are VERY different from what is in Ubuntu.

Revision history for this message
Lars Noodén (larsnooden) wrote :

Sorry. I've rolled back. 2.4.4997-1ubuntu1 on AMD64 allows adding an account and on i386 it won't get past the 'verify certificate' stage leaving an empty dialog box instead. I can try the i386 version on a freshly installed system later today if that helps.

Revision history for this message
Lars Noodén (larsnooden) wrote :

For right now trusty on i386 gives this when trying to install jitsi. I'll try later

$ sudo apt-get install jitsi
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 jitsi : Depends: default-jre but it is not going to be installed or
                  java6-runtime
E: Unable to correct problems, you have held broken packages.

Revision history for this message
Ingo Bauersachs (ibauersachs) wrote :

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 reproduce the certificate window issue, please send your logs over to <email address hidden>.

Revision history for this message
Lars Noodén (larsnooden) wrote :

Ok. I'll try again with tomorrow's i386 snapshot. The 4 April i386 snapshot won't load Jitsi from the repository.

The AMD64 Ubuntu repository package seems to work to make and receive calls.

Revision history for this message
Lars Noodén (larsnooden) wrote :
Revision history for this message
Rolf Leggewie (r0lf) wrote :

OK, I'll mark this particular problem as fixed by duping it to bug 894302.

If you experience any other issues with the Ubuntu packages please report them to Launchpad. For problems with the upstream packages, please contact <email address hidden> as Ingo suggested.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.