[sip-comm-dev] Installation damaged system...and other problems


#1

I won't attempt to navigate your bug reporting system, but I thought you would like to know of several problems I encountered when setting up SIP Communicator on a Ubuntu Karmic system. I'll be happy to answer specific questions and supply logs, but I don't have time for any extended debugging.

The computer is new enough and fast enough. It's an Intel Core 2 Duo, with 1 GB memory, and an almost new and empty system.

Installation problems
1. Ubuntu almost requires a public key for the package, although it can be overridden. This is your bug 787.

2. Installation of SIP Communicator from the package on your Web site damaged my system. It appears to have attempted to install Java over an already installed program. In doing so it opened an unresponsive dialog in Terminal that had to be terminated. Fortunately, the system supplied instructions to initiate self repair.

I can supply logs if you are very specific about which logs.

SIP Communicator problems
Default, ALSA devices. I have used it successfully for echo tests to 441@sip.diamondcard.us. However:

1. Doesn't start incoming sound until several seconds into the call.
2. Program is slow to start, slow to register, and slow to hang up. It may require a minute or two to startup and register. It takes maybe 10-20 seconds to hang up.
3. Program often takes 2 attempts to start. Java shows in the System Monitor, but the UI doesn't appear on the first attempt.
4. Setup UI is broken. Dropdown lists for sound devices do not show the whole string.

···

_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/201469227/direct/01/


#2

Hello,

I won't attempt to navigate your bug reporting system, but I thought you
would like to know of several problems I encountered when setting up SIP
Communicator on a Ubuntu Karmic system. I'll be happy to answer specific
questions and supply logs, but I don't have time for any extended debugging.

The computer is new enough and fast enough. It's an Intel Core 2 Duo, with
1 GB memory, and an almost new and empty system.

Installation problems
1. Ubuntu almost requires a public key for the package, although it can be
overridden.

I believe you are referring to a message from apt that's telling you
SIP Communicator's repository is not a trusted one. If yes, then this
is not a really bug, it's simply how apt works. The message is a
warning only, so you don't really need to override it. However, if you
want to then you simply need to:

#apt-get install sip-communicator-keyring

(You may want to have a look at our Debian repository instructions:
http://www.sip-communicator.org/index.php/Main/DebianRepository )

This is your bug 787.

Ah! Not quite. Issue #787 refers to providing a checksum for the
downloadable binaries in order to provide a way of verifying that an
SC binary is actually one.

2. Installation of SIP Communicator from the package on your Web site
damaged my system. It appears to have attempted to install Java over an
already installed program. In doing so it opened an unresponsive dialog in
Terminal that had to be terminated. Fortunately, the system supplied
instructions to initiate self repair.

I am sorry all this happened during your SC installation but it all
sounds more like a (probably temprorary) issue with the dependencies
on the Ubuntu repositories. SIP Communicator's Debian/Ubuntu package
does not "install" java per se, it simply states that it needs it and
then apt takes care of installing it. All issues with the Java
installation are hence quite outside the scope of our .deb package.

I can supply logs if you are very specific about which logs.

By all means, as it would probably help clarify the situation, but
again, I doubt there's something we could do on our level in order to
resolve this since it is probably an issue with the Ubuntu repo.

SIP Communicator problems
Default, ALSA devices. I have used it successfully for echo tests to
441@sip.diamondcard.us. However:

1. Doesn't start incoming sound until several seconds into the call.
2. Program is slow to start, slow to register, and slow to hang up. It may
require a minute or two to startup and register. It takes maybe 10-20
seconds to hang up.
3. Program often takes 2 attempts to start. Java shows in the System
Monitor, but the UI doesn't appear on the first attempt.

Hmm, the above are quite strange and most probably an issue that we
need to take care of ourselves. Could you please send us your log
files from ~/.sip-communicator/log ? We may need further traces after
that though so please bear with us until we try to determine what's
going wrong.

4. Setup UI is broken. Dropdown lists for sound devices do not show the
whole string.

Can you be a bit more descriptive? What are the names appearing and
how are they truncated?

Cheers,
Emil

···

On Mon, Feb 22, 2010 at 4:27 PM, Abig Lizard <vanillamozilla@hotmail.com> wrote: